Use this when
A prospective client has described a need and you are ready to present an approach, price, timeline, and decision path.
Context and outcome
Reflect the client’s situation briefly, then define the outcome your work is intended to produce.
- Client problem or opportunity in their language
- Desired business or project outcome
- Assumptions that materially affect the proposed approach
Scope and exclusions
Describe observable deliverables and place important boundaries next to them.
- Deliverables and acceptance criteria
- Number of concepts, pages, interviews, integrations, or environments
- Explicit exclusions and client responsibilities
- How additional work will be estimated and approved
Milestones and commercial terms
Connect timing and payment to understandable project events.
- Target start, review, and delivery windows
- Dependencies that can move the schedule
- Fee, currency, taxes, deposit, and milestone payments
- Proposal expiry date and acceptance method
Revision and handoff
Define what feedback, revision, acceptance, and final delivery mean before work begins.
- Included revision rounds and feedback format
- Review turnaround expected from the client
- Final files, access, documentation, or training included
- What happens after the proposal is accepted
Adaptable sample language
Objective: launch a responsive marketing site that the client team can update without developer support.
Included: discovery, sitemap, wireframes, six page templates, responsive build, and handover.
Excluded: brand identity, copywriting, paid-media setup, and integrations not listed above.
Acceptance: confirm this proposal by 10 September 2026 to reserve the proposed start window.
Check before using
- Do not promise an outcome that depends on factors outside your control.
- Keep the proposal consistent with the contract that follows.
- Use a qualified lawyer for legal terms appropriate to your jurisdiction and risk.
Continue the workflow