Social Media
Campaign Session
Claude Sonnet 5 · 6 turns · 18.9k tokens
Seven launch posts in a row will exhaust the audience, so the arc earns attention before it asks for anything.
- 01Day 1 · Problem — the admin tax on sales teams. No product mention at all.
- 02Day 2 · Proof — the 41-day sales cycle number, with the method shown.
- 03Day 3 · Reveal — the launch post. This one carries the link.
- 04Day 4 · Depth — carousel on how the automation actually works.
- 05Day 5 · Voice — a customer quote, not a testimonial graphic.
- 06Day 6 · Objection — what it does not do, said plainly.
- 07Day 7 · Invite — the demo call to action, once.
- Heads of Revenue & Sales Ops46%
- Founders at 10–200 staff28%
- RevOps and enablement17%
- Everyone else9%
They read on mobile before 09:00. Anything past the third line needs a reason to tap "see more".
Day 3 is in the preview — it is the only post carrying a link, which is why the other six can stay useful rather than promotional.
Rewrote the opening around the number rather than the product. It names a cost the reader already feels, which is harder to scroll past than a benefit claim.
Your sales team spends 11 hours a week on data entry. That is not a CRM problem. That is a CRM you bought and nobody uses.
We built Dreams AI CRM around a simple test: if a rep has to remember to update it, it is already broken. Every call logged automatically. Every deal stage inferred from what actually happened, not what someone typed on a Friday afternoon. Our pilot teams closed in 41 days instead of 52. We are showing the method behind that number, not just the number.
B scores lower but tends to out-comment A. Worth running both if the audience is cold.
The 11 hours figure matches what we measured internally. Sending this to my ops lead.
Does the stage inference work with a custom pipeline, or only the default one?