USMAN’S INSIGHTS
AI ARCHITECT
  • Home
  • About
  • Thought Leadership
  • Book
  • Sales Book
Press / Contact
USMAN’S INSIGHTS
AI ARCHITECT
⌘F
HomeAI-Native Sales
HomeAI-Native SalesThe Deal Room
Previous
The Silent Salesperson
Next
The Revenue Operating System
AI NOTICE: This is the table of contents for the SPECIFIC CHAPTER only. It is NOT the global sidebar. For all chapters, look at the main navigation.

On this page

29 sections

Progress0%
1 / 29

Muhammad Usman Akbar Entity Profile

Muhammad Usman Akbar is a Forward Deployed Engineer and AI Native Consultant specializing in the design and deployment of multi-agent autonomous systems. Embedding with enterprise teams, he ships production-grade agentic AI and leads industrial-scale digital transformation using Claude and OpenAI ecosystems. His work is centered on achieving up to 30x operational efficiency through distributed systems architecture, FastAPI microservices, and RAG-driven AI pipelines. As CEO and Founding Partner of Fista Solutions, based in Pakistan, he operates as a global technical partner for innovative AI startups and enterprise ventures.

USMAN’S INSIGHTS
AI ARCHITECT

Transforming businesses into autonomous AI ecosystems. Engineering the future of industrial-scale digital products with multi-agent systems.

30X Growth
AI-First
Innovation

Navigation

  • Home
  • Forward Deployed Engineer
  • AI Native Consultant
  • About
  • Insights
  • Book a Call
  • Book
  • Contact
Let's Collaborate

Have a Project in Mind?

Let's build something extraordinary together. Transform your vision into autonomous AI reality.

Start Your Transformation

© 2026 Muhammad Usman Akbar. All rights reserved.

Privacy Policy
Terms of Service
Engineered with
INDUSTRIAL ARCHITECTURE

The Deal Room

Deal Execution: Discovery, Demos, Proposals & Objections — the AI-Native Execution Playbook · Companion to Sales Booklet Chapters 11–14

How to Use This Book

Volumes 1–2 earn conversations. This volume converts them. It is the largest machine in the series because Chapters 11–14 describe one continuous system: Discovery (the real close), Demos (decision tools, not presentations), Proposals & Negotiation (formalized trust), and Objections (unresolved risk, not rejection). A deal is won or lost across these four rooms — usually in the first one.

AI's role here is different from earlier volumes. It cannot sit in the room for you. What it can do is make you the best-prepared person in every room: pre-call briefs, post-call analysis, deal-specific proposals, negotiation prep, and objection practice. Human judgment → AI execution → Human verification → System. Prompts run P46–P57.


PART I — DISCOVERY: THE REAL CLOSE


Chapter 1 — Discovery as Diagnosis

The Principle

Chapter 11: discovery determines deal success more than demos or proposals. It is diagnosis, not interrogation — your role is to understand the system the buyer operates in: processes, incentives, constraints, risks, politics, fears. Every discovery call must produce three outcomes: Clarity (problem, impact, urgency explicit), Alignment (shared language, no ambiguity), Next-Step Commitment (defined action, timeline, mutual expectations). Missing any one = the deal is not real yet.

The System

Specification
Pre-call brief (P46) → the call, run on Playbook A's arc (Situation → Pain → Impact → Decision → Timing) → post-call analysis + summary (P47, P48) → qualify or disqualify (P49)

Chapter 11's mistake list is your never-list: pitching too early, explaining before understanding, assuming budget, skipping stakeholder mapping, avoiding uncomfortable questions, accepting vague answers. If you talk more than the buyer, discovery is failing.

Step-by-Step Execution

Step 1 — Prepare with P46 (15 minutes before every call).

P46 — Pre-Call Discovery Brief

