Make the design scope inspectable
This original proposal is for a fictional cafe's Home, Menu and Contact page designs. It proposes a content map, three page layouts and an annotated handoff. It does not build or launch a website. The assumed fees are USD 400 for discovery, USD 1200 for layouts and USD 600 for handoff: USD 2200 before any taxes or third-party costs, whose treatment remains [TO CONFIRM]. No actual client or agency price is claimed.

Price a named output, and make the boundary visible before work begins. Home organizes the cafe's introduction and visit information. Menu organizes supplied menu content. Contact organizes supplied location and contact information. Actual copy, images, hours, address and rights to use assets require client confirmation; the proposal invents none of them.
HubSpot's website proposal template connects project components, timeline and pricing. Use that structure to make the request concrete. The independent example is narrower: design review and handoff only, with no signed agreement, development, deployment or performance promise.
Put dependencies beside the estimate
The proposed phases allow two working days for discovery, three for layouts and two for handoff: seven working days of phase effort. The estimate assumes required content and feedback are available at each gate. It is not seven consecutive calendar days or a guaranteed launch date.
The design phase proposes two consolidated review rounds across the three layouts. Extra pages, additional rounds or changes to agreed content require a new scope decision. Booking, payments, CMS setup, coding, hosting and maintenance are excluded. A contact-page layout is not a functioning contact form.
At handoff, the client should be able to review the three layouts, content map and annotations together. Implementation testing and any accessibility-conformance claim belong to a separately defined, actually tested scope. Confirm the implementation owner, file format, asset rights, approval route and commercial terms before treating the proposal as an agreement.
Draft from the pages and deliverables
Create one offline HTML web design proposal review copy.
Actual client problem and supplied page/content facts: [PASTE]
Included outputs, exclusions and review-round limits: [PASTE]
Phase effort, content/feedback dependencies and approval gates: [PASTE]
Itemized fees, currency and confirmed terms: [PASTE]
Separate design deliverables from coding, forms, hosting and launch. Sum supplied fees and phase effort; preserve a mismatch with [CHECK SCOPE] rather than silently repairing it. Mark missing content, rights, dates, implementation owner or terms [TO CONFIRM]. Never invent clients, sales outcomes, functioning integrations, accessibility conformance, approvals or binding agreement. Show named pages, explicit exclusions, conditional phases and an itemized fee table. No external assets, signatures, acceptance/payment controls or sending claims. End with one client scope decision and the actual review/handoff process.
Get the scope decision before the project starts
Ask the client whether the three-page design scope answers the original need or whether booking needs a separate implementation proposal. If the pages, fees and exclusions are hard to compare, read them together in the prepared HTML review copy in NOS, then revise the actual proposal and agreement through the normal client process.
Send the revised scope with the decision that changed it. Confirm the handoff and approval route directly; editing a reading copy does not notify the client, accept the proposal or launch a website.