## Slide 1

This is a fictional engagement and an illustrative quote, not an offer to a real customer. Begin with the visitor and editor outcomes. Do not imply that a redesigned website guarantees a commercial result.

## Slide 2

Explain how each acceptance check can actually be observed. Five participants support a bounded usability check, not a conversion forecast. The editor handover is a real task demonstration, not merely delivery of a PDF guide.

## Slide 3

Read the exclusions without apologizing for them. Authentication and payment work are significant separate systems. Clarify whether a requested feature belongs to this engagement before estimating its implementation.

## Slide 4

Give each deliverable a reviewer and an acceptance condition. The six-page structure needs one consolidated review. Accessibility acceptance concerns the agreed checks; avoid promising universal certification.

## Slide 5

Describe the working method through decisions: clarify, prototype, then implement. The early mobile journey is a risk-reduction step. It is not an additional deliverable outside the agreed scope.

## Slide 6

Working days describe planned effort and sequence after kickoff conditions are met. They are not an unconditional calendar deadline. Pause at each gate to confirm whether the client can support the review cadence.

## Slide 7

Ask the client to name people for the three roles before kickoff. The labels are responsibilities, not assumed staffing. Escalation should be timely and documented, without blaming individuals for missing inputs.

## Slide 8

The subtotal is computed from quantities and integer minor-unit rates. Read the currency and unit before discussing the amount. Tax treatment and payment milestones are illustrative and must be confirmed in the agreement.

## Slide 9

Assumptions are price and schedule boundaries. Invite corrections now. If approved copy cannot arrive before implementation, revise the sequence and acceptance plan rather than inventing final content.

## Slide 10

Walk through a realistic change request. First define it, then assess impact, then secure an explicit decision through the parties’ process. A changed slide does not substitute for an agreed contract amendment.

## Slide 11

Explain the mitigation and the residual uncertainty for each risk. Avoid hiding a platform limitation behind optimism. The early prototype should turn uncertain feasibility into an observable decision.

## Slide 12

Close with the exact client decision. Do not present this deck as a signed agreement. Capture open questions, the named decision owner and the prerequisites needed before the kickoff is booked.