The problem this solves
Deals cool in the gap between 'send me a proposal' and the proposal arriving. The buyer's enthusiasm peaks on the call; every day of drafting delay lets doubt, competitors, and other priorities back into the room. Yet proposals routinely take days, because writing one means switching from selling into document production: restating scope, formatting a template, and finding the two focused hours the week refuses to yield.
The irony is that the substance already exists. By the time a proposal is requested, the scope has been discussed and effectively agreed in the thread; what remains is transcription into a presentable, signable artifact. That transcription is precisely the kind of work that steals selling time while adding no judgment - the judgment already happened in the conversation itself.
Follow-through has a notification problem too. A proposal drafted but unnoticed helps nobody; the seller is on calls, and the draft-ready moment gets lost among a hundred notifications. The handoff works when it arrives on the channel the seller actually feels buzz - which for most sellers between meetings means WhatsApp. A ping there gets the two-minute review done between meetings instead of tomorrow.
How the mission runs
- Extract the scope from the thread. The agent reads the scope as discussed in the mission thread - deliverables, timeline, pricing, terms already mentioned - and assembles it into a structured outline. Anything ambiguous is flagged as an open item in the draft rather than silently guessed, so gaps surface at review instead of at signature.
- Draft the one-pager. The proposal is written to one page by design: scope, timeline, investment, and next step, in clean client-facing language. One page respects the buyer's attention and forces clarity on the seller's side; supporting detail can always follow once the core is agreed.
- Create the document in PandaDoc. The agent builds the proposal in PandaDoc as a ready-to-send draft - formatted, structured for signature, and sitting in your account. It is deliberately left unsent: a proposal is a commitment, and commitments go out on a human decision after review.
- Ping you on WhatsApp when the link is ready. The moment the draft exists, a WhatsApp message lands with the direct link. You open it from wherever you are, give it the two-minute read, fix anything the thread under-specified, and send it while the buyer's enthusiasm is still today's news.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A finished one-page proposal sitting in PandaDoc - scope, timeline, investment, and next step drawn from the thread - plus a WhatsApp ping with the draft link the moment it is ready. Open items the thread left ambiguous are flagged inline so review is fast and honest. The gap between 'send me a proposal' and a reviewable document shrinks from days to the length of one mission.
Make it yours
- Chain it to the meeting: run the mission right after the call while the scope discussion is freshest in the thread.
- Keep a per-service outline in the prompt so recurring proposal types come out consistent while the scope details stay deal-specific.
- Swap the ping destination to your team channel when proposals need a second pair of eyes before the sender ever sees them.
Frequently asked questions
Does the proposal go to the client automatically?
No. The mission ends at a draft in PandaDoc and a ping to you. Sending a proposal is a commercial commitment, and that action stays human by design. What the agent removes is the production delay, so your review happens the same day the client asked instead of at the end of the week.
What if the thread did not cover pricing or terms?
The draft marks them as open items in place rather than inventing numbers. You will see exactly which sections need your input during the review pass. In practice this doubles as a checklist of what the sales conversation skipped, which is useful information on its own.
Why a one-page format?
Because proposals are read on phones between meetings, and the decision-relevant content - what, when, how much, what next - fits a page when written with discipline. A tight page gets read and forwarded; the expanded detail belongs in the contract stage after the yes.