Services · the four-stage pipeline
Launch-ready brands for venture-backed companies.
For teams with a funding round or a launch date. We resolve a brand and a website from evidence, in one sprint, and hand over the tokens.
Who it is for
Seed to Series B, with a date on the calendar.
The problem, in the buyer's words
The pitch is next month. The deck has changed three times. The site still shows the template. Every designer we brief gives us taste, and we need reasons we can defend to the board.
What we do about it: resolve every design parameter from your positioning, your category's convention and one or two deliberate breaks, then write the reasoning down next to the value. The board reads the reasoning. The developer reads the tokens.
The sprint
Four stages, each with a named deliverable.
01
Discovery
A 20-minute guided call. We read your positioning, name the category you will be judged against, and choose three of the seven modules for this sprint.
Nothing is designed yet. The call ends with a fixed price in writing.
Deliverable
The discovery record: positioning, category, the two breaks, the three modules, the forcing date, the price.
02
Design Parameters
Colour, type, spacing, shape and motion resolved from the three inputs. Each value carries its mechanism, its source and its evidence grade.
Where a value follows the category we say so. Where it breaks the category, we say why.
Deliverable
The token file (CSS custom properties, imported unchanged into the build) and the parameter sheet, 18 rows, graded.
03
Design Anatomy
Every page as a spec sheet: section order, the components on it, the copy register, the proof it carries and the ask it ends on. Webflow-native, so the build is a transcription, not an interpretation.
Deliverable
Template spec sheets for home, work, services, about and contact, plus the component list with states.
04
Development
The build on the tokens, the CMS with alt text required at field level, Core Web Vitals budgets gated before launch, and the governance note that says how the system changes by version.
Deliverable
The live site, the CMS, the token hand-off, the accessibility statement, the governance document.
The seven modules
Three are chosen on the call. The rest can be added.
| Module | What it covers | Stage |
|---|---|---|
| 01 · Web development | The build itself: templates, CMS, performance budgets, hand-off. | 04 |
| 02 · SEO | Information architecture, page titles, schema, internal linking, the technical audit. | 03–04 |
| 03 · GEO | Visibility in AI answer engines: structured data, a readable llms.txt, sourced claims on every page. | 03–04 |
| 04 · Marketing | The launch sequence, the social kit, the caption playbook, the deck. | 02–04 |
| 05 · Analytics | Events tied to the conversion ladder, Core Web Vitals field data, a monthly read. | 04 |
| 06 · CRM | The form, the pipeline it feeds, the follow-up that does not need a sequence. | 04 |
| 07 · ERM | The operations layer the site talks to: stock, bookings, scheduling, projects, invoicing. | 04 |
Two offers are in progress and not yet named: a whitelabel CMS (Payload CMS v3 with Next.js, managed or self-hosted, no licence enforcement) and hosting. They are described here as offers, not as products, until a name is signed.
Engagement model
Sprint, module or retainer. The price is written down first.
Sprint
Fixed scope, fixed price.
The four stages, three modules, one forcing date. 50 % to book, 50 % on delivery.
Module
One of the seven, standalone.
For a site that already has its parameters and needs one capability added.
Retainer
Governance and additions, monthly.
The system changes by version, not by drift. We hold the version.
Is this for you
Four things that are true of the teams we work with.
- 01
Venture-backed, seed to Series B.
- 02
A launch date or a funding round inside the next quarter.
- 03
One decision-maker who can approve a parameter sheet in a week.
- 04
A willingness to publish the reasoning, including the case study.
Questions
Five things we are asked on the call.
How long is a sprint?
Long enough to reach the forcing date you give us on the call, and no longer. The duration is written into the discovery record with the price. We do not publish a generic number because a number without its project is the thing we are built against.
Do we keep the tokens?
Yes. The token file is yours from day one, in plain CSS custom properties, with the parameter sheet that explains each value. Nothing in it references Brentwell; our colours, faces, chamfer and voice never leak into a client build.
Webflow or code?
The design anatomy is Webflow-native, so a Webflow build is the default. Where the site talks to an operations layer or needs a CMS with alt text enforced at field level, we build on our own CMS (Payload CMS v3 with Next.js) and hand it over, managed or self-hosted.
Will you show our screens?
Only with written approval on file, and only with the metrics that belong to your project. If you prefer not to be named, the case is published as “client name withheld” with the decisions and the reasoning, and no screens.
What does the price cover?
The four stages, the three modules chosen on the call, two rounds of revisions per stage, the token hand-off, the accessibility statement and the governance document. Extra modules are quoted as modules. There are no hourly rates and no surprises after the record is signed.
How it starts
One call. Twenty minutes. Three questions.
Who you are, when you launch, and which three of the seven modules matter first. You leave the call with a fixed price in writing.