Per project
Send a spec, get a price and a date against it, approve, and I build.
FitsOverflow now and then, or a single build you would rather not hire for.
White label for agencies
Your client sites, built to spec, with my name nowhere on them.
I build small business websites that agencies sell under their own brand. You get a fixed turnaround from a signed-off spec, a clean handover, and a builder your client never hears from unless you want them to.
Businesses that sell sites faster than they can build them.
This page is for companies that resell websites to their own clients. If you want a site for your own business, start on the home page.
- Marketing, SEO, and brand studios that sell sites with no developer on staff
- IT providers and MSPs fielding website requests from the businesses they support
- Printers, sign shops, and photographers whose customers are small businesses
- Independent business and brand consultants
- Web agencies that need overflow help in a busy stretch
Turnaround
Dates in business days, from a signed-off spec.
These are the dates I hold. The clock on each one starts from a complete brief and a spec you have signed off.
- Five-page site
- 3 business days
- Rebuild or migration
- 5 business days
- Standalone landing page
- 2 business days
- Every page past five
- +1 business day
If you need a landing page sooner, I can ship it the next business day for a rush fee settled before work starts. There is no rush option for a full build or a rebuild. The dates above are already as tight as I can promise, and a date I keep is worth more to you than a fee for one I miss.
I run a single white-label build at once. If a slot is taken, your brief gets the next open one, and you hear that date before you commit. A brief that arrives incomplete, or assets that arrive late, push every later date back by however long the delay lasts. These dates run shorter than my direct builds because your spec arrives finished, while a direct build includes gathering content from the owner.
What every build ships with.
- No trace of me
- No credit line, backlink, generator tag, or author metadata, in the pages or in the code. The work stays out of my portfolio unless you agree in writing, so you can present it as your own.
- WCAG 2.2 AA, tested
- Tested before handover, with the results reported to you. It is the standard I build to, not a certification, and keeping content added later accessible is your client's job.
- Core Web Vitals, measured
- Measured for mobile, with the numbers sent to you before handover, so you have something real to show your client.
- Technical on-page SEO
- Page titles, meta descriptions, heading structure, schema markup, an XML sitemap, and a robots.txt file.
- Policy starting points
- A privacy policy and terms of use, drafted as a starting point. They are not legal advice, and your client has them reviewed by a qualified professional before launch.
- A clean handover
- The repository, the deployment, and every account sit in your name or your client's. None of them stays in mine.
Terms
Three terms, stated up front.
I never contact your client on my own.
That holds during the build and after it. I speak to your client only when you ask me to in writing, and then as part of your team. Non-circumvention is written into the agreement and runs for 12 months past your last project with me.
The signed-off spec is the scope.
A promise you made your client that isn't in the spec isn't part of the build. Tell me about those promises before sign-off and I'll price them in, so they never turn into a dispute halfway through.
You pay me even if your client pays you late.
Your client's payment terms are between you and them, and my invoice runs on its own schedule either way. Of everything on this page, this term is the one that isn't open to negotiation.
Three ways to buy the capacity.
Reserved monthly capacity
You agree to a set volume each month and I keep that capacity open for you. Capacity you don't use in a month doesn't carry into the next.
FitsRegular volume, where you need a lead time you can promise your clients.
Build partner
Reserved capacity, plus a standing seat in your delivery process. Where you want it, I join client calls as part of your team.
FitsAgencies that want a production team without adding one to payroll.
Commercial terms
How payment and paperwork work.
This page lists no rates. The partner rate card is written for your agency and sent as a PDF after the partner call.
- Payment
- Half when you approve the spec, half on delivery.
- Revisions
- Two consolidated rounds come with every build. After that, changes are billed by the hour, at the hourly rate on your rate card.
- Ownership
- The intellectual property transfers to you once the build is paid in full, and you can pass it on to your client.
- Third-party costs
- Hosting, domains, licenses, and stock images are billed by each provider in your name or your client's. I add no markup.
- Confidentiality
- It runs in both directions. The fact that I build for you, and the terms of the deal, stay private on both sides.
- Paperwork
- You sign two documents once: a master services agreement and a white-label rider. Every project after that needs only a short statement of work.
On Eastern time, with set call windows.
I work on Eastern time, the same clock as New York and Atlanta. Calls run on weekdays from 5pm to 8pm ET, which is 2pm to 5pm for an agency on Pacific time, and on weekends from 9am to 8pm ET. If your process needs me on a call at 10am on a Tuesday, that part won't work, and you should know it now rather than on the first project.
- Weekdays
- 5pm to 8pm ET
- Weekends
- 9am to 8pm ET
From first call to first build.
Book a partner call
Twenty minutes. Tell me what you sell, how often, and to whom. The rate card follows as a PDF, written for your agency.
Send the brief
List the pages, what each one has to do, who is responsible for each integration, the source of the copy and images, and how your client will judge the result.
Get a price and a date
Both in writing, against that brief. If something is missing, I name it instead of guessing and billing for the guess later.
Sign once
Both documents arrive with your first project. After that, each build needs only its statement of work.
Questions before the call.
Will my client ever find out who built the site?
Not from me, and not from the code. There is no credit, backlink, generator tag, or author metadata, and I don't contact your client unless you ask me to. What you tell them is your decision.
Why is there no price on this page?
The rate card is written for each agency and goes out as a PDF after the partner call. It stays private between you and me, which keeps it away from the clients you are pricing for.
Can you start before the brief is finished?
I can tell you what's missing, but the turnaround dates only start from a complete brief and a signed-off spec. Until then, you get a list of the gaps, not a guess.
What if my client changes their mind halfway through?
Changes inside the signed-off spec go into your two revision rounds. A change outside it is new scope, so I price it and date it, and you approve that before I start on it.
What do you build the sites on?
Astro, hosted on Cloudflare, by default, which suits a site that is mostly pages. Anything app-like, such as logins, booking flows, or live data, I build in Nuxt. If your team already works on one platform, I build on that instead, and the spec names it so there is no surprise at handover.
Can you work with an agency in the United States?
Yes. Everything from the first call to the handover happens remotely, on Eastern time, in the call windows above.
Talk through your next build.
Book a partner call and bring the project you are trying to staff. You'll leave knowing whether my calendar and my terms fit it, and the rate card follows as a PDF.