What to Post on LinkedIn as a Founder When You Don't Know What to Write

You finally clear an afternoon for marketing after two weeks of building and selling. You open LinkedIn, start a post, delete it, and scroll other founders' feeds for inspiration. An hour later you've published something generic, or nothing at all.

If that sounds familiar, the problem usually isn't creativity or discipline. It's inventory. Every week you collect plenty of post material from sales calls, support questions and build decisions. You just don't capture it anywhere, so each burst of marketing starts from zero.

This guide shows you how to fix that with a running problem bank, a four-post framework for turning each buyer problem into content, and a posting floor you can hold even during a launch.

Why you never know what to post (and what it's costing you)

When you're building the product and selling it yourself, marketing happens in bursts. The plan lives in your head, and the first launch task, bug or sales call pushes it aside. By the time you come back to it, the context is gone and you're facing a blank page again.

The cost adds up in ways that are easy to miss:

• Hours of blank-page time per burst. Most of the session goes to deciding what to say, not writing it.
• A feed that goes quiet for weeks. Prospects who check your profile see a gap, or a post from two months ago.
• Buyers who only hear from you when you're pitching. Without a steady presence, every conversation starts cold, and almost every customer comes from your own outreach.

Here's the reframe: you don't lack ideas. You lack a captured list of them. The best material for founder-led marketing is already showing up in your week, in the exact words your buyers use to describe their problems.

Why the usual fixes don't stick

Most founders have tried at least one of these. Each solves part of the problem and leaves the hardest part in place.

Generic "50 LinkedIn post ideas" lists. They aren't about your buyer. Posts built from them read like everyone else's and attract other founders, not the people you sell to.

Batch-writing marathons. Writing ten posts in a weekend works once. Then the next launch arrives, the queue runs dry, and you're back to bursts.

AI writing tools. They speed up the first draft, but not the decision about what to say. They can also state product claims you'd never make, such as features you don't have or results you can't back up, so review turns into rewriting.

Copying other founders' formats. A borrowed hook without your own point of view gets likes from peers. It rarely gets a DM from a prospect.

What's missing in all four is a source of topics that's specific to your buyers and refills itself as you work.

Start with a problem bank, not a content calendar

A problem bank is a running list of the specific problems buyers describe to you, in their words. It comes before any calendar, because a calendar with nothing meaningful to fill it is just another blank page.

Where to mine it this week

You don't need new research. Look at what already happened in the last seven days:

• Sales and demo calls: what made them take the call? What did they say they were struggling with?
• Onboarding questions: what confused new users, or what did they expect the product to do?
• Support tickets: which problems come up more than once?
• Objections: why did someone hesitate or say "not now"?
• Churn or lost-deal reasons: what did they go back to, and why?
• Your own origin story: what problem made you build this in the first place?

How to capture each entry

Keep it short. For every problem, write down three things:

1. The problem as the buyer said it. Use their words, not your product's vocabulary.
2. Who said it. Their role, not their name ("ops lead at a 20-person agency").
3. What they wanted instead. The outcome they were reaching for.

A spreadsheet, a notes app or a doc pinned to your desktop all work. The format matters less than adding to it every week.

Aim for 10 problems to start. As the next section shows, that's enough for more than a month of posts.

Turn one buyer problem into four posts

Each problem in your bank can carry four distinct posts. Together they move a reader from recognizing the problem to trusting your perspective on it.

Post 1: "I keep hearing this"

State the problem in the buyer's words and explain why it matters. This is the post that makes the right reader stop scrolling and think, "that's me."

Post 2: "Why it happens"

Give your point of view on the root cause. This is where founder credibility comes from. You've spent more time on this problem than almost anyone, so say what you think is really going on.

Post 3: "What doesn't work"

Walk through the common approaches and where they fall short. Draw on what your customers tried before they found you. Be fair. The goal is to show you understand the trade-offs, not to dunk on alternatives.

Post 4: "What we'd do instead"

Offer one practical step the reader can take today, even if they never buy from you. Posts that are useful on their own build the trust that makes a later pitch land.

Worked example (illustrative)

This example is made up to show the framework. It isn't a real customer.

Say you sell scheduling software for independent physical therapy clinics. On a demo call, a clinic owner said: "I spend Sunday nights rebuilding next week's schedule because of no-shows."

• Post 1, "I keep hearing this": "Three clinic owners told me this month they lose their Sunday nights to rebuilding the schedule. One called it 'the second job nobody pays me for.' Here's what that time actually costs a small practice."
• Post 2, "Why it happens": "No-shows aren't really a patient problem. They're a timing problem. Reminders go out too early or not at all, and the waitlist lives in a notebook, so open slots never get filled in time."
• Post 3, "What doesn't work": "The usual fixes are charging no-show fees, double-booking and calling patients the day before. Each one helps a little and creates a new problem: angry patients, overloaded therapists or a front desk stuck on the phone."
• Post 4, "What we'd do instead": "One change you can make this week: keep a short list of patients who said they'd take a last-minute slot, and text them the moment a cancellation comes in. You'll fill more gaps than any reminder schedule will."

One problem, four posts, and not a single blank-page moment. Multiply that across 10 problems and you have 40 posts' worth of direction.

Set a posting floor you can hold during a launch

How often should founders post on LinkedIn? Recent commentary points away from a magic number and toward a reliable minimum.

According to a 2026 roundup on futuretweets.com covering research from Buffer, Quid and quso.ai, consistency (a reliable cadence) is now the minimum standard, while extra volume helps more on some channels and audiences than others. In other words, showing up predictably matters before showing up often.

Symaxx makes a similar case: base your rhythm on real capacity, including research, production, approvals, publishing and responding to comments, rather than a generic posting frequency. Its example of a minimum rhythm is two strong posts a week, kept up for a 90-day test.

For a solo founder, the practical move is to set a posting floor:

• Pick a number you could hit in the busiest week of the quarter, not the quietest. For most solo founders, that's one or two posts a week.
• Treat it as a floor, not a target. In a quiet week, post more. In a launch week, hit the floor and stop.
• Commit for 90 days before judging results.

It also helps to know why cadence breaks. Captivation Agency argues that content inconsistency usually comes from reactive, deadline-driven workflows rather than a lack of care. That matches the solo-founder experience: you care about marketing, but it loses every fight with an urgent task. Fixing the system, so the next post is already decided, matters more than willpower.

Make it a 15-minute weekly routine

The problem bank only works if you keep feeding it. Here's a routine that fits on a Monday morning:

1. Add new problems (5 minutes). Skim last week's call notes, tickets and emails. Add any new problem in the buyer's words.
2. Pick the next post (1 minute). Choose the next problem and the next post type in its sequence. No blank-page decision needed.
3. Draft and check claims (about 10 minutes). Write the post, then check every statement about your product against what you'd actually stand behind. If you wouldn't say it on a sales call, cut it.
4. Track buyer responses. Note which problems get replies or DMs from actual prospects, not just likes. Move those problems to the top of the bank and write more around them.

Over a few weeks, step four teaches you which problems your market cares about most. That sharpens your posts and your sales conversations.

When the list should start running itself

Once the routine works, the next bottleneck is keeping the bank and the calendar updated during the weeks you're heads-down on a launch or a big deal. That's exactly when the habit tends to slip.

This is where problem-led content planning tools can take over the upkeep. Kleos, for example, plans a rolling 30-day calendar around your buyers' problems and drafts LinkedIn posts checked against your confirmed product facts and ruled-out claims. Nothing is published without your approval, so your part becomes a quick review instead of a writing session.

Whether you run it by hand or with help, the outcome to aim for is the same: a steady presence on LinkedIn and a clear next post, so marketing takes minutes of approval instead of hours of staring at a blank screen.

Your next step

This week, open your last five sales or demo call notes and write down 10 buyer problems in their own words. Pick the one you heard most often and draft all four posts using the framework above. That gives you a month of posts at a one-a-week floor.

When you're ready to keep that list full without the Monday upkeep, see how a calendar planned around your buyers' problems works.