Know whether the client ask is included before your team says yes.

Request

Please swap the homepage hero copy, replace two portfolio photos, and add three FAQ entries before launch.

Evidence

• The signed SOW includes copy edits, photo swaps, the existing FAQ page, and two pre-launch revision rounds.
• A follow-up approval email confirms hero-copy changes, portfolio photo swaps, and a few FAQ additions are covered.

Reply angle

These updates fit the approved pre-launch revision scope, so we can proceed without a change order.

Request

The contact form stopped sending messages three days after launch. Can you fix it today?

Evidence

• The signed support terms include a 14-day post-launch warranty for bugs in delivered functionality, including contact-form failures.
• The request is for a delivered bug, not a new feature or expansion to the approved site scope.

Reply angle

This falls under the post-launch warranty coverage, so we can proceed with the bug fix inside the current support window.

Request

Can you add Stripe checkout and paid consultation booking to the site before launch?

Evidence

• The signed SOW excludes payment processing, booking calendars, and custom operational tools unless approved through change order.
• The clarification email explicitly says payment collection and online booking were not approved in the current package.

Reply angle

Those features sit outside the signed scope and would need a formal change order before we schedule the work.

Request

Jordan mentioned in Slack that a simple analytics dashboard might help for launch. Can you add it?

Evidence

• The signed SOW excludes analytics dashboards unless they are approved through a change order.
• The only positive signal is an informal Slack mention, which is too weak to count as written approval for new dashboard work.

Reply angle

The current documents do not support a clean yes. We should clarify the exact dashboard ask and formal approval path before treating it as included work.