Build a Champion-Ready Business Case & Internal Pitch: 5-Prompt Chain

What this chain helps you accomplish

Turn a real discovery conversation into an internal decision package that a potential customer advocate can review, adapt, and use in discussions you may not attend.

Five connected prompts help you verify what the buyer actually said; assess whether your contact is a genuine advocate or still a helpful coach; map the people and approvals involved; assemble a defensible business case; draft a concise internal pitch, leave-behind, and objection responses; and agree on the next buyer-validated actions.

You finish with an Internal Business Case, a Champion Enablement Pack, and a Champion Alignment & Next-Step Plan. The outputs clearly separate confirmed evidence from assumptions, and they do not manufacture return on investment, budget approval, buyer support, or urgency.

The package is a draft until the seller checks it and the customer contact explicitly confirms what they are comfortable presenting internally. An AI-generated pitch is not evidence that someone has agreed to champion your solution.

When to use it

• After substantive discovery: You have attributable notes about a business problem, desired outcome, and possible next decision, but need to help the buyer explain the case internally.
• Before a wider buying-group conversation: A supportive contact has offered to engage colleagues, or you need to establish who else must evaluate the proposal.
• During an evaluation or expansion decision: Several functions may care about value, risk, budget, implementation, or competing priorities.
• When internal momentum is uncertain: You want to distinguish a genuine advocate from an informative contact and propose a credible next step without assuming endorsement.

Do not use this as a substitute for discovery. If you have no attributable buyer evidence, start with research and discovery questions. If there is no willing internal advocate, the chain should produce an advocacy-readiness and stakeholder-access plan—not falsely claim a champion is already selling for you.

Do not use it to fabricate a financial case. If baseline metrics, benefit assumptions, or commercial terms are missing, the business case must remain qualitative or contain explicitly labeled scenarios requiring buyer validation.

Before you begin

Minimum tools: Any conversational AI application capable of receiving and generating text in one continuing chat. A paid plan, web browsing, CRM integration, document-generation feature, and automation are not necessary. Optional file uploads can help only if supported in your chosen tool. You can paste appropriately sanitized notes directly into ChatGPT, Claude, Gemini, or another text-capable tool. Compatibility of specific premium features has not been tested.

Prepare the following inputs. The double-brace placeholders below are ordinary text to replace before pasting; they are not connected to Promptifi or your CRM.

• {{ACCOUNT_NAME}} — Required. Customer or prospect name from your account record. Example: Cedarfield Equipment. If you cannot identify the account, stop.
• {{DEAL_STAGE_AND_DECISION}} — Required. Current relationship or opportunity stage and the specific next customer decision you are trying to enable. Source: CRM plus your notes. Example: discovery completed; determine whether to explore a supervised pilot. If no decision is defined, choose a discovery or evaluation decision instead of presuming a purchase.
• {{OFFER_AND_SCOPE}} — Required. What your product or service actually offers, its limitations, and intended use in this deal. Source: approved product materials. Example: a service that centralizes incoming service-request status; implementation still needs scoping. If scope is uncertain, state the uncertainty.
• {{DISCOVERY_EVIDENCE}} — Required for a buyer-facing package. Dated, attributable discovery notes and actual buyer statements, each labeled D1, D2, etc. For each provide speaker, date, precise meaning, and any qualification. Example: D1 — Nov. 2, 2026 — Service Director stated handoff status is hard to track; no impact figure given. If none, enter NONE; Prompt 1 must stop with a discovery-gap plan rather than an invented case.
• {{ADVOCATE_CONTACT}} — Required as a status field; may be unverified. Known person, verified title, relationship, evidence of influence, personal stake, and examples of actual internal advocacy. Source: seller notes and what the contact has said or done. Example: Jordan Lee, Service Director; offered to introduce operations lead; no evidence yet of executive sponsorship. If unknown, enter NOT ESTABLISHED.
• {{BUYING_GROUP_AND_APPROVAL}} — Optional. Known people, verified roles, objectives, objections, decision criteria, procurement/security/legal steps, and their sources. Example: CFO reviews capital purchases per D2; final approval authority not verified. If missing, enter UNKNOWN.
• {{COMMERCIAL_TERMS}} — Optional. Seller-approved price, term, currency, implementation cost, and any exclusions, with quote version or date. Example: annual subscription $48,000; one-time onboarding $8,000; proposal dated Nov. 3, 2026. If absent, enter NOT PROVIDED; do not estimate prices.
• {{VALUE_INPUTS}} — Optional. Buyer-reported baseline, volume, minutes/hours, loaded labor rates, error costs, or other measurable benefits, with source and validation status. Example: 1,100 service requests per month according to D3; time lost per request unknown. If absent, enter NONE; no defensible ROI can be calculated.
• {{APPROVED_PROOF}} — Optional. Approved claims, relevant customer evidence, and explicit sharing permissions. Example: company-approved fact sheet, version 2; no published quantified results. If none, enter NONE.
• {{GUARDRAILS_AND_TIMING}} — Optional. Seller constraints, customer approval preferences, timeline known from buyer, information restrictions, and anything that must not be mentioned. Example: do not cite another customer or mention unapproved savings figures. If none, enter NONE.

Source rule: A seller note records what a named person actually said; it does not establish that the statement is objectively true. Mark confirmed statements as buyer-reported where appropriate. Separate CONFIRMED/BUYER-REPORTED, ASSUMED, and UNKNOWN. Preserve D# identifiers and dates.

Data handling: Use a company-approved AI environment. Do not paste confidential pricing, private meeting transcripts, sensitive personal data, or customer information unless your company and the customer permit that use. Redact identifiers where necessary.

Preparation time: The first run depends on the availability and quality of discovery notes, not on an unverified time-savings claim.

How to run the chain

1. Open a new conversation in an approved text-capable AI tool. Fill in and paste the complete Starting Deal Context from Chain Steps. Include the dated D# evidence you are authorized to share.
2. Copy and run Prompt 1 only. Inspect the evidence ledger and the contact's actual advocacy status; correct mistaken statements before continuing.
3. Explicitly approve the result using: APPROVED — Discovery & Advocate Readiness Brief — v1. Use only this version in later prompts. Change the artifact name and version after each step.
4. Run Prompt 2 in the same chat. It must name and use the approved artifact from Prompt 1, then stop. Review and approve the Buying-Group & Approval Route Map.
5. Run Prompts 3, 4, and 5 one at a time, checking and approving each complete artifact before the next step. Do not run the whole chain as one combined prompt.
6. Save the approved Internal Business Case, Champion Enablement Pack, and Champion Alignment & Next-Step Plan in a company-approved location. Confirm the buyer-facing draft with the actual contact before sharing it more widely.

Two different approvals: Seller approval authorizes an AI artifact as the input for the next prompt. It is not approval by the buyer to send, present, attribute, endorse, or purchase anything. Obtain explicit buyer permission before using their voice, quoting them externally, or distributing the draft.

How to correct an output: Specify the artifact name, current approved/draft version, exact mistake, and corrected source. Request a complete next-version rewrite, review it, and explicitly approve it. Rerun later prompts if their inputs have changed.

If context is lost: Start another chat, paste the Starting Deal Context plus the latest approved prerequisite artifacts and versions, and run only the next numbered prompt. The optional handoff template appears at the end of Chain Steps.

Completion standard: The business case accurately states the evidence and unresolved economics; the pitch and leave-behind use only customer-acceptable claims; objections have honest answers; and the next-step plan states who must validate or authorize each action. No buyer action occurs automatically.