One person accountable for your rollout, your regions and your escalations — not a queue.
Estate agreements
What we put in writing for a group operation.
An enterprise agreement should be a list of obligations, not a list of adjectives. Everything on this page is written into the Estate contract and can be checked against it.
99.9%Monthly availability, with credits
24/7Duty cover with a named lead
10 daysChange notice, with opt-out
3Residency regions: UK, EU, US
01 / 03
Commitments
Six obligations that go into the agreement.
99.9% monthly availability with service credits written into the agreement.
Your historical commitments are replayed through the platform before a single planner logs in.
Release notes 10 working days ahead, with an opt-out window on anything that touches your rules.
Security pack, DPA, insurance certificates and financial statements in one dossier.
A documented, tested export of every commitment, event and evidence asset you have put in.
02 / 03
Multi-entity
One group, several operating companies, shared crews.
Estate tenancies keep contracts, reporting and access separate between entities while letting crews and regions be shared where the group actually shares them.
Entity-scoped contractsTiering, penalty schedules and evidence rules are held per entity, never merged into a group default.
Shared crew poolsAn engineer can be assigned across entity boundaries with the cost attributed to the right operating company.
Role resolutionA regional duty lead sees their region across entities; an entity finance lead sees only theirs.
Group reportingAttainment rolls up to the group without losing the per-contract attribution underneath it.
Procurement pack
Everything your buyer asks for, in one dossier.
- SOC 2 Type II report and ISO 27001 certificate
- Penetration test executive summary
- Data processing agreement and standard contractual clauses
- Sub-processor register with change notice terms
- Insurance certificates and last two filed accounts
- Business continuity and tested exit plan
03 / 03
Rollout
A migration with a dry run before anyone logs in.
Your historical commitments are replayed through the platform first, so the board a planner sees on day one already looks like their operation.
Week 1
Shape one commitment type
We take the promise that hurts most, define its window, tier and evidence rule, and connect its source system.
Week 2–3
Run one region in parallel
Planners work the old way and the new way at once. Nothing is switched off until the board is trusted.
Week 4
Turn on the drift guard
The first signal rule goes live in dry run, then live. Escalations follow your existing duty ladder.
Month 2
Open the desk
Exception actions are written by your own ops leads, not by us. Regions come on one at a time.
Month 3
Hand the report to the client
Attainment and evidence packs generate against the contract and land in the customer's portal.
Next step
Send us the security questionnaire first.
Most enterprise conversations start with procurement, not product. Send the questionnaire and the trust pack comes back inside two working days.
- SOC 2 Type II under NDA
- DPA and SCCs ready to sign
- Named security contact, not a shared inbox