Sales · Proposals
Proposals drafted from your call notes, not from a template
Every proposal is 70% the same document and 30% the reason this customer is different. The 30% is the part worth your evening.
What the worker does
Proposal writing in Polaris means assigning a task to an AI worker whose skill file holds your section order, scope language and pricing rules. The worker reads the call notes and the deal context from your docs, drafts the proposal, ticks the acceptance criteria you set, and delivers it as a file attached to a comment. The rep edits the argument and sends it.
- Connections
- Google Drive · HubSpot
- Delivered as
- A generated file on the task
- Never automated
- Price, terms, and sending
The Friday-night proposal
A proposal usually gets written at the worst possible time: after the call, before the follow-up, by the person who most needs to be preparing for tomorrow. So it gets built by opening the last one and replacing names, which is how a paragraph about a different customer's warehouse ends up in a software contract.
A worker starts from the same materials the rep would, and it does not get tired at the fourth section.
Where each part of the document comes from
| Section | Source | Who is responsible |
|---|---|---|
| Understanding of the problem | Discovery notes in Docs | Worker drafts, rep corrects the emphasis |
| Scope of work | The skill file plus the deal's notes | Worker drafts from your standard scopes |
| Timeline | Your delivery norms in the skill file | Rep confirms it is achievable |
| Pricing | Never generated | Rep, every time |
| Terms | Your approved terms document | Worker inserts, legal owns the wording |
| The reason us | Discovery notes | Rep writes or rewrites |
Acceptance criteria worth setting
The worker ticks each one as it works, so you see what it believes it did before you open the file.
Every claim traceable
No statement about the customer's situation that is not in the notes. This is the criterion that stops invented context.
Pricing left blank
A visible placeholder rather than a number, so nobody can send a proposal with a machine's guess in it.
Named deliverables
Each line of scope has an artifact and a date, not a verb.
One page of summary
A summary the buyer can forward to somebody who was not on the call.
Related sales work
Account briefs waiting for you before the first call
Ten minutes of research changes a first call. Nobody has ten minutes before a first call.
Battle cards that are still true this quarter
Enablement content is written once, used constantly, and updated never. The updating is the assignable part.
A pipeline review that is assembled before the meeting
The forecast meeting is worth having. Spending the first twenty minutes reconstructing what happened is not.
Questions people ask
+Can it produce a PDF?
Yes. Deliveries arrive as comments on the task and can include generated files, including PDFs and documents, attached where the rest of the deal context lives.
+Where do the call notes come from?
From Docs in Polaris, or from files in a connected Google Drive. The notes need to exist somewhere the worker can read; a proposal drafted from nothing reads exactly like a proposal drafted from nothing.
+How do we stop it inventing customer details?
Make traceability an acceptance criterion: no statement about the customer that is not in the notes. The worker ticks the criteria as it goes, and anything it could not source it reports in the delivery comment.
+Is a proposal draft worth about $2?
It is billed on the human-equivalent hours the formula computes from observable effort, including the finished prose produced, so a long proposal costs more than a short one. Each session is a line on the work log you can challenge.
Related
Sales work, with the admin handed to an AI teammate
Selling is a conversation. Almost everything around the conversation is production work, and production work can be assigned.
Battle cards that are still true this quarter
Enablement content is written once, used constantly, and updated never. The updating is the assignable part.
Account briefs waiting for you before the first call
Ten minutes of research changes a first call. Nobody has ten minutes before a first call.
Hire an AI content writer
Briefs go in as tasks, drafts come back as versioned docs you can comment on line by line, and your voice rules live in a file rather than in one person's head.
Connect Google Drive to Polaris
Files a worker produces already arrive as attachments on the task. Files your team already keeps in Drive are the part still waiting.
Acceptance criteria
Written before the work, checkable after it, and binary either way.
When the deliverable is a file
A chat reply is not a deliverable if the thing you needed was a document somebody can open.