The point where work gets scattered
Broad promises such as “improve operations” hide the difference between advice, implementation and a business outcome. A client needs to know which is being proposed and what evidence will be delivered.
State the situation without overselling certainty
Summarize the client’s observed issue and distinguish it from an untested explanation. A project can investigate why approvals are slow without asserting that a particular department is the cause.
- Name the practical decision the engagement will inform.
- Record available baseline information and missing inputs.
- Describe deliverables you control instead of guaranteeing savings or revenue.
Show how the approach produces deliverables
Link interviews, analysis and workshops to a defined output. Explain what the client must make available and when a missing input would change the plan.
- Specify interview or workshop counts and participants.
- List report sections, working files or presentations.
- Separate recommendations from implementation and ongoing support.
- Give the sponsor a clear review and next-decision point.
Consulting proposal review checklist
Read the proposal as if the sponsor will explain the engagement to a colleague. The boundary between analysis and execution should survive that retelling.
- The problem uses information actually supplied.
- Every activity supports a named output.
- Dependencies, exclusions and dates are explicit.
- Proposed fee stages add up in one currency.
- No outcome is a guarantee or an already achieved result.
The working template
Use the complete text below, or download the text file and edit it in your preferred document editor.
CONSULTING PROPOSAL Client / consultant / version / date: [details] Situation: [observations; sources; uncertainties] Decision or objective: [what the engagement helps the client decide] Approach: [stages and activities] Deliverables: [output; contents; format] Client participation: [people; information; access; availability] Schedule: [stage; target date; dependency] Review: [reviewer; checks against scope; feedback date] Assumptions: [conditions needing confirmation] Exclusions: [implementation, support or other boundaries] Proposed fee and currency: [items and total] Proposed payment stages: [amount; trigger] Changes: [review effect on work, price and timing before proceeding] Open questions: [question; owner] Next decision: [approve this version, request changes or clarify]Download text template
A filled example
Fictional example for illustration. Replace its facts and amounts with the details you actually agree.
FICTIONAL FILLED EXAMPLE — proposal, not a promise of results Oak Field Supply reports that purchase approvals are difficult to trace. Consultant Dana proposes a three-week review to help its operations lead choose a simpler approval process. The cause has not been established. Work includes four staff interviews, review of a client-selected sample of ten completed requests, one process map and a recommendations workshop. Oak supplies redacted examples and schedules participants. The deliverable is a findings report with observed issues, two options and implementation questions. System configuration and staff training are excluded. Dana proposes a fixed $2,400 USD fee: $1,200 after acceptance and $1,200 after the scoped report and workshop. The sponsor reviews whether the agreed work is complete, rather than using projected benefits as acceptance criteria. The next step is to confirm interview availability and decide on proposal v1.
Keep the context with the conversation
Prepare the sponsor’s next-step message in Bankeiz using only the conversation context you choose. Optional metered Business assistance does not replace your review of findings, scope or separately approved payment actions.
Understand your Twin · See Business access and metered AI usage