Create a Client Proposal with Scope and Delivery Evidence
Turn a supplied client brief into comparable scopes, transparent estimates and PDF/Word handoff files. Keep assumptions, uncovered requirements and planned dates explicit.
Fastest way
Ask your AI to do it
Paste this into the AI agent you already use:
Use Client Proposal Studio with my supplied client brief. Separate verified facts, assumptions and estimates. Ask about missing scope and responsibilities. Prepare 1–3 materially different offers with priced deliverables, exclusions and acceptance criteria. Generate into a new folder, reconcile totals and payment stages, then inspect PDF and Word layouts. Do not send, sign or charge anything.
What is a proposal, and what is approval?
Client Proposal Studio creates a comparison room and complete proposal documents with offer-specific delivery briefs. Selecting an offer in the preview does not record acceptance, sign an agreement or charge the client. Treat the output as a reviewed proposal until a separate engagement is approved.
Collect the brief and resolve missing decisions
- Supply the client context, requirements, source references, owners, deadlines and budget constraints.
- Read references/brief.md and references/decisions.md. Separate facts from assumptions, estimates and proposed outcomes.
- Use 1–3 materially different scopes. One complete offer is better than three tiers with the same work.
Make the scope observable
Turn the accepted scope into a decision presentation
Explain the scoped proposal in a deck — Reuse agreed deliverables and exclusions without inventing acceptance.
| Deliverable | Acceptance evidence | Boundary |
|---|---|---|
| Five-page product site | Approved copy, responsive review and working supplied links | Authentication and payment backend excluded unless separately scoped |
| Operator handoff | Named owner, editable source and documented next steps | A planned calendar is not a business-day guarantee |
Generate the fictional practice proposal first
Use Python 3.10+ and install the package requirements in a virtual environment. After setup, the builder runs offline. The command below uses the included fictional brief; replace it with your own approved input for a client proposal. On Windows use .venv\Scripts\python.exe.
Read this release’s setup before running the example
Confirm installation and invocation in your host
python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.txt
.venv/bin/python scripts/build-proposal.py --input examples/proposal.json --output ./practice-proposalCheck money, coverage and native documents
- Reconcile quantities, rates, discounts and entered tax with calculations.json. Payment stages must sum exactly to the estimate.
- Compare requirement coverage, exclusions and each offers/<id>/scope.json with the selected delivery brief.
- Open or render the PDF and Word documents in the intended viewers. Check long tables, page breaks and glyphs, including a permitted local font for PDF when needed.
Inspect the current example output → — Compare the visible result with the exported files and checks described in this section.
Keep edits and delivery files consistent
Change brief.json and regenerate into a fresh folder for structural changes. Editing Word alone does not update the PDF, HTML or calculations. Recheck any edited values and the final manifest. Deliver the agreed offer's brief with the complete proposal; sending it to a client remains a separate action.