Proposal Generator
1. The Problem
A proposal is both a sales document and a delivery commitment. Writing a good one from scratch takes 2–4 hours of a senior person's time — time that cannot be delegated to someone junior because the proposal must reflect deep understanding of the client's situation. Multiply that across twenty proposals per month and you have consumed 40–80 hours of high-value capacity on document production. The proposal process is a tax on your best people's time, paid every time you try to grow.
2. Integration & Webhook Setup
Follow the exact steps below to configure and deploy this automation inside your OpenClaw workspace.
- 1Create a new agent named `proposal-generator`. Configure your `RATE_CARD` section with your service offerings, standard scopes, and pricing tiers — the agent uses this to build the services and investment sections of each proposal.
- 2Build your `PROPOSAL_TEMPLATE` structure: define the sections that appear in every proposal (executive summary, proposed approach, team, investment, timeline, next steps) and add your brand language, standard terms, and case study snippets for each section.
- 3Set up your discovery call data ingestion: the agent can accept structured notes from a configured Notion template, a CRM activity log, or a simple form you complete immediately after each call. The more structured the discovery data, the more accurate the output.
- 4Configure client research: the agent automatically pulls company information from Companies House (UK), LinkedIn, and recent news before writing the executive summary. Add any client-specific context manually in the `CLIENT_NOTES` field after the discovery call.
- 5Connect your e-signature tool (DocuSign or HelloSign) so approved proposals can be sent with a single click — and the agent is notified when the proposal is opened, viewed, and signed.
3. The Context Payload (context.json)
Save this file as: .openclaw/agents/proposal-generator/context.json
{
"automation_id": "15",
"title": "Proposal Generator",
"level": 2,
"tier": "Agency Foundation",
"setup_time": "3–4 hours",
"estimated_api_cost": "~$10–$20/mo",
"client_price_range": "$500–$2,000",
"agents": [
{
"role": "orchestrator",
"model": "claude-3-5-sonnet",
"temperature": 0.2,
"max_tokens": 4096
}
],
"memory": "session",
"output_format": "structured_json",
"human_review_gate": true,
"documentation_standard": "required"
}4. Execution Commands
Run these commands from your openclaw-workshop/ directory to validate, test, and schedule this automation. Commands are taken directly from The OpenClaw Income Engine, Appendix F.
# ── STEP 1: Generate a proposal for a specific CRM deal ──
$ openclaw run proposal-generator --deal-id <hubspot_deal_id>
$
# ── STEP 2: Review the generated proposal (PDF in Drive) ──
# Open the PDF from your Proposals Drive folder → review and approve.
$
# ── STEP 3: Approve and send via DocuSign ──
$ openclaw approve proposal-generator --proposal-id <id> --action send-docusign
$
# ── STEP 4: Monitor DocuSign status ──
$ openclaw run proposal-generator --docusign-status --proposal-id <id>
$
# ── Generate a proposal from meeting notes (no CRM deal required) ──
$ openclaw run proposal-generator --notes "Client wants X, budget is Y, main concern is Z" --service "{{SERVICE_NAME}}"
$
# ── Set up a webhook trigger from CRM proposal-stage ──
$ openclaw webhook create proposal-generator --trigger crm_deal_stage_change
# Set trigger to fire when deal stage = "Proposal Requested"
$
# ── Switch e-sign provider to HelloSign ──
$ openclaw run proposal-generator --context.esign.provider="hellosign"