Skip to main content

One senior team builds it, to the spec we agreed

Positioning, the sales process, systems, brand or the website: whatever the strategy calls for gets built in parallel by the same people. You review at set checkpoints, and you're never the one managing the project.

02.Build

You walk away with:

The work, built to the exact spec we agreed on. No scope creep. No surprise invoices.

Typically weeks 3 to 7

When
Typically weeks 3 to 7
Your time
Checkpoint reviews and quick decisions
Run by
One senior in-house team
You get
The work, built to the agreed spec
Why it runs this way

Handoffs are where good strategy gets lost

In a lot of projects, the strategist hands a deck to a copywriter, who hands words to a designer, who hands files to a developer. Each handoff loses a little of the original intent, and by launch the site says something nobody quite decided.

We keep it in one room. The people who wrote your strategy stay on the build, messaging and design move together, and engineering starts while the design is still settling, so problems surface early instead of in week seven.

And because the scope is agreed in writing before we start, you know the price. If something new comes up, we size it and you decide. Nothing gets added quietly.

0hours billed. Every project is a fixed fee, scoped before work starts.
How we price
Parallel, not passed along

Five workstreams, one team, three checkpoints

A typical Conversion System build. Hover or tap a workstream to see what happens in it. Your proposal sets the real dates.

Wk 3Wk 4Wk 5Wk 6Wk 7
Checkpoints
  1. Checkpoint 1, end of week 3: Structure and message direction
  2. Checkpoint 2, end of week 5: Design and copy review
  3. Checkpoint 3, end of week 7: Finished work on staging

Messaging and copy

Headlines, page copy, proof and calls to action, written from the strategy.

When something new comes up

How a change gets handled, so the price never drifts

  1. 1You spot somethingA new idea, a missed page or a change of mind. It happens on every project.
  2. 2We size it in writingWhat it involves, what it would change and what it would cost, before anyone starts on it.
  3. 3You decideAdd it, swap it for something already in scope, or park it for after launch.
  4. 4Then it's builtOnly once you've agreed, and it goes into the change log so nothing is a surprise later.
Step by step

How the build moves from plan to finished work

  1. 1Week 3StructureInformation architecture: which pages exist, what each one is for and the path a buyer takes through them. This is where the hesitation map turns into a layout.
  2. 2Weeks 3 to 5Messaging and copyThe strategy becomes real words: headlines, page copy, proof, calls to action and form wording, written to be scanned by busy buyers.
  3. 3Weeks 4 to 6DesignDesign built around the copy and the decision it supports, using a reusable design system your team can extend later without us in the room.
  4. 4Weeks 5 to 7Engineering and integrationsDevelopment, CRM and form connections, speed and accessibility work, all on a private staging site you can click through at any time.
  5. 5End of week 7Final checkpointThe finished work, checked against the spec and the strategy, ready for launch testing.
Side by side

Who does what in Build

Your part

  • Feedback at agreed checkpoints
  • Quick decisions when we need one
  • One consolidated set of comments per review

Our part

  • Messaging, design and copy
  • Engineering, integrations and CRM
  • Progress shared at every checkpoint
  • Keeping the scope and the price where we agreed
What you walk away with

Finished work you can click through before anyone else sees it

By the end of the build, everything below is done and waiting on a private staging site.

  • 01A site built on the strategyEvery page has a job, and every headline traces back to the argument we agreed.
  • 02Copy that sounds like your best salespersonWritten for scanning buyers, with proof next to every claim.
  • 03A reusable design systemComponents your team can use for new pages without starting from scratch.
  • 04Working integrationsForms, CRM and booking connected and tested, so leads land where your team works.
  • 05Speed and accessibility built inFast pages and accessible markup from the start, rather than patched on at the end.
  • 06A written change logAnything that changed from the original scope, sized and approved in writing.
Side by side

What a strategy-led build feels like from your side

Who you talk toHow it often goes: An account manager relaying messagesHow we run it: The senior people doing the work
How work movesHow it often goes: Copy, then design, then code, one after anotherHow we run it: In parallel, checked against one strategy
When something new comes upHow it often goes: It's added, and the invoice growsHow we run it: We size it in writing and you decide
How you see progressHow it often goes: A big reveal near the endHow we run it: A staging site and three set checkpoints

Questions about the Build phase

scope it properly

Get a fixed price before a single pixel moves.

On a free call, up to an hour, we talk through what your build would include, what would drive the price and what we'd leave out.