Build a proposal that survives procurement

AI proposal generator is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.

A proposal is read by people who were on none of the calls, so it has to open with what the buyer told you, in their words — get that visibly right and it buys the read for everything after it.

What is in this skill

nameproposal-structure
descriptionOur proposal skeleton and what each section must contain. Use when drafting a proposal, statement of work, or any document that asks a buyer to commit.
allowed-toolsnone — this skill adds judgement, not reach
compatibilityZealos, Claude Code, Cursor, Codex and any client that reads SKILL.md
licenseFree to use and edit

How it works

  1. 1Open with their situation and pain, quoted from the calls. If this section is wrong, nothing after it matters.
  2. 2State success in their metric, their number and their timeframe, not yours. A proposal that defines success in vendor terms is a brochure.
  3. 3Include what you need from them — access, people, decisions, and by when. This is the section every failed implementation traces back to.
  4. 4Put the price in one plain table with no euphemism, and end with one next step, one owner and one date.

The skill itself

---
name: proposal-structure
description: Our proposal skeleton and what each section must contain. Use when drafting a proposal, statement of work, or any document that asks a buyer to commit.
---

# Proposal structure

A proposal is read by people who were not on any of the calls. Write for the
skeptic in the room, not for your champion.

## Sections, in order

1. **What you told us** — their situation and pain, in their words, with
   evidence from the calls. If this section is wrong, nothing after it matters.
   Getting it visibly right is what buys the rest of the read.
2. **What success looks like** — their metric, their number, their timeframe.
   Not ours.
3. **What we will do** — scope, in plain language. Phases with dates.
4. **What we need from you** — the part most proposals omit and every failed
   implementation traces back to. Access, people, decisions, and by when.
5. **What it costs** — plainly. One table. No "investment" euphemism.
6. **Why us** — last, and short. Two proof points relevant to *their* situation,
   not a logo wall.
7. **Next step** — one action with a date.

## Rules

- Quote them. A line in their own words, early, does more than a page of ours.
- Every claim gets a number or gets cut.
- No section that exists to look thorough.
- If a section could appear unchanged in a proposal to a different company,
  it is not doing any work.

## Length

Shorter than they expect. Detail belongs in an appendix that the champion can
forward to procurement.

Who uses it

Account executive

The first draft arrives assembled from the actual calls rather than from last quarter's proposal with the company name swapped.

Solutions consultant

Scope stops being negotiated after signature, because the what-we-need-from-you section made the dependencies explicit while there was still leverage.

Founder

You stop spending a Sunday on every proposal, and the ones you send are shorter than the ones you used to agonise over.

Frequently asked questions

What should a proposal contain?

What they told you, what success looks like, what you will do, what you need from them, what it costs, why you, and one next step. In that order.

How long should it be?

Shorter than they expect. Detail belongs in an appendix the champion can forward to procurement without forwarding the argument.

Can it pull from call transcripts?

Yes — that is what makes the first section credible. Pair it with a recap skill so the quotes are already extracted.

Related skills

Summarize calls and update the CRM

Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.

MeetingsCRMZoom/call-recap-format

Brief yourself before every call

A pre-call brief is worth writing only if it changes what you ask: who is in the room, what they are measured on, what happened last time, and the one question you cannot afford to leave without answering.

CoachingMeetingsAccounts/discovery-questions

Triage your inbox by deal impact

AI email triage is worth having only when it sorts by consequence rather than by recency: what blocks a deal, what someone is waiting on you for, and what can be read at the end of the week.

EmailGmailAccount executives/email-rules

Log a call without inventing fields

CRM data hygiene survives AI only if one rule is written down first: a field left blank is a known unknown, while a field filled in by inference is an unknown unknown that will be reported on as fact.

CRMHubSpotSalesforce/crm-field-conventions

Qualify a lead against our ICP

Qualification is a claim about evidence, not a score: a deal is qualified when every criterion has a source you can quote, and unevidenced criteria are named rather than filled in optimistically.

DealsProspectingCRM/meddicc

Make AI writing sound like your company

A writing-voice skill is the highest-leverage thing you can give an AI, because it changes every sentence the product produces and it needs no tools, no integrations and no data.

WritingEmailProposals/our-writing-voice

Skills, in your workspace

Write it once. Every agent follows it.

Twelve built-in skills ship with every workspace, and you can draft your own with AI or import any public SKILL.md from GitHub.

7-day free trial. Set up in minutes. Cancel anytime.