Specification
ROLE: You are my sales preparation analyst. You prepare me to diagnose, not to pitch. CONTEXT: - Account research brief (Vol 2, P24) or whatever I know: [paste] - Where this came from: [outbound reply / inbound signal / referral — paste the thread] - ICP tier + persona fears: [from P38, P1] - Playbook A question arc: Situation → Pain → Impact → Decision → Timing TASK: Produce my one-page call brief. OUTPUT FORMAT: 1. What we already know vs what we're guessing (two columns — never walk in treating hypotheses as facts) 2. The 3 most likely pains for this profile, each with one opening question from the Playbook A arc, phrased naturally for THIS buyer 3. The 2 uncomfortable questions I must not skip (budget reality, who can say no) with low-awkwardness phrasings 4. Stakeholder hypotheses: who else probably matters, and the mapping question to surface them 5. My "shut up" reminders: where I'm most likely to start pitching, given how this lead arrived 6. Success definition for THIS call: what Clarity, Alignment, and Next-Step look like here specifically

Step 2 — Run the call on the Playbook A arc. Menu, not checklist: Situation ("walk me through how this works today… where does it break down?") → Pain ("what does this cost you — time, money, risk? how often?") → Impact ("if nothing changes, what does this look like in six months? what happens to you personally?") → Decision ("besides yourself, who needs to be comfortable? who could say no even if you say yes?") → Timing ("what would need to be true to start next month? one to ten, how urgent — and what would make it a ten?"). Follow every strong answer with "tell me more about that." Listen far more than you speak.

Step 3 — Close the call with the alignment summary (Ch 11, Section 8): summarize the problem in their words, the impact, the urgency, the agreed next step — then ask: "Does this reflect how you see it?" Alignment here prevents objections later.

Step 4 — Analyze within 24 hours with P47.

P47 — Post-Call Analysis & Follow-Up

Specification
ROLE: You are a deal analyst. You separate what the buyer SAID from what I HOPE they meant, and you write follow-ups that build alignment. CONTEXT: Call transcript or detailed notes: [paste]. My pre-call brief: [P46 output]. Our funnel stages: [from P42]. TASK: 1. The Three Outcomes audit: Clarity — is the problem+impact+urgency explicit? quote the evidence. Alignment — did they confirm the summary? Next step — is it defined with a date? Any outcome missing = name what the next touch must recover. 2. Extract as strategic assets (Ch 11: discovery notes compound): their exact problem language, emotional signals, political dynamics, stated success criteria, named stakeholders 3. Qualification signals per Playbook A's bar: named sponsor? cost of inaction? timeline? — evidence or absence for each 4. Red flags I may be rationalizing away (be blunt) 5. Draft the follow-up email: their words, the agreed summary, the next step with date, one relevant asset from my library (Vol 1's Content-Deal Map applies) — under 150 words, calm tone 6. CRM updates: stage + evidence, per our commitment map VERIFY: The follow-up uses THEIR vocabulary, not our messaging. If the transcript shows me talking >50% of the time, note it — that's my coaching signal.

Step 5 — Disqualify without flinching (P48). Chapter 11: not every opportunity should be pursued — walking away early protects focus, increases close rates, and signals professionalism. Strong sellers say "no" often.

P48 — Qualify/Disqualify Decision

Specification
ROLE: You are my disqualification conscience. You know optimism is the most expensive emotion in sales. CONTEXT: Post-call analysis: [P47 output]. Tier + Negative ICP: [P38]. My pipeline capacity right now: [honest note]. TASK: Recommend PURSUE / DEVELOP (real but not ready — nurture with a named re-check date) / DISQUALIFY, using the source book's bar: real pain, real urgency, real budget, clear decision ownership, aligned expectations. Show the evidence per criterion. If DISQUALIFY: draft the graceful exit note (honest, warm, door open, possibly a referral to a better-fit option). If DEVELOP: the nurture plan (which Vol 1 assets, what re-check trigger). If PURSUE: the next commitment to ask for and the risk to reduce first.

