For sites with logins, live product data or components shared with your React app. Sanity for editors, Vercel or Cloudflare for hosting. The same person designs the site, builds it and ships the changes after.
Next.js earns its weight when pages differ per visitor, read from your product's API, or share components with a React app. If every visitor sees the same pages, I will tell you Astro is the better build. More framework than the site needs is a cost you pay on every change. Read the comparison.
A sample site with invented data. Pick a request: a fix, a new section, or a new page. On a real site each one arrives as a preview, and nothing goes live until someone approves it.
Five stages, in this order. Each one ends with something you can open and check.
Which pages are static, which render per request, which sit behind a login, and where the data for each one comes from. This stage settles the build: Next.js, or Astro if nothing on the site needs Next.js.
4 in hand so far
Marketing content modeled in Sanity; product data read from your API, not copied into a CMS where it will go stale.
7 in hand so far
Tokens and React components, written so they can be shared with your app later if you want them to be.
10 in hand so far
Account areas, forms, payments and the calls to your backend, each tested against real responses including the failed ones.
14 in hand so far
Redirects, sitemap, a performance pass on the routes that render per request, then the domain moves early in the week while I am watching.
18 things handed over, all yours
The same build on a calendar: what you do, what I do, and when.
You
Plan
Build
Launch
Marketing pages are still generated ahead of time. Only the routes that genuinely differ per visitor render on request, so the parts that can be fast are.
Editors publish in Sanity Studio and the affected pages refresh, without rebuilding the whole site or opening a ticket.
Pricing, plans and status come from the system that owns them. When the product changes, the website does not need a second edit.
Login uses the provider your product already uses, so a customer has one account and one session across both.
Plain TypeScript in your GitHub, deployed from your hosting account. Your engineers can read it without asking me what anything means.
After launch, requests arrive through the Console or the channel agreed at kickoff and come back as previews. Nothing ships until you approve it.
Changes
Where your team asks for something
Site
What visitors load
Content
Where editors write and publish
Hosting
Where it runs, in your accounts
Astro if every visitor sees the same pages. Next.js if the site has logins, reads live product data or shares React components with your app. I build both on one price list, and the first call usually settles which.
Yes. Marketing pages live in Sanity, and publishing refreshes the pages that changed. The account and product routes stay in code, where a content edit cannot break them.
The parts the website needs: API routes, form handling, auth, payments and the calls to your product. Billing logic, data pipelines and anything your product depends on stay with your engineers, and I build against their API.
Yes, if the codebase is worth keeping. I will read it first and say what I would change, and whether the marketing site would be better as Astro.
A move from another platform is fixed price from $5,000, quoted after the inventory. A new build is scoped the same way. Ongoing work afterwards is $3,500 a month with no minimum term. The cost page breaks the bands down.
I do, all of it. There is no handoff to a junior and no second team. The trade is capacity: there is no second team to absorb a rush, so scope and cost are agreed in writing before work starts. More on that.
In your Vercel or Cloudflare account. The repository is in your GitHub.
I can scope a migration. Send a brief and I will reply by email with next steps.