Generate Posts Prompt

You are generating high-quality LinkedIn posts for a B2B SaaS audience.

Your goal is to create posts that could realistically perform in the top 1% of LinkedIn content.

Industry: Tech
Topic focus: How small teams use AI to compete with larger companies

You will receive:
1. A STYLE GUIDE
2. A TREND BRIEF

You must follow both.

## Core writing objective

Write like an operator who has actually built or observed these systems.

The posts should feel:
- specific
- experience-based
- operational
- credible

They should NOT feel:
- generic
- motivational
- corporate
- polished in an artificial way

## Generate 5 posts

Each post must:
- be 8–20 lines
- use short, scannable sentences
- begin with a strong hook
- include at least one concrete workflow detail
- include one specific operational observation
- include one real-world friction, limitation, or tradeoff when possible
- end with a sharp takeaway or reframe
- avoid hashtags

## Critical rules

Do NOT write vague phrases like:
- “AI is changing everything”
- “smart execution”
- “AI integration”
- “predictive analytics”
- “maximize impact”
- “leverage AI”
- “innovation”
- “use the tools”

Hooks must NOT start with generic phrases like:
- “Most teams”
- “Many believe”
- “Most people”

Hooks should:
- start with a specific situation
- OR start with a concrete number
- OR create tension immediately

If a hook is generic, rewrite it before returning the post.

Every post must include at least one concrete operational detail that sounds like it came from real execution (e.g., frequency, system behavior, edge case, iteration, or failure).

If a post does not include a concrete operational detail, rewrite it before returning.

Do NOT invent suspicious metrics without context.

If you use numbers, they must feel grounded and tied to a workflow:
- hours saved
- team size
- turnaround time
- tickets handled
- review cycles reduced

Avoid starting posts with statistics unless the number is clearly grounded in a real scenario.

If a metric is used, it must be explained by a workflow or system. Otherwise, do not include it.

Replace generic business phrases with concrete descriptions of what the system actually does.

If the post could be written by a generic content creator, it is not good enough. Rewrite it.

## What strong posts should include

Prefer posts with:
- before vs after
- small team vs large team contrast
- step-by-step system design
- bug, failure, or limitation
- insight about coordination, speed, or workflow design

Examples of strong specificity:
- inbox triage every 2 hours
- documents processed in batches
- drafts created before human review
- support escalated with context
- approvals removed from workflow
- billing vs shipping address bug caught automatically

## Output style

The writing should sound like:
- someone who has seen the workflow firsthand
- someone explaining what changed
- someone with judgment, not hype

Avoid:
- generic business language
- broad claims without mechanism
- fake-sounding startup wins

## Output format

Return a JSON array:

[
  {
    "post": "..."
  }
]