Marketing How-To Guides · Execution Snippet
How to show expertise instead of claiming it
A buyer has no way to check a claim of expertise, so they stop trying. Show one thing the firm noticed that a smart stranger couldn’t have looked up, and the claim stops being necessary.
Demonstrating Expertise Without Claiming It
Gates. Relevance: no. Credibility: secondary. Proof: primary. Safety: no. Access: no.
The symptom
The firm publishes. Constantly.
A weekly post, a quarterly outlook, a regulatory alert out the door within two days of anything changing. The material is accurate. Partners review it before it goes. This has been running for three years.
No prospect has ever mentioned a word of it.
Not in a first meeting, not in a pitch, not in the stretch of a call where somebody usually says something polite about the newsletter. The analytics look fine. Opens, reads, the occasional share from a person who already works there. And when a buyer explains how the firm made the shortlist, the reason is always something else. A referral. A name somebody recognized.
Which leaves a question the content calendar was never built to answer. If three years of published expertise didn’t move a single decision, what was being published?
Why it keeps happening
Because asserting expertise costs an afternoon and demonstrating it costs a partner.
A credentials list, a client logo wall, and the phrase deep experience can be assembled between lunch and the end of the day by someone who has never done the work. Showing the reasoning is a different transaction. It takes a partner’s time, the expensive kind, and it puts a judgment on the record that a client or a competitor might disagree with in public.
So firms publish the cheap version and file it under thought leadership.
We’ve written that copy. Every firm says it’s a trusted advisor with decades of experience and a client-first approach, and we’ve written a version of that line more times than we want to admit, and it never once helped a buyer choose. It arrives as a claim, and a claim about expertise is the one claim nobody can check without hiring you first.
The calendar finishes the job. What fills a publishing schedule reliably is whatever can be produced without interrupting billable work. Publish on a logic and somebody has to decide what’s worth saying. Publish on a calendar and Thursday decides.
What the buyer is doing at the Proof gate
Reading for something that couldn’t have been written by a person who hasn’t done the work.
Faking that was always possible and it’s now free. Any capable generalist can produce an article that sounds like three decades in an industry, in a few minutes, and buyers worked this out faster than firms did. A line from an earlier piece in this series holds up: AI makes experts faster. It makes novices louder. The appearance of expertise stopped working as evidence the moment the appearance went to zero.
What survives the collapse is the noticing. The observation that only shows up after a hundred reps. The configuration that precedes trouble. The question nobody expects. Same documents. Same data. Same lens. The pattern library is what thinks the different thought. Knowledge describes the ceiling; expertise knows what you see and feel standing under it.
Retrieval is the other half of it. Generic output trains the machines to see you as generic. A firm publishing at the median of its category has taught every system that indexes it to file the firm there, and buyers arrive with a shortlist somebody else assembled.
Accuracy is available everywhere now, on demand and at no cost. It settles nothing at this gate.
The correction
Publish the patterns the firm paid to learn.
They were bought with reps: hundreds of engagements, real feedback, and the occasional expensive mistake that permanently rearranged how a partner reads a balance sheet. Expertise is what happens when the information runs out. No model has any of it, because the reps happened inside the firm and nobody wrote them down.
Start with three sitting in your partners’ heads right now.
The line item read first. An experienced partner opens a new client’s file at the same place every time, and it’s rarely the place the client expects. Publish which line, and what it usually means when it looks wrong. That one piece does more than a case study, because the buyer reading it recognizes their own file.
The configuration that makes a partner uneasy before anyone else has flagged anything. A staffing pattern. A customer concentration that’s been drifting for two years. A sequence of approvals that keeps landing with the same person... Name the setup and what it tends to precede. Least likely thing in the firm to get published, because it’s a prediction and predictions can be wrong.
The question asked in a first meeting that nobody expects. Publish the question and why you ask it. It’s hearing a client describe a problem and recognizing the problem they did not describe.
Then rebuild one existing piece to that standard. One. Take the best-performing thing on the site and cut every sentence a smart stranger could have looked up. If they could have found it, it’s assembly, and assembly is free now. What’s left after the cut is the piece, and it’ll be the first thing a prospect ever quotes back to you.
Before and after
Before. Our team brings deep experience serving mid-market manufacturers, combining decades of sector expertise with a client-first approach.
After. The first thing we read in a manufacturer’s file is the freight line. When freight per unit stops moving with volume, two plants are usually quoting the same lane separately and nobody owns the total. It gets reported as a logistics problem, which is how it survives budget review after budget review.
The hard call
Publishing the pattern means handing over the thing the firm charges for, and putting a partner’s judgment somewhere people can argue with it.
The first worry doesn’t survive contact with how buyers behave. A reader who recognizes their own file hasn’t stopped needing the firm. They’ve discovered the firm can see something they couldn’t name, and value given freely, no invoice attached, is the one proof of intent and competence a skeptic can’t argue with.
The second is real and worth paying for. Judgments can be wrong, and the partner whose name is on one will hear about it. That exposure is the signal. Claims are safe because nobody can check them.
Run this on your own material
Pull last quarter’s published work. All of it. Posts, alerts, the outlook, the piece somebody ghostwrote for a partner who never read it.
Two piles. Things a smart stranger could have looked up. Things only this firm could have noticed, because someone here sat through the reps that produced them.
Sort honestly. A summary of a rule change goes in the first pile even when the summary is excellent. An explanation of which of your clients that change will hurt first, and what they should do about it, goes in the second.
If the first pile wins, your firm is competing with the machine at the machine’s game and paying partner time for the privilege.
Do the sort before next quarter’s calendar gets approved. Once it’s approved, you’ll fill it.
Signals you’ve cleared it
Advance when a prospect repeats your own observation back to you in a first meeting, usually slightly wrong and with more confidence than you had. When a piece gets forwarded inside a company to someone who’s never heard of the firm. When a competitor’s material starts sounding like yours, which is irritating and is also the clearest evidence available that the pattern was real.
Hold when the response to a published piece is agreement with no specifics. Nice piece means it read well and gave the reader nothing to use. Hold when the partners can’t point to one sentence a competitor would refuse to sign, because anything every firm in the category could have published has already been read somewhere else. And hold when the work keeps going out on schedule and nobody can say what the last one argued.
Where this connects
Engagement Success in an AI World · When Everyone Stopped Reading, on the collapse in the cost of sounding expert.
Research Library · Entry 18, expertise, pattern recognition and judgment.
Next move · Go to How to write a case study.