पाठशाला Pathshala · वृद्धि Vṛddhi, Growth · Lesson 23 · Scale

The sales playbook: from heroics to repeatability

While the founders sell, the method lives in their heads. A playbook writes down the customer, the pitch, the objections and the process so that a new rep can close a deal inside ninety days.

Pathshala, The Founder Library · 11 October 2026 · 7 min read

Two hands pass a relay baton against a bright sky. — Photograph: BOOM 💥 Photography · Pexels

In most Indian startups that sell to businesses, the first crore of revenue is closed by a founder who knows every buyer by name and every objection by heart. The second crore is supposed to come from salespeople who know neither. The gap between the two is a document nobody has written.

Heroic selling is the right way to start: the [first hundred calls](/library/founder-led-sales-first-hundred-calls) teach the founder what the market wants. It stops working the day the founder hires, because heroics cannot be handed over. Steli Efti puts the turn in one line in his Stripe Atlas AMA: eventually you have to start selling in ways that you could teach somebody else to do. The playbook is that teaching, written down. This lesson builds one in four parts, the customer, the pitch, the objections and the process, and then measures it the only way that matters: how fast a new rep closes.

When to write it

Too early and the playbook describes guesses; too late and the first reps learn by copying whoever sits nearest. Pete Kazanjy’s Founding Sales gives two tests. The founder should have sold a few dozen deals personally. And the win rate on qualified opportunities should be steady, in what he calls the typical good range of 15 to 30 per cent; below that, around 10 per cent, the messaging, product or pricing needs work before anyone is hired to repeat it. When both are true, write the playbook in the six weeks before the first class of reps arrives. Efti’s advice is to hire that class as two or three people at once, so that the playbook rather than one person is being tested.

Keep it short enough to be read and specific enough to be used: twenty to thirty pages in a shared document, with links to recordings, the CRM and the pricing sheet. A playbook that a new rep reads once in the first week and never opens again has failed. The test is whether a rep in month two goes back to it before a hard call.

Part one: the customer, as a filter

The first section answers who to sell to, and who not to. Write the [ideal customer profile](/library/ideal-customer-profile-on-one-page) as a filter a rep can run against a list without asking anyone: industry, size by revenue or headcount, the systems they already use, the trigger events that make this quarter the right one, and the disqualifiers. Add the buying roles from your closed deals: who feels the pain, who signs and who can stop the deal. A typical Indian mid-market software sale has a user, a department head and a finance controller who reads the contract; a typical SME sale has an owner who decides everything and a CA whose opinion the owner asks for.

Then list five closed customers who fit the profile perfectly, with the reason each one bought in their own words, and three deals the founders lost or should never have chased, with the reason. New reps learn the profile faster from cases than from rules. Kazanjy’s stages of a sales organisation make the same point from the other side: the test of the first account executives is that they close customers who fit the profile at least as efficiently as the founder did.

Part two: the pitch, discovery first

Kazanjy’s chapter on pitching sets the order of a good first meeting: quick pleasantries, then discovery, typically the first five to ten minutes, then the presentation, a live demo, proof points and pricing. The most important thing discovery establishes is whether the prospect has the business pain the product exists to solve. Write the pitch section in that order. List the discovery questions that worked for the founders, keep them as a living list a future rep can read, and for each one note what a good answer and a disqualifying answer sound like.

Then write the narrative as chapters, not as a script: the problem, what it costs, how buyers solve it today, why that falls short, what the product does differently, proof from a customer like this one, and price. Record the founders running the pitch well, and record them running it badly. A rep who can deliver each chapter in their own words, in the buyer’s language, and who knows which chapter to skip for which buyer, will out-sell one who memorised a deck.

Part three: every objection, with the answer that worked

