Strapi, Contentful, headless WordPress, or Sanity wired to Next.js, Astro, or SvelteKit on Vercel, Cloudflare, or Netlify. Used when content needs to render in multiple places, marketing ops needs velocity, or edge performance matters at sub-1s.
What you get
- Content modeling workshop — the most important hour of the engagement.
- Headless backend set up with role-based access for your team.
- Front-end build on the framework that fits your team (Next/Astro/SvelteKit).
- Multi-environment deploy pipeline (preview → staging → production).
- Editor onboarding session so marketing isn’t blocked on engineering.
What it doesn’t include
- Backend development beyond CMS configuration (custom microservices = separate engagement).
- App development (this is for web).
- “Make it headless because everyone’s doing it” — I’ll push back if traditional CMS would serve you better.
Timeline
6–12 weeks. Content modeling takes the first 2 weeks; the rest is build, integration, and onboarding. Headless rebuilds of existing sites are typically faster than full re-platforms because content already exists.
Pricing posture
Flat-fee, milestone-based. 30% kickoff, 30% staging-ready, 40% launch. Hosting + tooling costs are pass-through.
