Stop Apologising for Your Own Sales Page: A Case for Blunter British Copy

There's a particular kind of British sentence that appears on almost every website we read. It goes something like: "We're a small team, but we just wanted to share a few options that might be useful if you're thinking about it." Nine hedges. Zero conviction. And yet, if you asked the person who wrote it, they'd tell you they were being polite.

They were. That's the problem.

Politeness has a direction, and most brands point it the wrong way

British English is built for softening. We apologise to doorframes. We say "sorry, can I just..." when we are, in fact, about to ask for something entirely reasonable. We understate catastrophes ("the launch was a bit of a wobble") and overstate gratitude. It's a social lubricant, and up close it makes us lovely to deal with.

In writing, though, politeness has a direction, and it matters enormously which way you point it.

Pointed at the reader — their time, their attention, their intelligence — politeness is a strength. "Short version: two minutes, no jargon, here's the number." That's courtesy with a spine. It respects somebody enough not to waste them.

Pointed at yourself — your right to exist, your competence, your entitlement to take up space — politeness becomes a liability. Every "just", every "sorry to bother you", every "we're not experts, but..." is a small withdrawal from your own credibility. Do it four times in a paragraph and you've overdrawn the account.

The usual suspects

Read your own web copy out loud and listen for these. They hide in plain sight.

• The pre-emptive apology. "Sorry for the long email." "Apologies for the delay in getting back to you." Fine in a service email when a delay actually happened. Weird in a homepage hero, where nothing has gone wrong yet.
• The permission request. "If that's okay?" "Hope that's alright." You are not asking a favour by publishing a service page.
• The diminisher. "Just a quick note", "a little something we've been working on", "a few small updates". Everything you've built is apparently tiny.
• The false modest clause. "We might be biased, but..." You are. Everyone is. Say the thing anyway.
• The double hedge. "We could possibly potentially look at..." Pick one verb and commit to it.

Individually these are invisible. Collectively they produce a voice that sounds like a capable person apologising for being in the room.

A working rule

Here's the rule we'd put on the wall: hedge the claim, never the speaker.

If your claim needs qualifying — because it's provisional, regulated, or genuinely uncertain — qualify the claim in plain terms. "Timelines depend on your current setup; most projects like this take six to eight weeks." That's honest and authoritative at the same time. Nobody's confused about who's in charge of the sentence.

What you don't do is pre-soften the speaker. "We're not sure if this is relevant, but we might be able to help, maybe." Now the reader has two uncertainties to process: the project timeline and whether you believe in your own business.

Quick swaps that don't turn you into a robot

You don't need to start writing like a billboard. Just move the cushion.

• "I just wanted to ask if..." → "Quick question:"
• "Sorry to chase, but..." → "Following up on this —"
• "We're a small team, but we..." → "We're a small team. That means you get the person who actually does the work."
• "Hope that makes sense!" → "Shout if anything needs clarifying."
• "We think this might be useful for you" → "This is for teams doing X."
• "A little update on our pricing" → "Our pricing changed on 1 October."

Notice that none of these are rude. Several are warmer than the original, because warmth without apology is what confidence reads like.

Where the hedges should stay

Let's be balanced about this, because bluntness is not a personality. There are places where British understatement is doing necessary work:

• Complaints and service recovery. Here, "sorry" is not weakness, it's accountability. Don't blunt it.
• Regulated or financial claims. Hedging is a legal requirement, and a plainly worded caveat beats a bold lie.
• Accessibility and content warnings. Softening language helps people decide whether to keep reading.
• Anything involving people's money, health, or data. Careful is correct.

The distinction is simple enough: keep the hedges that protect the reader. Cut the ones that protect you.

The test

Before you publish, take your opening paragraph and ask: if a competitor wrote this, would I think they were being thoughtful — or that they weren't sure they deserved the sale?

If it's the second one, you don't need a new strategy. You need to delete four words and stand up straight. The politeness was never the problem. The direction was.