Approved in days, not months

The most expensive customer story is the one that is finished and unpublished. The interview went beautifully. The draft is strong. Everyone who has read it agrees it is good. And it has been sitting in someone's inbox for six weeks, going cold, while the campaign it was written for whizzes past.

Most approval delays are not caused by the customer. They are caused by internal stakeholders and process, sure, but also by how we ask. After twenty-five years of asking - on both sides of the fence - I can tell you the difference between a six-week approval and a same-week approval is almost never someone's diary; it's the shape of the request.

This guide is the shape that works - and it works on your own stakeholders too, which (let's face it) is where a bunch of stories stall.

The approval conversation you have at the end was actually decided at the beginning. When you invite an advocate to take part, the single most reassuring sentence you can say is: nothing goes out without you. You will see every word, and you approve it before anyone else does.

That sentence does two jobs. It gets you the interview, because control is what nervous participants actually want. And it reframes the eventual approval from a favour into a promise. An advocate who was told "you'll approve this at the end" opens the approval email as the final step of a plan to which they agreed; an advocate who receives a surprise draft opens it as a new demand on their time.

While you are there, ask the question that saves you a month later: "When it's ready, who besides you needs to say yes?" Hopefully no-one, yet every organisation seems to have someone with a quiet veto - comms, legal, a brand team. Finding this out in week one is free. Discovering it in week nine, after the advocate has approved and someone upstairs has not, is how stories die.

We often talk about approval as if the customer were the bottleneck. Think about where your last story actually stalled: was it the advocate, or was it your own side? Product marketing wanting the story to become a brochure, brand wanting the story to be about your org (customer logo removed), a sponsor exec surfacing in week five with a view. Internal review cycles are often the longest ones, and unlike the customer's, we cannot blame it on someone else's diary.

Two rules keep it survivable.

First, sequence. The customer sees the draft only after your own house has finished arguing. Nothing burns an advocate's goodwill like approving a story and then receiving a "slightly updated version" because someone internal had a late thought. You have spent their yes; asking for it twice reads as chaos, and the second yes always comes slower than the first. Internal round first, customer second, every time.

Second, run the internal round with exactly the discipline you would use on the customer: a named list of who must say yes (and who is merely being kept informed - the difference matters), the story as a finished page rather than a document (if you can), one consolidated round, a date. "Circulated to the team for thoughts" is how a story enters week six.

The biggest accelerator I know costs nothing: send the story as it will actually appear, not as an editable file.

A Word attachment says: here is a working document; please get in amongst it. Tracked changes, comment bubbles, "just a few small edits", a second version, a third. The format itself is asking for edits.

A finished page - laid out, branded - says something completely different: this is done, and it is good; are you happy? People line-edit documents. They approve pages.

PDFs are way faster than Word docs for approval. Web pages are even faster than PDFs. "Attached for your review" is the slowest sentence in customer marketing. Show the real thing. The closer the review artifact is to the published artifact, the faster the yes.

Look at the approval email you sent last time. How many questions was the advocate actually being asked? Any feedback? Happy with the quotes? Does your team want to see it? Shall we discuss timing? Each one is another reason to reply "let me come back to you" - which means never. What about a yes/no via WhatsApp? Perhaps not, but make it easy to say yes.

The fast ask has three parts, and only three:

One person, because a link forwarded "to the team" belongs to nobody. One simple link, because a login is a wall, and an attachment is an invitation to edit. "Is it accurate and are you happy?" can be answered in the time it takes to read the story - anything else becomes a meeting.

And a date, because deadlines are kindness. An open-ended request is a burden the advocate carries around; a date is a small task with an ending. Nobody will be offended by "we're planning to publish on the 14th" yet plenty of stories have died of politeness without it.

Remember what the approval moment feels like from the other side. Your advocate lent you their name, their face and their employer's logo, and now they are looking at the result wondering how it reflects on them - internally as much as externally.

So make the story a gift. If the draft makes the advocate look good - if their judgement is the engine of the story (rather than your product) - they will not just approve it; they will chase their own comms team to get it cleared, because they want it published. The advocate that is proud of their story is worth more than any process we can design.

The reverse is also true. A story that reads as an advert with their name attached gets slow-walked, because approving it does nothing for them. Speed, it turns out, is partly an editorial quality. Something to remind product marketing about.

When stakeholder feedback does come, take it all at once. Publicise the deadline and mean it. Then apply the round in one pass.

What kills momentum is the drip: an edit on Tuesday, a colleague's thought on Friday, someone second-guessing the interview the following week, each triggering its own revision, each revision restarting a review. Every round trip costs days and - worse - re-opens decisions already made.

When the yes comes, record it. Who approved, which version, on what date - written down where you can find it in two years, when the advocate has changed jobs and their successor asks why their company is on your website.

This is not bureaucracy; it's the bedrock of customer advocacy. A recorded approval protects the advocate ("this is exactly what I agreed to"), protects you (the compliance answer arrives in one click), and - increasingly - it feeds the machine-readable layer that lets AI assistants treat your story as citable, verified proof rather than marketing copy. An approval that only lives in an email thread does none of that.

If you want to see what a recorded, structured approval looks like as a public standard, that is precisely what Proofpoints publishes with every story - the named advocate, the recorded approval and its date, on a permanent page. The standard is at proofpoints.com/standards. But whatever tool you use, the principle stands: the yes is an event; treat it like one.

Set the terms at the invitation - approval is a promise, not a surprise. Find the quiet veto early, in their building and in yours. Settle your own stakeholders before the customer sees a word. Send a finished page, never a working document. Ask one person one question with one polite date. Write a story the advocate wants published, and they will fight for it internally. Take feedback in a single round. Record the yes as an event. None of this is faster because it cuts corners; it is faster because every step removes a reason to stall.

How long should customer story approval actually take? With a finished page, one named approver and a polite deadline: days. A week is normal; same-day happens more than you would think when the advocate likes the story. If your average is measured in months, the process - not the customer - is where the time is going.

What if the advocate just goes quiet? Silence is rarely refusal; it is usually a task without a deadline. Send one short nudge referencing the date you set, then a second offering to help ("anything blocking this that I can fix?"). If a review link has expired, re-issue it fresh rather than pointing at the old one - a dead link is the perfect excuse to keep procrastinating.

The advocate approved, but their comms team is sitting on it. Now what? This is the week-one question surfacing at week nine. Route everything through your advocate - it's their relationship, and comms teams move faster for a colleague than for a vendor. And next time, ask "who besides you needs to say yes?" at the invitation, and perhaps offer comms the quote list early so they review two hundred words instead of two thousand.

The customer is fine; my own organisation is the bottleneck. What then? Treat your colleagues exactly like the customer: named approvers rather than "the team", a finished page rather than a document, one consolidated round, a date. Separate who must say yes from who is merely informed - most internal reviewers are the second kind and will happily accept a "for visibility" note instead of a veto. Product marketing provides technical capability and product naming feedback only.

Should I let the customer edit the story? Accuracy, always - facts, numbers, titles and quotes are theirs to correct. Style, carefully - it's their story, yet it's your publication and craft, and stories edited by committee converge on boring. The one-round rule keeps this fair: accuracy fixes are non-negotiable, taste debates get one pass, and then you finalise.

Do I need a signature, or is an email fine? Varies by org. Some still want a wet signature in blood. Legally an email usually suffices; e-signature even better: this person, this version, this date, captured by the system that published the story - beats a "fine by me" buried in a thread. The difference shows up two years later, when someone asks you to prove it.

Robin Hamilton is the founder of Proofpoints and writes Proof Positive, a fortnightly publication on the editorial judgement underneath customer storytelling. Twenty-five years in B2B customer advocacy, both sides of the fence, dozens of programs.