The client remembers agreeing something different
The scope lived in a slide deck and three email threads. Nobody can point to the version that was signed off.
For agencies and dev shops
Agree the scope. Build it with agents. Prove you delivered it.
Publish the spec your client signs off, and they acknowledge the exact version. Your agents build against its criteria. When it’s done, hand over progress packs and release notes on your own letterhead. Client reviewers are free on every plan.
Sound familiar?
Agents made delivery faster. Scope arguments didn’t get shorter.
A change request arrived in a chat message
It was built before anyone priced it, approved it, or wrote down what it replaced.
The handover took longer than the build
Assembling what was delivered, against what, and who signed it off, is still a manual job at the end of every phase.
How agencies use Mataara
One record from signed scope to handover.
Scope as a published document
Publish the spec to your client. They acknowledge the version they read, and that’s on record.
Change Requests with approvals
Every change has an owner, a reason, the scope it touches and an approval before delivery starts.
Agents scoped to one client
Run each client as its own Product and give each agent a key that can only see that Product. For agent keys, an empty allow-list means denied: one-step setup won't create one, and any agent key left empty is refused every call.
Packs on your letterhead
Stakeholder packs and release notes, published and exported as PDF with your logo, header and footer.
Decisions and commitments
Record what was decided and why, and what you promised the client by when, with at-risk warnings when delivery slips.
Clients review for free
Clients and stakeholders read, comment and acknowledge as free reviewers. You pay for the makers who write the plan.
One client, one Product
Keep clients apart without a second account.
Run each client as its own Product. Scope every agent’s key to the Products it works on, so the agent for one client can’t read another’s. Agent access keys are on Business and Enterprise.
Evidence pack for handover
One file per Feature or change request: what was agreed, built, tested and approved, and who acknowledged it. Feature packs on Plus; change request packs for a whole phase on Business.
Questions
Straight answers for agencies.
Can my client log in?
Yes. Invite them as a reviewer in your organisation. They see what you publish to them and acknowledge the version they read. Reviewers are free.
Can I white-label it?
Your logo, header and footer go on every PDF you export. Full white-label of the app isn’t offered.
How do I keep clients separate?
Run one Product per client and scope each agent’s key to that Product. An agent can’t see a Product it wasn’t given.
What does it cost?
You pay per maker, the people on your team who write the plan. Clients and reviewers are free. See Pricing.
Your next client project
Run your next client project with a scope they signed.
Register, publish the scope, and send your client the link to acknowledge it.
Compare plans: Pricing. Questions? Talk to us.