Sorry Isn't a Feature: Rewriting the British Launch Page

There's a particular email that lands in my inbox most weeks. The subject line usually reads something like: Sorry for the extra email — quick update. The body opens with an apology for the length of the message, follows with a hedge about whether the product is really for you, and closes by hoping it might perhaps be a bit useful.

Somewhere in there is a genuinely good product. You'd never know it from the copy.

The reflex, and where it comes from

Understatement is a national sport. We're a country that says "not bad" when we mean excellent and "with respect" when we mean the opposite. That instinct is charming in a pub and expensive on a landing page.

Launch copy is one of the few places where a founder has a stranger's full attention for about eleven seconds. Spending three of those seconds apologising for taking up space is a strange way to use them. But it happens constantly, and it's rarely a strategy. It's usually nerves, dressed up as politeness.

Four ways the hedge shows up

1. The pre-emptive apology. "We know this isn't for everyone, but…" You've invited the reader to disqualify themselves before you've told them what the thing does. Some will take you up on it.

2. The diminishing adverb. "We've just built a small tool that simply helps you…" I counted six instances of "just" above the fold on one Manchester dev-tools site last month. Six. Every one of them was doing the same job: shrinking the product so the founder wouldn't have to defend it.

3. The trapdoor hedge. "Hopefully this is useful." It reads as humility. Structurally, it's a question — and it hands the reader the option to answer no.

4. The confession-as-feature-list. "It doesn't do X yet, and integrations are coming soon." Honesty is good. Publishing your roadmap gaps in the hero section on day one is not honesty, it's pre-emptive surrender.

Confidence is not the same as hype

Here's the fear that keeps the hedging in place: if I sound too sure of myself, I'll sound American. Fair worry. Nobody in the UK wants to write "revolutionary game-changing platform" with a straight face, and readers can smell it instantly.

But confidence and hype are different instruments. Hype is vague and loud. Confidence is specific and quiet.

• Hype: "Transform the way your team works."
• Confidence: "Cuts invoice reconciliation from 40 minutes to four."
• Hype: "World-class support."
• Confidence: "A real person answers within two hours, Monday to Friday."

Specificity does the work that adjectives can't. It's also the most British possible route to sounding assured — you're not boasting, you're just stating facts and letting the reader draw the conclusion.

Rewrites that hold up

A few swaps worth making before your next push:

• "Sorry to bother you — we've just launched a small beta." → "We've launched. Here's what it does, in one line."
• "Hopefully this might be useful for some of you." → "If you handle supplier invoices, this will save you about an hour a week."
• "We're only a tiny team, so please be gentle." → "Two of us built this. Feedback goes straight to both of us."
• "It's not perfect yet, but…" → Move it. Changelog, status page, or the FAQ. Not the hero.
• "We think it could potentially help with…" → "It helps with X. Try it on one workflow and see."

That last one matters more than it looks. "Try it on one workflow" is a low-stakes, very British invitation. It's confident about the outcome and modest about the commitment. You can have both.

Where the genuine caveats should live

None of this means hiding limits. Early-stage buyers are forgiving of gaps and unforgiving of surprises. The trick is placement, not omission.

Put the caveats where a serious evaluator will find them — a short "what it doesn't do yet" section near the bottom, a public changelog, a clear pricing page that says what's included. That way the curious buyer gets the full picture, and the skimmer gets a reason to click instead of a reason to leave.

A thirty-second test before you publish

Read the page out loud. Count the apologies, the "just"s, the "hopefully"s and the "we think"s. Then answer two questions as if you were a stranger: what does this do, and who is it for? If either answer takes more than one sentence, the copy is still hedging.

Understatement is a fine national brand. Launch day isn't the moment to deploy it. Be polite in the email, be clear on the page — and save the sorry for when you've actually got something to apologise for.