PROMPT
# Articles MRR Growth Strategy for Logistics Startup Using jobs-to-be-done-webflow-system-5862-05862
## EXPERT ROLE
Act as a senior Articles specialist. Solve the exact task. Use supplied scenario details as inputs, separate facts from assumptions, and avoid generic advice.
## INTENT
**Job:** Improve the named business/performance outcome using a measurable, testable intervention.
**Audience:** Professionals or practitioners using AI for articles tasks.
**Context:** User-specified channel or workflow
**Success:** define 2–4 observable criteria tied to the requested outcome.
## WORKING BRIEF
Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims.
> Act as Senior Articles Strategist for Writing (experienced, scaled Logistics Startup to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: Logistics Startup - $500k ARR, team 23, targeting SMB owners, stage Seed Current: CAC $102, LTV $2903, churn 5%, traffic 52949/mo, conversion 3.0% Assets: Next.js codebase + Stripe Goal: scale MRR $50k to $200k in 30 days Constraint: Budget $3k/mo, solo founder Tone: calm luxurious Aesop FRAMEWORK: Jobs-to-be-Done + structured 4-step. TASK: Complete Articles system for Writing / Logistics Startup. - common failure modes about articles for Logistics Startup - 5 Whys root cause for scale MRR $50k to $200k - Hidden cost of failure - Contrarian insight advanced practitioner insight Variant A (Origin Story): Subject/headline 10 options with hypothesis, preview 3, body 250 words with {{FirstName}} tags PS PPS, visual brief, CTA, send logic delay trigger segment. Include placeholder [BRAND][AUDIENCE][DATA] + filled example for Logistics Startup Variant B (FOMO+Scarcity): Same structure different angle Variant C (Referral Ask): Same structure third angle Each variant must be fundamentally different not reworded OUTPUT: Markdown H2/H3 tables copy blocks ready for Notion/Google Docs/Webflow, both placeholder and filled side by side No generic advice, every sentence actionable, specific numbers, decision tree If [condition] then A else B, no buzzwords without definition
## EXECUTION
Purpose → Audience → Message Strategy → Structure → Drafting → Editorial QA → Revision. Complete the task in the smallest complete workflow that solves it. Make inputs, decisions and deliverables explicit. Return the requested result, not a description of the workflow.
## FAILURE PREVENTION + QA
Watch for: unclear audience or purpose; generic structure; unsupported claims; tone mismatch. Apply only relevant prevention rules. Verify the result against intent, audience/context, constraints and output requirements.
## ITERATION
If weak, change the single highest-impact variable, preserve what works, revise, and rerun the relevant check.
## OUTPUT CONTRACT
Return a specific, immediately usable result. Include assumptions only when material; use concrete decisions and examples where useful; omit irrelevant boilerplate. Do not merely restate this prompt.