What You Get in a NELL Sales Playbook

A real sample, walked screen by screen -- so you know exactly what lands before you pay for it.

What You Get in a NELL Sales Playbook

A Sales Playbook is one tab inside a NELL Pro Builder brief. It is not a template pack you fill in yourself. It is a full B2B sales motion: MEDDIC qualification, a 30-minute discovery script, five sales stages with SLAs, pipeline math wired to your actual ACV, a forecasting method, and CRM hygiene rules -- all built around one real sample product and its buyer.

Pro Builder is sales-led and starts around $999/mo. What follows is that exact sample, walked screen by screen, so you know what you are buying before you pay for it.

Earlier than this? Start with a $49 DeepValidate report, get a working product and a paying customer, then come back for the sales motion. This tab assumes you already have both.

What this walkthrough covers

Where the Sales Playbook sits in the brief

The validation gate -- what the report will not pretend to know

The qualification framework, and why MEDDIC over BANT here

The MEDDIC letters, routed to a real insurance buyer

The discovery playbook -- pre-call prep, the 30-minute call, the question bank

Sniff tests to disqualify fast, and the demo-handoff gate

Five sales stages with SLAs, pipeline math, and the weekly funnel

Forecasting, the loss-reason taxonomy, and CRM hygiene rules

NELL's rationale and the brutal truth

The refine bar -- re-aiming the whole motion in one click

Who this is for

Three quick gates, because the wrong reader wastes an hour here.

Pre-revenue or still validating the idea. This is not your starting point. Begin with a DeepValidate report and come back once you have a working product and a buyer who has paid.

Built product, early revenue, founder still doing the selling. This is exactly the tab. You are trying to turn a motion that lives in your head into one someone else could run.

Already running a trained team on a disciplined CRM. You will read this as an audit more than a revelation. Still useful, lower slope.

The product this sample was built for

Every recommendation below is routed to one specific product and one specific buyer. Read the plan without that context and the AMS names, the $400/mo, the DOI letters all read as noise. So hold this in your head before the first screenshot.

What it is

A per-agent, per-state tracker for continuing-education (CE) credits and license renewals, built for independent insurance agencies. Picture the spreadsheet an ops manager keeps so no producer writes business on a lapsed license, turned into software that watches the deadlines for them.

Who buys it

US independent agencies with 20 to 200 producers across three or more states. The principal (or COO) holds the budget. The ops or compliance manager feels the pain and champions the tool. IT, or an outsourced MSP, is the security gate. That split, where the champion is not the buyer, shapes the entire playbook.

The pain

Manual reconciliation of CE deadlines and renewal dates, roughly five to fifteen hours a week. Miss one and it costs real money: a DOI letter, a state fine, or a producer selling on a dead license.

The gap it aims at

AgentSync serves carriers. Sircon and Agenzee serve single agents. The 20-to-200 mid-market sits unserved, between a spreadsheet and enterprise tooling. That is the wedge.

The stage

Built and live. Two agencies pay $400/mo. A third has been circling back for two months. Expected ACV is $4,800 to $18,000, on a 45-to-90 day cycle. Every number in the playbook traces back to these facts.

Hold that state in mind: two customers, one stalled third deal, a champion who is not the buyer. The whole playbook is an answer to that exact situation. When a recommendation looks oddly specific, it is because it was written for this founder, not for founders in general.

The walkthrough

Nineteen screens, in the order the report presents them. Each one: the question a good operator would ask, the answer up front, the real screenshot, then how to read it.

Where does the Sales Playbook sit?

It is the execution layer, not the strategy layer. The Sales Playbook is one tab in the Build & Execute stage of a Pro Builder brief, after GTM Strategy, Outreach, and Lead Gen. It assumes those upstream tabs exist and picks up where they leave off. You already know who to sell to. Here is how to actually sell.

OPERATOR’S READ

If you are shopping for a one-off sales script, this is the wrong purchase. The playbook leans on the buyer definition and channel work done in the tabs before it. You buy the brief, not the tab.

Validation gate: does the report trust its own numbers?

The first thing a good sales playbook does is tell you where it is guessing. Before any tactics, NELL runs a validation gate and fails some of its own checks. It flatly says no Launchpad validation data was passed in, that two paying customers at $400/mo is real revenue but not the same as validated willingness-to-pay across the 20-to-200 band, and that the pipeline math below should be treated as a hypothesis until three more discovery calls confirm the ACV and cycle time.

OPERATOR'S READ

A tool that tells you where its confidence is thin is worth more than one that fakes certainty. The decision this protects is real money: do not pour budget into outbound built on an ACV band you have not proven yet. Most 'AI sales playbooks' would have skipped straight to the tactics and let you find the hole in production.

