Built for the people who have to price the change.

I'm Jackson Berry, and I built Scope after seeing the same problem play out repeatedly on real jobs.

I graduated from Miami University (Ohio) in December 2025 with a degree in Sustainable Development and Real Estate, and I've spent the months since working on the general contractor side of construction projects. It didn't take long to notice a pattern: drawings get revised constantly, sometimes dozens of times over the life of a project, and every revision creates a small window where someone is working from the wrong version, or misses a change buried in a schedule table that never got circled on the plan. On the electrical side especially, where a single panel relocation can ripple into rerouted circuits, updated schedules, and real cost impact, that gap is expensive. I watched confusion over what actually changed turn into rework, disputed change orders, and lost time, not because anyone wasn't paying attention, but because manually comparing revision after revision by eye is genuinely hard to do perfectly, every time, on every sheet.

I'm not an electrician, and I don't pretend to be one. What I am is someone who spent enough time close to this problem, from the GC side, to see how much it actually costs, in money, in schedule, and in trust between everyone on a project trying to build off the same set of drawings. Scope started as a tool to solve that directly: read a revised drawing, say exactly what changed, and be honest about how confident it actually is, not just what was easy to build.

Questions, feedback, or found something Scope got wrong? I'd genuinely like to hear about it: jcberry724@gmail.com.