Proposal assistant for services
Turn discovery notes into a structured proposal draft with scope checks and human review.
This example explains a workflow design and its controls. It does not represent verified client results. Tooling and benefits must be validated in each project's context.

Solution example
Proposal assistant for services
Turn discovery notes into a structured proposal draft with scope checks and human review.
The design connects these steps: Request → Context gate → Discovery brief → Offer path → Proposal package → Google Doc → Review → Follow-up. Rules, exceptions and approvals are defined before external actions are connected.
Workflow map
From discovery to reviewable proposal
The system does not replace commercial judgment. It organizes context, prepares the pack, and blocks client-facing output until a person reviews it.
Main database: Supabase
The workflow uses Supabase as the source of truth: it stores each record, status, and key event so the team can see what happened, retry failures, and debug without searching every tool.
Tool icons
System rationale
The value is not just writing faster; it is reviewing better
Weak proposals usually fail before writing starts: responsibilities are missing, the promise is too broad, scope is not closed, or the CRM does not hold the full story. This workflow turns discovery into a reviewable package so the conversation is about commercial judgment, not hunting for notes.
Context first, drafting second
The automation does not try to polish incomplete notes. If scope, outcome, owner, timeline or commercial data are missing, it asks precise questions before creating a document.
One source for proposal and CRM
The brief, CRM note, outline, SOW and follow-up come from the same package. That avoids the proposal saying one thing while the deal record says another.
Approval is part of the system
AI prepares structure and language, but sending stays blocked until a person checks pricing, risk, assumptions and promises made to the client.
Professional add-ons on top
The scenario
Design scenario: Turn discovery notes into a structured proposal draft with scope checks and human review. The starting point is a workflow with scattered information, manual steps and responsibilities that need to be made explicit.
Before implementation, we review available data, responsible owners and decisions that need approval. Understand the workflow first.
The approach
The design connects these steps: Request → Context gate → Discovery brief → Offer path → Proposal package → Google Doc → Review → Follow-up. Rules, exceptions and approvals are defined before external actions are connected.
AI can help classify, extract or draft; sensitive actions retain human review. Clear controls at each step.
What was used
Tooling was chosen from the process outward, not from a pre-decided technical preference. Each piece needed a clear owner, a stable integration path and a simple way to inspect errors.
In practice, the build combined Supabase, Python/FastAPI, OpenRouter, Google Workspace adapter, HubSpot-ready note. The tools visible to the team stayed close to their daily work, while integration logic was documented and kept separate from sensitive commercial decisions.
Workflow design
Manual approach and proposed workflow
Manual approach
Proposed workflow
Visible artifacts
- Structured discovery brief
- Offer recommendation with confidence
- Proposal outline and SOW bullets
- Assumptions, exclusions and client responsibilities
- CRM note draft
- Human review checklist
- Follow-up email draft
Controls
- Missing-context branch stops thin proposals
- Human review required before any client-facing send
- Assumptions and exclusions are explicit
- Google document creation is optional and logged
- CRM context and proposal content come from the same source
What this aims to improve
The aim is to reduce manual coordination and make records, exceptions and the next action visible. Any improvement must be validated against the project's own data and operating conditions.
Project scoping establishes a baseline and success criteria so proposed improvements can be tested. Validate the benefit in context.
The workflow in one line
Tooling and boundaries
The design shows how Supabase, Python/FastAPI, OpenRouter, Google Workspace adapter, HubSpot-ready note can work together. Final tooling, scope and controls are agreed for each project.
Integrations need appropriate permissions, run logs and a way to review exceptions. The team should be able to understand and operate the workflow.
What this example demonstrates
- Minimum-context gate
- Discovery brief
- Offer recommendation
- Proposal package
- Review checklist
- Google Docs adapter
- Follow-up draft
- Missing-context branch stops thin proposals
- Human review required before any client-facing send
- Assumptions and exclusions are explicit
- Google document creation is optional and logged
- CRM context and proposal content come from the same source