Skip to main content
Paul Welty, PhD AI, WORK, AND STAYING HUMAN

· Paul Welty · resources

Content ideas for consultants: how to generate thought leadership from what you already know

Consultants don't lack expertise. They lack a system for surfacing what they already know. Six sources, a capture habit, and a filter for the noise.

The blank page in front of a consultant is a strange thing. You’ve spent fifteen years untangling problems that the people writing think pieces about your industry have never seen up close. You can sketch the structure of a typical engagement on a napkin in under a minute. And yet, when it’s time to write a 700-word LinkedIn post under your own name, you stare at the cursor and decide you have nothing to say.

The well is not empty. The bucket is missing.

The advice consultants get for “content ideation” usually misses this. It assumes you’re producing for a brand whose product you’re paid to promote, or that you’re a creator whose subject is themselves. Neither describes a consultant. So you get prompts and trend-spotting and listicle templates, the kind of scaffolding that helps a copywriter producing for a brand they don’t work in. You don’t need that. You need a way to notice that something you said offhand on a Tuesday call was, in fact, the article.

Below: six sources, a capture habit, a filter — content ideas for consultants drawn from the actual work, not from prompts or trend-spotting. Not theoretical. These are the moves I’ve seen consultants who publish consistently actually make, and the ones who go quiet for six months tend to be the ones who never built any of them.

Why generic ideation advice fails consultants

Most “how to come up with content ideas” guides assume one of two things: that you’re filling a content calendar for a brand, or that you’re a creator whose subject is themselves. Neither describes a consultant. Real content ideas for consultants come from the practice itself — the calls, the engagements, the things you say out loud when nobody’s filming.

A consultant’s audience is narrow on purpose. The CFO who’d hire you to fix a finance function doesn’t care about top-ten productivity hacks. They care about whether the post you wrote shows you understand the difference between a controller who can close the books and one who can’t. The CMO of a Series B doesn’t want a generic positioning framework. She wants to read someone who’s clearly sat in the chair.

That specificity is your edge, and it’s also why the prompt “what’s trending in your space?” doesn’t help. You aren’t chasing a feed. The job is to make legible something you already know.

The shift to make is small but important: stop asking what should I write about? and start asking what did I just learn, say, or argue about that’s worth a stranger reading? The sources below are different angles on that second question.

Six sources for ideas you already have

1. The objection you handled this week

Every engagement involves a client pushing back on something: a recommendation, a finding, a way of working. Whatever you said in response, in real time, with a real consequence riding on it, is an article.

The reason this works is that an objection is the question in your reader’s head, already tested against an actual stakeholder. You can’t pre-empt resistance better than by writing through resistance you’ve just survived.

Example shape: “This week a client asked me why we couldn’t just do X. Here’s the longer answer I didn’t have time to give.” That’s a post. Sometimes it’s a thread. Occasionally it’s a five-thousand-word essay.

The discipline is to capture the objection within twenty-four hours, while you can still hear the exact phrasing. After a week it dissolves into “we discussed pricing” and the specificity is gone.

2. The question you keep answering on calls

If you’re billable, you’re talking. And if you’re talking to enough prospects and clients, certain questions repeat.

Not the FAQ-page kind. The second-meeting kind. The “how do you actually decide when to…” question. The “we tried this and it didn’t work, what are we missing” question. The one you find yourself answering at minute thirty-four of every discovery call.

That repetition is the signal. The market is telling you what it does not understand and where your read on it is non-obvious. You don’t have to invent the angle; the call schedule has done it for you.

A practical move: at the end of each week, list the three questions you answered most often and write a single paragraph for each. Eighty percent of them won’t become anything. Twenty percent will, and that twenty percent is high-conversion content because the question is already validated.

3. The thing you’d say if you were less polite

There are takes you have about your industry that you trim before they leave your mouth. Sometimes for good reason: the client is in the room, the partner you’d alienate is in the room, or you simply don’t want to be the person who picks fights at conferences.

A softened-down version of those takes is often publishable. A take you’ve held back has friction in it, by definition, which means it distinguishes you from people who only ever say the safe thing.

The test is simple. If your post could have been written by ChatGPT in 2023, it isn’t a take. If it could only have been written by someone who’s been in the room you’ve been in, it is.

The risk is overshooting into edgelord territory. The fix is to argue the position and not insult the people who hold the opposite one. “Most of our industry treats X as best practice, and I think we’re wrong about it” is a post. “Anyone still doing X is an idiot” is a tantrum.

4. The framework you’ve quietly built

Every consultant who’s been at it more than a few years has built private tooling. A scoring rubric for whether a deal is worth pursuing. A two-by-two for which clients to fire. A checklist you run before every kickoff. A diagnostic question you ask in minute three of every first call.

These are gold, and most consultants underestimate how much, because they assume everyone has the same tools. They don’t. Yours is sharper than the version your reader has, partly because you built it for your specific niche and partly because you’ve used it three hundred times.

Publishing one of these is a tradeoff: you’re giving away IP that’s earned its keep. Some of it shouldn’t be public. The lightweight versions, the diagnostic question, the kickoff checklist, almost always should be, because the people who need them the most are exactly the people who’ll think whoever made this knows what they’re doing and remember your name when their procurement team asks for a shortlist.

