Loom or Vidyard? Picking the Right Tool for a B2B Outreach Team
Objective: Given a real team profile (size, CRM dependency, and the specific outreach job to be done), apply the lesson's decision tree to choose Loom or Vidyard and justify the call against the tradeoffs the lesson lays out, not just brand familiarity.
You're the marketing ops lead at TBO Tek, the B2B travel distribution platform connecting 147,000+ travel buyers to suppliers. The partnerships team wants to start sending personalized video outreach to travel agencies who haven't logged in for 60+ days, and they've asked you to pick one tool before the pilot starts next week.
Score the team against the lesson's decision tree (team size, CRM tracking need, analytics need) and recommend Loom or Vidyard with a one-paragraph justification a non-technical stakeholder can act on.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, no account friction, easy to share with a non-technical stakeholder
Free plan is enough to confirm what's included before recommending a paid tier
Paid upgrades (optional, faster/deeper)
The decision hinges on a feature that's only on Vidyard's paid tier
The process
1 step
Step 01 of 01
The lesson's decision tree splits on two questions in order: team size (under 50 vs. 50+/enterprise), then whether the team needs CRM-triggered follow-ups. Vidyard's heat-map analytics and CRM triggers only pay off once a team is running outbound at real volume through a CRM.
TBO Tek's partnerships team is 18 people, they already log every touch in Salesforce, and they want a follow-up task auto-created when a travel agency watches 80%+ of a video. Which tool does the decision tree point to, and why does team size alone not settle it here?
Procedure
- Score team size: 18 people falls under the lesson's 'under 50' Loom-leaning branch
- Score CRM tracking need: the team explicitly wants an automated Salesforce follow-up task on 80% watch, which the lesson flags as a Vidyard-specific trigger feature
- Note the branch conflict: team size alone says Loom, but the CRM-trigger requirement overrides it in the lesson's own tree ('Need CRM tracking? Yes -> Loom Business or Vidyard')
- Price out both paths at 18 seats using the lesson's listed pricing ($12.50/user/mo Loom paid vs. $59/user/mo Vidyard Plus) to give the stakeholder a real budget number
- Write the one-paragraph recommendation naming the tool and the specific feature that decided it
RECOMMENDATION: Vidyard (Plus plan) Team size (18) alone would point to Loom, but the requirement for an automated Salesforce follow-up task triggered at 80% watch is a Vidyard-specific feature the lesson calls out explicitly — Loom has no CRM-trigger layer at any plan tier. Cost at 18 seats: ~$1,062/mo (Vidyard Plus) vs. ~$225/mo (Loom paid). Recommend piloting Vidyard with 5 reps for one month before rolling out to all 18, since the CRM trigger is the whole point of the ask.
Healthy
The recommendation names the one deciding feature (CRM triggers) instead of just repeating 'team size says X.'
Unhealthy
Picking Loom because it's cheaper without addressing that the team's stated requirement (auto follow-up task) doesn't exist on Loom.
What this means
The decision tree has an override condition, not just a single branch. A stated automation requirement outranks the size heuristic every time.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Team picks the cheaper tool and then can't build the automation they asked for | Confirm the specific trigger/analytics requirement before pricing, not after | 5 min |
Final deliverable
A one-page scoring matrix plus a one-paragraph tool recommendation with a per-seat cost estimate.
See a reference example
Go Digit General Insurance, video outreach tool decision (excerpt) Team: 12-person renewals team, no CRM integration required, wants speed over analytics. Score: team size < 50 (Loom), no CRM trigger need (Loom), no analytics need (Loom). RECOMMENDATION: Loom Business ($12.50/user/mo). No branch override applies here — every criterion points the same direction.
Success criteria
You're done when you can:
- Correctly identifies which lesson criterion (size vs. CRM trigger) actually decides the recommendation
- Names the specific Vidyard-only feature the requirement depends on, not just 'more analytics'
- Includes a real per-seat cost estimate using the lesson's stated pricing