Six disciplines, practised closely. No retainers for thin work.

Most "tone of voice" documents are six adjectives and a colour swatch. Ours is the size of a short play and structured like one — because the question your team is actually asking when they sit down to write a press release at four in the afternoon is not "what is our brand essence" but "is the word delight on the banned list, and do we use the Oxford comma, and how do we open a customer-service email when the customer is right but rude."

A Voice System answers those questions. It includes an archetype — but only because the archetype gives the team a shorthand, not because we believe in archetypes religiously. It includes a working vocabulary, with the words we want and the words we want gone. It includes three calibrated example pieces — a homepage paragraph, an email, and a 90-character ad — that the team can hold up beside their own draft and ask: does it sit on the same shelf?

We deliver the document, walk three colleagues of yours through it for forty minutes each, and stay on Slack for two weeks while the first writer using it gets the hang of the rhythm.

A website is a story told out of order. The visitor arrives anywhere — a feature page from a Google search, a pricing page from a competitor’s comparison post — and has to be invited, in two seconds, to spend the next ninety with you. We write each page as if it were the first one anyone would read, and then we make sure it survives being the second.

We start by reading every page on the existing site out loud, into a recorder, and listening back at 1.5x. (You learn things.) We interview the founder, three customers, and one person who almost became a customer and did not. Then we write — not the new homepage first, but the third-most-important page, the one whose voice will tell us whether the new system survives a low-stakes test.

Designers love working with us because we annotate. Every paragraph carries a margin note about hierarchy, weight, and the moment we expect someone to scroll. The handover document is the one your designer wishes every copywriter would write.

A launch is not a marketing exercise. A launch is the company introducing itself to people who are about to make a small bet on whether to care. The headline has to be specific enough to remember and generous enough to forward. The founder letter has to sound like a person, not a press release. The press note has to translate the same idea into the shape a journalist can lift in eleven minutes.

We work with launches end-to-end: we sit in the room when you finalise the feature list, we argue about which thing is actually new, we draft the founder letter while the engineering team is still writing release notes. By the time the product ships, you have a clear, defensible story, and six aligned versions of it for the channels where it has to land.

We have launched a B2B observability tool, three consumer apps, an architecture practice, two fintech products, and a literary magazine. The work is the same — clarity is clarity.

There is a kind of writing that works once and a kind of writing that works for a decade. The second kind is rarer, slower, and worth the difference. We write long-form pieces — under your byline or ours — that make a single, specific claim and defend it well enough to be worth re-reading.

A piece we wrote in 2021 for a logistics-software client is still, four years later, the most-read page on their website and the second-most-common entry point for sales conversations. That piece took us eleven days. The cost amortises across every quarter that has come since.

We do not do "content marketing" in the volume sense. We do not write twelve listicles a quarter. We write four or five real pieces a year per client, and we research them like we are answering to an editor.

A name is the most-used piece of copy in any company. The CEO will say it ten thousand times. The investor will write it on a napkin. The customer will say it slightly wrong, and either fall in love with the wrong version or quietly stop using it. Naming is not branding theatre — it is high-frequency, high-stakes copywriting.

We run a structured five-day naming sprint. Day one is research. Day two is generation — we usually produce around two hundred names, then we throw away most of them. Day three is sound and rhythm checks; day four is trademark and domain pre-screening; day five is the recommendation memo.

You will receive five to seven names you can defend in a board meeting, ranked, with rationale and sound analysis, and one or two we recommend most strongly with a clear case for why.

Most teams know something is off, but they cannot say where. The product page reads fine, except — and the email sequence converts, but — and the social copy is funny, sort of. An audit gets specific.

We read every public-facing piece of copy you have, score it across nine axes, and produce a 16-page document that names the problems plainly. Not "your tone could be more consistent" — but "the homepage hero promises a different brand than the pricing page, and here are the three sentences responsible." Not "your blog could perform better" — but "five of your last twelve posts sound like generic SEO writing, and three of them are doing more harm than good."

The audit is sometimes a project on its own. More often it is the start of a Series engagement, because once a team sees the problems clearly, the question of what to fix first usually answers itself.