Scope control for software & design agencies
Scope creep has a price.See it before the work starts.
Acta checks every Linear task against your signed contract and flags what's unbillable, with the clause, the hours, and the dollars behind it.
Every flag cites your contract, your rate card, and your tracker. Not a guess.
Unlimited revisions are where margins go to die.
Scope grows quietly. An extra page, a third revision, an integration nobody priced. The contract said what was included. Nothing was watching it while the work happened.
Run the math on your own team. A 10-person agency writing off five unbilled hours a week at a $150 rate loses around $39,000 a year. Not in one painful invoice. One small task at a time, which is why nobody sees it until the project closes red.
The evidence behind the call.
Flagged because no baseline deliverable covers analytics work. The SOW scopes the marketing site only.
The contract supports two readings here, so Acta won't force a call. This one goes to you, with both readings laid out.
These are samples, not a real client's data.
Acta watches every task against the contract.
Approve the baseline
Upload the SOW. Acta extracts deliverables, boundaries, exclusions, and revision limits, each backed by a verbatim quote. You approve every line before it goes live.
Monitor the work
Connect Linear. Every issue that moves gets checked against the approved baseline. No timesheets. No new habits for your team.
Recover the value
Work that falls outside scope, or past the revision limit, gets flagged and priced at your rate card, clause cited. You send a change order backed by evidence, not by memory.
Start with a project you already closed.
Before Acta watches a live project, run an autopsy on a finished one. Upload the signed SOW, connect the Linear history, and Acta classifies every ticket against the baseline: in scope, out of scope, or unclear, each with the clause and the hours.
Illustrative · your number comes from your contract and your rate card
Most of that money is gone. You can't invoice a closed project. But the autopsy does two things a gut feeling can't: it proves the leak is real, and it shows you exactly where scope slipped past your team. The next contract gets written knowing that.
You don't wait weeks of live monitoring to find out whether Acta's calls hold up. Judge it against a project where you already know how the story ended.
Every flag shows its work.
Two things a timesheet will never do: cite the contract with precision, and learn from the calls your team makes.
Every flag shows its evidence
Each call cites the baseline clause by name, priced in hours and dollars. When the boundary is genuinely unclear, Acta marks it for review instead of forcing a verdict.
- Unclear work goes to review, not into a forced verdict
- Priced in hours × your rate card
- Reasoning you can read, not a template
It learns from your decisions
Mark a flag in scope and future calls learn from the correction. Absorb one and the cost lands in a running ledger, so you always know what you gave away.
- Learns from the decisions your team approves
- Absorbed vs. recovered, tracked in dollars
- Stays specific to your contracts and rate card
Next: scope your whole team can see.
Beta members are shaping what lands next, so scope stops being one person's job and becomes something the whole team can act on.
Ask Acta in Slack
Anyone on the team can ask “is this in scope?” without leaving Slack, and get the verdict, the clause, and the dollars back in seconds.
Alerts before the hours get spent
The moment work drifts out of scope, Acta notifies the right people in Slack or email. No one has to be watching a dashboard.
More of your stack, connected
Linear today, with Notion, Jira, and GitHub Projects next, so Acta watches scope wherever your team tracks the work.
Questions, answered.
Acta is scope control for agencies. It reads your signed scope, watches the Linear tasks your team already creates, and flags work that may fall outside the scope, with the hours, the dollar amount, and the clause it relates to.
Software and design agencies of roughly 5 to 20 people who bill against a signed scope or SOW and feel margin leaking to unbilled, out-of-scope work.
Yes, and that's how most teams start. Upload the SOW from a closed project and Acta classifies the historical Linear tickets against it, totaling what leaked. It's the fastest way to test Acta's judgment against a project you already know.
Yes. Your baselines and work data live in your own workspace and are never shared with other agencies or used to train anyone else's model.
Linear today. Notion, Jira, and GitHub Projects are on the roadmap, but only Linear is wired right now.
You upload the SOW, proposal, or scope doc. Acta extracts a structured baseline: deliverables, boundaries, exclusions, revision limits, each backed by a verbatim quote. You review and activate it; no baseline goes live unreviewed.
It's free during the private beta. Pricing comes later, and beta members help shape it.
You get one confirmation email right away. We onboard a small group each week and reply personally within two business days to schedule your setup. If your team isn't on Linear yet, your answer on the form is the vote that decides which tracker we build next.
Put your contract to work.
Acta is in private beta for software & design agencies of 5 to 20 people. Linear support today, more trackers on the way. Request access and we'll reply within two business days.
One confirmation email. No spam, no sharing your address.