Key Takeaways
- Enterprise deals rarely die to rival software. Freeman points out that when Ramp loses, “the majority of the time we're losing to the status quo, which is on us. That's not a product gap. That's a we need to look ourselves in the mirror. We did not create enough urgency.”
- Quota productivity ratios between 7:1 and 12:1 come from running sales as an engineering problem, staffing teams with former investment bankers and sellers from low-NPS competitors.
- Discussing pricing right after call one destroys enterprise pricing power. Freeman requires reps to co-author business value assessments with buyers instead of granting premature discounts.
- Cycle compression happens upstream through ruthless qualification. Sellers must tie their software directly to the champion's career advancement.
- Reps filter out window shoppers before committing engineering hours by using Freeman's Give-to-Get Stakeholder Qualification Method.
The Freeman's Give-to-Get Stakeholder Qualification Method
Founders often treat enterprise sales cycle length as an endgame problem. When deals stall, they drop prices, send executive check-in emails, or plead for updates. Freeman argues that cycle length is determined in the opening minutes of discovery. If a deal drags on for six months, the seller failed to qualify authority on day one: “The best way to compress sales cycles is qualifying with more rigor.”
To hit Ramp's productivity benchmarks, Freeman instructs sellers to manufacture urgency by linking the product to the buyer's professional status. “You got to latch on to a big business problem,” Freeman notes. “You got to find the right person internally that's motivated enough to actually make a change because it's going to impact their career.” When reps meet with non-executive prospects, they use a four-step exchange to test whether that contact has real organizational power before dedicating technical resources:
Step 1: Affirm Mutual Conviction
Conclude a successful initial discovery call by validating strong alignment and mutual conviction that the solution addresses the customer's core business problem.
Step 2: Offer Internal Resources (The Give)
Commit senior internal and technical resources to build tailored collateral and knock the next demonstration meeting out of the park.
Step 3: Require Executive Access (The Get)
Condition the allocation of technical resources on the prospect bringing their organizational decision-maker or key economic buyer (e.g., VP of Procurement or CFO) to the next meeting.
Step 4: Evaluate Champion Authority
Test the prospect's reaction: if they agree, they possess genuine internal influence; if they refuse or deflect, identify that they are window shopping without authority to effect change.
Freeman outlines the exact conversational script: “Hey Harry, today was awesome. I have a lot of conviction that we can solve this problem for your business. We're going to knock this demo out of the park. I'm going to bring on a bunch of my technical resources. In an effort to bring them onto the call, my ask would be that you bring Susan, your VP of procurement, into this next conversation.”
When This Works (and When It Doesn't)
This method works immediately after early discovery calls when dealing with non-executive prospects to verify whether they have the standing and commitment to drive organizational purchase decisions. It shields your engineering and solutions teams from building custom demos for mid-level managers who lack purchasing authority.
It breaks down if you deploy it on true economic buyers. If you are pitching the Chief Financial Officer, requiring them to bring a subordinate before seeing product capabilities insults their seniority and stalls momentum. It also fails if discovery was thin. If you failed to identify a business problem tied to your champion's career standing, asking for executive access feels like an unearned sales trap.
What to Do With This
Review your CRM today and find the deals sitting between discovery and a custom product demonstration.
Flag any deal where an engineer or solutions architect is preparing custom collateral for a manager or director. Email the prospect before confirming the calendar invite:
"We are preparing our lead systems engineer to join our next call and map your workflows. Because we are dedicating technical resources to this demo, our ask is that you bring your VP of Procurement or CFO into the conversation. Does Thursday at 2 PM work for both of you?"
If they refuse or make excuses, cancel the custom technical preparation. Run a standard, non-customized product overview instead, and drop that deal's forecast probability until the actual decision-maker attends.