Product
Scope Creep Reply
For the freelancer, small studio, or solo contractor who just got a 'while you are at it, can you also...' email from a client and needs to reply in the next 20 minutes without giving away the work for free, without sounding hostile, and without inventing a price. Paste the client's request, the original scope (if you have it), your rate, your honest estimate for the new work, and a realistic delivery date. Get back a 3 to 4 sentence structured reply that acknowledges the ask, anchors it as out-of-scope, quotes a specific change-order price and delivery date built from YOUR numbers, and offers to send a written change-order document. On the deep tier you also get a three-option frame (keep as-is, add for fee, swap for lower-priority item), a paste-ready formal change-order block, and a second-touch de-escalation reply calibrated to the relationship archetype for when the client pushes back. Global refusal of invented prices, passive-aggressive tells ('per my previous email,' 'as I mentioned,' 'I hope this makes sense'), and any language that threatens to withhold delivered or paid-for work.
About this tool
What does scope creep reply do?
For the freelancer, small studio, or solo contractor who just got a 'while you are at it, can you also...' email from a client and needs to reply in the next 20 minutes without giving away the work for free, without sounding hostile, and without inventing a price. Paste the client's request, the original scope (if you have it), your rate, your honest estimate for the new work, and a realistic delivery date. Get back a 3 to 4 sentence structured reply that acknowledges the ask, anchors it as out-of-scope, quotes a specific change-order price and delivery date built from YOUR numbers, and offers to send a written change-order document. On the deep tier you also get a three-option frame (keep as-is, add for fee, swap for lower-priority item), a paste-ready formal change-order block, and a second-touch de-escalation reply calibrated to the relationship archetype for when the client pushes back. Global refusal of invented prices, passive-aggressive tells ('per my previous email,' 'as I mentioned,' 'I hope this makes sense'), and any language that threatens to withhold delivered or paid-for work.
How does Scope Creep Reply work?
Paste the client's request verbatim, paste your original scope if you have it, tell it your rate, your honest estimate for the new work, and the revised delivery date you can actually hit, then pick a tone and a relationship archetype. One structured AI pass returns a 3 to 4 sentence reply that acknowledges the ask, anchors it as out-of-scope, quotes a specific change-order price built from your numbers (never invented), quotes a specific revised delivery date, and offers to send a formal change-order document. On the deep tier you also get a three-option frame (keep as-is, add for a fee, swap for a lower-priority item in the current scope), a paste-ready formal change-order block, and a second-touch de-escalation reply calibrated to your relationship archetype for when the client pushes back.
How do I reply to a client asking for out-of-scope work without ruining the relationship?
The tool composes exactly the reply the situation calls for: warm enough to keep the client, clear enough to protect the current scope. It acknowledges the ask in one line, names the ask as out-of-scope in one line, quotes a specific change-order price and revised delivery date in one line, and offers to send a formal change-order document in one line. Nothing threatens delivered or paid-for work, nothing lectures the client about scope, and the passive-aggressive tells that torch client relationships (per my previous email, as I mentioned, just circling back, kindly note, I hope this makes sense, moving forward) are stripped by rule and receipted so you can see the pass ran.
What is a change order and when should I send one?
A change order is a short written amendment to the original scope of work that names the new deliverable, the price for the new deliverable, and the revised delivery date, signed by both sides before the new work starts. Send one whenever a client asks for something outside the original SOW that would take real time or push the current milestone, even (especially) when the client is a repeat client and the ask sounds small. It protects both sides: the client sees the price and the schedule impact before you begin, and you have a signed paper trail if a payment dispute lands later.
How do I quote a change-order price without inventing it?
You give the tool your rate in whatever form you write it (an hourly rate, a flat rate, a day rate plus expenses) and your honest estimate for the new work (6 to 8 hours, 1 week, 3 days of design plus 1 day of review). The tool combines them literally and quotes the result as a specific price or a price range in the reply and in the change-order block. It never rounds in your disfavor, never invents a rate you did not supply, and never quietly upgrades your estimate to a bigger number. Every refusal to invent a price is logged in the safety_notes panel.
Will it invent a price, a delivery date, or a contract clause I did not give it?
No. There is a hard no-invention rule the model cannot bend. Every price in the reply is computed from the rate and estimate you typed; every delivery date is the one you typed; every clause in the change-order block is anchored to numbers you supplied. If the situation would benefit from a fact you did not give (a specific late-fee percentage, a prior signed total, a retainer clause), the tool writes the block around the gap and leaves the field open for you to fill in, instead of fabricating a term you cannot back up. Every refused fabrication is receipted in the safety_notes panel so you can verify the pass ran before you send.
What if the client keeps pushing scope creep after I send the reply?
The deep tier ships a de-escalation second-touch reply calibrated to your relationship archetype. First-project runs slightly warmer and re-anchors to the same price and date without discounting. Repeat-client names the prior good work in one line and re-anchors without conceding free work. Final-milestone reminds the client the current scope is nearly done and the new ask belongs to a follow-up SOW. Already-past-deadline hard-refuses any swap that would push the current milestone, states plainly that the current milestone comes first, and offers to schedule the new work only after the current milestone signs off. Every variant validates the client's logic in exactly one sentence, restates the anchor without saying as I said before, and refuses to threaten delivered or paid-for work.
Does a change order need to be signed?
Yes, before the new work starts. The change-order block the tool composes is a paste-ready formal document with labeled lines for New Work, Price, Revised Delivery, Revised Total, and a signature line reading Signed and accepted by ______________________ on ______________________. A verbal change order is worth what a verbal contract is worth, which is very little when a payment dispute lands 60 days after delivery. The 30 seconds it takes to countersign is cheap insurance against the client later claiming the new work was always in scope.
How is this different from asking ChatGPT to help me handle scope creep?
A freeform ChatGPT prompt happily invents a price you never gave it, reaches for the exact passive-aggressive phrases that make clients rage-quit (per my previous email, as I mentioned, just circling back, I hope this makes sense, sorry to have to say this, kindly note, moving forward), and cheerfully threatens to withhold delivered work when it thinks it is protecting you. Scope Creep Reply runs one structured pass with four hard rules: never invent a price or a delivery date, never write a phrase from the passive-aggressive freelancer-email lexicon, never threaten delivered or paid-for work, and always anchor the reply to the client's actual request and your actual scope. Every rewrite is logged in the receipts panel so you can verify the pass ran before you hit send.
Which tier should I pick, Quick or Deep?
Pick Quick (15 tokens on Gemini Flash Lite) for the client who emailed 25 minutes ago and you have a boundary to send before the next standup: still tone-and-relationship aware, still refuses to invent prices, still strips the top 8 passive-aggressive tells, still records every refusal in safety_notes. Pick Deep (30 tokens on Gemini Flash) for the client you actually want to keep on the project you actually want to protect: the boundary reply plus the three-option frame (keep, add for fee, swap), the paste-ready formal change-order block, the second-touch de-escalation reply calibrated to your relationship archetype, and the complete 2025 to 2026 passive-aggressive freelancer-email lexicon stripped with each rewrite receipted.
Is it free, and do I need a subscription?
There is no subscription. You spend tokens per run: 15 produde tokens for the Quick tier and 30 for the Deep tier. Tokens are a prepaid platform credit you buy once and spend across any produde tool, so you pay per scope-creep reply instead of a monthly freelance-ops SaaS fee. If a run fails, the full token cost is refunded to your wallet automatically.
What does it cost?
From 15 tokens. Pick a tier on the form above. Produde tokens are a prepaid platform credit; buy them once and spend on any tool.
Do I pay if a run doesn't complete?
No. You only pay for results. If a run can't finish, its full token cost stays in your wallet automatically.
Is my data stored?
Your input and the run output are saved to your account so you can browse history. They are not sold, shared with advertisers, or used to train shared models. See privacy for details.