Senior Next.js Developer for Dark Premium B2B Marketing Sites

I run a B2B conversion agency. We build marketing sites for funded companies. Custom Next.js, Sanity CMS, deployed on Vercel. Our designers ship React components straight from a token system. You turn them into fast, accessible production code. You already work this way. You use Claude Code or Cursor every day and ship meaningfully faster because of it. Your repos are organized so adding a new page next month is a half-day, not a rebuild. You write Tailwind v4 with tokens. You think in App Router. You run Lighthouse before you push. The aesthetic: dark, premium, fast. Think Linear-tier and Vercel-tier marketing sites. Heavy bold sans typography. Asymmetric layouts. Considered motion with Framer Motion springs. No templates. What a project looks like: 5-7 page marketing site, homepage plus ICP subpages. You get the design system, React components from the designer, and copy from me. You ship a clean Vercel repo with Sanity wired for blog and case studies, PostHog events per a naming spec I share once we connect. What you own week to week: Convert designer's React components into production Next.js (RSC + client islands) Wire Sanity CMS (schemas, GROQ queries, image optimization) Implement PostHog events using page_section_action naming convention Mobile-first at 375 / 768 / 1280 / 1920 Structure the repo so Claude Code can extend it later without breaking things Branch coordination with the designer Every PR ships with these five proofs: Vercel preview deploy URL in the PR description Lighthouse 90+ screenshot, mobile config Screenshot at 375px width 90-second Loom walking through the change on the preview URL Tracking events verified in PostHog Live Events with incognito click-through If you already work this way, these are 30 seconds per PR. This is for you if: You have shipped Next.js sites scoring 90+ on mobile Lighthouse and have screenshots to prove it. You read PRs before you write code. A clean commit history is part of the deliverable, not optional polish. You have a specific AI workflow that saves real hours and can describe it in one sentence. You give bad news inside 24 hours, not when it becomes a fire. You see this as the first 12 months of a much bigger role, not a one-off build. You would rather ship the preview URL than schedule a call. What you get: You shape the dev side, not just deliver tickets. Architecture decisions are yours. Standing dev role on a multi-client roster within 90 days. Hours scale from 10-15 to 20-30 as we sign client 2 and 3. Same-week invoice pay through Upwork. No chasing. Your name on case studies. Your portfolio compounds. A designer who hands you tight React components, not Figma boards. A tested AI skill stack already deployed. A documented production system you operate inside. Pipeline doc shared on Day 1. Direct line to me. No PM layer. To apply, include in your Upwork proposal: A live Next.js URL you built (URL only) A public GitHub or GitLab profile with the repo visible Lighthouse 90+ mobile screenshot from one of your sites (attach to proposal) One sentence on your AI tool of choice and one specific prompt-to-output workflow that saved you 5+ hours last month First milestone before the retainer begins: a small scoped task at your normal hourly rate, paid through an Upwork milestone. Usually a hero section or component built against our token system. This is real work, not a separate trial. Quick way for both of us to confirm fit before committing to ongoing hours. If it hits the bar, the retainer starts the same week. I respond to every proposal within 48 hours. If you are not moving forward, you will hear from me.