Subject: re: cutting your support ramp time
Hi [Name],
One more reason this might be worth a look: [Similar company] had the same "new reps drowning for weeks" problem and got first-week resolution rates up 22% after switching.
If ramp time isn't a priority right now, no worries — just reply "not now" and I'll close the loop.
Otherwise, open to 15 minutes Thursday?
[Your name]
Hi [Name],
Totally fair to scrutinize the number — that's the right instinct.
Quick reframe: right now, slow ramp is costing roughly [X hours] per new hire before they're productive. At your hiring pace that's the real line item; our price is a fraction of it.
So I can point you the right way — is the concern the budget itself, the payback timeline, or how we compare to [alternative]? Happy to dig into whichever it is.
[Your name]
Warm-up
- "Walk me through how your team handles [process] today." → listening for: their words for the pain.
- "What made you take this call?" → listening for: the trigger event.
Pain & cost
- "Where does that process break down most often?" → the symptom they feel.
- "What happens downstream when it breaks?" → the real cost.
- "How are you working around it now?" → urgency and budget for a fix.
...
Decision
- "Besides you, who'd weigh in on a change like this?" → hidden stakeholders.
ヒント「それはあなたにどのくらいのコストがかかっていますか」という質問は、後で ROI で売るができます。 正確な数字をキャプチャして、あなたの提案でそれらを引き戻します。
Subject: recap + next steps from today
Hi [Name],
Thanks for the time today — useful conversation.
What I heard matters most to you:
- Cutting new-rep ramp from ~6 weeks to under 2.
- Keeping answers accurate as your docs change weekly.
- A rollout that doesn't pull your leads off the floor.
Next steps:
- Me: send the security overview by Friday.
- You: loop in [IT contact] for the data question.
- Both: 30-min technical review next Wed.
Does Wednesday 2pm still work to lock that in?
[Your name]
Stage: Evaluation
Pain points:
- 6-week ramp for new support reps
- Docs change weekly, answers go stale
Budget signal: "We have room if it pays back in a quarter."
Decision makers: [Name] (Head of Support), + IT for security sign-off
Objections / risks: Worried about setup time during peak season
Next action: Send security overview — by Fri Jun 19
Hi [Name] — really liked your post on cutting support onboarding time; the "shadow an expert" point matched what I keep hearing from support leads. I work in that space and would enjoy following your take. Either way, thanks for sharing it.
A support team told me their new hires were "useless for a month." Their words, not mine.
The problem wasn't the people. New reps were hunting through 400 pages of docs that changed every week — so they guessed, or pinged a senior rep, who then stopped doing their own job.
We gave them one answer layer trained on those same docs. First-week resolution rates went from 51% to 73%.
The lesson: onboarding speed is usually a findability problem, not a training problem.
Curious how other support leaders are tackling ramp time — what's worked for you?
[Company] is spending roughly six weeks getting each new support rep to full productivity — time that costs both salary and senior-rep attention. This proposal outlines an answer layer trained on your existing documentation that gets new reps productive in under two weeks and keeps answers accurate as your docs change. Based on your current hiring pace, the expected payback is under one quarter. The investment is [PRICE] per year, including onboarding and your team's data setup. The sections below detail the rollout plan, security review, and success metrics we'd track together in the first 90 days.
Demo flow (map each beat to their pain):
1. Start at the new-rep view → "here's day one for a new hire." (pain: 6-week ramp)
2. Show a doc update auto-syncing → "answers never go stale." (pain: weekly doc changes)
3. Manager dashboard → resolution rate by rep. (pain: no visibility)
Wow moment: ask them for a real question their reps get, type it live, show the sourced answer.
Mid-demo questions:
- "Is this the kind of question that trips up new reps?"
- "Who on your side would live in this dashboard?"
Outcome: Lost
Primary reason: We were brought in too late — they'd already shortlisted two vendors before our first call.
Contributing factors:
- Champion liked us but wasn't the budget owner.
- Our security review took 9 days; competitor turned theirs around in 2.
- We never got a meeting with the CFO.
Competitor: Won on faster procurement, not product.
Do differently: Qualify "where are you in the process?" on call one, and pre-stage the security packet.