Back to all posts
Cost Guide7 min read·October 25, 2026

How Should Software Change Requests Be Priced?

TB
ThynkBlox Team
Engineering

To price software change requests, compare the requested result with the agreed scope, estimate the work needed to deliver and test the difference, and show the effect on cost and schedule. Separate new requirements from corrections needed to meet an existing agreement. Before work starts, record the approved scope, price or spending limit, acceptance criteria and revised delivery commitment.

What counts as a chargeable change?

Start with the agreed outcome. Use the statement of work, approved designs, acceptance criteria and recorded clarifications to establish what was included.

Suppose the agreed requirement says that an administrator can download a report containing all orders. Asking for scheduled delivery of that report introduces a new behaviour. A download that leaves out orders covered by the agreed requirement is a correction.

Use this distinction when reviewing a request:

SituationHow to assess it
A new user role or workflow is requestedIdentify the added scope and estimate its impact
Delivered behaviour fails an agreed acceptance criterionRecord a correction against that criterion
A requirement is unclear or documents conflictResolve the ambiguity before agreeing a charge
A previously accepted design is revisedIdentify the requested difference and any reusable work
An outside dependency changesCheck the agreed assumptions and responsibility before pricing

Do not treat every request raised after development begins as automatically chargeable. Equally, avoid treating every new expectation as an original requirement.

If the evidence is unclear, write down both interpretations. Agree what outcome will now be delivered and how the cost will be handled. Check the agreement before promising that either party must pay.

What should an impact analysis include?

An impact analysis should connect the requested behaviour to the work it creates. Ask the development partner to explain which parts need changing and why.

Cover these areas:

  • User experience: screens, messages, permissions and alternative paths.
  • Application behaviour: rules, calculations, integrations and stored information.
  • Existing information: whether records need updating or converting.
  • Testing: new acceptance checks and checks of affected existing behaviour.
  • Delivery: release preparation, instructions and any support needed.
  • Dependencies: decisions, access or outside changes required to finish.

Include assumptions and exclusions. For example, a quote for adding a report filter should say whether it includes saving filter preferences, changing the downloaded report and handling existing records with missing values.

Ask for the smallest useful version if the request is broad. That gives you a concrete option to assess without approving every possible extension.

Where the request introduces access to sensitive information, include permission checks in the estimate. Our guide to data security in modern applications offers further context for that discussion.

Which pricing method should you use?

Choose a method that matches how clearly the work can be defined.

A fixed price suits a request with agreed behaviour, acceptance criteria and bounded dependencies. Record what would require a revised quote. Avoid approving a fixed amount attached only to a vague feature name.

Time and materials with a cap gives you an agreed rate and a maximum authorised spend. Define how progress will be reported and require approval before exceeding the cap. Specify what happens if the cap is reached before completion.

Paid investigation followed by a quote is an option when an unknown blocks a credible estimate. Define the investigation's output: findings, options and a delivery estimate. Make clear whether implementation is included.

For each method, ask whether the price includes analysis, design, development, review, testing and release work. List outside charges separately, including any recurring cost introduced by the change.

A rate alone is not a complete quote. You also need an effort estimate, its assumptions and the basis for any allowance for uncertainty.

What does a clear change estimate look like?

The following example is illustrative. Its amounts, hours and delivery assumptions are not market benchmarks.

Assume the agreed scope includes downloading all orders. The requested change adds filtering by order status to both the screen and the downloaded report.

Work itemIllustrative effort
Confirm filter behaviour and acceptance criteria2 hours
Update the screen and report generation6 hours
Review the implementation2 hours
Test filters, downloads and existing report behaviour4 hours
Prepare and verify the release2 hours
**Total****16 hours**

At an illustrative rate of $75 per hour, the estimated fee is $1,200.

