Building an Enterprise Sales Team

There is a common scenario. The company has closed a few large customers, the founder is drowning in sales work, and an investor has said “build the sales engine.” A seasoned sales director is hired, then two account executives, then an SDR. Six months later the picture is this: the director says there is nobody to feed the pipeline, the founder says nothing is closing, and both are right.

The problem is not the people. What they are selling has not yet become a playbook, so nobody knows what to repeat. An enterprise sales team is not a capacity investment, it is a knowledge transfer investment. If you have nothing to transfer, the headcount is just a cost line.

When you need it

The founder or first seller should have closed at least five or six deals with the same customer profile, a similar persuasion story and a similar cycle length. The word “similar” matters. If every deal closes with different packaging, pricing and buyer sets, you do not have a process yet, you have a series of exceptions.

The second signal is the founder's time becoming the bottleneck. Inbound demand goes unserved and follow-ups slip, while the close rate is solid. That is the real reason to scale sales: knowing it works and being unable to keep up.

Signs it is too early: average contract value does not carry the cost of the team, the path to the decision maker differs with every customer, or you cannot answer “is our sales cycle one month or eight?” Also, if the founder is not ready to hand sales over, meaning they must join every call, building a team only creates a waiting room.

What most teams miss

Teams see the roles as an org chart: SDRs open doors, AEs close, CSMs renew. The chart is right, but the order is wrong. Roles do not come before the process, they come out of it.

The real work is getting the sale out of the founder's head. Which first sentence earns a meeting? Which question surfaces the real decision maker? Which objection shows up at which stage, and what resolves it? Until that is written down, a new seller will apply their own habits, not the founder's instincts.

What decides an enterprise sales team is not the hiring plan, it is whether you can write down the founder's instinct.

There is also logic behind splitting roles. Separating SDR and AE is not about specialization, it is about time: keeping expensive AE hours from going to anything other than closing. An AE who cannot fill their own pipeline and a company with no SDR at all are two faces of the same problem. But if you hire an SDR just to book meetings the AE does not accept, volume goes up and quality goes down.

The playbook

1. Document founder-led sales

Write up the last five won and three lost deals in the same template: who bought, who blocked, what the trigger event was, which competitor it was compared to, why we won or lost. The output: a one-page ICP definition, a buyer map and answers to the three most common objections. This document is the most valuable thing you can hand the first AE.

2. Break the process into stages with exit criteria

Define pipeline stages by buyer actions, not seller actions. “Demo delivered” is a seller action; “customer opened the technical evaluation to their own team” is a buyer action. Write an exit criterion for every stage. The output: a funnel in the CRM where everyone means the same thing. Without it, the revenue forecast is not a forecast, it is a wish.

3. Train the first AE alongside the founder

The first seller should not be someone who memorizes a closed script, but someone who closes alongside the founder and improves the process. For the first three months, join calls together, listen to recordings, and spend each week on a single objection. The output: the first deal that closes without the founder. That is the day you can talk about the next hire.

4. Add the SDR once an outbound channel works

Have the AE or founder run outbound first and find out which segment, message and channel produce meetings. The SDR comes to scale that proven message. The target metric is not just meetings booked but the share the AE accepts and that turns into pipeline.

5. Separate the CSM from sales but tie them to the same goal

Bring customer success in before the first renewal date. Onboarding, usage depth and expansion opportunities belong to the CSM, and incentives should include a share of renewal and expansion revenue. The output: an owner for every customer and a rhythm that starts 90 days before renewal.

6. Run a weekly pipeline rhythm

One pipeline review per week: deals entering, advancing, stuck and lost. Forecast with historical conversion rates per stage, not the seller's gut feeling. The output: a quarterly forecast and a record of how far reality diverged.

What to measure

• Sales cycle length and stage conversion rates: They show where you stall. Leading indicators, and the basis of any forecast.
• New AE ramp time: Months to first close measures how transferable your playbook is.
• Quota attainment distribution: If most of the team hits quota, the system works; if only one or two do, the problem is the system.
• Net revenue retention (NRR): A lagging but honest read on the quality of what was sold.

Pitfalls

Hiring the director first. A seasoned executive arriving where no process exists either brings their old playbook or wastes time. First a few AEs, then the manager.

Setting quota from the forecast. Give a new team a quota based on the company target and you demoralize them in the first quarter. Use ramp periods and real historical data.

Treating the CSM as support. A CSM who only closes tickets will not save a renewal. You need a role that owns expansion and risk signals.

Start this week

1. Write up the last five won and three lost deals in one template and mark what they share.
2. Review your CRM stages and write an exit criterion for each one as an observable buyer action.
3. Listen to the recordings of two upcoming sales calls with a teammate and list the objections.