No black boxes.
No runaround.
Three phases, fixed price agreed in writing up front, and most of it async - because status meetings are where projects go to die. Here's exactly how it runs.
Scope
You fill in a structured intake questionnaire covering your business, what you need built, and your budget range. I read it properly, look at whatever exists today, and come back with a fixed price and timeline in writing.
What happens in this phase:
-
▶
Async intake — A structured form, not an interrogation call. You answer in writing when it suits you, which produces better answers than a meeting does anyway.
-
▶
One short call if needed — 30 minutes max, agenda sent beforehand, only if the written brief leaves real gaps.
-
▶
Fixed written quote — Exact scope, exact price, exact timeline. If anything falls outside scope later, it gets quoted separately before any work starts.
What you'll get:
Scope document
What's being built, what isn't, and what happens if plans change.
Fixed price & timeline
In writing before you commit a dollar. The number doesn't move unless the scope does.
Payment schedule
Typically 50% to start, 50% on delivery. Card or bank transfer.
Duration: 2–4 business days from completed intake to signed quote.
Build
Focused build blocks of about two weeks. You watch progress through staging links you can click, not status reports you have to decode. One optional short call a week; everything else in writing.
What happens in this phase:
-
▶
Staging from day one — A live URL you can check whenever you like. Progress is visible, not promised.
-
▶
Weekly written update — What shipped, what's next, anything I need from you. Two minutes to read.
-
▶
Real engineering underneath — Version control, proper databases where needed, security basics done by default rather than as a line item.
What you'll get:
Working software on staging
Clickable, testable, early. Feedback lands while it's still cheap to act on.
Written progress trail
Every decision documented. Nothing lives only in someone's head.
QA pass
Browsers, mobile, accessibility basics, load behaviour - checked before launch, not after complaints.
Duration: typically 2–4 weeks depending on scope. Fixed at quote time.
Run
Launch is the start of the useful life, not the end of the project. You get a proper handover - documentation, credentials, source code ownership - plus the option of a care retainer so maintenance never becomes your problem.
What happens in this phase:
-
▶
Launch — DNS, deployment, analytics verified, forms tested end to end.
-
▶
Handover pack — Documentation written for a human: how things work, how to change content, who holds what credentials.
-
▶
Care retainer (optional) — Monitoring, updates, and small changes handled on an ongoing basis. Cancel with 30 days' notice.
What you'll get:
Live, working product
Deployed, monitored, and doing its job.
Full ownership
Source code, repositories, accounts - yours, with no lock-in and no hostage keys.
30-day post-launch support
Fixes related to the build, free. Then the retainer takes over if you want it.
Support window: 30 days, 48-hour response commitment. Retainer optional.
Service Standards
Published commitments, not aspirations. These are the terms every project runs under - you can hold us to each one.
| Standard | Commitment |
|---|---|
| Fixed quote turnaround | Written fixed-price quote within 2 business days of completed intake |
| Response time | Every client email answered within 1 business day |
| Progress visibility | Staging link live from week one, always current |
| Updates | Written progress update every week during builds |
| Defect warranty | 30 days post-launch, build defects fixed free |
| Ownership | Full code, credentials and documentation handover on final payment - no lock-in |
| Client cap | Maximum 3 concurrent engagements, ever |
| Care retainer | Cancel anytime with 30 days' notice |
Ready to scope something?
Start with services and pricing. If the numbers work, the intake form takes five minutes and costs nothing.