For agencies

White-label build · Astro · Sanity · Cloudflare Pages

You keep the client and the credit. I do the build, and your client never sees my name on it.

Written for studios who need engineering capacity for a month or two without hiring. The numbers on this page are measured, not rounded up — this site scores 96 on mobile Lighthouse 13.5.0 with a 1.9s largest paint and no layout shift, and it is the same build you would be getting.

What this is

Most studios do not have a shortage of design work. They have a shortage of hours — a project lands, the Figma is signed off, and nobody in the building writes Astro.

That gap is usually filled three ways: a developer who charges day rate and takes three weeks, a WordPress freelancer who is cheaper and slower, or nobody at all and the launch slips. I am the first option with a fixed price attached, and I am invisible in the finished product by default.

Pricing

Who does what

The boundary is deliberately boring, because the interesting version of this arrangement usually goes wrong on logistics rather than on code.

You keep

The client, the contract and the invoice
The relationship and the credit for the work
Visual strategy, design, copy direction and tone
The markup, and the decision about what to charge for it

I do

Translate Figma files into hand-written Astro components
Build the Sanity schema your client will actually be given
Performance, accessibility and the technical SEO that isn't guesswork
Deploy to Cloudflare, and hand over the repository

Nothing here is under NDA until one is signed. I do not put client work in my portfolio, and I will sign yours before I start rather than after you ask.

What transfers at handover

Three things, and none of them are mine.

GitHub: The repository is yours, in your own account, with the deploy pipeline already wired to it.

Sanity: Your client's CMS project, in their own account. Nobody loses access to their own content when a contract ends.

Hosting: Their domain, their Cloudflare account, their card. The free tier is theirs to keep, upgrade or walk away from.

↳ the part your client actually sees

A client panel is only good if nobody can break it, and most breakages are a long string typed into a field built for six words. I constrain the schema — single-line where it should be single-line, character limits where a sentence is the maximum, image fields that say what shape and size they want. Not impossible to get wrong; just hard.

How the editing setup works

The five things to agree in writing

An NDA is the easy document and usually the least useful one. These are the terms that decide whether the arrangement is pleasant or expensive.

When the code becomes yours

On final payment, not on handover. If I hand over a repository I haven't been paid for, I have no leverage and you have no reason to pay me. Both of us are better off if that is written down before either of us spends a month on it.

What counts as a revision

Two rounds per page, agreed before I start. A third round is a change request and priced like one — not a punishment, just the point where a build is genuinely a different build.

Who talks to the client

You do. I will join one call at kickoff to understand the design intent, and I am not on the account after that. If I am also in their inbox, you have not bought a white-label build, you have introduced me to your client.

What happens when scope moves

Either end the project with the work done to date invoiced, or price the change and carry on. Both are fine outcomes. Leaving it unsaid until the disagreement is the only version that is not.

Response times

A working day for questions, two for anything that needs a build. I work in IST, which is a five-hour offset from Australian Eastern time — workable rather than instant, and worth knowing before you promise a client same-day.

What I need from you

Four things, and the first one is the one that decides the date.

Final Figma

Signed off, with the mobile frames included. If they are missing, I am designing your layout while also writing it, and the fixed price stops meaning anything.

Copy

Or a firm date for it. Content is almost always the thing that moves a launch date.

Assets

Photography, logos, any brand files. I self-host rather than hotlinking, so larger files are fine.

A GitHub account

Yours or your client's. The repo goes there on day one, not at the end.

The honest part

Working this way means I own none of the client relationship. If that relationship goes wrong, you absorb it and I never hear about it — and if you find someone else, I find out from a LinkedIn post.

That is the trade, and it is worth naming rather than hiding: you get a predictable price and a build that is not mine to be attached to; I get steady work without a sales pipeline and no credit for the result. If you want a partner who will argue with you on the design and put their name on it, I am not that, and the direct route is better for you.

I have not built for a studio yet. Every number here is a price I am willing to work at, not one I have negotiated, and the first agency build will be priced the same as the tenth.

↳ see the actual work

Six sites, each measured rather than described, with the scores in the open. If you are deciding whether to hand a Figma file to a stranger, those are the six answers.

The work and its measurements

What to ask me first

Will my client know you built it?

Not unless you say so. There is no badge, no credit, no link back to me in the finished site, and nothing in the code that says who wrote it. You are welcome to say it was built in-house.

What happens to the $40 a month care plan?

It is mine, not yours to resell, but I will service your client's small changes under it at cost while the account is live. Longer term that is cheaper for both of you than a maintenance call at day rates.

Can you work in our stack instead?

Sometimes. Astro and Sanity are what I reach for, and switching to another framework is not free in either direction. Worth a conversation before you commit, not after.

What do you need signed first?

A short agreement covering the five terms above. An NDA too if you want one. Both are quick; I am not precious about the paperwork as long as it says who owns the code and when.

↳ next

If there is a live project with a Figma file and a date on it, send it over. You will get a straight answer about whether I am the right fit, including when I am not.

Send a project over