- Industry
- IT Company
- Department
- Sales
- Team
- Deal Conversion
- Kind
- Assistant
- Approver
- Delivery Director
- Code
- SAL-10
It drafts tailored proposals for client projects, managed services and SaaS deals: the understanding of the need, approach and phases, team shape, assumptions, commercial model (fixed price, time and materials or subscription) and the case studies that fit. It saves the draft on the opportunity and asks the delivery director to confirm the approach, effort and assumptions before it goes to the client.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the opportunity, account history, requirements documents and past proposals to this client..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Delivery Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it attaches the proposal draft to the opportunity and moves it to proposal review. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The proposal library: templates by deal type, the delivery methodology, rate card, standard assumptions and exclusions, approved case studies and client reference permissions.
Reads from
the CRM: the opportunity, account history, requirements documents and past proposals to this client.
Acts in
the CRM: it attaches the proposal draft to the opportunity and moves it to proposal review.
Hands back
An object with sections (a list with heading and text), team (a list with role and allocation), commercials (model, price_usd, payment milestones), assumptions (a list), exclusions (a list), margin_percent and requirement_coverage (a list with requirement and section).
Asks a person when
The forecast margin is below 30 percent, the proposal commits to an SLA or named team, or it uses a case study without consent.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Lowest proposed margin (%) | 30 | A proposal with a forecast margin below this needs the approver. |
| Most pages | 15 | Longer drafts are cut back. |
| Risk premium on fixed price (%) | 15 | Added to fixed-price effort for estimation risk. |
| Case studies need consent | On | When on, only case studies with client consent on file are used by name. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Answer every requirement and evaluation criterion, in the client's order.
- Price fixed-price work with a 15 percent risk premium on effort; state every assumption and exclusion.
- A forecast margin below 30 percent needs the Delivery Director.
- When on is true, name only clients whose consent is on file.
- Keep to 15 pages.
- Never promise a named person, a date or an SLA the delivery team has not confirmed.
See the Proposal Drafting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.