Founder LinkedIn Post: Why Niching Early Wins

Prompt v2.0

Founder LinkedIn Post: Why Niching Early Wins

founder contentlinkedin postnichingpromptstartup strategythought leadership
ChatGPTClaudeGemini⚠ Human review requiredπŸ“ Needs project context
Health 100/100 β–² 9 πŸ“‹ 58 copies

Trigger Phrase

Use prompt: Founder LinkedIn Post: Why Niching Early Wins

Prompt

169 words
ROLE:
You are a founder-operator writer creating LinkedIn posts that feel direct, practical, and experience-led.

GOAL:
Write a LinkedIn post explaining why early-stage founders should niche down earlier than they think.

INPUT:
Topic and core lesson: [WHAT THE POST SHOULD ARGUE]
Audience: [WHO THE POST IS FOR]
Optional proof or CTA: [EXAMPLE, STORY, OR CLOSING QUESTION]

CONTEXT:
This should read like a smart founder sharing a hard-earned lesson, not a generic content creator posting advice.

TASKS:
1. Write a strong opening hook.
2. Explain why niching improves clarity, messaging, and growth speed.
3. Include one practical example, contrast, or consequence of staying too broad.
4. End with a simple, low-pressure CTA suited to LinkedIn.

CONSTRAINTS:
- Do not invent missing inputs.
- Keep the post under 2,900 characters.
- Use short paragraphs.
- Avoid hashtags unless the user asks.
- Avoid clichΓ©s, guru language, and motivational waffle.

OUTPUT FORMAT:
- Hook
- Main post
- Closing CTA

IMPORTANT:
Wait for user data before starting. Write in British English. Prioritise practical insight over inspiration.

Before & After

❌ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

βœ… With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Copy the prompt text. Paste into ChatGPT, Claude, Gemini, or any AI chat. Fill in bracketed placeholders with your details. Run and review output.

Test It

Test command:
Trigger with: 'Test the Founder LinkedIn Post: Why Niching Early Wins with this input: [provide a short real example]'. Confirm output is specific, structured, and useful.
Expected output:
Most founders stay too broad for too long. A wide market sounds safer, but it usually weakens the message. The earlier you narrow the buyer and problem, the faster people understand why you matter.
Pass criteria:
  • Output is specific to the input provided β€” not generic. Output follows the stated format and length. No invented statistics, facts, prices, or dates. Placeholders are not left unfilled.

⚠️ Guardrails

  • Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result β€” ask for clarification.

πŸ“ Context File Tip

Career Brief context file

⚠️ Common Failure Modes

  • May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.

πŸ”§ Fix Prompt

Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.

πŸŽ› Available Modes

Quick Detailed Critic Final

πŸ”Œ Compatibility & Requirements

βœ… Works offline
πŸ“ Needs project context
πŸ‘€ Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools: No external tools required

πŸ“‹ Upgrade Notes

Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.

πŸ’‘ Suggest an improvement

Install Wizard

Choose your platform to get step-by-step install instructions: