How we work
Six stages from a price to a live site. This page is what happens in each one, what we need from you, and where you can see it happening.
The six stages
The same six stages the home page lists, with what each one actually involves. Every stage names what we need from you, because that is the half of a project timeline nobody publishes.
Stage 1: Choose
Configure your package online and see the price as you go. No form to fill in before you find out what it costs.
- What happens
- You configure a package, its add-ons and its timeline online, and the price updates as you go.
- You can save the quote and come back to it, or send it to whoever signs things off.
- If the work is genuinely custom, this is where a scoping sprint replaces the fixed price.
- What we need from you
- Nothing at this stage.
- What you approve
- Nothing is gated on your sign-off here.
- What your portal shows
- Nothing yet — there is no project until you order, and nothing on this stage needs an account.
Stage 2: Brief
A guided brief collects your goals, brand and content. Your delivery clock starts when the brief is complete, not when you pay — so the date we give you is one we control.
- What happens
- Your deposit settles and the project creates itself: milestones, tasks, your message thread, your brief and a named delivery lead.
- A guided brief collects your goals, your brand, your pages and your content, a section at a time, and you can stop and come back.
- Your delivery lead reviews it, flags anything missing, and holds a kickoff call.
- What we need from you
- The brief completed, plus your logo, brand assets and the copy for any page you are writing yourself. This is the one stage where the timeline is genuinely in your hands.
- What you approve
- Nothing is gated on your sign-off here.
- What your portal shows
- The brief with its progress, a blocked-on-you list that is specific about which item is missing, and your target launch date.
Your delivery clock starts when your brief is complete, not when you pay. How we can quote a timeline at all
Stage 3: Design
Your brand applied to a proven template, or two custom concepts, depending on the package. You sign it off in writing before anyone starts building.
- What happens
- Your brand applied to a proven template, or two original concepts, depending on the package.
- We review it internally before you ever see it, so what reaches you is work we would defend.
- You give feedback, we revise it, and the revision rounds included in your package are counted openly.
- What we need from you
- Feedback in one pass where you can manage it. Serial one-line replies are what turn a two-day revision into a fortnight.
- What you approve
- The design, in writing, in the portal. Nothing gets built until you have — and once you have, the build stage is unlocked and the design invoice is issued.
- What your portal shows
- Each concept with your comments pinned to the spot you are talking about, the revision rounds remaining, and who is waiting on whom.
Stage 4: Build
Pages, forms, SEO and analytics. You follow progress in your portal, where the percentage is milestone weights and the screen will show you the arithmetic.
- What happens
- Pages built, forms wired and tested end to end, SEO basics and analytics installed.
- Content goes in page by page — the pages you are supplying and the pages we are writing are tracked separately, and each is approved before it is built.
- Work is reviewed by a second pair of eyes before it counts as done.
- What we need from you
- Any content you are supplying, by the date in your portal. Missing content at build time becomes a placeholder and a visible blocker rather than a quiet hole in your site.
- What you approve
- Page content, as it lands. Nothing here needs a formal sign-off.
- What your portal shows
- A progress figure that is milestone weights rather than a feeling, the current milestone, and every task that is waiting on us.
Stage 5: Launch
The full QA checklist, accessibility included, then your approval, deployment, the DNS cutover and your training session.
- What happens
- The full QA checklist runs, and the launch button stays disabled until every item passes.
- We agree a launch window with you, take a final backup, deploy, cut the DNS over and verify the certificate.
- Redirects from your old URLs are checked by crawling them, then we smoke-test the site, submit the sitemap and turn monitoring on.
- You get a handover pack and a training session on your own dashboard, live, with someone talking you through it.
- What we need from you
- Your launch approval, and access to your domain if we are not already hosting it. The final invoice is also due — the platform blocks the DNS cutover while it is unpaid, and that is enforced in code rather than chased by email.
- What you approve
- The site, before it goes live. That approval is recorded.
- What your portal shows
- The QA checklist with every item's result, the launch window, and afterwards your live link and your warranty period.
Stage 6: Grow
Your care plan takes over: hosting, monitoring, backups, patching and content edits, with growth services when you want to do more.
- What happens
- Your care plan takes over: hosting, monitoring, backups, patching, uptime checks and your content edits.
- We check in after a week and after a month, because the questions people actually have arrive once they have used the thing.
- Anything broken inside your warranty period is our defect and is fixed free, at priority. Anything new is a change, and it is scoped and quoted before a minute is spent on it.
- What we need from you
- Nothing at this stage.
- What you approve
- Any change request, before work starts. Both sides see the same status, and the launch date is formally revised rather than quietly slipping.
- What your portal shows
- Your site's uptime and performance, your enquiries, your content, your invoices, and any change request with its quote.
How we can quote a timeline at all
Each package has a published timeline, and it holds because of three constraints we do not negotiate away. Naming them is more useful to you than a faster-sounding promise.
- The clock starts when your brief is complete
- Not when you pay. The single biggest cause of a slipped launch is waiting on content, and a timeline a client can pause by not replying is not a timeline. This way the date we give you is one we control and can be held to.
- Content is yours to supply, or ours to write as a priced add-on
- There is no room inside a one-week build to write five pages of researched copy. Copywriting is a published per-page add-on, and choosing it extends the timeline rather than compressing the work.
- On the fastest package, the 3D hero is a preset scene tinted to your brand
- A scene written from scratch for your sector is days of work on its own. It is available as an add-on on any package, and it changes the timeline accordingly.
Timelines are working days. Weekends and UK bank holidays are excluded when your launch date is calculated, so the date in your portal is a date and not an estimate that quietly assumes nobody takes a Monday off.
If we are waiting on you, the system says so on a schedule rather than leaving your delivery lead to decide when to nag. At two weeks of waiting, your project is formally marked at risk and you are told in writing that the launch date has moved.
Nothing launches until the checklist passes
Every build is checked against the same list, item by item, with the result and the evidence recorded against your project. A failure creates a task rather than a note somebody hopes to remember.
- Accessibility
- WCAG 2.2 AA, an automated scan with nothing outstanding, a keyboard-only pass and a screen-reader pass on the journeys that matter. This is a delivery requirement for us, not an add-on you can buy.
- Functionality
- Every link, every form actually delivering to a real inbox, every button, and the 404 page.
- Responsive
- Checked at six widths from a small phone to a wide desktop, not just resized in a browser window.
- Browsers
- Chrome, Safari, Firefox and Edge, current version and the one before it.
- Performance
- Core Web Vitals within Google's thresholds and a mobile Lighthouse score we are willing to publish.
- SEO
- Titles, descriptions, one H1 per page, alt text, sitemap, robots, canonicals, structured data, and Search Console verified.
- Analytics
- Analytics firing, your conversions configured, and both respecting the visitor's cookie choice.
- Legal
- Privacy, cookie and terms pages in place, a banner that blocks tracking before consent, and your company details in the footer.
- Security
- HTTPS enforced, security headers, no exposed admin, and a clean dependency scan.
- Content
- Proofread, no placeholder text anywhere, and your contact details and prices correct.
- Backups
- A backup taken and a restore actually verified, because an unverified backup is a hope.
- Handover
- Credentials documented and handed over safely, and your training session booked.
Launch day has a rehearsed rollback. The domain's cache time is lowered a day in advance specifically so that if a smoke test fails we can be back on your old site in minutes, tell you plainly, and fix it before trying again.
After you are live
The stage most quotes stop at. Yours includes a handover, a warranty and two check-ins, and then a care plan that is doing something every month whether or not you ask.
- Handover and training
- A handover pack with your credentials sent as a one-time link rather than sitting in an inbox forever, a how-to guide, your care-plan terms and support routes, and a live session on your own dashboard. Your content and design are yours outright on final payment.
- A warranty period
- For a stated period after launch, anything that is our error is a defect: fixed free, at priority, and recorded as a defect rather than argued about. Anything that is a new requirement is a change, scoped and quoted first.
- Two check-ins
- A week in and a month in. The useful questions arrive after someone has actually used the site, and a scheduled call is easier to take than one you have to ask for.
- A care plan doing the unglamorous work
- Hosting, uptime monitoring, backups with verified restores, security patching, and an allowance of content changes each month that you can spend by asking rather than by learning the dashboard first.
Start wherever suits you
The price does not need a conversation, and the conversation does not need a price. Either order works.