Objections are the part of the founder’s knowledge most worth writing down, because they repeat. Kazanjy sorts them into generic ones, authority, need, fear of change, timing, price, budget and reluctance; versions specific to your product, including missing features; and competition. His method for each is to find the real blocker first, with a direct question such as what specifically is blocking us from progressing right now, then answer it on its merits with business arguments and proof, and then return to the close. For fear of change his advice is to do the actual arithmetic of what staying with the status quo costs.

Build the objection log from the CRM and the founders’ memories: one row per objection, the words buyers actually use, how often it comes up, the answer that worked, the proof to send and the deals where it was handled well, with links to recordings. In India add the objections the founders have learnt to expect: we will think about it after the financial year closes, our CA has to see this, can you match the price of the local vendor, we already use Tally for this. Update the log monthly; a new objection appearing in three deals is a signal about the market, not only about the reps.

Part four: the process, as stages with exit criteria

Define each stage of the pipeline by what must be true to leave it, not by what the rep did. A lead becomes a qualified opportunity when discovery confirms the pain, the budget owner is known and there is a reason to act this quarter. An opportunity reaches proposal when the buyer has seen the demo and agreed the scope. Kazanjy calls the written version of this the rules of engagement: qualification criteria, who owns a lead at each step, and how it is handed between prospecting, closing and customer success, kept in a document all reps can reach and updated when the process changes. In his chapter on onboarding he states the CRM rule bluntly: if it is not in Salesforce, it does not count.

Add the numbers a rep should expect, taken from the founders’ own pipeline: how many first meetings a week, the conversion at each stage, the length of the cycle, the average deal. Kazanjy’s worked example is a rep running five new demos and ten follow-ups a week, about twenty new opportunities a month. With those numbers written down, a rep in week six can see whether they are behind and why, and the manager can see which stage is failing.

Ninety days to a first close

Kazanjy’s onboarding chapter is direct about the cost of skipping this: resist the temptation to shortcut onboarding. His design is a boot camp of one to two weeks, preceded by about ten hours of pre-work over two weeks, recordings of excellent and terrible calls, demo videos and readings. In the boot camp each rep presents every chapter of the pitch to the group and then spars in pairs, one as buyer and one as seller. Then the rep goes live on easy deals first, inbound leads with a high chance of closing, while the manager listens to calls. He notes that traditionally 30 to 50 per cent of each hiring class is lost within six months, which is the cost a good onboarding is meant to cut.

An experienced craftsman shows a young apprentice how to handle a part at a workbench. — A trade is passed on by showing, drilling and correcting. Sales onboarding that works runs the same way. Photograph: Andrea Piacquadio · Pexels

Set the target as a first closed deal within ninety days of joining, and the ramp to full productivity as short as the sales cycle allows. The figure shows why the target matters: the rep’s full cost is paid from the first day, and every month spent ramping is margin the company does not earn.

A founder who sells well is an asset. A founder whose selling is written down is a company.

At the defaults, a rep who takes six months to reach ₹4 lakh of monthly bookings, at 70 per cent gross margin and a full cost of ₹2 lakh a month, pays back their cost only in month nine, and the first year leaves about ₹2.6 lakh of margin over cost. Cut the ramp to three months and the crossing comes in month four and the first year leaves about ₹6.8 lakh. The ₹4.2 lakh difference, for every rep in every class, is what a good playbook is worth, and it is larger than most founders expect.

The quarterly playbook review

Monthly, for each rep in their first six months: days to first meeting, first proposal and first close; conversion at each stage against the founders’ figures; the three objections they lost deals on. Quarterly, the founders and the sales lead spend half a day on the document itself. Update the profile with the last quarter’s best and worst customers. Add every new objection that appeared in three or more deals, with the answer that worked. Replace the recordings with better ones from the reps. Recompute the stage conversions and the cycle length from the CRM. Then check the one number that says whether the playbook works: the median days from a rep’s joining date to their first closed deal, for the last class against the class before. If it is not falling towards ninety, find the stage where the new reps stall and rewrite that section first.

The rupee figures are illustrations; the method and the ratios are from the sources below. Write the objection log this week.