Qualification framework: which methodology actually fits this deal?

Pick the wrong framework and you kill velocity. NELL picks MEDDIC and explains why: the ACV band is $4,800 to $18,000 on a 45-to-90 day cycle, sold to a three-person committee. BANT is too shallow for a compliance sale where the champion is not the economic buyer. MEDDPICC adds Paper Process and Competition friction that would slow a deal this size. So MEDDIC, with a named fallback to SPICED if it proves too heavy.

OPERATOR'S READ

The 'Test in 7 days' line is the tell. It hands you a falsifiable experiment (run MEDDIC on the stalled third deal, see if you can fill Economic Buyer and Decision Criteria in one call) instead of a doctrine to memorize. That is the difference between a playbook and a blog post.

Metrics: how do you make the buyer quantify their own pain?

This is the M in MEDDIC, and it sets the pattern for every letter. Each letter is broken into three columns: the exact questions to ask, the qualified signals that mean it is landing, and the red flags that mean it is not. For Metrics, the questions push the buyer to name hours lost per week and a dollar figure on a past incident. The red flag is a buyer who says 'we manage it fine' and cannot produce a number.

OPERATOR'S READ

That question / signal / red-flag structure is the reusable unit. Lift it straight into your CRM as a qualification scorecard. The whole point is that your rep does not have to be you to know whether a call went well.

Economic buyer: are you selling to the person who can actually sign?

For a $10K-plus decision, the champion is usually not the buyer. The ops manager feels the pain, but the principal signs. NELL's questions are written to surface that gap early: walk me through how a software decision gets approved here, who signs, has the principal seen a demo of anything like this. The red flag it names is the champion who says 'I can approve this' at $10K when they almost never can.

OPERATOR'S READ

This is where the whole brief's brutal truth lives, so hold it. The founder's two wins came from agencies where the champion happened to also be the principal. Every deal from here is the harder shape, and this section is the fix. Keep reading to the last screen.

Identify pain: is there a compelling event, or just interest?

No compelling event, no deal, no matter how warm the call feels. The I in MEDDIC. The questions are built to surface a date, not a vibe: what happened in the last 90 days that made you take this call, is there a renewal wave or a state audit driving urgency, if you do nothing for another year what is the worst case. The red flags are 'just exploring' and 'sometime next year'.

OPERATOR'S READ

Compelling event is the single most skipped part of qualification, and the reason pipelines fill with deals that never close. If the buyer cannot name a trigger, the report tells you what to do with them (nurture, not forecast) rather than letting you count them.

Pre-call prep: what do you do before you ever dial?

Seven checks that turn a cold call into a call where you already know their exposure. Pull the agency's producer count from the NIPR public search to confirm the 20-to-200 band. Count states on the website footer. Identify the AMS from job postings. Google the agency name against DOI consent orders to surface prior enforcement. Load the two redacted customer stories as proof points before you dial.

OPERATOR'S READ

This is the line between spray-and-pray and showing up already knowing the buyer's compliance risk. Notice it uses only public sources (NIPR, state DOI, LinkedIn, job posts) so a founder with no data budget can run all of it today.

The call itself: what does a good 30-minute discovery sound like?

Minute by minute, the script fights your instinct to demo too early. Open (0 to 3) sets a one-sentence agenda and transfers ownership of the call. Pain discovery (3 to 10) runs a strict 80/20 listen/talk ratio with an explicit 'do not pitch'. Solution framing (10 to 20) describes the product only in the buyer's own words and shows two or three screens, not a 20-slide deck. Objection and commit (20 to 27) draws on the rebuttal bank and drives to a calendared next step. Close (27 to 30) recaps in the buyer's language and confirms email.

OPERATOR'S READ

The '80/20 listen/talk' and 'do not pitch' instructions are the valuable part. Founders lose discovery calls by demoing in minute four. This script physically slots the demo into minute ten, after the pain is on the table, so the demo lands on a problem the buyer just named out loud.

The question bank: do you get the actual words, or just categories?

Fifteen scripted questions, each with the reasoning and a follow-up for vague answers. Not 'ask about pain' but 'walk me through how you currently know that a producer's CE is due in 45 days, what is the workflow'. Under each question is a 'Why' line explaining the mechanism, and a follow-up prompt for when the buyer gives you a soft answer. They are grouped by MEDDIC letter so you know which gap each one fills.

OPERATOR'S READ

The 'Why' line is what makes these portable. You are not memorizing a script, you are learning the mechanism, so you can improvise on a live call and still be filling the right MEDDIC box.

