Guided Pilot
For proving Root against one real workflow, project or controlled process.
- Focused module scope
- Test environment
- Configuration workshops
- Guided acceptance testing
- Deployment recommendation
Start with the operating problem. Scale with the deployment.
Root pricing reflects the scope, customer boundary and support required—not the number of comments, tasks or records your team creates.
Site
For a live customer site or project needing connected operational control.
- Selected or full module suite
- Customer site and project configuration
- User and external-party access
- Storage and authentication setup
- Onboarding and administrator enablement
Portfolio
For organisations operating Root across several projects, sites or business units.
- Multi-site/project governance
- Reusable templates and standards
- Environment promotion controls
- Portfolio reporting approach
- Scaled support and rollout planning
What shapes a proposal
Clear commercial inputs.
Customer, sites, projects and environments.
The workflows enabled at launch and planned next.
Internal users, vendors, construction partners and support model.
Validation, storage, retention, identity and customer governance.
Do you charge per task, document or transaction?
No. Root is intended to support active use, so the commercial model is not based on restricting normal operational records.
Can we begin with only a few modules?
Yes. A focused starting scope is often the best way to prove the operating model, then connect adjacent workflows.
Are implementation and configuration included?
Every proposal states the included discovery, configuration, onboarding, testing and support so there is a clear path to use.
Can data and files be migrated at the end?
Customer portability and offboarding requirements can be agreed as part of the deployment and storage design.