Define an output the client can review
The fictional Cedar Supply engagement reviews an order handoff. Consultant Morgan Ellis proposes two one-hour interviews, a current-process map and an issues-and-decisions memo. No credentials, actual client relationship or reduction in errors is claimed.

Connect each deliverable to a client input. The map depends on a permitted sample of the current workflow and access to two interview participants. The memo records issues in that supplied material and decisions still needed. It does not promise system implementation or an unsupported percentage improvement.
Jotform’s consulting proposal example distinguishes deliverables and fee information. Use that separation: a client should be able to assess the work and price basis without treating a readable proposal as completed authorization.
Make effort and exclusions visible
Two one-hour interviews total two consultant hours. Six additional hours cover analysis and preparation of the map and memo, including one review meeting. At the illustrative $100 hourly rate, eight hours produce an $800 service fee. Tax, travel, payment timing and actual dates are [TO CONFIRM]; this is not a final tax-inclusive invoice.
The offer excludes software configuration, staff training and ongoing support. Confirm scope changes separately instead of letting a vague process-improvement heading absorb them. Ask the client to name the reviewer and provide permitted records before agreeing dates. Keep the actual agreement and approval in the required business workflow.
Build a proposal from the agreed discussion
Create a self-contained HTML consulting-proposal review copy.
Confirmed client/problem/consultant and source discussion notes: [PASTE]
Deliverables, exclusions and review allowance: [PASTE]
Client records, participants, reviewer and prerequisites: [PASTE]
Hours/rates/totals, tax/travel/payment and date terms: [PASTE]
Acceptance owner and required official agreement format: [PASTE]
Use only supplied facts. Mark missing terms [TO CONFIRM]. Do not invent credentials, outcomes, savings, approved dates or acceptance. Link each output to a client input and review decision. Recompute quantity/hour/rate calculations; retain conflicting totals as [CHECK TOTAL] and withhold affected final pricing. Distinguish service fee from final invoice. Reading implies no signature/payment action.
Use semantic headings, captioned fee tables with scoped headers and labeled rows at 360px; at least 16px text. Inline CSS only; no scripts, external assets, network, fake approval/payment/copy controls or editable fields. Keep the official agreement workflow authoritative. Return complete HTML and unresolved terms.
Ask whether the inputs and outputs fit
Send the draft to the client and ask whether participant access, sample records and a review owner are realistic. If scope and dependencies are hard to compare, read them together in the prepared HTML review copy in NOS, then revise the official proposal.
Send the revised scope with the decisions still needed. Confirm accepted work and dates through the normal agreement process before scheduling interviews. Updating a review copy does not notify the reviewer or approve the engagement.