Scope Creep 2026: The ₹1.2L Clause I Use in Gujarat
Quick Answer: I stop scope creep with a written change request clause that triggers at ₹1,20,000, which is 10% of a ₹12,00,000 annual project value. Any request above that threshold gets a fixed price, a revised date, and a signed one-page change order before I write code. The clause has protected more margin than any pricing increase I have made, and it is the direct result of the pricing mistakes I made in year one.
Author: Deepak Bagada — founder of SaaS Next in Junagadh, Gujarat. I have shipped 40+ production builds, and I have learned that the profitable projects are not the ones with the highest quote. They are the ones where the boundary between included and extra work is written down before the first sprint.
Key Takeaways
- Set the threshold in rupees, not in feelings. "Small change" means nothing. ₹1,20,000 is a number both sides can verify.
- Price the change before you estimate it. A change order with a fixed fee and a fixed date prevents the slow drift that turns a six-week build into a five-month build.
- The clause is a client filter. Good clients respect a clear boundary; clients who negotiate every line item after signing are the ones who consume the margin.
- Do not use this on discovery. Early product work needs a paid discovery phase, not a change-order fight over an undefined scope.
The Project That Taught Me the Number
In February 2026 I signed an ₹85,000 Laravel 13 build for a Rajkot distributor. The stack was Postgres, Redis, and a 4GB VPS, with a p95 dashboard latency target of 400ms. The scope was a dealer portal: login, product catalog, order placement, and a simple admin dashboard. Six weeks, fixed fee, 30 days of support.
The first change came in week two: "Can dealers see their credit limit?" That was a read-only field, so I added it. The second: "Can they download a PDF statement?" That was two days, so I added it. The third: "Can we add a second warehouse and split stock?" That was a schema change, a permissions change, and a reporting change. I said yes because the client was friendly and the project was already late.
By week eleven the portal had a warehouse module, a credit engine, and a WhatsApp notification job. I had spent 214 hours on a 120-hour quote. At ₹85,000, my effective rate was ₹397 per hour. The client was happy. I was not.
The lesson was not "charge more". It was "define the boundary before the friendly requests start". I wrote the clause below in March 2026 and have used it on every project since.
What Counts as a Change
A change is any request that adds a screen, a role, an integration, a report, a data field that affects the schema, or a workflow state that was not in the signed scope. It is not a bug fix, a copy change, or a question about how an existing feature works.
| Request | Change? | Why |
|---|---|---|
| "The invoice total is wrong" | No | Defect in the signed scope |
| "Add GST breakup to the invoice" | Yes | New data and a new template |
| "Change the button label" | No | Copy, under 30 minutes |
| "Add a dealer role with credit limits" | Yes | New role, schema, and permissions |
| "Make the dashboard faster" | Depends | Defect if it misses the agreed budget; change if it adds caching infrastructure |
| "Export the same report to Excel" | Yes | New format and a new endpoint |
| "Fix the login on Safari" | No | Defect in the signed scope |
The table does two jobs. It gives the client a fast answer, and it stops me from arguing about intent at 21:00 on a Friday. If a request is not on the "included" list, it is a change until we agree otherwise.
The ₹1,20,000 Clause
The threshold is 10% of the annual project value, a rule I explain in my SME consulting playbook. For a ₹12,00,000 build, that is ₹1,20,000. A single request above the threshold always gets a change order. A cluster of small requests that crosses the threshold in a month also gets one, which closes the "five tiny asks" loophole.
CHANGE REQUEST CLAUSE (v3, March 2026)
1. Included scope
The deliverables listed in Annexure A are included in the fixed fee.
Anything not listed is out of scope.
2. Change threshold
A request with an estimated effort above 8 hours, or a cumulative
value above INR 1,20,000 in any calendar month, requires a written
change order signed by both parties before work begins.
3. Change pricing
Change orders are priced at INR 2,500 per hour, or at the fixed
price stated in the change order. The fixed price prevails.
4. Schedule impact
Every change order states the revised delivery date. The original
date is not extended unless the change order says so.
5. Small fixes
Defects in included scope are fixed at no charge. Copy changes under
30 minutes are free. Everything else follows clause 2.
6. Silence is not approval
A verbal request, a WhatsApp message, or a meeting note is not a
signed change order. Work starts after signature and advance payment.
The hourly rate is deliberately higher than my project rate. I do not want to make money from change orders; I want the client to bundle requests into one decision instead of sending them one at a time. When the rate is high, the conversation becomes "what is the smallest version that solves this", which is the right conversation.
The Client Script
The clause only works if the delivery is calm. My first response to an out-of-scope request is never "that will cost extra". It is a restatement of the request, a boundary check, and a choice.
Subject: RE: Dealer credit limit screen
Hi [Name],
Yes, we can add the credit limit screen. It is outside the signed
scope, so here is the change order:
- Credit limit field on the dealer profile
- Visible to admin and accounts roles only
- CSV import for opening balances
- Fixed price: INR 42,000
- Revised delivery: 12 November 2026
If you approve, reply "approved" and I will send the payment link.
If the priority is different, we can swap this for the WhatsApp
notification item in the current scope and keep the date.
Deepak
The last paragraph is the part most freelancers miss. A change request is not only a price; it is a trade against the current backlog. When the client can swap one item for another, the project stays on schedule and nobody feels extorted.
Production War Story: The ₹3.4L Scope Spiral
A Surat textile exporter signed a ₹2,80,000 build for a catalog and order portal in April 2026. The scope had 11 screens. By June the client had asked for a dealer mobile app, a loyalty ledger, and a Tally sync. I tracked the requests in a spreadsheet but did not issue change orders because the relationship was strong and the client had paid on time.
At the end of June the work was 63% complete, the invoice was fully paid, and the remaining work was worth about ₹3,40,000 at my rate. I had two options: absorb it or stop. I stopped, sent a one-page summary of the 19 out-of-scope items, and offered a revised phase-two quote.
The client was angry for two days. Then they approved a ₹1,90,000 phase two with three of the 19 items. The other 16 disappeared because they were never priorities; they were ideas that became "requirements" because saying yes was easier than saying "later".
That project is why the clause now has a monthly cumulative threshold, and why the Junagadh build playbook starts with a scope boundary instead of a sprint plan. One big request is easy to spot. Fifteen small ones are not.
Production War Story: The Clause That Saved a Relationship
In August 2026 a Junagadh CA firm asked for a reconciliation dashboard two weeks before launch. The request was ₹1,40,000 of work by my estimate, above the threshold.
I sent the change order with two options: full scope at ₹1,40,000 with a three-week delay, or a read-only version at ₹38,000 that shipped on the original date. The partner chose the read-only version and asked for the editing workflow in the next quarter.
The launch happened on time. The client referred two other firms. The ₹38,000 change order did more for my reputation than the original ₹4,20,000 build, because it proved I would not silently absorb work and then resent the client.
How I Estimate a Change Order in 20 Minutes
I do not run a full discovery for a change. I use a three-line estimate and a buffer, then let the client decide. The buffer is explicit, not hidden.
| Line | Example | Hours |
|---|---|---|
| Data model change | Add credit_limit and an audit table |
4 |
| API and validation | Two endpoints, policy checks | 6 |
| UI and tests | Admin form, CSV import, two tests | 8 |
| Buffer (25%) | Integration and review | 4.5 |
| Total | 22.5 hours at ₹2,500 | ₹56,250 |
If the estimate is wrong by 30%, I still make a reasonable rate. If it is wrong by 60%, I stop and re-quote. The buffer is not a secret; clients who have shipped software understand that estimates are ranges.
When NOT to Use This Clause
Do not use it during paid discovery. Discovery is the process of finding the scope, and a change-order fight during discovery destroys trust. Charge for discovery separately, then sign the build with a fixed scope.
Do not use it on a small fixed-price project under ₹50,000 unless you also cap revisions. The administrative overhead of a change order can exceed the margin on a two-week job. A simple "two rounds of revisions included" line is enough.
Do not use it with a client who has no decision-maker. If every request goes to a committee, the change order becomes a committee document. Walk away or price the coordination time into the project.
Do not use the clause as a threat. The tone is "here is the price and the trade", not "you are trying to get free work". I have seen contractors win the argument and lose the referral, which is a bad trade for a solo studio.
Bottom Line
The ₹1,20,000 clause works because it replaces a vague boundary with a number, a price, and a revised date. It protects the project from the friendly requests that arrive after signing, and it gives the client a real choice instead of a surprise invoice. Write the clause before the kickoff, send the change order within 24 hours, and keep the tone matter-of-fact. The clients who respect it are the clients worth keeping.
Frequently Asked Questions
What is a scope creep clause?
A scope creep clause defines what work is included in a fixed fee, what counts as a change, and how a change is priced and scheduled. My clause triggers a written change order above ₹1,20,000 or eight hours of effort, and it states that verbal requests are not approval.
How much should I charge for a change request?
I charge ₹2,500 per hour or a fixed price for the change, whichever is stated in the change order. The rate is higher than my project rate on purpose: it encourages clients to bundle requests and choose the smallest version that solves the problem.
Does a change request clause upset clients?
It upsets clients who expect unlimited work for a fixed fee. Most clients accept it because it gives them a clear price and date instead of a vague promise. Deepak Bagada sends the clause with the proposal, so the boundary is part of the deal rather than a surprise after kickoff.
What is the difference between a bug fix and a change request?
A bug fix restores behaviour that was already in the signed scope, such as a wrong invoice total or a broken login. A change request adds a screen, role, integration, report, or schema field that was not in the scope. Copy changes under 30 minutes are free in my contracts.