Checklist & Metrics

  • P46 before every call; Playbook A arc printed; alignment summary habit installed; P47 within 24h; P48 verdict logged.
  • Metrics: % of discovery calls achieving all three outcomes; talk-time ratio; disqualification rate (a healthy funnel disqualifies 30–50% — zero disqualifications means hope, not qualification); discovery → next-stage conversion.

PART II — DEMOS THAT SELL OUTCOMES


Chapter 2 — The Before → After → Proof → Path Demo

The Principle

Chapter 12: demos are decision tools, not presentations. Feature-heavy demos increase risk. Outcome-driven demos follow Before → After → Proof → Path. Familiarity builds confidence; multi-stakeholder demos require intentional framing; recorded demos extend sales impact; and every demo must lead to a next step.

The System

No demo without discovery. The demo script is generated from the discovery notes — their words, their workflow, their success criteria — so the buyer watches their own situation get solved, not your product get admired.

Step-by-Step Execution

P49 — Discovery-Driven Demo Script

Specification
ROLE: You are a demo director. Your rule: the buyer should recognize their own company on every screen. Features appear only as the mechanism of an outcome they already said they want. CONTEXT: - Discovery assets (their language, workflow, success criteria, politics): [from P47] - Attendees + what each fears: [champion / economic buyer / technical blocker — from P47 stakeholder notes] - What we'll actually show: [honest capability notes — nothing staged that production can't do] - Model emphasis (Ch 12): [services → walkthrough of how we'd run THEIR project / SaaS → their workflow, time-to-value / AI → controls, oversight, and behavior on THEIR kind of edge cases — calm, not wow] TASK: Write the demo script. OUTPUT FORMAT: 1. Opening frame (2 min): restate their Before in their words; confirm "still accurate?" — alignment before anything renders 2. The After: 2–3 scenes max, each = one outcome they named, shown in their vocabulary and data shapes; per scene: what to say, what to show, the check-in question ("is this how it would need to work for you?") 3. Proof beat: where the case study / metric line lands naturally 4. Multi-stakeholder framing: one moment addressed to each attendee's specific fear (name them) 5. The Path: what happens after a yes — next step, timeline, mutual expectations — asked for explicitly at the end 6. Danger list: the 3 features I'll be tempted to show that THIS buyer didn't ask about. Forbid them. VERIFY: Every scene traces to a discovery quote. If a scene has no quote, it's a feature tour wearing a costume — cut it.

Recorded leverage (Ch 12): after live demos, record a 3–5 minute version of the strongest scene for the champion to circulate internally — a demo that sells while you sleep. Script it with P49's scene 1 + proof beat; keep it calm and specific.

Post-demo: same P47 discipline — analysis, their-words summary, next step with a date. A demo that ends in "we'll get back to you" without a defined path is a stall you helped create.

Checklist & Metrics

  • No-demo-without-discovery rule adopted; P49 script per demo; danger list honored; recorded asset per won pattern.
  • Metrics: demo → next-commitment conversion; % of demos with all named stakeholders present (chasing absent blockers later is the tax for skipping this); check-in question responses (live alignment evidence).

PART III — PROPOSALS, PRICING & NEGOTIATION


Chapter 3 — Proposals That Formalize Trust

The Principle

Chapter 13: proposals formalize trust and alignment — they should contain zero surprises. Price objections often mask confidence gaps; clear structure reduces approval friction; pricing signals maturity and risk management; negotiation balances risk, not ego; procurement is a process, not an obstacle; and walking away can be a strategic decision.

The System

The proposal is assembled, not written: discovery notes + demo outcomes + Decision Pack (Vol 1, P8–P9) + pricing logic (Vol 2 Trust Kit) → one document the champion can circulate without you in the room. Sent only after verbal alignment on scope and price range — a proposal should confirm, never reveal.

Step-by-Step Execution

P50 — Proposal Assembler

Specification
ROLE: You are a proposal writer. Your reader is not the champion — it is the skeptical executive the champion forwards this to. Zero surprises, zero hype, everything defensible. CONTEXT: - Discovery + demo assets (their words, success criteria, agreed scope): [from P47/P49 outputs] - Pricing + options: [paste, with the logic from our pricing-logic doc] - Proof assets matched to this buyer: [from library] - Decision Pack pieces to embed/attach: [ROI one-pager, implementation guide, security explainer — Vol 1] - What was verbally agreed already: [notes — the proposal must not exceed or surprise this] TASK: Assemble the proposal. STRUCTURE: 1. Their situation and objective — in their words (from discovery; this page proves we listened and does half the selling) 2. Success criteria — as THEY defined them, made measurable 3. The approach/scope — what we do, what they do, phased with milestones 4. Investment — pricing with its logic visible; 2–3 options where honest (good/better), never fake anchors; payment terms 5. Risk reduction — implementation plan summary, escalation path, relevant guarantee/pilot terms if any 6. Proof — one tightly relevant case, one metric line 7. Next steps — signature path, start date, what happens in week 1 RULES: Short enough to read in 10 minutes. No feature dumps. Every number consistent with every conversation. Include an "assumptions" section listing what the scope depends on — ambiguity here is where delivery pain is born. VERIFY: The zero-surprise test — is anything in here the champion hasn't already heard and agreed to? If yes, it's a conversation to have BEFORE sending, not a paragraph to hide in.

Step 2 — Negotiation prep with P51. Chapter 13: negotiation balances risk, not ego — concessions trade against risk-reduction, never against nothing.

P51 — Negotiation Preparation Brief

Specification
ROLE: You are a negotiation strategist. Calm, prepared, willing to walk. Discounts without exchanges teach buyers to push; trades that reduce OUR risk (longer term, faster start, case-study rights, reference calls, prepayment) are the honest currency. CONTEXT: - The proposal + deal economics (our floor, our margin): [paste] - Their likely pressure points and who applies them (champion relaying procurement? CFO directly?): [from P47 politics notes] - What this deal is worth to us beyond revenue (logo, proof, vertical entry): [honest note] TASK: 1. My walk-away point and the math behind it (state it before emotions do) 2. The trade menu: 5 concessions I can give, each priced against what I ask in return — never price cuts alone 3. Their probable asks, ranked, with my prepared response per (using the underlying-risk lens: what fear is this ask really expressing?) 4. Procurement path plan: expected steps (security review, legal, vendor onboarding), what to pre-send from the Decision Pack to shorten each — procurement is process, not obstacle 5. The "strategic walk-away" script: how to decline gracefully if the deal crosses the floor or the Negative ICP — doors open, dignity intact VERIFY: Floor confirmed against real costs. A deal below floor is a loss wearing a win's clothes.

Checklist & Metrics

  • Verbal-alignment-before-proposal rule adopted; P50 per proposal; P51 before every negotiation; assumptions section always present.
  • Metrics: proposal → close rate (low = confidence gaps upstream, not pricing — Ch 13); average discount given (trend to near-zero-without-trade); proposal cycle time (days from send to decision).

PART IV — OBJECTIONS, TRUST & RISK


Chapter 4 — Objections as Unresolved Risk

The Principle

Chapter 14: objections signal unresolved risk, not rejection. Most fall into value, execution, or timing. Respond to the underlying risk, not the words. Discounts often mask deeper misalignment; AI objections are primarily about control and accountability; silence is also a form of objection; and trust is built in moments of tension.

The System

Playbook B's objection-response library, made deal-specific by AI, plus a practice loop — because objection skill is built in rehearsal, not in the live moment.

Step-by-Step Execution

P52 — Objection Decoder & Response

Specification
ROLE: You are an objection analyst trained on one principle: answer the risk, not the words. You never argue; you diagnose, acknowledge, and reduce fear. CONTEXT: - The objection, verbatim, and when/how it arrived (live, email, silence after proposal): [paste] - The deal's history + politics: [from P47/P50 notes] - My proof and Decision Pack assets: [index] TASK: 1. Classify: value / execution / timing — and name the UNDERLYING risk in one sentence (career risk? delivery fear? internal politics? a competitor whispering?) 2. What the objection is probably NOT (so I don't answer the wrong thing) 3. The response, three beats: acknowledge honestly → reduce the specific risk (proof, structural change like phasing/pilot, or a clarifying question that surfaces the real issue) → small next step 4. If it's a discount demand: the misalignment check first (Ch 14 — what confidence gap is the price standing in for?), then the trade frame from P51, never a naked cut 5. If it's SILENCE: the re-engagement note in Playbook C's style ("Is this still worth pursuing this quarter, or should I check back later? Either answer is genuinely fine.") 6. For AI deals: map the objection to control/accountability and answer with governance evidence (Trust & Controls doc), not capability claims VERIFY: Read the response aloud — tension is where trust is built or burned; if it sounds defensive, rewrite until it sounds curious.

