Proposal teams
Send the proposal with the source beside the sentence.
For teams answering an RFP or writing a client proposal. The draft is built from the request you upload. A reviewer signs it before it goes out.
Sample
Section 2 · Approach
Work begins the week after the kickoff meeting.
From the request to a draft someone can sign.
The same four moves on every bid. The files change. The check does not.
01
Read the request
Upload the RFP, the notes from the call, or both. The draft has to come from those files.
02
Draft the response
A playbook turns the request into an executive summary and a full response, in the language of the bid.
03
Check each claim
A factual sentence is marked Supported, Needs source, or Contradicted, with the passage it was checked against.
04
A person signs off
Sales review, or whoever owns the bid, approves the file before it is sent.
Playbooks for a bid.
Each one is a saved way of working, with the steps visible. Names below are the playbooks in the product.
Proposal Writer
Starts from the prospect’s notes, writes the summary and the full draft, then waits for sales review before anyone sends it.
Reviewer: Sales review
RFP Response Agent
Parses the RFP, maps the requirements, and drafts the response section by section. The sign-off is still the reviewer in the workflow above.
Competitive Intelligence
Researches the comparison the bid needs and writes it up so the proposal can cite the file, not a memory.
Design partner
Bring one document.
We sit with a small number of teams and run their own file: a proposal, an article, or a client draft. You see the margin notes on your words.