MVP Mini

What you get

1. 01

   Deployed on your domain

   On your hosting account with the DNS pointed and TLS working — not a preview link on our machine that somebody has to move later.

2. 02

   The words, not just the layout

   Copy drafted from what you tell us the page is for. A beautiful page saying nothing is the failure mode here, and it is the one nobody catches until it is live.

3. 03

   A form that reaches you

   Contact or signup wired to an inbox and tested by sending one through it, because a form that silently drops submissions is worse than no form.

4. 04

   Yours from the first commit

   It lands in your GitHub, not ours. Three pages is small enough to read end to end, which means you can actually check what you were given.

How the build runs

1 to 3 working days from kickoff. You review throughout rather than at the end — a staging URL is live from the first day and updated continuously.

1. Before day 1You tell us what the page has to make somebody do, and who they are. The scope comes back in writing, page by page. Changes are free here and expensive later.
2. Day 1Repo created, deploy running, a live staging URL you can watch. First pass at the copy and the layout.
3. Days 2–3The pages built, the form wired and tested, the domain pointed. If it is a single page, this is often the same afternoon.
4. At handoverLive on your domain, repo transferred, deploy running from your own account, and one test submission through the form so you have seen it arrive.
5. Within 7 daysYour one round of changes.

What the price covers, in numbers

A fixed price with an unbounded scope is not a price. These are generous enough that almost every honest brief fits — they exist so the one that does not is recognised at the scope stage rather than in week two.

• PagesUp to 3Distinct pages a visitor can reach. Sections within a long page are not separate pages — one scrolling landing page is one page.
• Forms1Contact or signup, delivering to one inbox. A second form, or one that writes to a database, is a different job.
• Rounds of changes1Within 7 days of handover. Fixes to things that do not match the scope are not a round; they are just fixes.
• Languages1One language. A translated second version is a separate quote, not a toggle.
• Accounts and paymentsNot includedNobody signs in and nothing is charged. Both are what the MVP is for, and both are why it costs five times as much.
• Content editingNot includedNo CMS or admin area. Changing the words later means editing the repo or asking us.

When it counts as delivered

Written down so “done” cannot drift. Every one of these is true before the balance is due.

• ✓ Every page in the scope is live on your domain over HTTPS
• ✓ The form has been submitted once and the message arrived in your inbox
• ✓ The repo is transferred to you and the deploy runs from your own account
• ✓ It reads correctly on a phone, which is where most of the traffic will be

Not included

Said plainly rather than left to be discovered. None of it is refused — it is simply a different job, quoted as one.

• — Accounts, sign-in or anything storing user data — that is the MVP
• — Payments, checkout or subscriptions
• — A CMS or admin area for editing the words yourself
• — Native iOS or Android apps — a three-page site does not have one
• — Brand, logo or visual identity design — it uses a clean default or your existing brand
• — Ongoing SEO, content or advertising after handover
• — Migrating an existing site's content or preserving its URLs
• — Ongoing hosting, maintenance, monitoring or support after the change round
• — Legal documents — terms, privacy policy, cookie notices
• — Analytics beyond a single tag you supply

If it turns out to be bigger

Every fixed-price build meets this eventually. Handled late it is an argument; written down in advance it is a conversation.

1. 01

   The scope document is the agreement

   One page, approved by you before anything is built, naming what is in and what is not. If something is not on it, it is not in the build — not as a refusal, but so that both of us know what was agreed when we are three days in and busy.

2. 02

   A brief bigger than the tier is caught at the scope stage

   That is what the stage is for. You will hear it before you have waited a week, not after. Then it is your choice: cut it back to fit, move up a tier and pay the difference, or take a refund. Nothing has been lost but a conversation.

3. 03

   Changes during the build are quoted, not absorbed

   Wanting something different once you see it is normal and welcome. It is also new work: it gets an estimate and a date before it starts, and it never quietly displaces something already agreed. A change that fits inside the scope in exchange for something coming out is free — that is a trade, not an addition.

4. 04

   A fix is not a change

   If it does not do what the scope document says, that is a defect and it gets fixed at no cost and without spending a round. Rounds are for things you have changed your mind about.

5. 05

   The limits above are the boundary of the price

   Not a refusal to do more. Beyond them is simply a bigger job, quoted as one — which is fairer than pretending a five-day week can absorb a five-week brief.

What we need from you

The date is measured from kickoff, and kickoff is when these are in. A week waiting on an answer is a week off the calendar.

• A clear idea of which part is being built

  Not the whole roadmap — the piece. Knowing that this build is the booking flow and not the billing is worth more than any technical vocabulary.

• The detail behind it

  The rules that live in your head: who is allowed to do what, what happens on the awkward Tuesday, the customer who always asks for the exception. That context is the difference between something that works and something that demos.

• Coding knowledge, if you have it

  Helpful, never required. It makes the review conversations quicker and it means the handover documentation lands sooner. Plenty of people buy a build having never opened an editor, and it goes fine.

• One person who decides

  Somebody who can answer a question the same day. Most delays on a short build are not technical.