Developers who don't know the stack
Astro and Sanity aren't mainstream. Finding a developer who actually knows them, not just claims to, is harder than it should be.
You've got the designs. I'll build the site.
Pure Astro and Sanity build from production-ready designs. No strategy, no design rounds, no SEO work. You hand over the files - I deliver a fast, accessible, standards-compliant website your client can manage themselves.
Built for agencies and designers who know their stack and need a developer who knows theirs. No hand-holding required on either side.
Your agency designs sites that deserve better than what most developers deliver
You've spent real time getting the design right - the hierarchy, the components, the content structure. Then you hand it to a developer and what comes back is slow, inaccessible, and built on a stack you didn't spec.
Or you build it yourself in a platform that gets the job done but doesn't produce the performance numbers your client deserves. Either way, the gap between the design and the final build is where quality slips.
You need a developer who can take production-ready files and deliver something that actually matches them - fast, typed, and built to last.
Performance that doesn't match the pitch
You told your client the site would be fast. The build comes in at 72 on Lighthouse. That gap is yours to explain.
Handoffs that create new problems
Messy codebases, CMS schemas built without thinking about the editor, no documentation. Your client is calling you six months later about something that should have been sorted at launch.
What I build with - and why it matters to your clients
Most developer handoffs produce something that scores 70–80 on Lighthouse. These builds routinely hit 100. That's not a claim - it's something you can put in front of your client after delivery and show them the numbers.
If you're pitching Astro to a client who cares about performance or sustainability, you need a developer who understands why the architecture produces those results - not just someone who followed a tutorial.
Astro - static-first
Pages are pre-rendered at build time. Zero JS sent to the browser unless a component explicitly needs it. Faster load times, lower carbon, better Core Web Vitals.
Sanity CMS
Structured content with a schema built for the site, not retrofitted. GROQ queries are clean and fast.
TypeScript throughout
Every component, query, and utility is typed. The codebase you receive is maintainable by any TypeScript developer - not just me.
Tailwind CSS 4
Utility-first styling on the latest version. No legacy config overhead. Consistent, responsive, and fast to iterate on if the design needs tweaking post-handoff.
Cloudflare + Vercel
Vercel for staging - shareable review links for your client. Cloudflare for production - global edge, fast TTFB, built-in DDoS protection.
Svelte / React for interactive UI
If a component needs interactivity, I reach for Svelte first - smallest bundle, fastest hydration. React/Preact for more complex interactive interfaces. Never both on the same page.
Is this the right fit for you?
This service is built for agencies, studios, and freelance designers who have already done the strategy and design work, and need a developer who can take those files and deliver a production-grade Astro and Sanity build without needing to be managed.
If you're a direct client without a design team behind you, the full content-driven site service will be a better fit. It includes everything from discovery through to launch.
This is for you if...
- You're a design agency or studio that doesn't build in Astro
- You have a freelance designer client who needs a developer they can brief directly
- You want Astro and Sanity specifically, not WordPress, not a template
- You have production-ready designs and can supply copy before work starts
- You want a fixed price and a predictable timeline
Not the right fit if...
- You don't have finished designs - the brief will stall before it starts
- You need strategy, SEO, or content as part of the project
- You need a headless Shopify build - that's the Build Only - Commerce service
- You're looking for a developer to manage the design process too
What you get. What you don't.
This is a build service, not a full-service engagement. It's priced accordingly - because you've already done the hard work. Here's exactly what's in scope.
Included:
Astro build, static-first
Pages pre-rendered at build time. No server on every request. Lighthouse-ready out of the box. TypeScript throughout.
Sanity CMS setup
Schema built to match your content structure. Studio configured for your client. GROQ queries wired to the front end. Live Preview if needed.
Blog and content routes
Dynamic blog routes, paginated collection pages, RSS feed, and any category or tag filtering in scope. Built to your design.
WCAG 2.2 AA accessibility
Semantic HTML, correct heading order, keyboard navigation, focus states, alt text, ARIA where needed. Not bolted on at the end.
Staging and production deploy
Vercel for staging review. Cloudflare for production. CI/CD configured from the repo. One round of amends post-review.
Git handoff and Loom walkthrough
Full codebase delivered via Git. A short recorded walkthrough so your client knows how to use the CMS without needing to call you.
Not included:
Strategy and discovery
No audience research, competitor analysis, or positioning work. That's your territory. I pick up from production-ready designs.
Design
No wireframing, visual design, or brand work. Figma files or equivalent design specs must be supplied before work begins.
SEO and content
No keyword research, meta writing, or on-page SEO strategy. I'll implement meta tags and schema if you supply the content - but I won't create it.
Copywriting
All copy must be supplied. I can wire placeholder text to the CMS, but writing is not in scope for this service.
Ongoing maintenance
This is a one-off build. Post-launch support isn't included - though it can be arranged separately if needed.
Clean handoff. Clean delivery.
The process is deliberately simple. You've done the strategy and design. My job is to build it properly - pixel-accurate, performant, and ready for your client to take over without needing a developer on retainer.
-
You share the brief
Send over your design files (Figma preferred), any copy docs, and a note on the CMS structure you have in mind. A short call to align is included if needed.
-
Fixed quote, fixed scope
Based on the brief, I'll give you a fixed price and timeline. No hourly billing, no scope creep surprises. If your scope changes, we agree a new price before I touch anything extra.
-
I build it
Astro + Sanity, TypeScript throughout, Tailwind CSS 4 for styling. Staged on Vercel so you and your client can review at any point. One round of amends included.
-
You take delivery
Full codebase handoff via Git. Deployed to Cloudflare on production. Sanity CMS configured and ready. A short Loom walkthrough included so your client isn't left guessing.
Starting from £3,000
Every project is quoted as a fixed price based on the brief. £3000 is a starting point for a standard content site build - more complex scopes are priced accordingly. You'll have an exact number before any work starts.
Fixed price agreed before work starts. 50% deposit, 50% on delivery.
Free, no obligation. Just a conversation.
Every build-only content site includes:
- Astro + Sanity build from supplied design
- TypeScript, Tailwind CSS 4
- Blog and dynamic content routes
- WCAG 2.2 AA accessibility minimum
- Staging on Vercel, production on Cloudflare
- One round of amends post-review
- Git handoff + Loom walkthrough
- Strategy, discovery or SEO work
- Design or wireframing
- Copywriting
- Ongoing maintenance
Common questions
Do you work with any design tool, or does it have to be Figma?
Figma is preferred - it gives me the component specs, spacing, and variable data I need cleanly. I can work from other tools but Figma is the smoothest handoff. If you're unsure, get in touch before briefing.
What does "production-ready designs" mean exactly?
Desktop and mobile views for every page in scope, named components, specified typography and spacing, and all assets (images, icons, logos) exported and ready. If the designs are still in progress when the project starts, the timeline will slip - so we wait until they're done.
Can I white-label this service for my agency?
Yes. I work as a subcontractor under your brand. No direct contact with your client unless you want me to - it's up to you how you structure the relationship. NDAs are fine.
How long does a build take?
A typical content site build takes 4–6 weeks from brief to delivery, assuming designs and copy are ready from day one. Timeline is agreed upfront and held to. If your brief is larger or more complex, we'll agree an extended schedule before work starts.
What if we need changes after delivery?
One round of amends is included post-delivery. Anything beyond that is quoted and billed separately. If your client is likely to need ongoing changes, the Editor or Creator maintenance plans might be worth considering - though those are for Joontide-built sites, not external agency projects.
Do you have a portfolio of Astro builds I can show a client?
I've been building websites for 15+ years with past clients including Netflix, Sky, and Canon. Astro-specific case studies are in progress - if you need something to share with a client while those are being documented, get in touch and I can walk you through the stack directly.
Got a brief? Let's talk.
30 minutes. No pitch, no fluff. Bring your brief, your designs, and any questions about the stack. If it's a good fit, you'll know by the end of the call.
Free, no obligation. Just a conversation.