DEV Community

DevQuoteFlow
DevQuoteFlow

Posted on Originally published at scopeshipweekly.substack.com

A One-Page Change-Order Beats a Verbal “Quick Tweak”

#freelancing #webdev #invoicing #indiehackers

A One-Page Change-Order Beats a Verbal “Quick Tweak”

Mid-project scope creep almost never arrives as a formal email titled “Change Request.”

It arrives as a Slack message:

  • “Can we add a blog listing page while you are in that section?”
  • “Can the contact form also create a CRM lead — quick?”
  • “Can the homepage hero rotate three banners instead of one?”

If you say yes and keep coding, you donate hours. If you say no without a process, you look inflexible. The professional middle path is a written change-order: short, priced, and approved in writing before the new work starts.

This article is not a reprint of our earlier Dev.to post on separating engineering hours from payment percentages. That piece is about how cash moves. This one is about what happens when the scope moves.

Honesty rules: no invented close rates, no fake client stories, no affiliate links. Hour and dollar figures below are examples only. Prefer a 0% late-fee / work-pause policy over interest-like late fees.

Why a chat “yes” fails later

A verbal “sounds good” from one stakeholder is not a budget decision. Three problems show up later:

  1. No paper trail. When the invoice rises, the client remembers the feature, not the cost conversation.
  2. No schedule impact. Extra pages and integrations push QA and launch; without a written delay note, the original date still looks like your miss.
  3. No payment gate. Unapproved extras often land in the final milestone, where cash is already tight.

None of these are solved by adding late-payment interest. Interest does not define the new work. A one-page change-order does.

Copy-paste: one-page change-order

Adapt this to the project. The hours and rate are illustrations, not a recommended market rate.

Change Order #[N]
Project: [Client / Site name]
Date: [YYYY-MM-DD]
Requested by: [Name / channel]
Description of change: [What will be built, in plain language]
Why it is out of original scope: [Proposal section, or “not listed in in-scope deliverables”]
Estimated engineering hours: [e.g. 6 hours — example only]
Rate: $[Your rate]/hr (set your own)
Change fee: $[Hours × Rate]
Schedule impact: [e.g. +2 business days to Milestone 2 delivery]
Payment terms: Due within Net 7 of written approval. Work on this change starts only after written approval.
Late-payment interest: 0%. If unpaid past due, non-critical work on this change pauses.
Approval: Reply “Approved — Change Order #[N]” from the named decision-maker, or sign below.
Enter fullscreen mode Exit fullscreen mode

Keep it to one page. Specificity beats persuasion.

Three rules that keep the process fair

  1. Anything not in the original in-scope list needs a change-order, including “small” UI tweaks that touch several templates.
  2. Work starts after written approval, not after a thumbs-up emoji.
  3. Bundle related asks. Three tiny requests in one week can be one change-order with three line items, one fee, and one schedule note.

How this fits milestone billing

If you use a milestone split such as 40/30/30 (an example, not a required formula), attach an approved change-order either:

  • as a separate mini-invoice due Net 7, or
  • as a line item on the next open milestone, with payment shares still adding up to 100%.

Keep estimated hours (effort) and cash-flow share % (when money moves) as two columns. They are allowed to disagree. For a worked pricing example, see our free guide:

https://devquoteflow.surge.sh/guides/how-to-price-a-website-project-as-a-freelancer.html

When “done” itself is unclear, write an acceptance checklist and require explicit written approval before you issue the milestone invoice. Silence is not acceptance. We walk through that gate here:

https://scopeshipweekly.substack.com/p/issue-6-the-acceptance-sign-off-gate

A practical next step

You can paste the template above into any document. If you want to update hours and payment shares and preview an English A4 proposal in the browser, the free starter on DevQuoteFlow allows up to 2 proposals per month with branded English PDF export:

https://devquoteflow.surge.sh/#workspace

Published Pro pricing is $15/month or $144/year via Paddle, for unlimited proposals, white-label PDFs, and Arabic/English PDF export. Review the checkout total and applicable taxes before paying. This article is not a discount.

Prepared with AI assistance; reviewed and approved by the DevQuoteFlow founder.

Top comments (0)