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 Foundations Lab
Next
The GTM Blueprint
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

30 sections

Progress0%
1 / 30

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 Foundations Lab

Foundations: Market, ICP & Value Proposition — the AI-Native Execution Playbook · Companion to Sales Booklet Chapters 1–6

How to Use This Book

The Sales Booklet's opening arc (Chapters 1–6) makes one compound argument: sales in 2026 is decision engineering, not persuasion — and the engineering starts long before any conversation. Your business model (Ch 2), your market understanding (Ch 3–4), your ICP (Ch 5 — "the #1 sales skill"), and your value proposition (Ch 6) determine 80% of your sales outcomes before a single email is sent.

This volume turns those chapters into a living lab — not a strategy binder written once, but four working systems reviewed on a cadence, fed by real deal data. Volume 1's Foundation Sprint (P1–P4) built the quick versions; this volume builds the deep versions and the rituals that keep them true.

Operating rule, unchanged: Human judgment → AI execution → Human verification → System. Prompts run P33–P42.


Chapter 1 — The Business Model Decision: Services, Product, or Hybrid

The Principle

Chapter 2 of the Booklet: services, products, and hybrid models are tools, not identities. Services create cash, clarity, and credibility. Products create leverage, scale, and valuation. Hybrid models dominate in reality — and smart founders evolve instead of arguing with reality.

The System

A twice-yearly Model Review: an honest, numbers-driven look at where your revenue actually comes from, what each stream costs to sell and deliver, and whether your model should evolve. Sales logic stays constant across models (Ch 2); execution — pricing, cycle length, proof requirements, team shape — changes. Your model choice cascades into every later volume.

Step-by-Step Execution

Step 1 — Run the model economics comparison with P33.

P33 — Business Model Economics Analyzer

Specification
ROLE: You are a pragmatic business model analyst for software/AI founders. You favor evidence over aspiration and cash flow over narrative. CONTEXT: - What we sell today, revenue split by stream: [services $ / product $ / recurring $, rough numbers fine] - Per stream: typical deal size, sales cycle length, delivery cost/margin, repeatability (how similar is each delivery?): [notes] - My ambition and constraints (runway, team size, appetite): [honest notes] TASK: Analyze my model and its evolution options. OUTPUT FORMAT: 1. Current-state scorecard per stream: cash contribution, margin, sales effort per dollar, scalability ceiling 2. What my WON-deal evidence says buyers actually want to buy from me (which may differ from what I want to sell — flag the gap) 3. Three evolution paths (stay / productize a service / add services to product), each with: what changes in sales execution, the first 90-day move, the risk 4. The hybrid question: which combination maximizes cash + credibility NOW while building leverage LATER 5. One recommendation with reasoning — and the tripwire metric that would change it VERIFY: Check every number against actual invoices/contracts. Aspirational inputs produce aspirational strategy.

Step 2 — Cascade the decision. Write a half-page Model Decision Doc: what we sell, in what order we lead with it, what we deliberately don't sell this year. Every later prompt in the series that asks "what do you sell" gets its answer from this doc.

Checklist & Metrics

  • P33 run with real numbers; Model Decision Doc written; calendar review set for +6 months.
  • Metric: revenue mix vs planned mix, reviewed twice yearly. Drift is data, not failure — it tells you what the market is voting for.

Chapter 2 — Market Mapping: Many Markets, Not One

The Principle

Chapter 3: the software industry is many markets, not one. Buyers think in consequences, not features. Money flows to four things — cost, revenue, risk, and time. And vertical focus increases sales velocity and pricing power.

The System

A Market Map: the segments you could serve, scored by pain intensity, budget flow, accessibility, and fit — producing one primary vertical (and at most one secondary) where you concentrate everything from Volumes 1–2.

Step-by-Step Execution

P34 — Market Mapping & Vertical Selection

