Proposals start from a blank page
You remember the call, but the details are in a recording. Rebuilding scope, goals and timeline from scratch takes an evening.
AI proposal writing turns the transcript of a discovery call into a structured first draft in your own template, using the client's words and your past proposals. Pricing is left blank for you to fill in. You review and send it yourself, and the assistant reminds you to chase the reply.
You remember the call, but the details are in a recording. Rebuilding scope, goals and timeline from scratch takes an evening.
The best explanation of your process is in a proposal from last spring. Finding and adapting it takes as long as writing it again.
The prospect compares three proposals. The one that arrives within a day of the call, in their language, often gets read first.
| When | The assistant | You or your team | Result |
|---|---|---|---|
| A discovery call is tagged "proposal" in your recorder or calendar | Reads the transcript and pulls out the client's goals, constraints, stakeholders, timeline and budget signals, quoting their own phrases. | You glance at the extracted brief and correct any misunderstanding. | A one-page client brief that proves you listened. |
| The brief is confirmed | Selects the closest past proposals and service descriptions from your Drive, then drafts each section in your template: context, scope, approach, timeline and assumptions. | You edit the scope and remove anything you would not promise. | A full draft in your brand format, built in minutes. |
| The draft reaches the pricing section | Leaves the price lines blank with a note listing the scope items that usually drive cost, and shows two similar past quotes for reference. | You set every price and discount yourself. | The figures in the proposal are always ones a person chose. |
| You mark the draft Ready | Exports a PDF or a link in your template and prepares a cover email with the key outcome and a proposed next step. | You send the email from your own account. | The proposal reaches the client within a day of the call. |
| The proposal has been sent for 3 days with no reply | Reminds you and drafts a short follow-up that refers to a goal from the call, not a generic "just checking in". | You approve and send, or snooze it for a week. | No proposal is left unchased because the sender got busy. |
| A proposal is accepted or declined | Updates the deal in your CRM, and for a win, drafts the onboarding checklist and kickoff email for review. | You confirm the outcome and approve the kickoff message. | The next step starts the day the answer arrives. |
A 45-minute discovery call with a new prospect finishes. You tag the recording "proposal".
The client brief is ready: their goals in their words, the two constraints they mentioned and a timeline they gave.
The full draft is in your template. You fix one scope line and fill in the price table from your own numbers.
You mark it Ready. A PDF and a cover email draft appear. You read the email, tweak the first line and send.
No reply yet. The assistant prompts you with a follow-up draft that mentions the client's own deadline.
The client accepts. The CRM stage changes, and an onboarding checklist and kickoff draft are waiting for you.
If a tool has an API or an export, it can usually be connected.
Pricing, discounts and payment terms are never filled in by the assistant. It shows reference points; the number is yours.
Scope is drafted from what was said on the call and from your approved service descriptions, and anything uncertain is flagged for you.
It reads only the folders you point it to, and one client's proposal is never used as source text for another client's.
The assistant drafts. A person on your team sends.
This isn't a template with your logo on it. Every build starts from how your business actually runs — so there's no off-the-shelf demo, and we won't pretend otherwise.
We map how your week and your business actually run, and pick the first tasks worth handing over.
On the strategy call we build one of your real tasks with AI, on screen — your data, not a generic demo.
We scope the build with you on a strategy session and quote it in writing — agreed before a single workflow is built.
The assistant is wired into your tools, with inputs set up for each person on your team.
We go live, then tune reminders, reports and sign-offs as your team settles in.
The assistant reads the transcript of your discovery call, extracts the client's goals, constraints and timeline, and drafts each section in your own proposal template, borrowing wording from your past proposals. You review the draft, set the prices and send it. The first draft takes minutes instead of an evening.
No. Price lines are left blank for you, and scope comes only from the call and your approved service descriptions. Anything the assistant cannot support from those sources is flagged in the draft as a question for you, instead of being filled in with a guess.
Proposal software gives you a nice container and e-signature. It does not listen to the call or write the content. A built assistant fills your template from the discovery call and past proposals, leaves pricing to you, and chases the reply. You can still send through the software you like.
Yes. It works inside your own template, with your headings, tone and standard sections, and learns from proposals you have already won. If you have two service lines with different structures, each gets its own template, so a design proposal never reads like a consulting one.
Then the assistant works from the notes you give it, such as a voice memo, a few bullet points or an email thread. The draft is thinner without a transcript, so most owners switch on call recording for sales conversations, with the other party's consent.
It runs on your accounts and reads only the folders and recordings you connect. Each proposal is built from that client's call and your own library, not from other clients' documents, and you can remove the assistant's access whenever you wish.