The accompanying proposal should also state:

  • The statuses users can select and the default selection.
  • Whether multiple statuses can be selected together.
  • What appears when no orders match.
  • Whether the downloaded report uses exactly the same filter.
  • What is excluded, such as saved preferences or scheduled reports.
  • The schedule effect and any decisions needed before work begins.

If uncertainty remains, describe it directly. For example: “This estimate assumes existing orders already have a usable status. If that assumption fails, we will present options before proceeding.”

How should schedule and testing affect the price?

Show effort and elapsed time separately. Sixteen hours of work does not establish a delivery commitment by itself.

Ask the proposal to state whether the change moves an existing milestone, fits within available capacity or requires another item to move. Identify any customer decision or outside dependency that affects the delivery commitment.

Make testing part of the approved work. For the report example, acceptance should cover the selected orders, the empty result and agreement between the screen and download. Checks should also cover the existing unfiltered report.

Request observable acceptance criteria: “The download contains only orders matching the selected statuses” is more useful than “The filter works correctly.”

For more on defining that work, see software testing and quality assurance.

Can you swap scope instead of increasing the budget?

Yes, if both parties agree to remove or reduce other work and record the trade.

Compare the remaining effort for each item. If work on the removed feature is already complete, do not assume its original estimate is available as a credit. Ask what unfinished work is avoided and whether removal itself needs any changes.

A useful scope swap records:

  • The feature or behaviour being removed.
  • The replacement being added.
  • Any work already completed that remains payable under the agreement.
  • The net price and schedule effect.
  • Revised acceptance criteria.

For an illustrative swap, an added filter might require 16 hours while an unstarted report layout would require 10 hours. The difference is 6 hours before accounting for any shared work or removal effort.

Keep the decision visible. A budget-neutral swap still changes what the customer receives.

What should the approval record contain?

Keep one accessible record containing the request and the decision. It should be specific enough for someone reviewing it later to understand what was authorised.

Include:

  • The original requirement and requested difference.
  • The reason for the change.
  • Included work, exclusions and assumptions.
  • Price, pricing method and any spending cap.
  • Testing and acceptance criteria.
  • Schedule effects and dependencies.
  • Scope removed or deferred.
  • Who approved the proposal and which version they approved.

Use a clear approval statement, such as: “Approved at the stated fixed price, including the listed testing and revised milestone.”

If the proposal changes after approval, seek approval for the revision. Keep rejected and deferred requests distinguishable from authorised work.

What common pricing mistakes should you avoid?

Pricing from a screenshot alone. Ask what happens behind the screen, including permissions, stored information, downloads and error handling.

Charging twice for the same agreed outcome. Map the request to the original requirement before classifying it as additional scope.

Leaving testing outside the estimate. Specify the checks needed to accept the change and protect affected behaviour.

Using unexplained contingency. Identify the uncertainty, the allowance and how unused or additional effort will be treated.

Starting with a vague approval. Confirm the scope, amount and schedule consequence together.

Turning every clarification into an invoice. Establish a lightweight way to answer questions and distinguish clarification from changed requirements.

What else should founders ask?

Should every small change have a separate quote?

Use an approval process proportionate to the work. You can agree a small-change allowance with a spending limit and written records. Define what it covers and when a separate estimate is required.

Who should pay when a requirement was misunderstood?

Compare the agreed wording, designs and clarifications with the delivered behaviour. Where they conflict or leave a gap, resolve responsibility under the agreement before authorising a charge.

Should you accept one total price without a breakdown?

Ask for enough detail to assess the scope, assumptions, testing and schedule effect. You do not need every coding task itemised, but you should understand what the price buys and what could change it.

What if the work is urgent?

Record the immediate objective, authorised spending limit and person who can approve further work. Keep a record of what was done, then assess any remaining work before expanding the request.

*This post is general information, not legal advice. Check your own agreement and consult a qualified lawyer where rights or obligations are unclear. Last reviewed: October 2026.*

Ready to build?

Let's turn these ideas into your next product.

Start your project