5. The article that made you mutter

You read something this week and had a reaction. Not just “interesting.” An actual reaction. Disagreement, partial agreement, agreement-with-an-important-caveat, frustration that the author missed the obvious follow-up question.

That reaction is content. The structure is straightforward: name what you read, name the part you reacted to, give your read. You aren’t writing a takedown. You’re extending the conversation in public, the way you’d extend it in a Slack channel with a colleague you respect.

This is the easiest source to underuse. Most consultants read constantly and let the reactions die in their browser tabs. A simple capture rule, if I had a reaction strong enough to talk about it at dinner, I write a paragraph before closing the tab, turns a habit you already have into a steady supply of posts.

6. The pattern across your last five engagements

Step back from any single client and look at five in a row. There’s almost always something: a problem you keep getting hired to solve, a misunderstanding that keeps recurring, a fix that keeps working when nothing else does.

That cross-engagement pattern is the most defensible content you have, because no one else has access to it. A competitor can read the same books. A creator can have the same opinions. Only you have your client portfolio.

The form is usually a longer piece, eight hundred to two thousand words, because the value is in the specifics: “In each of the last five engagements, the founder told me X, and in four of them, the actual problem turned out to be Y.” That’s an article that buys credibility for a year.

The privacy bar is real. Anonymize, generalize, ask permission for anything that could identify a client. The pattern itself, abstracted, is yours to publish.

The capture habit

None of the six sources above produces content unless you write things down when they happen. The single biggest reason consultants don’t publish is not lack of ideas. It’s that the idea was alive at 4pm on Tuesday and dead by Wednesday morning because nothing was captured.

The capture mechanism doesn’t have to be sophisticated. A note app open on your phone. A running doc titled Ideas that you append to without editing. A weekly Friday-afternoon habit of writing five lines about what happened in client work this week. I know one fractional COO who keeps a Moleskine in his glove compartment because most of his ideas show up on the drive home from the client’s office, and he’s lost too many of them to the parking lot.

The rule that matters is to capture the specific phrasing. “Pricing came up again” is useless next week. “The CMO asked why we couldn’t just hire a junior to do this and we ended up talking about why volume isn’t the problem” is the seed of a real post six months later.

This is also the workflow Authexis is built around: voice memo or quick note in, structured idea queue out, drafts written in your voice from what you actually captured. The capture habit is what turns the idea-generation problem from coming up with things to write into picking which of the things you already noticed to write about first. The tool is honest about its role. It doesn’t invent your ideas. It surfaces and structures the ones you’ve already had.

The filter: what to skip

Capture wide. Publish narrow. Not every captured idea deserves to ship.

Three filters worth applying.

  1. Specificity test. Could this only have been written by someone who’s done your work? If yes, ship it. If a generalist could have written it from a Wikipedia page, skip it.
  2. Stakes test. Is there anything at stake in the post: a position, a recommendation, a critique? Posts with no stakes read as content marketing, even when they aren’t. They’re the LinkedIn equivalent of small talk.
  3. Readers-you-want test. Will the post be useful to the kind of buyer you actually want? A piece that goes viral with the wrong audience can crowd out the right one. Better to write narrower for the people who’d hire you.

The combination of those three filters tends to cut a captured pile down by half, which is the right ratio. The other half is what you publish.

What this looks like in a working week

A consultant who’s actually doing this isn’t grinding through ideation sessions. They’re noticing on Tuesday, capturing on Tuesday, writing on Friday from the four or five things they noticed that week, and shipping on Monday. The whole thing takes a few hours, not a strategy off-site.

The people who say they have nothing to write about are almost never empty. They’re un-captured and un-filtered. Once either is fixed, the well is bottomless, because the well isn’t ideas. It’s the work itself, and the work doesn’t stop.

If you’d like a tool that runs the capture-and-structure side for you in your voice, start your free trial. If you’d rather see how the workflow stacks up against the AI tool you already use, Authexis vs ChatGPT is the comparison.

Why customer tools are organized wrong

This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.

Infrastructure shapes thought

The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.

Server-side dashboard architecture: Why moving data fetching off the browser changes everything

How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.

The work of being available now

A book on AI, judgment, and staying human at work.

The practice of work in progress

Practical essays on how work actually gets done.

The room thinks aloud

Over 48 hours, four bots in the fleet co-developed a methodology rule about variance — without anyone asking them to — and the newest one applied it to a routing decision before he'd ever met the original conversation.

The room caught up to the CEO

A fleet-wide positioning pivot that landed in forty minutes because three of Paul's essays had already done the work.

AI as staff, not software

Two frames for what AI is doing to work. The tool frame makes tools smarter. The staff frame makes roles unnecessary. Those aren't the same product, the same company, or the same industry.

I built a content tool that starts from your voice, not a prompt

Every AI content tool starts from a prompt. Authexis starts from your voice — literally. Here's what I learned about the gap between generating content and creating content that sounds like you.

Work log synthesis: February 27, 2026

Cross-project synthesis for February 27, 2026

Work log synthesis: February 26, 2026

Cross-project synthesis for February 26, 2026