Resources
Print-ready frameworks, copy-paste scripts, and quick-reference sheets. Everything here is designed to be used immediately — in a meeting prep session, a notes app, or printed and folded into a notebook.
Before any important meeting (5-minute prep)
Answer these five questions before you walk in. If you cannot answer any one of them, you are not ready.
- Their goal in their words: What does the person across the table need to be able to say to their team or boss after this conversation goes well?
- Your ask: One primary ask. One fallback ask. No more.
- The two objections you expect: Write them down. Write a one-sentence response to each.
- Your one proof artifact: One number, one quote, one screenshot. Choose based on what they find credible, not you.
- The next step: A specific action, owner, and date. Not "follow up soon."
Copy-paste: cold outreach email
Subject: [specific thing they said, shipped, or published] → [their outcome in plain language]
Hi [Name] — [One true observation about them or their company. Be specific. Not "I've been following your work." A real artifact.]
[Teams / people in their situation] often run into [pain in their language, not yours]. [One sentence on what changes if they work with you — written as outcome, not feature.]
Worth a 12-minute call [specific day] or [specific day]? If this isn't your area, who should I talk to?
[Your name]
Copy-paste: opening a live meeting
"Thanks for the time. In the next [timebox], I want to give you [specific thing] and then get your reaction to one decision: [X]. I'll leave [time] for questions. Here's where we are."
Copy-paste: follow-up after silence
Subject: Quick question on [topic]
[Name] — One new thing: [a real development — customer result, scope change, question you forgot to ask].
Quick question: [one specific, answerable question].
If the timing has changed, no problem — just let me know and I'll close this out on my end.
Copy-paste: handling "we need to think about it"
"Of course — can you help me understand what specifically you'd want to think through? I want to make sure I haven't left something unanswered."
[Listen. Then, if vague:]
"I want to be direct with you — I'd rather hear an honest 'not right now' than leave you feeling like you have to keep this open. Is there something about the fit that isn't quite working?"
Copy-paste: the pricing sentence
"Based on what you've told me — [summary of their specific situation] — I'd recommend [option] at [price]. That covers [what they said they needed]. What's your reaction to that?"
Discovery question bank
Use any five from this list on a first call. Remove any you can answer with research before the meeting.
- "What prompted this conversation now — as opposed to three months ago?"
- "If this went well in 90 days, what would be different for your team specifically?"
- "Walk me through how you handle this today — step by step."
- "What have you already tried, and what did you learn from it?"
- "What would you need to see to feel confident — not just interested?"
- "What would make you confidently say no — and be comfortable with that call?"
- "Who else cares about this outcome, even if they're not in this conversation?"
- "How have you funded changes like this in the past — OPEX, project budget, or something else?"
- "What are the other priorities competing with this right now?"
- "What happens if this decision doesn't get made in your stated timeframe?"
Objection first-response bank
For each objection, state a label before anything else. These are starting points — fill in their specific nouns.
| What they say | Label (use their words) | Pivot question |
|---|---|---|
| "Too expensive" | "Sounds like the return isn't clear enough yet to justify the cost against other uses of that budget." | "Is the constraint that the budget isn't available, or that the ROI case isn't compelling enough?" |
| "We need to think about it" | "Sounds like there's something specific you'd want to pressure-test before committing." | "What specifically would you want to think through? I want to make sure I haven't left something unanswered." |
| "Send me more info" | "Sounds like you want to evaluate this on your own terms before deciding if a follow-up is worth the time." | "What specific question would you want it to answer? I'd rather send three right pages than twenty." |
| "We're already using X" | "Sounds like switching costs are a real factor — not just price but the disruption of moving off something working." | "When you say it's working — what's it not doing that had you take this meeting?" |
| "Not a priority right now" | "Sounds like timing is the main factor — this is on the list but other things are ahead of it." | "What would need to change for this to move up the list? Is it a capacity thing, a budget cycle, or something else?" |
Glossary
| Term | How it's used here |
|---|---|
| Ask | The specific next step you want — a meeting, a decision, an introduction, a resource. Not "your thoughts." |
| Champion | The person inside an organization who advocates for you when you're not in the room. Without one, enterprise deals rarely close. |
| Discovery | The process of learning what the buyer actually needs, how they buy, and what would make them say no confidently. |
| Forcing function | An external event that makes a decision genuinely time-sensitive — a renewal, a deadline, a regulatory date. Distinguishes real timelines from polite ones. |
| Label | Naming the concern or emotion underneath an objection, in their language, before responding to it. |
| Objection | Information about risk, fit, or process — not rudeness. Treat it as data, not as an attack. |
| Pre-wire | Having individual conversations with key stakeholders before a group meeting — to understand their concerns and incorporate them before the room. |
| Proof | Evidence sized to the buyer's definition of credibility, not yours. One artifact is almost always better than five. |
| Qualification | The discipline of determining whether a deal is real — whether the right people are involved, the money exists, the problem is genuine, and the timeline is grounded. |
| Rift | The specific change or tension that makes this conversation necessary now rather than next quarter. |
| Soft no | A polite deferral — "we need to think about it," "let's revisit this," "send more info" — that often means a decision has been made but not stated. |
| Veto | The unstated fear that causes a stakeholder to block progress. Usually comes as delay rather than refusal. |
The reading sequence
If you're new here and want a structured path through the content:
- The Five-Line Idea Brief — the shortest form of a pitch
- Stakeholder Heat Map — know your room before you write anything
- The 12-Minute Arc — structure for any update, demo, or talk
- Discovery Without Interrogation — the core of all selling
- Objections: Label and Pivot — what to do when they push back
- Qualifying Without Interrogating — is this deal real?
- The Pricing Conversation — talking about money without apologizing
- Guide builder — put your situation in, get a tailored outline