Receptor.AI

Summary
 

We're Receptor.AI, a TechBio company building an AI-driven drug discovery platform. We're looking for an outsource web developer for an ongoing engagement.
 

The first task is migrating our marketing site (receptor.ai) from Webflow to a modern code-based stack. But migration is just the starting point: after that, we need continued support - publishing new pages, maintaining and updating existing ones, placing new content (product pages, case studies, blog posts, campaign landing pages), fixing issues, and evolving the site over time.
 

If you're only interested in a single fixed-price build, this isn't the right fit - we're looking for someone we can keep working with long-term, paid hourly.
 

Requirements

• Experience working in an outsource/contractor capacity, comfortable with an ongoing relationship with variable scope (not only one-off fixed-scope projects).
• Proven experience (portfolio, case studies) migrating sites from Webflow to a code-based platform - not only greenfield builds from scratch.
• Solid knowledge of modern frontend frameworks (Next.js/React or equivalent) - the exact stack is open for discussion, not a fixed requirement on your side.
• Experience with headless CMS setups (Storyblok, Payload, Sanity, or similar), including configuring an editing interface usable by a non-technical content team.
• Understanding of SEO-safe migration practices: redirect mapping, noindex on staging, preserving metadata/canonicals.
• Experience migrating and verifying analytics and integrations: GA4, Google Tag Manager, Google Search Console, forms/CRM, cookie consent.
• Willingness to coordinate with a separate SEO/GEO specialist rather than handling SEO in isolation.
• Git/GitHub - required.
• Responsive to smaller, time-sensitive requests (a new page, a content edit, a bug fix), not only large projects.
• Bonus: experience working with AI coding agents (Claude Code, Cursor) on real projects.
• Bonus: strong written English for documentation and communication.
   

To apply, please send

• 2–3 relevant Next.js (or your proposed stack) websites, ideally including at least one Webflow-to-code migration.
• Your experience with headless CMS and ongoing content-maintenance work (not just initial builds).
• How you typically structure an ongoing engagement (hours per month, response times).
• Your hourly rate.

Start your proposal with "receptor" so we know you read the full posting.
 

Working model

• Remote.
• Hourly payment.
• Expected time commitment varies: heavier during the initial migration, lighter afterward for maintenance, new pages, and content placement.