Your price is fixed. Their requests are not.

Stria is the change-order tool for freelancers and studios who sell fixed-price work — the site build, the identity package, the fixed-scope sprint. A fixed fee does not move when the work grows, so every extra round comes out of your margin rather than your client's budget.

Scope creep does not arrive as a formal request. It arrives in an email, phrased as a favour, on a Friday — and the moment you reply "sure, no problem" the work becomes free. Forward that email to Stria and it checks the request against the scope you locked, flags the ones that fall outside it, and prices them against your rate card before you answer. Where it cites your agreement it quotes your own wording: the excerpt is re-sliced from your stored scope on the server, so a citation cannot be invented.

How the Scope Sentinel works

  • Forward or CC — Stria reads the client mail you send it. There is no mailbox to connect and no inbox access to grant
  • Check — each request is judged against the locked scope for that client's project, not against a guess
  • Price — a finding outside scope is costed against your rate card, with the basis shown so you can stand behind the number in front of a client
  • Recover — turn the finding into a change order your client signs, and bill it
  • Always answers — every forwarded message comes back with either a determination or the one setup step that will unlock it

Then the rest of the loop closes it

  • Share — send a passwordless client link from a Figma file, Loom, Google Doc, image, or PDF
  • Review — pin-point feedback, classified minor polish vs structural change
  • Sign off — email-verified approval with a content hash, version, timestamp, and IP
  • Prove — an immutable ledger you can export to a print-ready PDF

Why Stria

  • Scope creep caught in the inbox, before the work happens — not reconstructed afterwards from an argument
  • Detection is included on the free plan, with a monthly and a daily allowance. Paying buys the one-click change order, not permission to look
  • Passwordless for clients — no accounts, no per-seat reviewer fees
  • Email-verified, immutable sign-off — not just an "Approve" button
  • Signable SOWs, contracts, and change orders — lock scope at both ends
  • Flat team pricing and a forever-free tier

What happens after the verdict: knowing it is out of scope is the easy half

Every tool in this category sells you the detection and stops there. But a verdict does not pay anybody. You still have to price it, get it agreed, hold the work, invoice it, chase it, and know what is outstanding. Here is the whole run, in the order it happens.

  1. Agree it — Lock what is included Deliverables, quantities, the assumptions you priced against, and how many revision rounds are in the number. Locking is one-way: a locked scope can be superseded by a new version, never quietly edited, and every version stays on the record. This is the step people skip, and skipping it is why the rest of this list cannot run. What locking actually does
  2. Catch it — The request arrives the way requests really arrive In an email, phrased as a favour, usually on a Friday. Forward it to that client’s Stria address and it is captured — nothing to connect, no inbox access to grant, nothing to install. A comment your client leaves on a shared deliverable takes the same path from here on. How forwarding works
  3. Judge it — A verdict that quotes your own scope back at you In scope, partly in scope, likely out of scope, or needs clarification. The excerpt you read is cut out of your own document by the server, never written by the model — and a quotation that cannot be located in your scope is not shown at all. The verdict drops to needs clarification instead of guessing, which is the opposite of a confidence score. Inside the determination
  4. Price it — It becomes a priced change order Priced against your rate card with the basis shown, and totalled on the server rather than in the browser, so the figure your client sees is the figure your records hold. The same request cannot be billed twice — not on a second change order, and not twice on the same one. Price a change
  5. Sign it — Your client signs, and the scope amends itself The signature lands on a document, and the locked scope moves to a new version carrying what was just agreed. That matters more than it sounds: the next request gets judged against the scope as it stands today, not as it stood in March, so the boundary keeps up with the project instead of drifting behind it. How the signature holds up

This is where the other tools stop

They tell you it is out of scope, hand you a document, and leave the part where the money actually arrives to you and a spreadsheet.

We read the marketing pages of 5 scope-creep products built for this exact problem, most recently on August 13, 2026. The furthest any of them takes you is the signed change order you just reached — one of them adds an evidence-pack PDF and ends there. Not one of them mentions the deposit that holds the files, the invoice, the reminder that goes out on day five or the sheet of who still owes you.

So the 4 steps below are the ones nobody in this category is selling, and they are the ones that decide whether the finding was worth anything. A change order you never invoiced is a well-documented favour.

  1. Hold it — The deposit holds the files until it clears Not a polite line at the bottom of an invoice. While a deposit is outstanding Stria will not sign a download link for the deliverable files, and will not sign one if the check itself fails either — an unknown answer holds the file rather than releasing it. Your client still sees the scope, the thread and the approvals. Just not the artwork. You can release it yourself, whenever you decide to. See the whole loop once
  2. Bill it — An invoice with your tax on it, not a guess at it Your tax label, your registration number, and a rate per line — so one invoice can carry a domestic rate and a zero-rated export without becoming two invoices. The label and the number are copied onto the invoice when it is raised, so changing your registration next year cannot rewrite an invoice you already sent. Where a due date comes from
  3. Chase it — Reminders escalate so you do not have to Friendly, then firm, then a final notice: three by default, at least five days apart, on the cadence you set. A late fee waits until the final notice has actually gone out, because a fee nobody was warned about starts an argument rather than collecting a payment. Chase what is late
  4. Bank it — Every client you are owed by, on one sheet One list across every client and every project: what is outstanding, what is overdue and by how many days, held per currency rather than blended into a single total you could never reconcile against your bank. This is the page that answers the question you actually open the app to ask. Read your receivables

And all of it is collected on your own Stripe account

Your account, your customer relationship, your payouts. Stria never holds the money and takes no percentage of it — there is no platform fee on top of what Stripe charges you, because the charge is made directly on your account rather than routed through ours. Compare the fees side by side

Check a request against your scope · Start free · See pricing · Open the live demo · Help centre

Featured on

Featured on Aura++ Featured on Toolfio Launched on stria Stria on Nick Launches Launched on Launch Streak Featured on EasyLaunch Stria Reviews