Build an AI Sales Operating System

An AI sales operating system is a repeatable way to turn buyer conversations into a current deal record, next steps and reviewed sales deliverables. It combines your company context, your writing voice, evidence from each call and rules for advancing a deal.

Deal OS packages that workflow in plain-text files you own. Its core method and 14 copy-and-paste prompts are AI-agnostic. Use them in your company-approved AI chat, including ChatGPT, Claude, Gemini or Copilot. File uploads, persistent projects and automation depend on your tool and plan. You do not need automation to start.

This guide walks through the folder, onboarding and the work after a call. The rule to carry through every step: a seller's claim and a buyer's confirmation are different evidence.

The Files You Keep

Markdown files use the .md extension. They are ordinary text with headings and lists. You can open them in a text editor, paste them into a chat or attach them to an AI tool that reads files.

These are the main parts of the Deal OS starter folder:

deal-os/
  START-HERE.md
  GIVE-THIS-TO-YOUR-AI.md
  company/company-file.md
  voice/voice-file.md
  deals/_template/deal-file.md
  method/
  prompts/
  example/

• Company File: what you sell, who buys it, pricing, approved customer proof and the CRM fields your team uses. Keep proof tied to the product it supports.
• Voice File: how you write to buyers, with your own examples and preferences.
• Deal File: one account's evidence, stakeholders, current stage, risks and next steps. Duplicate the template for each deal.
• Method and prompts: the rules for interpreting evidence and doing recurring tasks, from CRM notes to a check before sending a draft.
• Examples: fictional companies and deals that show how completed files look. Replace example facts with your own.

Keep your saved files as the current record. A chat's memory is not a reliable substitute for checking which version of a deal file it read.

Set Up Deal OS

1. Extract the purchased ZIP. Open START-HERE.md inside the deal-os folder. Keep the PDF guide beside the folder for reference.
2. Start a chat in your approved AI account. Attach GIVE-THIS-TO-YOUR-AI.md. Attach the ZIP too if your tool reads ZIPs. Otherwise, attach the Company File and Voice File separately. Paste their text if attachments are unavailable.
3. Type “Onboard me.” The onboarding instructions ask the AI to interview you, fill the files from your answers and walk you through your first task. Leave unknowns empty rather than inventing answers.
4. Review and save the files it returns. Check product names, pricing and customer results. Remove any sample facts that do not belong to your business.
5. Choose one deal. Copy the deal template into its own account folder. Use a transcript with known speakers and a call date. For an existing deal, process calls oldest first so corrections remain traceable.

The onboarding guide budgets about an hour, mostly for your answers. You can stop and save your files partway through. Use only buyer data your company permits in that AI account, with the required recording consent.

Run the Workflow After a Call

1. Supply the Current Record

Provide the latest Deal File, the call transcript and the relevant Company File and Voice File. Include the instructions for the task you want to run. The first copy-and-paste task in the bundle is prompts/01-crm-notes.md.

Ask the AI to identify missing inputs before drafting. If speakers appear only as “Speaker 1” and “Speaker 2,” identify them first. The model should not guess who is the buyer.

2. Separate Evidence From Assumptions

Deal OS uses four evidence states:

• CONFIRMED: the buyer stated or agreed to the fact on the record, with an exact quote, speaker, call date and timestamp.
• MENTIONED: the topic came up without buyer confirmation. A seller's statement followed by “okay” belongs here.
• ATTESTED: the rep reports something that happened off the call, with its actual date and a note. It counts toward applicable stage gates, not health or forecast.
• UNKNOWN: the record does not establish the fact.

Open the transcript and check the quotes. A citation makes a claim checkable; it does not make the model correct. When a buyer corrects a number, update the current fact and retain the earlier evidence.

3. Check the Stage Before Advancing

Deal OS covers account research, discovery, business alignment, validation, consensus, negotiation and closed outcomes. Each stage has exit criteria. An open criterion blocks the recommended move. Review one stage at a time, even when the CRM already shows a later stage.

This is a decision rule in the method. A plain-text file cannot prevent someone from dragging a deal to another stage in their CRM. The rep and manager still need to apply the rule.

4. Draft, Check and Save

Use the reviewed record to draft CRM updates, a buyer follow-up or preparation for the next meeting. Every next step needs an owner and a specific date. If nobody agreed to a date, mark it as missing. Keep proposed dates separate from agreed commitments.

Run prompts/14-send-check.md before sending buyer-facing work, then review it yourself. In a chat or project, request the whole updated Deal File, save it and replace the older working copy. Update your CRM from that same reviewed record.

A Worked Example: A Failed Demo Check

The bundle includes Calder Logistics, a fictional dealacross three calls. Its published sample outputs were generated in Claude on October 18, 2026, using fictional November and December call dates. They illustrate the method, not a customer outcome or a benchmark across AI providers.

In the demo, a check returns 47 correct results out of 50: 94% against a 95% requirement. Marcus, the buyer, says at [10:02]:

“Ninety-four isnt ninety-five. Fix the handwritten ones and I'm in.”

The check stays open. Marcus's support is conditional. The next action is a re-test, and the deal does not clear validation until the required evidence exists. An enthusiastic recap cannot change the result.

The same example includes a buyer correcting a dollar amount and a seller introducing another product without approved customer proof. Those are useful checks when trying a different AI tool: does it preserve the correction, and does it refuse to borrow one product's results for another?

Choose Your AI Tool by Capability

Start with the approved tool you already use. The portable part is your files, instructions and evidence. Responses still vary by model, so compare each output with the source material.

• Text chat: paste a task's instructions and relevant source text. Save the response manually. If the input is too large, use a tool with enough capacity rather than silently omitting evidence.
• File uploads or projects: attach the files and keep them current. Check which files the tool actually read. Uploading a folder does not guarantee every file is available in every answer.
• File-writing automation: use it only when your tool supports it and you have checked the changes. Keep a previous version so an incorrect update is recoverable.

The current bundle also includes 12 Claude skills and a Claude desktop workflow. Those are optional implementations. They are not universal plug-ins for ChatGPT, Gemini or Copilot, and their automation should not be assumed to work unchanged in another tool. The text-based workflow remains the common starting point.

Common Questions

Does Deal OS Replace a CRM?

No. It prepares the evidence, notes and decisions you put into your CRM. Your CRM continues to hold your team's pipeline and reporting. Keep stage, owner, dates and next steps consistent between them.

Do I Need to Code or Buy a Particular AI Subscription?

No coding is required for the copy-and-paste workflow. Deal OS does not require one AI provider. Your provider's limits and your company's data policy determine which account and features you can use. Paid automation features are optional.

What Should I Test First?

Use one completed call. Check whether the output distinguishes buyer statements from seller claims, leaves unknown facts unknown and gives accurate sources. Which statement in your current deal summary would you struggle to trace back to the buyer?

What Comes With Deal OS?

The download includes the guide, onboarding folder, Company and Voice Files, Deal File template, 14 prompts, 12 optional Claude skills, stage criteria, nine plays, five templates and a fictional worked example. The files stay yours when you change AI tools.