Founders and posting: how to show up without losing your deep work
A practical system for founders who want to post regularly without breaking their focus: batch the writing, capture ideas, and keep a weekly rhythm.
Founders hear the same advice again and again: be visible, share what you are learning, build in public. It is decent advice. It also lands on people who are already stretched across product, customers, hiring and everything else that needs a decision today.
The usual result is an all-or-nothing pattern. You post five times in a week, get busy, disappear for a month, feel guilty, and start again. The posts are written in a hurry, and the context switching eats the deep work that actually moves the company forward.
This guide describes a calmer approach. It does not need a lot of time. It needs a little structure.
Why posting feels so expensive
Writing a post is not hard. The cost is the interruption. A founder who stops mid-task to write something clever for LinkedIn pays twice: once for the writing, and again for the twenty minutes it takes to get back into the original problem.
Two other things make it worse:
- Deciding what to write. Staring at an empty box and asking “what should I say?” is slow and stressful.
- Deciding whether it is good enough. Without a rule for when something is ready, posts sit in drafts for days.
You can fix all three problems by moving the decisions out of the moment. That is what the system below does.
Part one: capture ideas as they happen
Good post ideas rarely show up when you sit down to write. They turn up after a customer call, during a code review, in the shower, or while reading something annoying. If you do not catch them, they vanish.
Keep one place for ideas and make it effortless to add to. A notes app, a text file or your phone’s voice memo will do. The rule is simple: capture in under ten seconds, do not polish.
A useful idea is rarely more than a line:
- “Customer asked why we don’t offer annual billing, and the real answer was interesting.”
- “Mistake: shipped the feature before talking to three users.”
- “What I wish I knew before hiring the first person.”
Include a line about why it stuck with you. That reminder is often what turns a flat note into a real post later.
Part two: batch the writing
Once ideas pile up, write them in one sitting instead of scattered through the week. Batching works because you stay in one mode of thinking, so the cost of switching is paid once.
A simple batch looks like this:
- Pick a fixed slot. Forty-five to sixty minutes, same day each week. Many founders choose a low-energy moment, such as Friday afternoon, because writing a first draft needs less focus than building does.
- Choose three to five ideas from your list.
- Write a rough draft for each. Do not edit as you go. Get the point down, then move on.
- Do one edit pass for each, reading it aloud and trimming anything that sounds like a press release.
- Put each one in a calendar slot for the coming week.
Three solid posts a week is a perfectly good target for most founders. If that feels like too much, start with one. A post a week that you never skip beats five a week that you drop after a month.
Part three: keep a weekly rhythm
A rhythm turns posting from a decision into a default. A simple version looks like this:
- Monday (10 minutes): pick next week’s ideas from your list.
- Wednesday (15 minutes): post, then reply to comments.
- Friday (45 minutes): batch-write the next set of posts.
- Daily (10 to 15 minutes): two or three thoughtful comments on other people’s posts.
Your numbers will differ. The point is that each task has a home, so you stop deciding each morning whether to post.
Replying matters as much as posting. Founders often find that a few good comments on the right people’s posts do more for their visibility than a rushed post of their own. Our article on thoughtful comments goes deeper on that.
Protect the deep work
A system for posting should not eat the thing it is supposed to support. A few guardrails help:
- Keep notifications off during focus blocks. Check LinkedIn and X at set times, not whenever they ping.
- Never post during your best hours. Whatever time of day you think most clearly, spend it building.
- Set a timer on commenting. Ten minutes goes quickly; without a limit it can become an hour.
- Decide your “good enough” rule ahead of time. For example: it says one useful thing, it sounds like me, and the first lines make sense on their own. If so, it ships.
What to write about
Founders often worry they have nothing worth sharing. You almost certainly do. Look at the work you did this week and ask:
- What did I get wrong, and what did I change?
- What question did a customer ask that I had to think about?
- What decision did I make, and what were the trade-offs?
- What would I tell my past self from a year ago?
Specific and honest beats polished and vague. A post about a small mistake and what it taught you usually lands better than a grand statement about the future of your industry.
Where Reply Monk can help
Reply Monk is built around this kind of rhythm. Ideas can be captured as you think of them, and fresh ideas arrive each Monday. The composer gives you a first draft in your own voice to edit, rather than a blank page. The calendar holds your posting slots and sends a reminder when it is time to post, so you do not have to remember. You still review and post everything yourself. If you would rather start on paper, the free weekly LinkedIn planner gives you a page to fill in.
A one-week starter plan
If you want to try this without overthinking it:
- Today: create your ideas list and add five things from the last two weeks.
- This Friday: block 45 minutes and write two rough posts.
- Next Monday and Wednesday: schedule them, post them, reply to anyone who comments.
- Next Friday: write two more.
- After a month, look at what people responded to and write more of that.
The goal is not to become a full-time content creator. It is to be a founder who is visible enough that the right customers, hires and partners can find you, while the real work still gets done.