OperatorRadar
DiscoverAI ToolsAI AgentsInsights
Submit a ToolFind My Solution
OperatorRadar

Find the tools, systems, and ideas that move your business forward. Timeless business thinking, rebuilt for the AI era.

Discover

  • Discover
  • AI Tools
  • AI Agents
  • Software
  • Agencies
  • Categories

Decide

  • Decision Guides
  • Compare
  • Find My Solution
  • Insights

Execute

  • Prompts
  • Workflows
  • Submit a Tool
  • Contact

Company

  • About
  • Privacy
  • Terms

© 2026 OperatorRadar. All rights reserved.

Built by Ekofi

  1. Home
  2. Prompts
  3. Turn Operator Insight Into LinkedIn Post
Featured
beginner
Claude or ChatGPT (verify current model choice)
v1.0.0

Turn Operator Insight Into LinkedIn Post

Turn a specific operator lesson into a LinkedIn post that builds credibility. No generic advice, no hype—just the pattern you noticed and why it matters.

Full prompt

You are a SaaS operator writing for other founders and operators on LinkedIn.

Convert this business observation into a credible, non-generic LinkedIn post:

Observation: {{observation}}
Context (what led to this): {{context}}
Who should care: {{audience}}
The mistake or pattern: {{mistake_or_pattern}}
What you'd do differently: {{lesson}}

Write a post that:
1. Opens with a sharp, quotable line (the kind that works as a subtitle).
2. Describes the specific situation—not a generic principle.
3. Names the pattern or failure mode clearly.
4. Offers one concrete takeaway (not five tips).
5. Ends with a question or reflection, not a link or sign-up.
6. Avoids: motivational language, "here's what I learned," buzzwords, emoji overload.
7. Stays 150–280 words.

Post:

How to use

1. Spend 5 minutes writing down a real mistake or insight from this week—something specific enough that you'd tell a founder over coffee. 2. Fill in the five placeholders: what you observed, the context, who needs to know, the pattern, and your lesson. 3. Run the prompt. 4. Edit for your voice—the output is a draft, not gospel. 5. Post on LinkedIn. Track engagement; operators engage more with specific failure modes than with wins.

Example input

Observation: We hired a VP Sales who looked great on paper but failed because we didn't have a sales process to hand them.
Context: We were doing $2M ARR, all inbound, no formal sales ops. We thought a senior hire would build it. They quit after 4 months.
Who should care: Founders scaling from product-led to sales-led.
The mistake: Hiring for a role that doesn't exist yet.
What you'd do differently: Build the process first, then hire the person to scale it.

Example output

Hiring a VP Sales before you have a sales process is like hiring a chef before you have a kitchen.

We did this at $2M ARR. We'd been all inbound, no structure. We thought a strong operator could build the sales machine from scratch. They couldn't. Not because they weren't good—because there was nothing to scale.

They left after 4 months. We spent 6 months after that doing the work they were supposed to do: defining our ICP, building a qualification framework, setting up a pipeline. Then we hired someone junior who could actually execute.

The pattern: Founders often hire for the role they wish they had, not the role they need right now.

If you're moving from product-led to sales-led, don't hire the VP yet. Hire a sales coordinator or junior AE. Run the process yourself for a quarter. Document what works. Then bring in the senior person to scale what you've already proven.

The senior hire isn't the first step. They're the second.

What's a hire you made too early?

Customization tips

  • Replace {{observation}} with something that cost you money or time—not a theoretical problem. Specificity is what stops the scroll.
  • Make {{mistake_or_pattern}} the centerpiece. Operators bond over shared failures, not shared wins. Name it clearly: 'Hiring for a role that doesn't exist yet' beats 'scaling challenges.'
  • End with a genuine question ({{lesson}} as a reflection), not a CTA. 'What's a hire you made too early?' invites comment. 'Sign up for my course' invites mute.
  • Keep {{context}} to one sentence. The situation, not the backstory. Founders have 6 seconds.
  • Avoid softening language: 'I learned,' 'I realized,' 'it turns out.' Start with the sharp line. Let the story prove the lesson.