Someone Hated It: A UK Founder's Field Guide to the First Public Complaint

There's a specific noise a founder makes when they see their first one-star review. It's not quite a gasp. It's more of a small, involuntary exhale, followed by the immediate desire to check whether the reviewer has a LinkedIn profile.

Almost every founder we've spoken to for Start Network can remember the exact day. Not the month, not the week — the day. The review itself is usually banal. A late delivery. A coach who didn't turn up. A subscription that was harder to cancel than it should have been. What makes it sting is that it's public, and it arrived without warning, and a stranger has written a three-line verdict on a business you have poured two years of your life into.

So here's what actually helped, according to people who've been through it.

First: the 24-hour rule (and why nobody follows it)

Every founder we spoke to said the same thing in slightly different words — do not reply on day one. Not because you're being strategic, but because you are, at that moment, chemically incapable of writing a good reply.

"I drafted six responses," says Priya, who runs a small e-commerce brand out of Sheffield. "The first one was a legal threat. The second was an apology so grovelling it made us look guilty of something. The third was 900 words long. I sent none of them, went to the gym, and wrote the one that worked the next morning in about four minutes."

The overnight gap does two things. It lets you check the facts, and it lets the anger metabolise into something you can use.

Triage before you type

Before you write anything, work out which of these four buckets you're actually in. The reply is completely different for each.

• A genuine service failure. Something went wrong, it was your fault, and you can fix it. This is the easy one and the most common one.
• A mismatch of expectation. They wanted something you don't sell. Frustrating, worth clarifying publicly, usually not worth a fight.
• A safety or compliance issue. Anything involving food, children, health claims, or a product that might have hurt someone. This goes to your insurer and, if it's serious enough, to a solicitor the same week.
• Something that isn't a review at all. Abuse, a competitor, a person who was never a customer, or a demand for money to take it down.

That last bucket is rarer than it feels when you're staring at it at 11pm, but it does happen. If someone is threatening to keep the review up unless you refund them, screenshot the whole exchange and stop engaging. Both Google and Trustpilot have reporting processes for reviews that break their content policies, and UK consumer law — the Digital Markets, Competition and Consumers Act 2024, in particular — takes a dim view of reviews that are fake or manipulated in either direction. What you must not do is offer someone money or a freebie to delete a negative review. That can land you in more trouble than the review ever could.

The reply that does most of the work

Here's the thing founders consistently underestimate: future customers reading a bad review are mostly looking at how you responded. A calm, specific, human reply under a one-star review can do more for conversion than three five-star reviews from your mates.

A structure that keeps coming up:

Thanks for taking the time to write this, [Name] — and I'm sorry the [specific thing] didn't work. That's not the experience we want anyone to have. I've emailed you directly with [the fix / a refund / a replacement]. If it's easier, my number is [X]. — [Your name], founder

Four elements, in this order: acknowledge the specific thing, apologise without arguing, say what you've actually done, and move it off the platform. Never explain, never itemise the customer's mistakes, never mention how tired your team is. Nobody reading it wants context. They want to see that you're a person who handles things.

For an angry email rather than a public review, the same logic applies with one change — you can be much shorter:

Hi [Name], I've read this properly and you're right to be frustrated. Here's what I'm doing about it: [one line]. I'll confirm once it's sorted. Sorry again.

Founders who've done this at volume report the same strange outcome: a decent chunk of angry people write back and soften. A few quietly edit their review. Most just go away, which is also fine.

When to stop replying

If the second or third exchange is going nowhere, close the loop publicly and stop. Something like "I understand we see this differently — I've refunded you in full and I don't think there's more I can usefully add here." Then actually stop. Arguments in review threads are the only thing that reliably turns a small problem into a reputational one.

"The moment I stopped trying to win," says Callum, who runs a small training business in Bristol, "the whole thing shrank. It was one star out of forty. I'd been carrying it around like a court summons."

The reputational question, honestly

Most founders' first instinct is is this damaging my business? Usually, no. One negative review among a healthy spread is read as proof that your reviews are real. What does damage a business is a pattern — the same complaint showing up three times in a quarter.

So the useful thing to do with review number one isn't to delete it. It's to read it as free operations data. Print it. Put it in the next team meeting. Ask what would have had to be true for that person to have had a good experience. That's the whole lesson, and it's usually cheaper than the mistake you'd have made in six months without it.

One star, one lesson. Then back to work.