Specification
ROLE: You are a GTM strategist who believes vertical focus beats broad reach. You score markets on evidence and mechanism, and you label inference clearly. CONTEXT: - What we sell + Model Decision Doc: [paste] - Segments we've touched so far, with outcomes: [won/lost/ignored, per segment] - Segments I'm curious about and why: [notes] - My unfair advantages (domain knowledge, network, existing proof): [notes] TASK: Build my market map. OUTPUT FORMAT: 1. 6–10 candidate segments (vertical × size band), each scored 1–5 on: pain intensity (frequent, visible, owned by someone?), money mechanism (does solving it clearly save cost, add revenue, cut risk, or save time? name which), accessibility (can I reach these buyers with Vols 1–2 motions?), proof fit (does my existing evidence transfer?) 2. For the top 3: the consequence chain — what breaks in their business, who feels it, what it costs, who owns fixing it 3. The recommendation: one primary vertical + rationale + what "all-in" means for content (Vol 1), outbound (Vol 2), and proof priorities 4. Kill criteria: what evidence within 2 quarters would mean this vertical was wrong VERIFY: Scores citing no evidence are hypotheses — test the top segment with 10 real conversations before reallocating everything.

Checklist & Metrics

  • Market Map built; primary vertical chosen; Vols 1–2 assets re-aimed at it.
  • Metrics: win rate and cycle length in the chosen vertical vs elsewhere — vertical focus should show up in both within 2 quarters.

Chapter 3 — Research That Drives Revenue (Not Reports)

The Principle

Chapter 4: market research exists to reduce sales uncertainty. Buyer-centric research beats reports and forecasts. Markets buy when pain is frequent, visible, and owned. Sales conversations are the best research source — and research ends when patterns stabilize.

The System

Two engines: (1) desk research, AI-accelerated, for competitor and buyer-language intelligence; (2) conversation research — a standing interview practice, because ten real conversations beat any report. Segmentation optimizes revenue, not reach.

Step-by-Step Execution

Step 1 — Competitor teardown with P35 (quarterly).

P35 — Competitor Teardown & Battlecard

Specification
ROLE: You are a competitive intelligence analyst. You work only from the material provided plus clearly-labeled general knowledge. You never invent competitor claims. CONTEXT: - Competitor: [name]. Raw material I collected: [their site copy, pricing page, case studies, reviews from G2/Clutch, job posts — paste] - Our Model Decision Doc + value prop: [paste] TASK: Produce a one-page battlecard. OUTPUT FORMAT: 1. Their promise, ICP, and pricing posture — in their words (quoted from my material) 2. Where buyers praise them and where buyers complain (from reviews; quote the recurring complaint language — this is objection gold) 3. Where we genuinely win, where they genuinely win, where it's a tie — honest, three columns 4. The trap questions a buyer comparing us should ask them (fair ones, grounded in real gaps) 5. What NEVER to say about them (no disparagement — Ch 27 ethics apply) VERIFY: Every claim traces to pasted material. Update quarterly; stale battlecards lose deals.

Step 2 — The buyer interview practice with P36. Five interviews per quarter with ICP-fit people (customers, lost prospects, market peers). Not sales calls — research calls.

P36 — Buyer Research Interview Kit

Specification
ROLE: You are a customer research specialist. Your interviews surface pain frequency, visibility, and ownership — the three signals that predict buying (per my source book). You never pitch. CONTEXT: Who I'm interviewing: [role, segment, relationship]. What I most need to learn this quarter: [1–2 uncertainty areas]. TASK: Produce (1) a 3-line outreach ask (20 minutes, genuinely research, small thank-you if appropriate), (2) 10 questions moving from their world → pain frequency/visibility → who owns it → what they've tried → how buying decisions actually happen there (budget, politics), (3) 3 probes for turning vague answers into specifics, (4) a debrief template: pain / frequency / owner / urgency / buying process / verbatim quotes.

Step 3 — Pattern synthesis with P37 (quarterly). Paste all debriefs + recent win/loss notes; ask for stabilized patterns vs open questions. When patterns stabilize (Ch 4), stop researching and start executing harder.

P37 — Research Pattern Synthesizer

Specification
ROLE: You are a research synthesist. You separate patterns (seen 3+ times) from anecdotes (seen once) and say plainly when data is insufficient. CONTEXT: This quarter's interview debriefs + win/loss notes: [paste]. Last quarter's synthesis (if any): [paste]. TASK: Output (1) stabilized patterns — pain, language, buying process — with the evidence count behind each; (2) changes vs last quarter; (3) updates to push into: ICP Sheet, Question Bank (Vol 1), Message House, trigger map (Vol 2) — as specific edits; (4) the 1–2 remaining uncertainties worth next quarter's interviews; (5) the "stop researching" call: which areas are stable enough to simply execute on.

