20Sales: Inside Ramp's Sales Playbook: How to Build a Sales Machine with Max Freeman, SVP Sales @ Ramp

The Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch · October 10, 2026

5 Selected Lessons:

heuristic · 2 reasoning_pattern · 1 framework · 1 priority · 1

Leaders must be a 'dual threat': stay in the trenches while building organizational leverage

priority based on: lived experience Max Freeman

Source

The Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch — 20Sales: Inside Ramp's Sales Playbook: How to Build a Sales Machine with Max Freeman, SVP Sales @ Ramp (October 10, 2026) · at 51:56 ▸

When this applies

when any manager's early hands-on habits risk becoming a bottleneck as their team and scope grow

The takeaway

A growing leader must simultaneously operate strategically ('in the clouds') and stay hands-on ('in the trenches') — doing only one eventually breaks either credibility or scalability.

Why it works

Personally solving every important problem wins individual deals but teaches the team to depend on the leader rather than developing their own capability, which caps organizational scale even as it feels productive in the moment.

One level up

The skills that make someone successful at one stage of scale (individual heroics) can become the exact constraint limiting the next stage, requiring deliberate behavior change rather than more of the same.

Where it stops holding

This stops working if a leader interprets 'staying in the trenches' as license to keep personally rescuing every deal, which recreates the original dependency problem.

Detail

hierarchy:

Build organizational leverage/capability (train the team, not just solve problems personally)
Stay personally close to the customer and the work (make cold calls, send cold emails daily) to retain credibility and insight

rationale: Jumping into every deal wins in the short run but teaches the org to rely on the leader, becoming a constraint as scope grows; conversely, losing touch with the frontline makes a leader unable to add real value or earn followers' respect ('nothing less inspiring than taking instruction from someone that you don't believe can do the job better than you').

In their words

I need to build more and more barrels inside of the go-to-market organization. Otherwise, I'm not doing my job effectively as a leader

spoken at 51:56 ▸

Embed technical customer success as an NDR/expansion engine

framework based on: lived experience Max Freeman

Source

When this applies

when deciding how to structure the post-sale function for a complex product that requires technical deployment to realize value

The takeaway

Where initial deployment quality directly determines future expansion revenue, keep that function in-house and staffed with domain experts rather than outsourcing it as a paid service.

Why it works

Owning deployment with highly technical CS staff (e.g., CPAs who know ERP/accounting systems) ensures the initial implementation delivers real value, which earns the right to cross-sell/upsell further products over time; a generic professional-services hand-off can't replicate this depth or incentive alignment.

One level up

Align organizational ownership with where the long-term economic outcome (retention/expansion) is actually created.

Where it stops holding

This stops working when the product's economics can't subsidize a highly technical CS team, or when deployment complexity is low enough that professional services genuinely suffices (the speaker explicitly notes 'that might work for Snowflake' but not for Ramp).

Detail

procedure:

Make customer success an organizational construct (not a paid add-on), staffed with technically qualified people (e.g., CPAs, ERP-proficient).
Treat initial deployment as the highest-leverage moment — do it perfectly to earn future cross-sell rights.
Use CS as the mechanism for ongoing cross-sell/upsell/expansion across a growing product portfolio.

benchmarks: {}

rationale: The product's economics can subsidize this technical CS investment because it drives NDR and portfolio expansion over time.

In their words

You kind of have to think of customer success as the economic engine that is going to drive NDR for your portfolio of customers over time.

spoken at 43:39 ▸

Treat sales as an engineering/data-infrastructure problem

reasoning_pattern based on: lived experience Max Freeman

Source

When this applies

when any manual, repetitive human process needs to scale beyond linear headcount growth

The takeaway

When a core growth lever is bottlenecked by manual human labor, invest engineering resources to convert it into an automated, measurable system rather than just hiring more people.

Why it works

Manual outbound (writing, calling, researching) caps coverage at whatever a handful of humans can physically do; building internal tooling/automation converts a headcount-bound process into a systems-bound one that can scale with TAM.

One level up

Treat any scaling constraint as an engineering problem to be automated and instrumented, not merely a staffing problem to be solved with more hires.

Where it stops holding

This stops working when the founders won't allocate engineering resources to go-to-market, or when the task genuinely requires human judgment that can't be systematized (e.g., complex negotiation).

Detail

approach: Identify the repetitive/manual bottleneck in the sales process (e.g., signal-finding, list-building, pre-call research), then dedicate engineers to build internal automation for it, making the system recursive via ongoing A/B testing.

signals:

manual process can't scale past a few hundred touches/day
TAM is growing faster than headcount can cover
founders willing to allocate engineering resources to sales tooling

rationale: Sales reps should focus on speaking with customers and solving business problems, not researching or scraping data manually; that capacity should be bought back via automation.

In their words

Sales is very much an engineering problem when you break it down. It's a data infrastructure problem. It's a math problem.

spoken at 16:27 ▸

Confront conflicts of interest early rather than discovering them late

heuristic based on: lived experience Max Freeman

Source

When this applies

when any deal-maker senses a hidden conflict of interest that could derail a late-stage commitment

The takeaway

Name the elephant in the room as soon as you see it, rather than hoping it resolves itself.

Why it works

Surfacing a known risk early lets you test the buyer's objectivity and avoid wasting resources rallying internal support for a deal that was never winnable on merits.

One level up

Visibility into risk early is worth more than comfort maintained by silence.

Where it stops holding

This stops working when raising the issue damages trust more than the risk itself would have, or when you lack enough rapport to ask directly.

Detail

rule: If you detect a potential conflict (e.g., shared board member with a competitor), ask the buyer directly and early whether it will affect the decision.

threshold: as soon as it's 'early enough in the cycle'

rationale: A seller should never find out about a disqualifying conflict only after rallying internal resources through a full sales cycle.

In their words

Hey, Harry, I know you're evaluating us and another competitor. I see you have a shared board member with that competitor. Is that going to get in the way of this decision?

spoken at 9:20 ▸

No comp plan / 100% OTE for the first two quarters of a new sales role

heuristic based on: lived experience Max Freeman

Source

When this applies

when setting performance targets for any brand-new role where historical data doesn't yet exist

The takeaway

Don't set performance targets for a role until you have enough data to calibrate them; use a flat guaranteed structure in the interim.

Why it works

Without historical ramp and conversion data, any quota is a guess; guessing too high destroys morale and too low creates runaway payouts, so removing the quota variable until data exists avoids both failure modes.

One level up

Defer commitment under uncertainty; gather data before locking in incentive structures that are costly to reverse.

Where it stops holding

This stops working once sufficient ramped-rep data exists (sub-6-month cycle businesses should have it within a couple of ramp cycles), after which continuing flat OTE removes useful incentive pressure.

Detail

rule: Pay 100% OTE (no quota-based variable) for at least the first two quarters of a new sales role; introduce quota once stage-progression data exists.

threshold: at least 2 quarters, or until there's enough ramped pipeline data (achievable within ~90 days for sub-6-month cycle businesses)

rationale: Guessing a quota too early either overpays wildly or demoralizes reps with unattainable targets, and confidence lost is hard to regain.

In their words

I usually advise to do 100% OTE for at least the first two quarters. You just don't know what you don't know.

spoken at 27:32 ▸