Enterprise Sales for Founders: A B2B Sales Playbook

Enterprise sales for founders means running the whole cycle of selling to a large organization yourself: finding the person who owns the problem, qualifying budget and authority, proving value in a short paid pilot, clearing security, legal and procurement, and making sure the product actually gets used. Before product-market fit, the founder usually sells, and in our view a short, well-defined process beats a long, friendly one.

Definition: Enterprise sales is a high-touch B2B sale to a large organization in which several people (a champion, an economic buyer, technical and security reviewers, legal and procurement) must each say yes before a contract is signed.

A big company doesn't buy anything. People inside it do, one signature at a time.

This playbook follows the deal from first hypothesis to renewal: a stage map with exit criteria, how we qualify, how we price, a pilot template you can copy and the pipeline arithmetic that tells you how many meetings you need. If you are still chasing your first ten customers of any size, start with our guide to founder-led sales for technical founders. This one is about selling to big companies.

Why founders usually run enterprise sales first

We'd be wary of trying to hire your way out of the first enterprise deals. Early sales is an experiment. You are testing who has the problem, what they will pay and what the product has to do to earn a signature.

That loop needs three things: credibility with the customer, authority to change the roadmap and a direct line to the people building the product. At most startups, only a founder has all three.

Technical founders often assume they're bad at this. They usually aren't. They bring the two things buyers trust most: deep knowledge of the problem and real conviction that the product solves it. Selling at this stage is diagnosis and help, not persuasion tricks.

What makes the enterprise version hard is that the customer is a system of people, each with their own incentives and rules. You have to map who wants change, who feels threatened by it and who controls the money before a deal will move.

The buyer side has shifted too. Gartner's research on the B2B buying journey finds that 99 percent of B2B purchases are driven by organizational change and that 75 percent of B2B buyers prefer a rep-free sales experience. Yet buyers who combine a supplier's digital tools with a sales rep are 1.8 times more likely to complete a high-quality deal. Our read, and it's only one read of the data: publish good self-serve material, and still run the early deals yourself.

That has two consequences for how you run the company:

• Consider changing your top metric. For an enterprise startup, the weekly number is usually letters of intent, pilots (free, then paid) or signed contracts, not sign-ups or page views.
• Know what sales is for. Aaron Levie, co-founder of Box, draws a clean line: sales should close big deals, not drive product adoption. Box spread through end users sharing files and then sold to the wider organization.

Top-down or bottom-up: let the product decide

The Box path tends to work when a team can adopt the product on its own. If your product needs several departments to coordinate before anyone can use it (hospital software that touches IT, billing and clinical staff, say), you will likely need to sell top-down to a senior leader who can make that coordination happen.

Pick by how your product gets adopted, not by which story sounds better in a pitch. Our guide to go-to-market strategy walks through that choice.

An enterprise deal map: stages, owners and exit criteria

Here is one way to map an enterprise opportunity. The funnel runs from prospecting and outreach through qualification, pricing, closing and implementation. In practice that expands into nine stages, each with an owner and a condition worth confirming before you move on.

The exit criteria are the whole point of the map. A deal without a named budget holder isn't qualified in our book, however excited your champion sounds. And a signed contract isn't really done until stage 8 is.

How to qualify enterprise sales deals: discovery and the buying committee

Spend the first call asking, not pitching. The call has two jobs: decide whether this prospect is real, and book a tailored demo if it is. Our discovery script covers four areas:

1. The problem. Why did they take the call? How long has this been a problem, who else feels it and what does it cost them?
2. The history. Why haven't they solved it already? What do they use today, and who chose it?
3. The money. Is there budget, and roughly how much?
4. The process. How does the organization buy software, who makes the final call and who else weighs in?

An early "no" is a small win. It saves both sides weeks.

Be just as picky about who you talk to. Taking every call that will have you selects for people who are easy to talk to, not people who will buy. And selling a big-company product to other startups teaches you very little about enterprise buyers. We make the broader case in our take on why founders close the wrong deals.

Map the buying committee

Once a deal is real, name every person who can help or block it:

• Champion: feels the pain, wants the product and sells it internally when you're not there. Treat this person almost like a co-founder inside the account.
• Economic buyer: controls the budget and signs.
• Detractor: often the person who built or chose the current solution.
• Technical approver and IT: often risk-averse; bring them in for security review unless they are also the users.
• Security gatekeeper: owns the questionnaire and certification requirements.
• Procurement: paid to extract a discount, and needs to win something.
• Legal: owns the redlines.
• Finance: owns budget cycles and whether a purchase counts as capital or operating expense.
• Day-to-day users: decide whether the product sticks after signature.

