How the workgets made.
Thirty days from first call to live site, in five phases with a fixed price agreed before phase one ends — no open-ended discovery, no invoice that grows.
The five phases
(05)- 01DiscoveryDay 1–3
- 02Strategy and structureDay 4–8
- 03DesignDay 9–18
- 04BuildDay 19–27
- 05Launch and handoverDay 28–30
Finished work, on a clock.
Every phase ends in something you can hold: a document, a file, a URL. If a phase produces nothing you can open, it was not a phase.
- /01
Discovery
Day 1–3A working session, not a questionnaire. We get to what the business actually sells, who it sells to, and which single action the site has to produce. Everything after this is measured against that answer.
- Project brief
- Success metric
- Fixed quote
- /02
Strategy and structure
Day 4–8Sitemap, page-by-page content plan and the argument each page has to make. We write the real copy at this stage, because designing around placeholder text is how sites end up saying nothing.
- Sitemap
- Copy deck
- Wireframes
- /03
Design
Day 9–18Full visual design in Figma, desktop and mobile, with a component library so the site stays consistent as it grows. Two review rounds are built in. The first lands before anything gets built.
- Figma designs
- Design system
- 2 revision rounds
- /04
Build
Day 19–27Webflow or Next.js depending on who maintains it after launch. Responsive to 320px, accessible, fast on a Nigerian 3G connection as well as European fibre, with every repeating section wired to the CMS.
- Responsive build
- CMS collections
- Speed pass
- /05
Launch and handover
Day 28–30Your domain, your accounts, your analytics. Handover includes a recorded CMS walkthrough so your team can update the site the same week, and thirty days of support while it beds in.
- Live site
- Recorded walkthrough
- 30 days support
Three things, and that is all.
Everything else is on us. These are what keep thirty days at thirty.
- /01
One decision maker
The person who can approve a direction without a committee. Projects stall on sign-off, never on design.
- /02
Your raw material
Logo files, photography, product detail, anything written about the business already. Rough is fine, we shape it.
- /03
Feedback in one pass
Collected comments once per round rather than drip-fed over a week. It is the single biggest thing that keeps a build on schedule.
- Days, brief to live
- 30
- Revision rounds included
- 2
- Surprise invoices
- 0
The five things everyone asks.
What if we miss a deadline on our side?
The timeline shifts by the same number of days, and we tell you the new launch date the moment it happens rather than at the end. Nothing is re-quoted for a delay that is a few days long.
Can we start mid-process if we already have designs?
Yes. If the designs are sound we pick up at phase 04 and price the build alone. If they are not, we will say so before you pay for a build on a weak foundation.
Webflow or Next.js — who decides?
We recommend, you decide. Webflow if your team will edit the site often and nobody there writes code. Next.js if the site is really a product, or it has to talk to systems you already run.
What does a revision round actually cover?
Any change to layout, copy, type, colour or section order inside the agreed scope. A new page or a new feature is not a revision, and gets quoted before we touch it.
What happens after the 30 days?
Nothing automatic. No retainer is required and no licence keeps running. If you want ongoing work we scope it separately, and if you do not, the site is entirely yours.
