{"slug":"business/social-proof-brief-2026-07-29","title":"Wednesday Content Publishing Brief — Social Proof Day","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/social-proof-brief-2026-07-29.mdx","bytes":13489,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Date:** 2026-07-29  \n**Theme:** Social proof (customer story, video, visual assets)  \n**Status:** Draft ready for review  \n**Owner:** PMM hat + Founder + CS  \n**Source docs:** [64 Case Study Templates](../commercial/12-corporate/64-case-study-templates.md) · [28 Customer Outcomes](../commercial/05-value-pricing/28-customer-outcomes.md) · [75 CS Metrics](../commercial/13-operations/75-customer-success-metrics.md) · [58 Social Media Strategy](../commercial/11-marketing/58-social-media-strategy.md) · [33 ICP](../commercial/06-customers/33-ideal-customer-profile.md)\n\n---\n\n## 1. Customer Story — Draft / Review\n\n### Asset: Case Study B — The Catch Story (mini, ~250 words)\n\n**Headline:** How CloudFirst caught a renewal risk 45 days before the score moved  \n**Customer:** CloudFirst · David Chen, Head of RevOps  \n**Placeholder:** Name and quote are from existing repo testimonials (`apps/marketing/components/testimonials-section.tsx`). Exact text and naming permission must be confirmed with CS before publish.\n\n### Draft\n\nSITUATION. David Chen's team used to watch renewal scores move after the damage was already done. A churn signal would appear in Zendesk, then flip the health score in Salesforce a week later, then freeze the expansion budget. By the time the human surface caught it, the save-play window had narrowed to retention offers.\n\nTHE SIGNAL. CloudFirst connects HubSpot, Zendesk, Stripe, and Slack to the Workbench. The Twin composes signals across all four surfaces. Last quarter, it stitched three weak events together: a drop in weekly product usage, a support ticket that mentioned a competing platform in the transcript, and a Slack thread where the account manager wrote \"budget review is Q3.\" Within the bench the Twin surfaced a single risk card with links back to each source.\n\nTHE ACTION. David did not receive an automated email. He received a proposed action inside the bench: draft a save outreach, schedule a QBR, flag the account for Monday morning. He reviewed the evidence, edited the draft, and approved. The Twin only executes what a human approves.\n\nTHE OUTCOME. CloudFirst renewed. The same quarter, QBR prep dropped from roughly four hours each to 18 minutes. ATA per seat per week went from 3.1 to 8.4 in six weeks. David's quote: _\"The Twin caught a renewal risk 45 days before we would have seen it. That's real intelligence.\"_\n\n### Flagship readiness\n\nDo not publish Template A (flagship, ~800 words) until:\n\n- Baseline completeness is instrumented ([28 §4](../commercial/05-value-pricing/28-customer-outcomes.md)).\n- Realized-value review is complete and documented.\n- Customer approves exact text.\n\n### Editorial checklist\n\n- [x] Names a failure before a feature (renewal score lag / post-damage surprises)\n- [x] ≥1 number or evidence artifact per section (45 days, 4 hrs → 18 min, 3.1 → 8.4, evidence-chain)\n- [x] Terminology clean: no \"digital memory,\" no \"canonical spine,\" no hype-words\n- [x] Product earns its place or gets cut: IntegrateWise appears as the alternative mechanism, not the opening\n- [x] Voice: evidence before conclusions, short paragraphs, one claim per paragraph\n\n---\n\n## 2. Short Video — Customer Testimonial / Demo Clip\n\n### 60-second testimonial script (David Chen, Head of RevOps, CloudFirst)\n\n| Time      | Visual / B-roll                                                                  | Audio                                                                                                                                                                                                                   |\n| --------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| 0:00–0:12 | Workbench UI: risk alert card with evidence chips (usage, ticket, Slack, Stripe) | —                                                                                                                                                                                                                       |\n| 0:12–0:30 | Split screen: David speaking + bench showing composed signal                     | \"Last quarter, our renewal score moved after the damage was done. The Twin stitched a usage drop, a support ticket, and a Slack conversation into one risk card — 45 days before it would have surfaced in Salesforce.\" |\n| 0:30–0:50 | Screen recording: Approve Twin's Action panel — draft, edit, click approve       | —                                                                                                                                                                                                                       |\n| 0:50–0:75 | Outcomes card: QBR prep 4 hrs → 18 min; ATA 3.1 → 8.4                            | —                                                                                                                                                                                                                       |\n| 0:75–0:90 | David: \"It's never once acted without us. That's the difference.\"                | —                                                                                                                                                                                                                       |\n\n### 15-second teaser (LinkedIn / YouTube Shorts)\n\n```\nText overlay: We caught a churn risk 45 days before the score moved.\nVisual: 2-second clip of approval receipt timestamp.\nCaption: IntegrateWise + @cloudfirst (pending co-promotion).\n```\n\n### Production checklist\n\n- [ ] CS confirms David Chen availability and filming location (remote or on-site).\n- [ ] Export risk-alert screenshot (`docs/assets/risk-alert-screenshot.png`) for placeholder B-roll until raw screen recording is available.\n- [ ] Add captions (accessibility + silent autoplay).\n- [ ] Host on YouTube (unlisted) for embedding; zero native LinkedIn programming until a hire owns it ([58 §1](../commercial/11-marketing/58-social-media-strategy.md)).\n\n---\n\n## 3. Visual Assets\n\n| Asset                                         | Format / Size  | Status      | Owner   | Path / Source                            |\n| --------------------------------------------- | -------------- | ----------- | ------- | ---------------------------------------- |\n| Risk-alert screenshot (bench UI)              | PNG 16:9 + 4:5 | **Pending** | PMM hat | `docs/assets/risk-alert-screenshot.png`  |\n| Evidence-chain diagram (composed signal flow) | SVG            | **Pending** | Design  | `docs/assets/evidence-chain-diagram.svg` |\n| David Chen quote card                         | PNG 1080×1080  | **Pending** | PMM hat | `docs/assets/quote-chen-risk.png`        |\n| Napkin-math graphic (morning tax + QBR prep)  | PNG/SVG        | **Pending** | PMM hat | `docs/assets/napkin-renewal-math.png`    |\n| CloudFirst logo lockup                        | SVG            | **Pending** | Design  | `docs/assets/logo-cloudfirst.svg`        |\n\n**Design directives:**\n\n- Quote card: reuse layout from `apps/marketing/components/testimonials-section.tsx` (glass card, gradient avatar, one-line metric).\n- Napkin-math: match existing social-card fleet in `docs/marketing/` (`social-card-invisible-tax.html`, `social-card-memory.html`).\n- Evidence-chain diagram: one-page flow, 5 nodes max. Nodes: usage drop → ticket sentiment → Slack thread → composed signal → approved save-play.\n\n---\n\n## 4. Publishing Channels\n\n| Channel                       | Asset                                                    | Timing                     | Owner        |\n| ----------------------------- | -------------------------------------------------------- | -------------------------- | ------------ |\n| Marketing site blog           | Catch Story (full)                                       | Wed 2026-07-29 08:00 ET    | PMM hat      |\n| Marketing site — Testimonials | Add David Chen quote card                                | Wed 2026-07-29 08:00 ET    | PMM hat      |\n| LinkedIn — Founder long-post  | Native rewrite (~500 words)                              | Wed 2026-07-29 08:00 AM ET | Founder      |\n| LinkedIn — Carousel           | 5-slide social proof carousel                            | Wed 2026-07-29 09:00 AM ET | PMM hat      |\n| Excerpt 1 (Wed)               | \"We caught a churn risk 45 days before the score moved.\" | Wed 2026-07-29 12:00 ET    | Founder      |\n| Excerpt 2 (Thu)               | \"4 hours of QBR prep. Reduced to 18 minutes.\"            | Thu 2026-07-30 12:00 ET    | Founder      |\n| Excerpt 3 (Fri)               | \"ATA per seat per week: 3.1 → 8.4.\"                      | Fri 2026-07-31 12:00 ET    | Founder      |\n| YouTube (unlisted)            | 60-sec testimonial                                       | Wed (filming TBD)          | Founder + CS |\n| Newsletter                    | Catch Story + CTA                                        | Fri 2026-07-31             | PMM hat      |\n\n**Channel physics ([58 §2](../commercial/11-marketing/58-social-media-strategy.md)):**\n\n- Links in first comment only. No links in post body.\n- 0–1 hashtags.\n- No edits in first hour.\n- Reply SLA: 24 hours. Pain-revealing replies → soft-bridge DM. ICP visitor → connection note referencing the thread.\n\n---\n\n## 5. Customer Co-Promotion\n\n**Customer:** CloudFirst (David Chen, Head of RevOps) — placeholder until CS confirms.\n\n### Pre-publish gate (must pass before named publication)\n\n- [ ] CS confirms David Chen is still at CloudFirst and within active renewal period.\n- [ ] Obtain signed quote text on the exact wording above.\n- [ ] Validate metrics against account's realized-value review ([75 §2](../commercial/13-operations/75-customer-success-metrics.md)): 45-day lead time, QBR prep delta, ATA trajectory.\n- [ ] Get written permission to use the CloudFirst logo and customer name in external copy.\n\n### Co-promotion package\n\n| What IntegrateWise provides                                                                           | What CloudFirst provides                              |\n| ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |\n| Named blog case study + LinkedIn long-post                                                            | 1 LinkedIn repost from David's personal account       |\n| 1-page PDF case study (Template A style)                                                              | 1 mention in CloudFirst's customer success newsletter |\n| 8-slide champion deck (Template C) per [64 §4](../commercial/12-corporate/64-case-study-templates.md) | Logo lockup + headshot for quote card                 |\n| Video testimonial (raw + cut)                                                                         | 1 referral or referral-intro in QBR                   |\n\n### Fallback if customer declines naming\n\n- Industry-described attribution per [64 Rules of Evidence](../commercial/12-corporate/64-case-study-templates.md): \"a 40-CSM fintech.\"\n- Rotate into proof band on marketing site (`docs/landing-page/components/section-03-social-proof.jsx`).\n\n---\n\n## Pending Actions\n\n1. **CS** — schedule 15-min check-in with David Chen for quote permission; confirm rename rights.\n2. **PMM hat** — draft 8-slide champion deck (Template C) for CloudFirst.\n3. **Design** — produce risk-alert screenshot, evidence-chain diagram, quote card, napkin-math graphic, logo lockup.\n4. **Founder** — block 1-hour filming session or remote recording setup with David Chen.\n5. **PMM hat** — update `docs/internal/publishing-queue.md` with Wednesday rows and push to `apps/marketing/content/blog/index.ts` after review.\n\n---\n\n## Queue Update\n\n| ID                | Asset                                       | Format      | Status                         | Scheduled               | Owner            |\n| ----------------- | ------------------------------------------- | ----------- | ------------------------------ | ----------------------- | ---------------- |\n| WED-2026-07-29-01 | Catch Story — CloudFirst renewal risk       | Blog post   | Draft ready                    | Wed 2026-07-29 08:00 ET | PMM hat          |\n| WED-2026-07-29-02 | LinkedIn long-post — Catch Story rewrite    | Long-post   | Draft ready                    | Wed 2026-07-29 08:00 ET | Founder          |\n| WED-2026-07-29-03 | LinkedIn carousel — Social proof (5 slides) | Carousel    | Pending                        | Wed 2026-07-29 09:00 ET | PMM hat          |\n| WED-2026-07-29-04 | Excerpt posts (×3)                          | Short posts | Not started                    | Wed–Fri 12:00 ET        | Founder          |\n| WED-2026-07-29-05 | 60-sec testimonial video                    | Video       | Script ready / filming pending | Wed 2026-07-29 (TBD)    | Founder + CS     |\n| WED-2026-07-29-06 | Visual assets (5 items)                     | PNG / SVG   | Pending                        | Wed 2026-07-29          | PMM hat + Design |\n| WED-2026-07-29-07 | Newsletter teaser — Catch Story             | Email       | Pending                        | Fri 2026-07-31          | PMM hat          |\n"}