Write down how you might win each one. Many decisions about your deal happen in rooms you're not in, so arm your champion with a one-page summary of what the product does, what it's worth and why the price is fair.

And try not to look desperate. Senior buyers can usually smell it, and it weakens your hand in every negotiation that follows.

Use MEDDPICC as a test, not paperwork

Larger sales teams formalize qualification with MEDDIC, which Dick Dunkel created at Parametric Technology Corporation (PTC) in 1996, working with Jack Napoli, per the MEDDICC organization's history of the framework. The letters stand for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain and Champion. MEDDPICC adds Paper process and Competition.

A founder doesn't need the full forms. The letters still make a good honesty check. If you can't name the economic buyer or describe the paper process, your forecast is probably a guess wearing a spreadsheet.

Price the enterprise deal from the customer's value equation

We'd set the price from the value you create, and write that value down with your champion. List, line by line, what the product will save or earn: labor hours, error costs, new revenue. Then ask the champion to attack every assumption.

Tom Blomfield, a Y Combinator partner who co-founded Monzo, gives the cleanest version of the arithmetic. A support team of 100 agents at a fully loaded $100,000 each costs $10 million a year, so a tool that removes 20 percent of the work creates $2 million of value. He suggests charging 25 to 50 percent of the value delivered, $500,000 to $1 million here, with about a third ($667,000, roughly $700,000) as a sensible default.

Three guardrails help keep that number honest:

• Cost sets the floor, not the price. Many software companies aim for gross margins of roughly 80 to 90 percent, and count cloud and model credits as a real cash cost.
• Stay out of price wars if you can. Competing on value, integrations or a narrow niche is usually the stronger position.
• Check that the price can pay for the sales motion. One rule of thumb, from the same YC pricing talk, is about $5 of new annual recurring revenue for every $1 of a salesperson's total pay. An account executive earning $100,000 should close roughly $500,000 a year, which works for $25,000 contracts and falls apart for $1,000 ones.

Most founders are tempted to charge too little. Resist it. In one story from Optimizely's early days, a co-founder quoted $10,000 a month, got talked down to $2,000 and still closed, which suggests the first number wasn't the ceiling either. For price structure and tiers, see our guide on how to price your product.

Turn pilots into contracts: the one-page pilot template

Move up the commitment ladder faster than feels comfortable. Many B2B founders climb four rungs:

1. Open-ended unpaid design partnerships.
2. Free pilots.
3. Short paid pilots.
4. Where you can get it, an annual or monthly contract with a 30 or 60 day opt-out that converts to recurring revenue automatically.

The last rung turns one sales process into a recurring contract. In our view more founders climb too slowly than jump too early. An unpaid design partnership with no end date tends to turn into custom development for one customer, with a logo as the only payment.

Standard paper is a good starting point. Common Paper publishes free standard pilot agreements and order forms under a Creative Commons license, and a one-page order form like this one keeps the deal moving:

PILOT-TO-CONTRACT TERMS (one page)

