Stop Complaining You Have Nothing to Post: Your Client Work Already Wrote Itself

The Hierarchy of Publishable Material

Not everything from a client engagement is safe to publish, and not everything safe is worth publishing. Start with what ranks highest:

1. Patterns, not projects: the mistake you now see in the majority of your engagements. "Half the audit findings we see trace back to one provider onboarding step" names no one and helps everyone.
2. Decision frameworks: the criteria you actually applied when a client chose between two architectures or two vendors. The interactions matter more than the outcome, and no client identity survives in a decision tree.
3. Quantified asymmetries: range statistics with the origin scrubbed: "In the last twenty assessments, review-response time ranged from two days to four months."
4. Your own process errors: what you got wrong in an engagement early on and now do differently. Self-criticism is untouchable legally and earns more trust than any polished case study.
5. Non-client evidence: live teardowns of failed startups, publicized breaches, new regulation. Confidentiality is never even in question.

Base your weekly calendar two parts pattern or decision content to one part external commentary, and you will never run short again.

The Three-Part Anonymisation Test

Before a draft goes out, it must clear three tests. Test one: de-identification. Remove company names, logos, industries small enough to triangulate on two details, headcount with location, and named individuals in quotes. A "20-person fintech in Singapore" described after a public breach may as well carry the name; collapse it to "a regulated fintech".

Test two: consent. Where a story depends on a named or obviously identifiable client, get written permission first. Most clients agree readily for good news; almost none want to be the anonymised disaster story, and you should grant them that right without resentment.

Test three: the colleague test. Show the draft to someone outside your industry. If they can guess the client from details you considered innocuous, revise it. If they cannot, and can still understand the lesson, you are clear.

Then there is the contract layer: reread your standard engagement agreement for publicity and non-disclosure clauses before publishing anything tied to real work, and when in doubt, take the pattern-only route. Patterns never breach; atoms of real projects sometimes do.

The Repurposing Workflow That Runs Weekly

Turning client work into content needs a workflow, otherwise founder energy runs out by week three. The system I coach: capture during and immediately after client work, while detail is fresh.

1. Capture: after each engagement closes its major milestone, spend ten minutes writing a private note: what surprised the client, what broke, what you advised, what refused to work.
2. Convert: once a week, pick one private note and decide its publishable layer: pattern, framework, or self-critique. Anonymise, apply the three tests, and build a post in the standard shape: hook, story, lesson, forward step.
3. Broadcast it in layers: one long post, a comment teaser, and optionally a carousel where the steps suit visual layout. Same material, three touchpoints.
4. Archive and reuse: your published posts are themselves a library: republish updated versions of a strong post from six months before with new evidence. Content on LinkedIn ages fast enough that a refreshed post reads as new to all but your most devoted readers.

Ten minutes per engagement plus one weekly conversion session generates three publishable posts, indefinitely, from work you are already paid to do.

Running capture-to-publish discipline alongside a full client load is exactly what founders hand to us: the done-for-you service conducts the anonymisation, drafts every post, and runs a weekly call that pulls the raw material out of your head in fifteen minutes, all on a flat monthly subscription. Book a 15-minute call or see how the done-for-you system works.