How do you sell to enterprise as a small startup?

The fastest path to your first enterprise contract is to stop competing on the dimensions large vendors compete on—feature completeness, brand, and support SLAs—and instead compete on the one dimension they can never match: personal obsession with a single customer's problem. Win one customer deeply before you try to win many customers broadly. That sequence is not just tactically smart; it is the only sequence that works.

Why acting 'big' kills your early enterprise deals

Most founders instinctively try to look larger than they are when approaching enterprise buyers. They build polished decks, hide their team size, and use formal sales language they associate with the big vendors the buyer already knows. This is exactly backwards. Garry Tan's observation—that founders fall into a trap of imitating even the flaws of big companies, like indifference to individual users, in the name of seeming 'professional'—captures the mistake precisely. Enterprise buyers at the working level are not looking for another large vendor; they already have several and are frustrated by all of them. What they are quietly desperate for is someone who will actually listen and solve the specific problem they described, not the generic version of that problem.

Your smallness is a competitive advantage if you deploy it deliberately. A VP at a Fortune 500 company cannot get their current ERP vendor on a call with a product engineer by Friday. You can arrange that call in two hours. You can ship a configuration change the same week they ask for it. You can send a founder—not a customer success manager reading from a script—to their office. These are not consolation prizes for lacking resources; they are capabilities that large vendors have permanently engineered out of themselves. The moment you start hiding them, you throw away your only asymmetric edge.

The single-customer consulting strategy that seeds real product-market fit

Paul Graham's advice for B2B startups is to take attentiveness to an extreme: pick one user and treat the engagement as if you were a consultant building exclusively for them. This is not a sales tactic dressed up in product language—it is the fastest feedback loop available to an early-stage team. When you are that close to one enterprise buyer, you learn things you would never discover through surveys, demos, or generalized market research. You find out which internal stakeholder actually controls the budget versus who shows up to meetings. You discover that the compliance requirement everyone mentions in passing is actually a hard blocker, not a nice-to-have. You learn what the buyer's boss is measured on, which is usually different from what the buyer tells you they need.

The practical mechanics: schedule a weekly call with your champion at a specific working level, not just the economic buyer. Sit in on at least one internal meeting where your product's use case comes up naturally. Ask to shadow someone doing the job your product touches for a half-day. Most vendors never ask for this access, so most buyers will say yes. What you build from that depth of exposure will not only solve their problem—it will solve it in the exact vocabulary, workflow, and integration context they actually operate in, which is what makes a small startup's solution feel more enterprise-ready than a large vendor's more technically complete product.

Getting in the door: the cold contact problem

The hardest part of enterprise sales for a startup is not closing; it is getting a genuine first conversation with someone who has both the authority to buy and the problem you solve. Cold outbound to generic inboxes does not work at any meaningful rate. The reason is structural: enterprise buyers are already managing vendor relationships with dozens of companies, and their default response to unsolicited contact is to route it to a junior gatekeeper whose job is to say no efficiently.

The paths that actually create access are narrower but far more reliable. First, work backward from any existing relationship—a former colleague at the target company, a mutual investor contact, a founder in your YC or accelerator batch who has sold into the same vertical. A warm introduction that carries a specific endorsement ('they built exactly what you described needing last quarter') gets you a real meeting. Second, build in public in the buyer's community before you need to sell. Writing a detailed technical post-mortem, speaking at the industry conference where your buyers gather, or publishing a small free tool that solves a related problem puts you in front of buyers in a context where they initiated contact. Third, design your initial outreach around a specific insight about the buyer's situation—reference a public filing, a product announcement, or a regulatory change that creates urgency for them now. The goal is to trigger a 'how did you know about that?' response, not a 'thanks, I'll forward this to procurement' response.

What does not work: partnerships with large companies as a growth channel in early stages. The hope that a big partner will funnel enterprise buyers to you consistently ends in a long pilot that goes nowhere, because the partner's sales team has no incentive to carry your product when they already have a quota on their own. Use partnerships for credibility signals once you have traction, not as a substitute for direct sales before you have it.

