Host: Victor Vatus, Founder of TrackRec
Featuring:
-
Eli Portnoy, Co-founder of BackEngine
-
Jeanne Marie Wilke, RevOps Advisor
-
Rafaella Fontes, Director of Strategy & Operations at BackEngine
It’s the last week of the quarter. Your top rep has a whale deal committed, and then it vanishes in 48 hours. Or you hire a rock star who crushes every interview, then produces nothing once they're in the seat.
In sales, bad news is normal. Surprises are what keep revenue leaders up at night.
In this session, Eli Portnoy, Jeanne Marie Wilke, and Rafaella Fontes explored how to build the “anti-surprise engine”: disciplined process, cultural consistency, and AI-powered execution that keeps revenue predictable at every stage.
TL;DR
- Hiring surprises start in the interview room. Structured scorecards, independent evaluations, and practical skills tests reduce bad hires.
- Onboarding ends when someone understands the culture, not just the tools. YORO, You Only Ramp Once.
- Playbooks fail at execution because they do not live where reps work. Enforcement is structural, not behavioral.
- AI’s biggest revenue opportunity is embedding methodology directly into workflow.
- CS leaders who reach the executive level treat the voice of the customer as a strategic asset.
The Hiring Surprise: Measure What Actually Matters
Surprises can be prevented earliest in the interview process. Under hiring pressure, teams skip structure. That is how strong resumes turn into weak performance.
Jeanne Marie Wilke’s approach:
- Assign each interviewer a distinct focus area.
- Use scorecards.
- Score independently before comparing notes.
Groupthink kills signal. Batch hiring improves calibration by comparing candidates against each other.
Practical testing is essential. Have candidates deliver their pitch live. Push back. Observe how they respond to feedback. Coachability in an interview predicts development on the job.
The loop should not end at the offer letter. Revisit interview scorecards at 30, 60, and 90 days. If high scores do not predict performance, fix the rubric.
Key takeaway: Structured, independently scored interviews are the first defense against hiring surprises.
The Onboarding Surprise: Everyone Skips the Culture Step
Most failed hires are not skill failures. They are fit failures.
Fit means understanding how decisions get made, how people communicate, and what success looks like beyond the formal playbook.
Onboarding treated as a systems checklist misses the core issue.
Wilke reinforced YORO, You Only Ramp Once. Rushing someone to “ready” status after a few days creates a predictable failure two to three months later.
A proper ramp teaches:
- Industry context
- Customer narrative
- How to operate inside the organization
Key takeaway: Onboarding ends when someone understands how to succeed inside your culture.
The Execution Surprise: Why Playbooks Collect Dust
Most teams have a solid playbook. Most reps ignore it.
This creates pipeline surprises. Deals are “locked.” Investors ask about process. No one can confirm adherence.
The problem is structural. Playbooks live in documents. Reps live in inboxes, calls, and CRM.
There is no natural moment mid-call to open a methodology document.
Referencing Phil Jackson’s triangle system: it is not about the specific system. It is about committing to one. Top reps may not need it daily. The rest of the team does. A system raises the floor and gives even top performers something to return to during slumps.
Key takeaway: The issue is not a bad playbook. It is a playbook disconnected from workflow.
The AI Opportunity: Putting the Playbook in the Workflow
AI enables embedding methodology directly into daily execution.
While drafting an email, preparing for a call, or building a QBR, AI can surface relevant guidance from your playbook in real time.
This shortens feedback loops. Teams iterate continuously instead of monthly.
Fontes added another layer: pattern recognition at scale. Experienced investors develop instinct by seeing patterns repeatedly. AI applies that pattern recognition across all customer touchpoints simultaneously.
It aggregates calls, emails, CRM notes, and other signals to surface account health insights that no single metric can capture.
Example: when planning BackEngine’s Supper Series dinners across US cities, Fontes asked in Slack which accounts to prioritize in each city. The answer reflected the full relationship history across interactions.
Key takeaway: When methodology lives inside workflow, execution becomes the default. AI makes this possible.
For Founding CSMs: Build the Engine While Flying the Plane
A registrant asked: how do you build CS from scratch?
You cannot wait for perfect process. You build while operating.
Wilke’s advice: stay close to the voice of the customer. Process without customer signal drifts quickly.
Fontes emphasized community. Borrow frameworks from peers. Adapt to your ICP.
Portnoy reframed the role: executive-level CS leaders become the internal voice of the customer. They influence product, finance, and leadership decisions.
That strategic function elevates CS from retention to business driver.
Key takeaway: Start with the customer. Borrow intelligently. Position CS as the organization’s primary feedback loop.
Q&A
How do you prevent strong interview performers from underdelivering?
Close the loop. Score independently. Revisit scores at 30, 60, and 90 days. Identify which criteria predict success and refine continuously.
What is the most common onboarding mistake?
Treating onboarding as systems training instead of cultural integration. Tools can be learned quickly. Operating effectively inside a company cannot.
What if a rep ignores the playbook?
First assess whether the playbook is embedded in workflow. If it is not, the system needs redesign. For top performers, the goal is not restriction but stability during downturns.
How should leaders use AI without losing the human element?
Use AI to surface institutional knowledge at the moment of need. It supports judgment. It does not replace relationships.
Advice for a founding CSM managing customers while building process?
Do not wait for perfection. Stay close to customers. Use peer communities. From day one, act as the internal voice of the customer.