Your web product, shipped in 90 days. Or 100% refund.
One operator, fixed scope, signed deadline. Built for productised offers, community platforms, and bootstrapped tools — not brochure sites.
Your web product, shipped in 90 days. Or 100% refund.
One operator, fixed scope, signed deadline. Built for productised offers, community platforms, and bootstrapped tools — not brochure sites.
Your web product, shipped in 90 days. Or 100% refund.
One operator, fixed scope, signed deadline. Built for productised offers, community platforms, and bootstrapped tools — not brochure sites.
What this is.
A 90-day build for a real web product. SaaS, community platforms, ecommerce, niche tools — anything where the value lives in the software, not the marketing pages. We agree the scope on a call, sign the price and the deadline, and I build it. Day 90 you get the product live. Or every fee back.
Is this format for your project?
One operator, fixed scope, money-back. It works on a specific kind of project at a specific moment.
Built for this
- 01
You've tested the idea on a landing page or a rough tool, and you know what the real product needs to do.
- 02
You've been chipping away at the build on weekends for months and you want it done properly, once.
- 03
You're starting from zero on a technically ambitious project and you'd rather not spend a year learning to ship it.
- 04
You want a real product with real architecture, built to grow with your business.
- 05
You've made the call — you're ready to commit to the scope and the date.
Not built for this
- 01
You want a brochure or marketing site. Different price, different operator.
- 02
You want to redesign something that already ships and works. (Going from a working MVP to the full product is a build, not a redesign — that's a fit.)
- 03
The product isn't defined yet. Scope is signed on Day 0; discovery happens on the scoping call before that.
If you can describe your build in one product sentence,
you’re probably a fit.
From call to shipped, in four steps.
One operator, not an agency. No retainer — the engagement ends cleanly at Day 90.
Scoping call
30 minutes, free. We see if your project fits the format. If it doesn't, I tell you on the call.
Scope document
Drafted within a week. Defines every feature in writing. Both signatures, fixed price, 90-day clock starts.
The build
Direct working sessions, weekly demos, no account managers. You see progress in production from the first week.
Ship or refund
Day 90. Four conditions met = shipped. Otherwise, full refund.
DramShed is the UK whisky-community platform two founders had been stuck launching for over a year. I rebuilt it from scratch, got it live, and we’re still working together today.
How the 90 days actually work.
Four beats that cover the full 90 days — in the exact wording you’d see on the contract. No fine print waiting elsewhere.
One scope. One operator. Full refund on the line.
What you walk away with.
- checkProduction deployment on your infrastructure
- checkSource code, perpetual licence
- checkOne-page ops handover doc
- checkAnalytics and monitoring, wired in from day one
Two slots, because four would make the guarantee a lie.
I’m Robert. Five years building web products, full-stack, mostly for founders who needed the real thing and not a prototype.
I built an automation for my uncle’s construction business once that saved him ten hours a week of admin he’d been doing by hand for years. The day it went live he asked what else was possible. That question is most of why I do this. The products I find most interesting are the ones where, once they’re running, the way people use them tells you how to improve them.
Quarter Build runs at 90 days because I’ve watched founders burn a year or more on builds that should have shipped in a quarter. Short enough to force the decisions that matter, long enough to ship something robust.
I work alone, two at a time, because the refund clause only holds if I can pull every hour back to one project the moment it starts slipping. Four in flight, and the guarantee is theatre.
Quarter Build exists because most software contracts are written so the people writing them never get hurt. This one is the opposite: one scope, one deadline, money on the line. If I miss Day 90, that’s my problem — not yours.
— Robert Chiru
The five questions before signing.
The scoping call exists to catch this before anyone signs. If your project doesn't fit 90 days, I'll say so on the call. If we both think it fits, the scope document defines exactly what's in — anything else becomes a change order, priced and timed separately.
Change orders. We agree the addition in writing, price it, time it, and the 90-day clock pauses until we both sign. Then it restarts. The guarantee applies to whatever is on the signed scope at any given moment.
Fees paid to me. It doesn't cover third-party costs — hosting, domains, Stripe fees, paid APIs, design assets. You keep all the code I've written to date, perpetual license, refund or not.
Because the guarantee is only credible at low concurrency. If I have four projects in flight and one starts slipping, I can't pull hours back without slipping the others. Two is the most I'll commit to.
You get one operator, not a team. You see code in production from week 1, not in a final reveal at the end. The person writing the scope is the person writing the code is the person on the hook for the refund. Agencies don't structure their work that way.
Ready to start a Quarter Build?
A 30-minute scoping call. If your project doesn’t fit, I’ll tell you on the call.