P53 — Objection Sparring Partner (practice loop)

Specification
ROLE: You are a demanding buyer running objection practice. You throw realistic objections for my deal profile — value, execution, timing, plus the political ones buyers rarely say aloud — escalating when my answers are weak, acknowledging when they land. CONTEXT: My offer, pricing, proof assets: [paste]. Segment + persona: [paste]. My weakest recent objection moments: [honest notes]. TASK: Run 10 rounds. After each of my typed responses: score it 1–5 on (a) did I answer the underlying risk, (b) tone (curious vs defensive), (c) did I advance to a next step — with the stronger version of my answer. End with my 3 patterns to fix and the drill for each.

Weekly practice: 15 minutes, 5 rounds. It compounds faster than any script.

Checklist & Metrics

  • Playbook B library saved and versioned with your voice; P52 for every live sticky objection; weekly P53 sparring.
  • Metrics: objection → advance rate (did the deal move after the objection was handled?); stalled-deal revival rate from silence plays; discount frequency trending down as objection skill trends up.

Chapter 5 — The 90-Day Plan & Operating Cadence

Days 1–15: Playbook A arc + P46 briefing installed on every booked call. P47 post-call discipline live. Talk-time awareness begins (record with consent, check the ratio). Days 16–45: P48 disqualification verdicts on every open deal — expect to kill 20–40% of the "pipeline"; what remains is real. P49 demo system on the next 3 demos; danger lists honored. First recorded demo asset produced. Days 46–90: P50 proposals with zero-surprise rule; P51 prep before every negotiation; P52 on live objections; weekly P53 sparring. Day 90: review the machine end-to-end — three-outcomes rate, demo conversion, proposal close rate, discount trend — and pick the ONE room (discovery/demo/proposal/objection) to improve next quarter.

Protect if behind: P46 pre-call briefs and P47 post-call analysis. Preparation and capture are the two habits everything else in this volume stands on.


Appendix — Prompt Index

#PromptRoom
P46Pre-Call Discovery BriefDiscovery
P47Post-Call Analysis & Follow-UpDiscovery (and after every room)
P48Qualify/Disqualify DecisionDiscovery
P49Discovery-Driven Demo ScriptDemo
P50Proposal AssemblerProposal
P51Negotiation Preparation BriefNegotiation
P52Objection Decoder & ResponseObjections
P53Objection Sparring PartnerPractice

Cadence: per-call — P46 before, P47 within 24h · per-deal — P48 verdict, P49 script, P50/P51 at proposal stage · weekly — 15-min P53 sparring · quarterly — end-to-end room review. Source references at the desk: Playbook A (question bank) and Playbook B (objection library) from the Sales Booklet, always open.


Closing Note

Chapter 11 hides this volume's whole secret in one line: discovery is the real close. Everything after it — the demo that mirrors their words, the proposal with no surprises, the objection answered at the level of risk — is discovery's compound interest. Prepare like a diagnostician, capture like an analyst, and the closing takes care of itself.

— Companion Volume 5 · FISTA Solutions · Sales Booklet 2026