Change order script · New feature
Client asks for extra landing pages
The site build included 20 pages. Marketing now wants six campaign landing pages before launch. This script turns a favor request into a quick, approved add-on.
Rafael Costa10:42 AM
We're running a spring campaign, can you spin up 6 landing pages using the templates you've already built? Just swapping copy really.
Possible scope change, visible to your team only
Cites SOW section 3.2, Page population. Estimated 18.5 hours. Change order draft ready for PM review.
The situation
Templates exist, so new pages feel free. They are not: each landing page needs copy population, image sizing, form setup, tracking, mobile checks and QA. Six pages is a few days of work. The SOW caps agency-populated pages at 20, which have already been used. The client may also be unaware that the editor training means their team can build these themselves.
Why this script works
The script offers three options, including a free one where the client's team builds pages using the templates. Offering a self-serve path shows the agency is not trying to bill for everything, which makes the paid option feel fair.
- Scenario
- New feature
- Clause to cite
- SOW section 3.2, Page population
- Typical effort
- 18.5 hours
- Typical change order
- $3,053 at $165/hr
- Reply within
- Same business day
The script
Three versions: the quick reply, the email and the nudge.
Start in the channel where the request arrived, then follow with the email and change order. Copy any version and replace the bracketed placeholders.
Youdraft, reply in thread
Hi [Name], great timing for a spring campaign! The templates are built for exactly this. Our SOW covers population of 20 pages (section 3.2), and those are used up, so here are a few options: your team builds them in the editor (we can do a 30-minute refresher), we build all 6 as a small add-on, or a mix. I'll send the add-on estimate today so you can compare.
Replace every [bracketed] placeholder before sending. Your PM approves every message, TWINJAM never contacts clients on its own.
What not to say
Small wording changes decide whether the client hears help or a bill.
| Avoid | Say instead | Why |
|---|---|---|
| “It's not just swapping copy.” | “Each page includes forms, tracking and QA, here is what it involves.” | Corrects the assumption by explaining, not contradicting. |
| “Sure, we'll knock them out.” | “Here are three ways to get them live.” | A silent yes resets the page cap to zero. |
| “That'll cost you.” | “Option 1 is free with a quick refresher.” | A free option builds trust in the paid ones. |
SOW clause to cite
SOW section 3.2, Page population
Agency will populate up to 20 pages using client-supplied final copy and images. Remaining pages are populated by the client using the trained editor workflow, or by the agency under the Change Control clause.
No clause like this in your SOW? Use one of the SOW templates for your next engagement, and have your counsel review final contract language.
CO-BDG-SITE-07
Client asks for extra landing pages
| Line item | Hours | Amount |
|---|---|---|
| Population of 6 landing pages from client copyContent developer | 9 | $1,485 |
| HubSpot form setup and campaign UTM trackingDeveloper | 4 | $660 |
| Mobile checks and QA across 6 pagesQA engineer | 4 | $660 |
| Coordination and launch checklistProject manager | 1.5 | $248 |
| Total | 18.5 | $3,053 |
Priced at a $165 blended hourly rate. Cites SOW section 3.2, Page population.
Step by step
From the client’s message to a signed change order.
The script is one step. The process around it is what keeps scope conversations short and friendly.
- 1
Check the request against your signed SOW. For this scenario the clause to cite is usually SOW section 3.2, Page population.
- 2
Reply the same day in the channel where the request arrived, using the Slack version. Agree with the goal before you mention scope.
- 3
Estimate the work as line items with hours. This scenario typically lands around 18.5 hours.
- 4
Send the email version with the change order attached and two or three options, including a lighter or free path where one exists.
- 5
Set a decision date tied to the schedule. If there is no reply in three business days, send the follow-up.
- 6
Record the approval or the decision to defer, so the SOW baseline stays accurate for the next request.
Related scripts
- New featureClient asks for a new payment gatewayThe checkout was scoped for Stripe. Now the client wants PayPal and Klarna too. Here is how to say yes to the idea and yes to the budget in the same message.
- New featureClient wants a new user roleThe app was scoped with three roles. The client wants a fourth, a regional manager who sees some data but not all. This script shows why roles are bigger than they look.
- New featureClient requests a feature after launchThe project launched last week and the warranty covers defects. The client sends a feature request labelled as a bug. Here is how to separate the two kindly.
- Extra revisionClient requests a fourth design revisionThe SOW includes two revision rounds. The client is asking for round four. This script keeps the relationship warm while making the next round a paid, scoped decision.
Agency Change Order Scriptbook
12 polite Slack and email templates to ask for more budget without friction.
The scriptbook collects the twelve conversations agency PMs dread most, from the fourth design round to the after-launch feature, with the SOW clause to cite and a change order form for each.
Spot the request before the work starts.
TWINJAM flags out-of-scope requests in Slack, Teams and Jira, cites the SOW clause and drafts a change order like this one for your PM to approve.