Checklist & Metrics

  • Quarterly rhythm live: 2–3 battlecards current, 5 interviews done, synthesis run, edits pushed to foundation docs.
  • Metric: foundation-doc edits per quarter sourced from research (zero = the lab is dead).

Chapter 4 — The ICP Lab: From Profile to Discipline

The Principle

Chapter 5: most sales problems are ICP problems. High-quality ICPs own pain and budget. Triggers matter more than features. Narrow ICPs scale faster than broad ones — and ICP discipline is a founder responsibility that lead scoring protects.

The System

Volume 1's P1 built the ICP Sheet; Volume 2's P22 operationalized it into lists. The Lab adds three layers: tiering (A/B/C fit definitions with checkable criteria), the negative ICP (who you refuse, written down), and the quarterly ICP review fed by win/loss data.

Step-by-Step Execution

P38 — ICP Deep Tiering & Negative ICP

Specification
ROLE: You are an ICP analyst. You believe narrow beats broad and that the "no list" protects margins more than the "yes list" grows them. CONTEXT: - Current ICP Sheet: [from P1] + market map choice: [from P34] - All deals from the last 2 quarters: [won/lost/no-decision, with segment, size, cycle, margin, delivery pain afterward] - Deals that closed but we REGRET (bad margin, scope hell, churn): [list] TASK: 1. Tier definitions as checkable criteria: A (drop everything), B (solid), C (only if capacity) — grounded in which deals actually produced profit AND smooth delivery 2. The Negative ICP: 5–8 explicit refusal criteria drawn from the regret list, each with the mechanism (why these deals go wrong for us) 3. Trigger-weighted scoring: how a live trigger (from Vol 2's P23) moves a B to the front of the queue 4. The one-line disqualification scripts: polite ways to decline C-minus and negative-ICP inquiries without burning goodwill VERIFY: Founder signs the Negative ICP. It only works if it is allowed to cost you bad revenue.

P39 — Quarterly Win/Loss ICP Review

Specification
ROLE: You are a revenue analyst running my quarterly ICP truth session. CONTEXT: This quarter's closed deals (won + lost + no-decision) with: segment, tier at entry, trigger present?, cycle length, discount given, outcome, loss reason where known: [paste]. Current tier definitions: [P38]. TASK: (1) Win rate, cycle, and average deal size BY TIER — does the tiering predict reality? (2) Misclassifications: deals we tiered wrong, and the criterion that would have caught them; (3) Negative-ICP leakage: regret deals that slipped through, and the rule to close the gap; (4) Proposed edits to tier criteria (max 3 — stability matters); (5) The message to the team in one paragraph: what we chase, what we decline, next quarter.

Checklist & Metrics

  • Tiers + Negative ICP written and signed; disqualification scripts saved; quarterly review in calendar.
  • Metrics: win rate by tier (A should visibly beat B beat C — if not, tiers are decorative); % of pipeline in Tier A/B (target ≥80%); regret deals per quarter (target: trending to zero).

Chapter 5 — Value Proposition Engineering & Testing

The Principle

Chapter 6: value propositions justify change, not features. Pain without impact does not sell; impact without ROI does not close; ROI beats innovation in real buying decisions. Urgency is a required component — and the proposition must survive executive scrutiny.

The System

The Pain → Impact → ROI → Urgency chain, built per segment, then tested — first against a simulated executive panel (cheap, instant), then against real buyers (the truth). Value props are versioned like software: v1.0 ships, field evidence produces v1.1.

Step-by-Step Execution

P40 — Value Proposition Chain Builder

Specification
ROLE: You are a value proposition engineer. Your standard: the proposition must survive a skeptical CFO asking "so what?" three times in a row. CONTEXT: - Segment + persona: [from P38 tiers] - Their pain (from research synthesis P37): [paste, in buyer language] - Our verified proof: [before/after numbers from the proof library] - Model emphasis (Ch 6): [services → expertise & risk reduction / SaaS → adoption & time-to-value / AI → control, accountability & ROI] TASK: Build the full chain. OUTPUT FORMAT: 1. PAIN: the problem in one sentence of buyer language 2. IMPACT: what it costs them — operational, financial, personal (career risk of the owner) — with the calculation logic shown 3. ROI: the conservative math for fixing it with us (traceable to my proof; state the discount factor applied) 4. URGENCY: why now — the trigger, trend, or compounding cost that makes waiting expensive (never fake urgency; if none exists, say "urgency gap" — that's a targeting insight, not a copywriting problem) 5. The one-paragraph value proposition assembling all four 6. Three "so what?" stress answers: pain → so what → impact → so what → ROI→ so what → defensible decision VERIFY: Every number traces to proof or shown logic. The urgency claim must be one I'd repeat in a live deal.

P41 — Executive Panel Stress Test

Specification
ROLE: You are a hostile-but-fair executive panel: a CFO (cost/ROI skeptic), a CTO/CISO (risk & integration skeptic), and a COO (disruption & adoption skeptic). Each of you has killed a dozen vendor pitches this year. CONTEXT: The value proposition chain: [from P40]. What we actually sell and cost: [paste]. TASK: Each executive attacks the proposition in turn — 3 hard questions each, with what a weak answer sounds like. Then: (1) where the chain survived, (2) where it broke and the exact repair needed (better proof? tighter math? honest scope reduction?), (3) the revised weakest sentence, rewritten, (4) verdict per exec: would this get budget? one line why.

Test with reality: put the value prop into 10 live uses (outbound Email 1s, discovery openings, LinkedIn posts). Log reactions verbatim. Field evidence — not the panel — decides v1.1.

Checklist & Metrics

  • Chain built per top segment (P40), stress-tested (P41), version-logged, 10 field uses scheduled.
  • Metrics: field signals per version (replies, "that's exactly it" moments, discovery conversions); versions per year (2–4 is healthy evolution; zero means it's fossilizing — Ch 6: strong value propositions evolve with the market).

Chapter 6 — The 90-Day Plan & Operating Cadence

Days 1–15: P33 model analysis → Model Decision Doc. P34 market map → primary vertical chosen. Re-aim Vol 1 content queue and Vol 2 universe at the vertical. Days 16–45: P35 battlecards for top 2–3 competitors. First 5 research interviews (P36) booked and held. P38 tiering + Negative ICP signed. Disqualification scripts in use. Days 46–90: P40 + P41 value prop chain per top segment; 10 field uses logged. First quarterly rituals run: P37 synthesis, P39 win/loss review, edits pushed into all foundation docs. Day 90: the lab's first full cycle complete — foundations now update themselves quarterly instead of decaying.

If you fall behind, protect: the interviews (real conversations are irreplaceable), the Negative ICP (it protects everything downstream), and the quarterly review dates.


Appendix — Prompt Index & Cadence

#PromptPurpose
P33Business Model EconomicsModel Decision Doc
P34Market Mapping & Vertical SelectionPrimary vertical
P35Competitor TeardownBattlecards
P36Buyer Research Interview Kit5 interviews/quarter
P37Research Pattern SynthesizerQuarterly foundation edits
P38ICP Tiering & Negative ICPTier criteria + refusal list
P39Win/Loss ICP ReviewQuarterly truth session
P40Value Prop Chain BuilderPain → Impact → ROI → Urgency
P41Executive Panel Stress TestPre-field validation

Cadence: twice-yearly model review (P33) · quarterly: battlecard refresh, 5 interviews, P37 synthesis, P39 ICP review, value-prop versioning · continuous: disqualification discipline. Tool stack: Volume 1–2 stacks cover everything; no new tools required.


Closing Note

Chapters 1–6 of the Booklet all reduce to one discipline: know exactly who you serve, what it's worth to them, and what you refuse. Everything downstream — content, outbound, deals, scale — inherits either the clarity or the confusion you build here. Run the lab quarterly, and the foundations stop being documents and become an advantage that compounds.

— Companion Volume 3 · FISTA Solutions · Sales Booklet 2026