Budget: how do you make a $10K price look small?

You anchor it against the cost of the alternative, and the report hands you the anchor. The budget questions surface whether this comes from a real budget or a 'we will find it' budget, then set the reference point: if you hired a part-time compliance coordinator to do this manually, what would that cost you fully loaded. That answer sits around $40,000 to $60,000 a year, which makes a $10K-to-$18K tool look obviously cheap.

OPERATOR'S READ

Price is relative, always. A number is only expensive next to a smaller number and cheap next to a bigger one. The report gives you the bigger number to stand your price against, in the buyer's own words, so you never have to defend the price cold.

Sniff tests: when should you walk away fast?

Three disqualify-fast tests, each with a scripted, graceful exit. No metric by minute ten means demote to nurture. Champion-only, where the ops manager refuses to bring the principal, means escalate to a founder-led ask for 20 minutes with the buyer. Wrong ICP shape, fewer than 20 or more than 250 producers or a single state, means disqualify with a line that sends them to the right tool instead of selling them the wrong one.

OPERATOR'S READ

A serious playbook protects your calendar as hard as it fills your pipeline. The 'wrong ICP' exit even sends the prospect to Sircon or AgentSync by name, which sounds like giving up revenue but is how you become the person a market trusts.

Demo handoff: when is a deal actually ready to move forward?

Five checkboxes. If they are not ticked, you are demoing to someone who cannot buy. The buyer has quantified hours or cost, named the economic buyer and agreed to include them, named a compelling event within 90 days, confirmed the AMS and whether integration is a must-have, and the producer count and state footprint fit the ICP. All five, or it is not a demo, it is a courtesy.

OPERATOR'S READ

Stage discipline starts here. Most founders demo too early because a demo feels like progress. This gate reframes the demo as a reward the buyer earns by qualifying, which is also why the demo converts better when it does happen.

Sales stages: what are they, and how long should each take?

Five stages, each with an SLA and explicit entry and exit criteria. Discover (10 days), Demo (10 days), Pilot or POC (60 days, a paid pilot with named success criteria), Negotiate (21 days), Close (3 days). The pilot is the go/no-go moment that de-risks the annual commitment. Each stage carries a confidence marker, and several are honestly tagged 'insufficient public evidence' rather than dressed up as certain.

OPERATOR'S READ

The SLA is the alarm, not a target. A deal past 1.5x its stage SLA is not slow, it is stuck, and the playbook later auto-generates a rescue task for exactly that. Without SLAs, 'the deal is still alive' is a feeling. With them, it is a date you have blown.

Pipeline math: how many emails is your revenue target, actually?

The arithmetic that turns a target ARR into 'how many touches this week'. Two closed-won per month, at a $10,800 average contract value, is $1,800 net-new MRR and $21,600 net-new ARR per month. The number carries a 'Sourced' marker, and the ACV traces back to the Growth-tier midpoint set in the GTM Strategy tab, so the math is consistent across the whole brief rather than invented here.

OPERATOR'S READ

This is what makes a revenue goal actionable. 'Grow ARR' is a wish. 'Two closes a month at $10.8K' is a number you can divide backward into meetings, then replies, then sends, which is exactly what the next screen does.

The weekly funnel: where does it actually leak?

One hundred touches becomes four replies, two meetings, one demo, and 0.4 closes. The funnel runs the conversion backward from the target and then says the honest thing: reply rate is the bottleneck, not downstream conversion. At a 4% reply rate, 100 touches a week produces two closes a month. At 2%, you need 200. And it flags the shakiest rows as 'low confidence' or 'insufficient public evidence' instead of presenting invented conversion rates as fact.

OPERATOR'S READ

Two things to notice. First, it tells you the constraint (top-of-funnel volume and targeting), so you do not waste weeks optimizing a close rate that is already fine. Second, the 'insufficient public evidence' tags are a feature: the report will not pretend to know your reply rate, so you calibrate against your own first week of data.

Forecasting: how do you predict revenue without lying to yourself?

Stage-weighted probabilities plus a strict line between commit and best case. Discover counts for 10%, Demo 25%, Pilot 60%, Negotiate 80%, Close 95%. Commit means a paid pilot in flight with signed success criteria and an economic buyer engaged in the last 14 days. Best case is a demo held and principal briefed but no pilot signature. Everything upstream of demo is pipeline, not forecast. And there is a loss-reason taxonomy so 'they went dark' is not an allowed answer.

OPERATOR'S READ

