Map CRM Funnel Stages to a Weekly Teach Reel Cadence
Align teach Reels to awareness, consideration, and decision with a stage→intent table and weekly cadence—without hard-sell spam.
Map CRM Funnel Stages to a Weekly Teach Reel Cadence
Align teach content to awareness → consideration → decision with a stage→intent table and a weekly Reel cadence—without turning every clip into hard-sell spam. Approve one board per stage intent before batch render.
CRM stages describe buyer readiness. Teach Reels should match the question the buyer can answer now—not the deal you wish they would close today. Gated demos still belong later in the path; Reels earn the right to ask.
Stage → intent table
| CRM stage | Buyer question | Reel intent type | Example teach | Usually NOT in the Reel |
|---|---|---|---|---|
| Awareness | What is this problem? | Category / mechanism | "Why queues refill after you hire" | Pricing, contract length |
| Consideration | How do approaches differ? | Criteria / method | Contrast-by-criteria scorecard | Named competitor attacks |
| Decision | How do I do it here? | How-to / gotcha | "Set the routing rule in settings" | Full ROI model decks |
| Onboarding (post-win) | How do I succeed? | Activation how-to | "Invite teammate with role" | Renewal discount pitches |
| Expansion | What else should we use? | Adjacent feature teach | "Saved views for Monday triage" | Aggressive upsell scripts |
If a clip tries to answer two stages at once, split it. Awareness plus pricing is how soft teach becomes spam.
What belongs in a Reel vs a gated demo
Reel-worthy: one mechanism, one how-to, one gotcha, one scorecard question.
Gate or sales-assist: custom ROI, security questionnaires, multi-workspace migrations, contractual comparisons.
Use Reels to create assisted demos—not to replace them. Point CTAs to docs or a light checklist; reserve the hard gate for high-intent asks.
Sample weekly cadence (B2B SaaS)
| Day | Stage focus | Clip type | Length |
|---|---|---|---|
| Mon | Awareness | Why / problem mechanism | 45s |
| Wed | Consideration | Criteria or contrast method | 45s |
| Fri | Decision / onboarding | How-to or Gotcha | 30–45s |
Optional: one monthly Expansion Friday. Do not ship five Decision clips in a week unless a launch demands it—overweighting Decision trains the feed to expect pitches.
Tie release education to the Why / How / Gotcha trio when a feature ships mid-cadence: temporarily swap Wednesday for How, Friday for Gotcha, then return to the steady map.
Building the board queue from CRM reality
Sources that keep the map honest:
- Top lost-deal reasons (consideration intents)
- Top onboarding tickets (FAQ → backlog)
- Sales call snippets that are really how-tos
- Feature adoption gaps (expansion)
Each source row becomes a stage-tagged intent, then a board. Approve boards in a weekly 20-minute gate before anyone renders.
Measurement without vanity
Per stage, watch different signals:
- Awareness: saves, follows, grounded comments
- Consideration: scorecard CTA taps, comparison doc views
- Decision: checklist completions, demo assists
- Onboarding: ticket deflection on that tag
Views alone do not prove stage fit. Keep UTMs like aw / con / dec so you do not mis-attribute.
Cadence anti-patterns
- Every Reel ends on "Book a demo now"
- Awareness clips stuffed with feature laundry lists
- No Gotcha content (support debt piles up)
- Cadence collapses whenever a launch hits—rebuild with the trio instead of abandoning the map
- Invented funnel conversion benchmarks in the VO
Production checklist
- Each planned clip tagged with CRM stage + intent
- Stage→intent table reviewed with Sales + CS monthly
- Weekly calendar filled (Mon/Wed/Fri or your variant)
- One board per clip approved before batch render
- CTA matched to stage (docs/scorecard vs demo)
- Pacing fits 30/45/60 templates
- Safe zones checked for CTA shelves (9:16 safe zones)
Storyboard-first keeps the weekly batch from turning into regenerate-all chaos (storyboard-first workflow).
Aligning CRM fields to content tags
Add a content-intent picklist on campaign members or a parallel sheet: aw_mechanism, con_criteria, dec_howto, onboard_gotcha, expand_adjacent. Attribution meetings go faster when marketing and RevOps share stage language.
When product launches collide with cadence
Do not delete the weekly map. Overlay the launch trio:
- Replace one Awareness slot with Why
- Replace Consideration with How
- Replace Friday with Gotcha
Return to steady-state the following week. Permanent "launch mode" is how cadences die.
Example month (four weeks)
Week 1: steady map Week 2: launch trio overlay Week 3: steady map + one expansion short Week 4: FAQ-driven gotchas from support
Review assisted demos and ticket tags at month end—not daily panic on view counts.
Role split
| Role | Owns |
|---|---|
| PMM | Stage→intent map + boards |
| Growth | Cadence calendar + UTMs |
| Sales | Decision-stage accuracy |
| CS | Onboarding/gotcha intents |
| RevOps | Field/tag hygiene |
Without RevOps tags, marketing cannot prove stage fit. Without CS input, gotcha Fridays miss real pain.
Revisit the stage→intent table whenever your CRM stage definitions change. If RevOps merges stages, your Reel tags must merge too—or reporting will invent false stage winners.
Document the decision in the board changelog so future editors inherit the rationale instead of re-litigating host mode or stage tags from scratch.
Soft tool note
Whatever stack you use, approve one board per stage intent before batch render so the weekly cadence stays teach-shaped. Platforms such as Scro are built around that storyboard-first gate; the stage→intent table still works in your CRM content ops doc.