Social Media

Facebook Optimization Strategy for SaaS B2B PM Tool Using ACC

PROMPT

# Facebook Optimization Strategy for SaaS B2B PM Tool Using ACC

## EXPERT ROLE
Act as a senior Facebook 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 facebook 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 Facebook Strategist for Social Media (experienced, scaled SaaS B2B PM Tool to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: SaaS B2B PM Tool - $2M ARR, team 26, targeting enterprise CTOs, stage bootstrapped profitable Current: CAC $174, LTV $1875, churn 3%, traffic 20942/mo, conversion 5.5% Assets: 5k email list 30 testimonials Goal: reduce support 60% in 60 days Constraint: Budget $15k/mo, solo founder Tone: scientific McKinsey FRAMEWORK: ACC + structured 4-step. TASK: Complete Facebook system for Social Media / SaaS B2B PM Tool. - common failure modes about facebook for SaaS B2B PM Tool - 5 Whys root cause for reduce support 60% - 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 SaaS B2B PM Tool Variant B (Social Proof Avalanche): 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/Shopify Plus, 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

## STRATEGIC WORKFLOW
Audience Situation → Content Objective → Hook/Angle → Platform Execution → Measurement → Experiment → Decision. Diagnose the real problem, desired outcome, strongest constraint and material assumptions before execution. Make the causal chain explicit: situation → diagnosis → strategic hypothesis → execution. Distinguish what is known, inferred and still needs evidence.

## EXECUTION + MEASUREMENT
For each major action, state the decision it influences, the leading signal, the primary outcome metric, the measurement window and the evidence required to proceed. When relevant, map the action to the funnel stage or customer journey it is intended to change. Do not recommend a metric simply because it is easy to measure; connect it to the stated business objective.

## EXPERIMENT + DECISION
State one falsifiable hypothesis. Change one meaningful variable, keep the baseline stable, define the success metric, minimum evidence threshold and decision rule. Separate diagnostic tests from optimization tests. If evidence does not support the hypothesis, explain the next smallest test or strategic change instead of rewriting everything.

## FAILURE PREVENTION + QA
Watch for: weak first-glance hook; platform-inappropriate format; generic audience framing; engagement without business/content objective; no measurable test. Apply only relevant prevention rules. Verify audience fit, source integrity, measurable outcome, constraint compliance, causal logic, output completeness and whether the recommendation can actually be acted upon. Flag unsupported claims and scenario assumptions explicitly.

## 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.