1. Parties and champion: [Customer], sponsor [name, title]; [Startup], owner [founder name].
2. Problem: [one sentence in the customer's words].
3. Value equation: [baseline metric] x [expected improvement] = [$ value per year].
4. Success metrics: [metric 1 with target], [metric 2 with target], measured by [method].
5. Scope: [e.g. 1% of ticket volume / one region / one team of 10 users].
6. Customer commitments: named team of [n] people; data access by [date];
   start date tied to live project [name]; check-ins every [2 to 3] days.
7. Duration: [7 to 30] days from first live use (not from signature).
8. Pilot fee: $[amount] (kept within the sponsor's own signing authority).
9. Conversion: at the end of the pilot, converts to a 12-month subscription at
   $[annual price] unless the customer opts out in writing within [30] days.
10. Post-pilot review: meeting booked for [date] with [economic buyer] to review results.
11. In parallel: security questionnaire and SOC 2 report sent on [date];
    master agreement redlines started on [date].

Five habits that tend to make it work:

• Tie every metric to the value equation. The pilot should prove the specific claim the price rests on, for example that the tool resolves 20 percent of queries on a sample of 1,000.
• Reduce the champion's risk, not the commitment. Back-test on historical data, run side by side with the current process, or take a small slice of volume or one region, so a failure doesn't land on your sponsor.
• Ask for money and people. A fee makes the customer take the pilot seriously. Accept a smaller one if it fits a corporate card limit your champion can approve alone.
• Shrink time to first value. Track it like a north star metric. Skip integrations that need customer engineering time during the pilot, and use spreadsheet imports if that gets you live in days.
• Report opt-out revenue honestly. Tell investors which recurring revenue is still inside an opt-out window.

Clear procurement and own implementation

Procurement surprises founders who don't ask early. In the first meetings, find out how the company buys software and who signs off. Then start everything that can run in parallel, like the security questionnaire, while the pilot is live.

Keep contracts simple. Put timelines and scope in the order form rather than the master agreement. And lean on your champion, who can't solve their problem until procurement is finished either.

Four tactics that often shorten the cycle:

• Start certifications early. SOC 2 (plus HIPAA or ISO 27001 where relevant) can delay a deal by months if you begin after the buyer asks.
• Decide your redline limits in advance. Many founders concede anything that is an annoyance rather than company-ending, and hold firm on unlimited liability and any clause that hands over their IP. Legal often wins by exhaustion, so settle your position before the markup arrives.
• Leave procurement a win. Procurement needs to win something, which is one reason enterprise list prices carry large discounts. Plan the concession you can afford.
• Show up and set a date. Visiting the customer in person helps, as does agreeing a target close date with your champion, knowing it will probably slip.

Implementation is part of the sale

Pete Koomen, the Optimizely co-founder who now advises founders at Y Combinator, has described closing six-figure deals and finding at renewal that some customers hadn't run a single test. The marketing buyer couldn't get engineering to install the product.

The fix was a written implementation plan agreed with both teams before signing, and a founder project-managing the rollout like an internal launch. The gap can be large: one company in Blomfield's account had signed $4 million of contracts but implemented less than $2 million of them.

A signed contract nobody uses is a churn notice with a delay on it. Delivered value is what drives renewals and net revenue retention.

Enterprise sales pipeline math: a worked example

Work backward from your revenue goal. In this illustrative example, suppose you want $600,000 of new annual recurring revenue in the next twelve months at an average contract value of $60,000. That is 10 contracts.

Assume these stage conversion rates (illustrative; replace them with your own after 20 or 30 deals): 50 percent of first meetings qualify, 60 percent of qualified deals reach a successful tailored demo and technical validation, 50 percent of those start a paid pilot, and 70 percent of pilots convert.

target_arr, acv = 600_000, 60_000
rates = [0.5, 0.6, 0.5, 0.7]    # meeting->qualified->validated->pilot->contract
win = 1
for r in rates:
    win *= r
deals = target_arr / acv          # 10.0
meetings = deals / win            # 95.2
print(win, deals, round(meetings, 1))

The combined win rate from first meeting is 0.5 x 0.6 x 0.5 x 0.7 = 10.5 percent, so 10 contracts need about 95 first meetings. Stage by stage: about 14 to 15 paid pilots (10 / 0.7 = 14.3), about 29 technical validations (14.3 / 0.5), about 48 qualified opportunities (28.6 / 0.6) and about 95 first meetings (47.6 / 0.5).

Timing makes it tighter. If a deal takes six months from first meeting to signature, those meetings have to happen in the first 26 weeks of the year, about 3.7 a week. If it takes nine months, the window shrinks to about 13 weeks and the pace doubles to about 7.3 a week.

The same rates can weight the pipeline you already have. Midway through the year, 6 live pilots (70 percent each), 8 deals in validation (0.5 x 0.7 = 35 percent) and 12 qualified deals (0.6 x 0.5 x 0.7 = 21 percent) are worth $252,000 + $168,000 + $151,200 = $571,200 of weighted ARR.

Set that against the $5-to-$1 rule. $600,000 is roughly one account executive's annual target at $120,000 of total pay, which is why this is still founder work. Instrument each stage from the first deal, because conversion rates you don't measure are hard to improve.

Common enterprise sales mistakes

The ones we'd steer you away from:

• Endless free design partnerships with a famous logo and no end date or success metric.
• Talking to whoever answers instead of the people with the problem, the budget and the authority.
• Pitching before listening on the first call.
• Feature tours instead of a demo built as a story about the customer's user and problem, ideally on their own data.
• Underpricing, or pricing from cost rather than value.
• Building every feature one customer asks for. Listen closely, but be wary of copying requests straight into the roadmap. Many founders do better selling one narrow wedge to ten similar customers before broadening.
• Discovering the procurement process at the end, including security certifications you don't have yet.
• Treating the signature as the finish line rather than habitual use.
• Seeming desperate, which buyers notice and use.

This is the stage the GTM Accelerator was built for: 1752vc's 12-week, hands-on program for founders with a validated product and early traction who now need to sell, recruit, fundraise and build traction. Because it is remote and self-paced, you can work through pilot design and weekly pipeline reviews while real enterprise deals are in motion.

"Why not just hire a great enterprise rep?"

It's a fair question. Experienced account executives know procurement cold, have run hundreds of deals and can open doors a first-time founder can't. Your time is expensive, and the product needs you too.

But Early on, the sale is also research. A hired rep can close a deal you understand. It's much harder for them to discover what the deal should be: which buyer, which price, which pilot. That discovery tends to happen in the founder's head, on the call, and it's hard to hand off before the motion repeats.

Where we land on the enterprise sales process

Our take, with room for your product and market:

• Process weight. Keep it light until the motion repeats: ask questions, map the people, run short paid pilots. MEDDPICC, whose MEDDIC root grew up in a sales organization of about 300 reps at PTC, earns its place once you hire account executives who need a shared language for forecasting.
• Speed. Short cycles tend to win more often. The classic BANT test (budget, authority, needs and timing) and fast, rough proposals push in the same direction as short paid pilots and early qualification.
• Rep-free buying. Buyers say they want to research on their own, and the Gartner data backs that up, but deals that combine digital tools with a rep go better. Publish a one-pager, security documentation and a sandbox for the buyer's own research, and still run the deal personally.
• Bottom-up versus top-down. Serious operators disagree here because both work, in different products. Users can pull the product in when a team can adopt it alone; top-down selling usually fits when adoption needs coordination. Early on, hand-holding your first accounts is worth the time, as our guide to do things that don't scale explains.

The bottom line

Enterprise sales rewards founders who treat each deal as a small project with a named owner at every step, not as a relationship that will close itself.

Enthusiasm fills a pipeline.

Signatures, and usage, empty it.

Key takeaways

• Before product-market fit, the founder usually runs enterprise sales; hiring a salesperson too early often disappoints.
• It helps to treat each account as a system of people: find a senior champion, name the economic buyer and map every approver early.
• Consider pricing from a written value equation, commonly a quarter to a half of the value delivered, with cost only as a floor.
• Short paid pilots and annual contracts with a 30 to 60 day opt-out, both tied to agreed metrics, often work better than open-ended design partnerships.
• Starting security and legal work in parallel and project-managing implementation pays off, because renewals depend on real usage.
• Doing the pipeline math backward from your ARR goal shows roughly how many first meetings you need each week.

Frequently asked questions

How do you sell to large enterprises as a startup?

A common path is to start with a sharp hypothesis about who has the problem, reach a senior person who owns it, and spend the first call asking questions rather than pitching. Then build the value equation with your champion, run a short paid pilot against agreed metrics, start security and legal review early, and manage implementation yourself, offering what large vendors cannot: direct founder access and fast fixes.

Should a startup offer a free pilot to an enterprise customer?

Occasionally, for the first one or two customers, but free pilots tend to drag on with low engagement from the customer's team. In our view, a paid pilot of a few weeks with clear success criteria gets more commitment. Once you have references, many founders prefer an annual contract with a 30 or 60 day opt-out that converts automatically if the customer is happy.

What is MEDDPICC in sales?

MEDDPICC is a deal qualification checklist: Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion and Competition. It grew out of MEDDIC, created by Dick Dunkel at PTC in 1996 with Jack Napoli. Founders can use it as a quick test of how well they understand each enterprise deal before relying on a forecast.

What is a champion in enterprise sales?

A champion is the person inside the customer who feels the problem, wants your product and sells it internally when you are not in the room. Strong champions are senior enough to influence budget, share how the company buys software and help unblock legal and procurement. It often helps to treat your champion almost like a co-founder inside the account, and give them the materials to argue your case.

How can a startup speed up enterprise procurement?

One approach is to ask in the first meetings how the company buys software and who signs off, then start the security questionnaire, SOC 2 report and contract review in parallel with the pilot. Use simple standard contracts, keep timelines in the order form, concede on minor redlines, and hold firm only on company-ending terms such as unlimited liability or giving away your IP.

Sources

• Y Combinator: Enterprise Sales for Founders (Pete Koomen)
• Y Combinator: The Sales Playbook for Founders (Tom Blomfield)
• Y Combinator: How To Price For B2B (Tom Blomfield)
• Y Combinator: Enterprise sales for hackers (Ryan Junee)
• Y Combinator: How to Start a Startup: Building for the Enterprise (Aaron Levie)
• Y Combinator: How To Influence Decision Makers (Dalton Caldwell and Michael Seibel)
• Y Combinator: How to choose a metric and set your KPI (Michael Seibel)
• Gartner: The B2B Buying Journey
• MEDDICC: Who Created MEDDIC? The History Behind the Framework
• First Round Review: The Most Surefire Way I've Found to Win Enterprise Deals (September 2016)
• Common Paper: Standard Contracts