The loss taxonomy is the part most founders skip and later wish they had kept. 'Lost to do-nothing' and 'lost to AgentSync' are different problems with different fixes. If every loss is logged as 'went quiet', you learn nothing across a year of losses.

CRM hygiene: what keeps the pipeline from quietly rotting?

A short list of non-negotiable rules that most founders discover the hard way. Every deal carries a next-step date and a named owner or it is auto-flagged. Stage advancement requires the exit-criteria boxes checked, not a gut feel. MEDDIC fields are mandatory before a deal can reach Demo. Any deal past 1.5x its SLA generates a founder review task. And every 'circling back' response downgrades the deal by one stage until a new commit date is on the calendar.

OPERATOR'S READ

That last rule alone would fix most stalled pipelines. 'Circling back' is not a stage, it is the absence of one, and treating it as progress is how founders carry dead deals for months. This makes the CRM tell you the truth even when you do not want to hear it.

The rationale: does it explain the strategy, or just hand you tactics?

It closes with the reasoning, and a brutal truth, in plain language. NELL states it directly: the founder has two customers because they got lucky finding two champions who happened to also be the principals, a solo-op agency shape. The third deal is stalling because the ops manager is not the principal, and the founder has never had to sell to a real economic buyer. Every deal from here forward is that third deal. Fix the discovery process to demand economic-buyer engagement by the end of Stage 1, or the pipeline will be 'circling back' forever.

OPERATOR'S READ

This is the difference between a tool that validates you and one that challenges you. It could have congratulated the founder on two paying customers. Instead it names the survivorship bias in those wins and points at the exact habit that has to change. That candor is the product.

The refine bar: what if this motion is wrong for you?

The whole brief is one click away from a different shape. The refine bar lets you re-aim the entire report: founder-led selling, SMB velocity, enterprise motion, stricter qualification, shorter cycle, channel or partner-led, PLG-assisted. One credit per refine. You are not stuck with the first draft's assumptions about how you go to market.

OPERATOR'S READ

This is why it is worth more than a static document. If your real motion turns out to be partner-led rather than founder-led, you re-aim it, you do not re-buy it. The report is a living artifact you steer, not a PDF you file.

Is a Pro Builder brief worth around $999 a month?

Fair question, and the honest answer depends entirely on whether you will act on it.

Here is the comparison that matters. A fractional GTM lead who could produce this thinking runs $8,000 to $15,000 a month, if you can find one who will go this deep on your specific ACV and buyer. Pro Builder is the cheaper way to get the strategic layer plus the execution playbooks across every tab, and you can refine it as your motion changes. That is the case for it.

The case against it is just as real. If you are pre-product, or you will read the brief and not run any of it, or you already have a disciplined team that does this in its sleep, the money is better spent elsewhere. This is a tool for the founder in the middle: built product, early revenue, selling by feel, ready to make it a system. If that is not you yet, start smaller.

The point of this walkthrough is not to sell you Pro Builder. It is to show you exactly what a Sales Playbook contains so you can decide honestly whether you are at the stage where it pays for itself. If you are not, we would rather tell you than take the money.

Want a Sales Playbook like this for your product?

Book a 20-minute call. We will look at your stage and tell you honestly whether Pro Builder is the right fit, or whether you should start smaller. No pitch deck, just a read on where you are and what would actually move you forward.

Not ready for a call? A DeepValidate report is $49 and answers the earlier question: is this idea worth building at all? Start there, get a working product and a paying customer, and the sales motion is waiting when you come back.

Questions we get asked

Is the Sales Playbook sold on its own?

No. It is one tab inside a Pro Builder brief, and it leans on the buyer, channel, and pricing work done in the tabs before it. Bought alone it would be a script without a context.

Does it write my outreach emails for me?

It gives you the discovery questions, the call script, and the rebuttal logic. The actual outbound copy and sequences live in the Outreach tab of the same brief.

Is the sample data real?

The structure, reasoning, and numbers are real NELL output for a real sample product. The only change for this walkthrough is that the customer name in the header was redacted.

Why does the report say 'insufficient public evidence' on some rows?

Because NELL will not fabricate conversion rates or benchmarks it cannot source. It flags the thin spots so you calibrate against your own data instead of trusting a made-up number.

What if MEDDIC is too heavy for my deal?

The report tells you when to drop to a lighter framework like SPICED, and the refine bar lets you re-aim the whole motion toward SMB velocity or PLG in one step.

How is this different from asking a general AI for a sales playbook?

It is routed to your validated product, buyer, and ACV rather than the average of the internet, it cites real market data, and it flags its own uncertainty instead of confidently guessing. It also challenges the founder's assumptions rather than flattering them.