Structuring the deal to actually close

Enterprise deals stall because risk is asymmetric for the buyer. If they choose the wrong vendor, there are consequences—cost, disruption, political exposure. Your job in deal structure is to remove as much of that risk as possible without removing revenue from the transaction. A paid pilot with clearly defined success metrics agreed to in advance is the most useful instrument here. It is not a free trial (which signals low confidence in your product) and it is not a full contract (which the buyer's procurement team may slow-walk for months). A paid pilot of defined scope, with specific criteria that trigger conversion to a full contract, gives the champion internal cover and gives you a forcing function to demonstrate value on a timeline.

Come to the first pricing conversation with a number, not a question. Asking enterprise buyers 'what's your budget?' signals inexperience and makes them lower the ceiling before negotiations start. Research comparable contracts in the space—often discoverable through public procurement databases, competitor pricing pages, or founders who have sold similar products—and anchor with a number you can defend with a value argument. Enterprise buyers respect sellers who know what their product is worth; they exploit sellers who seem uncertain about it.

Finally, identify the internal champion early and invest in making them successful, not just informed. They will sell your product internally in every meeting you are not in. Give them clear talking points, competitive differentiation they can use against objections, and a narrative that connects your product to something their organization already cares about. The champion who can walk into their CFO's office and explain the ROI without calling you first is the champion who actually gets the deal done.

When to scale the motion and when to stay manual

Many founders rush to build a repeatable enterprise sales process before they have the evidence that one exists. The result is hiring sales reps to replicate a motion that was never really a motion—it was a founder personally leveraging unique relationships and product knowledge that a new hire cannot access. The pressure to scale is real, but scaling before you can describe your sales process as a series of concrete, repeatable steps is how early-stage startups waste their first sales headcount.

The signal that you are ready to start scaling is not a number of customers—it is the quality of your ability to predict what will happen next in a deal. If you can reliably say 'at this stage, the champion will need to present to these three stakeholders, and the most common objection will be X, and here is how we address it,' you have a repeatable motion. Until you can say that from experience—not from what you expect will happen—stay in founder-led sales and treat every deal as a learning opportunity, not a revenue transaction. The revenue matters, but the pattern recognition you are building in those early deals is what makes your company able to grow enterprise sales at all.

“Pick a single user and act as if they were consultants building something just for that one user.”

— Paul Graham, source

The one thing to do

Find one enterprise buyer with an acute, specific problem, treat them like a consulting client until you have solved it completely, and document everything you learn before you try to repeat it.

Frequently asked questions

Should a startup offer free pilots to enterprise customers to get in the door?

Paid pilots with defined success criteria are almost always better than free ones. Free trials signal uncertainty about your product's value and give the buyer no skin in the game, which means they often don't prioritize the evaluation. A small paid engagement—even at a below-market rate—creates accountability on both sides and makes internal champions take the process seriously.

How do you handle procurement and legal delays in enterprise deals?

Start the procurement and security review process earlier than feels necessary—ideally before the champion is fully sold—because these processes run on their own clock regardless of how well the demo went. Ask early in the sales cycle what the typical vendor approval process looks like, who owns it, and what documentation they will need. Surprises in procurement are usually the result of not asking those questions soon enough.

Is it a mistake to pursue enterprise deals before you have a polished product?

Not if you are transparent about it and you are selling to a buyer who has the specific problem you solve. Enterprise buyers who participate in early-stage partnerships often get pricing leverage, custom features, and direct access to founders in exchange for tolerating some roughness in the product. The mistake is hiding the early-stage reality rather than making it part of the value proposition.

How many enterprise customers do you need before you should hire your first sales rep?

The number matters less than whether you can describe your sales process in repeatable steps a new hire could follow. Most founders should close at least three to five enterprise deals themselves before hiring, because the process of doing it personally is what reveals what the repeatable steps actually are—as opposed to what you think they should be.

Sources

More playbook answers · Growth Prophet home