About
Built by people who run an MSP
ScopeAssistant is built by Raven Automation. We didn’t learn about project losses from a survey. We watched them happen in our own shop.
Why we built ScopeAssistant
Running our own MSP, we told ourselves the same story every owner does: projects are there because clients need them, they keep the managed-services agreement healthy, and they never quite make money. When a project ran long, it looked like a delivery problem.
It wasn’t. When we lined up quoted labor against actual, the product side was nearly always on budget. The overrun was labor, and it was baked in the day the quote went out: no PM time, no exclusions, no client responsibilities, and hours that assumed nothing would go wrong.
Templates didn’t fix it, and neither did general-purpose AI. Both write what you already know. So atRaven Automation, where we build automation for MSPs every day, we built ScopeAssistant: a tool whose job is to find the scope you left out, before the client ever sees a number.
We’re now working with a small group of founding-customer MSPs to prove the results with their own numbers, and we’d like you to be one of them.
What we believe
Fix it at the quote
Project margin is decided before the work starts. We build for the moment the scope gets written, not the post-mortem.
Don’t blame the techs
Engineers should deliver against a scope they could actually hit. A complete scope is how you make that fair.
A person signs off
AI drafts the scope and looks for what is missing. Someone on your team always approves it before a client sees it.
Prove it with real numbers
Our figures come from running an MSP. We will replace them with our founding customers’ before-and-after results as soon as they exist.
Put the missing hours back on the quote.
Join our founding customers and make a complete scope the default for every project.