Scope tracking for fixed-price software projects
Keep the projectyou signed.
Devposal checks every new client request against the proposal they approved, prices the extras as a change they approve from a link, and keeps a record of how the project grew. The agreement says no, so you don't have to.
Part of it works today in every proposal. See what's ready
How a two-month project becomes six
It's rarely one big change. It's a steady stream of small ones, agreed in passing, that nobody adds up until the deadline has already gone.
01
Requests arrive everywhere
A voice note on WhatsApp, a line at the end of a call, a comment in Figma, an email at 11pm. None of them is written next to what you agreed.
02
Each one is “only small”
A filter, an export, one more role, a report for the board. Each is a few hours. Together they're the second half of the project, unpaid.
03
Saying no feels personal
So you say yes, or you argue. Either way it's you against the client, and the relationship pays for it.
04
Months later, nobody remembers
When the deadline slips, the client remembers asking for small things. You remember a different project. Neither of you has the record.
One record of what was agreed, and everything asked since
Step 1
The signed proposal is the agreement
When your client approves a proposal, its deliverables are numbered S-1, S-2… and its exclusions X-1… That version is frozen with the signer's name, the time and a fingerprint, so there's one answer to “what did we agree?”.
Step 2
Paste what the client sent
A WhatsApp message, an email, call notes. Devposal finds each separate request in it and checks every one against the agreement: in scope, a small extra, not in the agreement, or something to ask. Each answer cites the numbers, and nothing goes to the client until you've confirmed it.
Step 3
Decide, and the reply writes itself
Do it, do it as goodwill, add it as a priced change, park it for later, or decline. Devposal drafts the message back in a warm, neutral or firm voice. The agreement does the saying no, so you don't have to.
Step 4
A record both of you can see
Every version, approval, request and decision on one timeline, with what was signed, what it is now, and a side-by-side diff of how the scope changed. When a deadline is questioned, you show the timeline instead of arguing from memory.
Be generous on purpose
Good clients ask for small things, and doing a few for free is part of a good relationship. Agree how much up front, for example 5% of the hours, and let both sides see it being used.
When the allowance runs out, the next small extra becomes a priced change. Nobody has to have the awkward conversation; the balance already did.
What works today, and what's next
The core is built into Devposal proposals already. The waitlist is for the rest: capturing requests where they happen, and a project page your client keeps open.
In every proposal now
- Proposals your client approves from a link, with a signed copy
- Numbered deliverables (S-1…) and exclusions (X-1…), shown on every proposal
- Paste a client message: every request checked against the agreement, or run the same check in your own ChatGPT or Claude
- Reply drafts in three tones
- A goodwill allowance your client can see
- Changes as an updated version the client re-approves, or as options they take or leave
- The project's history on your client's page: versions, approvals, requests and free extras
- A printable history with each approval's time and fingerprint, and a diff from signed to now
Coming for people on the waitlist
- Forward an email to a project address instead of pasting
- Slack, Linear, Jira and GitHub: requests checked where they're made
- A project page for your client with every open change in one place
- A weekly summary for both sides
- Team seats for studios
Your client's project stays yours
- Only the scope, never the code
- Devposal needs the text of what you agreed and what was asked. Not your repository, credentials or designs.
- Not used to train AI
- What you paste is used to answer you and nothing else.
- Yours to take or delete
- Export everything as a file whenever you like. Deleting your account deletes your projects.
- Evidence, not a lawyer
- Approvals carry a name, email, time and a fingerprint of the exact version. It isn't legal advice.
Questions
New to handling this? Read how to handle scope creep and try the cost-of-small-yeses calculator.
What is scope creep, and why does it hit fixed-price projects hardest?
Scope creep is new work that arrives after the price is agreed, usually as small requests that each seem too minor to discuss. On hourly work the client pays for every change; on a fixed price the developer absorbs it, which is how a two-month build turns into six months of unpaid work and a missed deadline.
How does Devposal decide whether a request is in scope?
It compares the request with the proposal your client signed. Every agreed deliverable has a number (S-1, S-2…) and every exclusion too (X-1…), and each request comes back labelled in scope, not in the agreement, a small extra, or needs a question, with a one-line reason that cites the numbers. You confirm or change every label before your client sees anything.
Does my client need an account?
No. Your client reads the proposal, approves changes and sees the project's history from a link, the same way they approve a proposal today.
What is the goodwill allowance?
A small number of hours for little extras that you agree up front, for example 5% of the project. Small requests you choose to do for free use it up, and your client can see the balance. When it runs out, the next small extra becomes a priced change, and the system says so, not you.
Is my project information safe?
Devposal only needs the text of your scope and the requests you paste in: never your code, credentials or repositories. It isn't used to train AI models, you can export everything, and deleting your account deletes your data.
Is a scope record legally binding?
The signed proposal and each approved change carry the signer's name, email, time and a fingerprint of the exact version, which is good evidence of what was agreed. It isn't legal advice or a substitute for a contract; for large projects, have a lawyer read your terms once.
How much will it cost?
What's built today (checking requests against the signed proposal, options, the shared history) is part of every Devposal plan. The parts still coming, like capturing requests where they happen, will be priced per active project, not per seat, and people on the waitlist get founding pricing for a fixed term.
The next “can we just add…” is already on its way.
Join the waitlist for scope tracking. Founding pricing, for a fixed term, for the people who join first.