Change order script · Environment & infra
Client wants an additional environment
The SOW has dev, staging and production. Now the client's QA team wants a UAT environment of its own. Here is how to scope infrastructure requests clearly.
Victor Osei10:42 AM
Our QA team wants a separate UAT environment so they can test without your team deploying over them. Can you set that up?
Possible scope change, visible to your team only
Cites SOW section 4.1, Environments. Estimated 22 hours. Change order draft ready for PM review.
The situation
A new environment is not a copy button. It needs infrastructure as code, pipeline changes, secrets, seeded data, monitoring and ongoing cloud costs. It also adds a deployment step to every release. The SOW lists three environments. The request is reasonable and signals that the client's QA practice is maturing.
Why this script works
The script agrees with the goal of stable testing, explains the parts of the work, and separates the one-time setup from the ongoing cloud cost the client will pay directly. It also offers a lower-cost alternative.
- Scenario
- Environment & infra
- Clause to cite
- SOW section 4.1, Environments
- Typical effort
- 22 hours
- Typical change order
- $3,630 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], makes total sense for QA to have a stable space to test. Our SOW (section 4.1) covers dev, staging and production, so a UAT environment is new work: infrastructure, pipeline stage, secrets and seeded test data, plus its own monthly cloud cost. I'll send an estimate along with a lighter option, scheduled staging freezes for QA, in case that's enough.
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 |
|---|---|---|
| “Just test on staging.” | “We can schedule staging freezes, or build UAT.” | Respects their need and offers a real option. |
| “Environments are expensive.” | “Here is the setup cost and the monthly cloud cost.” | Numbers, not adjectives. |
| “We'll spin one up.” | “Here is what the setup involves.” | Each environment is ongoing maintenance. |
SOW clause to cite
SOW section 4.1, Environments
Agency will provision dev, staging and production environments in the client's cloud account. Additional environments, regions or accounts are handled under the Change Control clause. Cloud consumption costs are paid by the client.
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-GPI-CLAIMS-07
Client wants an additional environment
| Line item | Hours | Amount |
|---|---|---|
| Infrastructure as code for UAT environmentDevOps engineer | 8 | $1,320 |
| Pipeline stage and promotion rulesDevOps engineer | 6 | $990 |
| Secrets, configuration and seeded test dataEngineer | 5 | $825 |
| Monitoring and handover to client QADevOps engineer | 3 | $495 |
| Total | 22 | $3,630 |
Priced at a $165 blended hourly rate. Cites SOW section 4.1, Environments.
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 4.1, Environments.
- 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 22 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
- Environment & infraClient needs legacy browser supportTwo weeks before launch, the client mentions their staff use an old browser on locked-down machines. Here is how to scope support without panic.
- 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.
- 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.
- Content lateClient misses the content delivery deadlineFinal copy and images were due two weeks ago. The launch date has not moved. This script resets the timeline kindly and makes the cost of compression visible.
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.