
ScopeDiff
A living record of what you're building for your client
This is for small teams / solo devs building software for clients -- you agree on a scope, sign it, then build.
Scope always changes after that. That's not a failure. Clients change their minds, priorities shift, new information comes up mid-project. Completely normal.
What's not normal is that the written record rarely catches up. A weekly email or a biweekly call is good at showing where things stand right now. Neither keeps a trail. Months in, nobody can say when something changed, who asked for it, or what the plan looked like before.
I found this out the hard way. Near the end of a year long project, a client asked why we'd built something that wasn't in the original scope doc. Even though they're the ones that asked for it themselves (months earlier) in Slack. I just couldn't prove it without scrolling back through a year of messages, which is slow, and in front of a client, looks exactly like making excuses.
That gap creates two specific problems:
The client forgets they asked for something, and it reads as you not delivering what was agreed.
You quietly build extra work that never gets recorded, and you either eat the cost or have an awkward conversation about it later.
ScopeDiff starts from the scope doc you both sign, turned into an actual list of deliverables instead of a wall of text. Keeping it current is the part I actually cared about getting right — you can update it yourself in a couple of clicks, or let it read your GitHub activity and draft the update for you: what moved, what doesn't map to anything you agreed on. Either way you're confirming a short list, not writing a report from scratch. Every time you publish, it saves a version, so there's an actual history: what changed, and when.
Your client gets one link, no login, clean enough that they'll actually read it — and it shows exactly what's new since they last looked. They can also leave a quick "reviewed this" receipt, so you know it landed.
Still early, so I don't know yet whether "confirm a weekly diff" is actually easier than what people do today. That's the real bet.
About
We signed a scope doc with a client and never updated it. A year later they said we hadn't built what we agreed to. A lot of it they'd asked for and forgotten. So I built ScopeDiff. It updates itself from your commits.

3 Comments
The version history is the strongest part here. The product isn't just tracking current scope; it's preserving how the agreement changed over time.
gonna try this on my next job, will report back
love this, was BURNED by this problem bakc when i used to freelance