Chapter 6 of 8 · Adaptable
Built to keep changing
Your business will change. The platform should change with it: everyday adjustments in your administrators' hands, bigger ones as short increments on the same foundation.
Your administrators, today
No ticket, no developer, no waiting.
- Custom fieldsAdd the details your team needs to companies, deals, requests, people and projects.
- Your namesCall Service “Customer care” or Sales “Business development”. Navigation follows.
- Apps on and offSwitch on an app when a team is ready; switching one off closes access in the database.
- Roles and permissionsCreate roles that match how responsibility actually works, down to individual permissions.
- Who can joinLimit invitations to your email domains, and see every membership change in the audit log.
With us, in an increment
Small, tested, released without disruption.
- New rules and stepsAn extra approver above a threshold, a new stage gate, an escalation after two days.
- Automation between appsA won deal that creates the project, its milestones and the kickoff booking.
- New apps on the same dataAsset tracking, inspections, quoting: new processes join the records you already have.
- IntegrationsAccounting, payroll, identity and messaging, so information flows without rekeying.
- Reports and dashboardsThe measures your leadership actually uses, read live from the records.
How a change happens
From request to running, tested and on record
- 1
Ask
Describe the change in your words
- 2
Shape
Agree the rule, its exceptions and who's affected
- 3
Build and test
Tested automatically, then by your people
- 4
Release
Designed for releases without service interruption: the old version runs until the new one is ready
- 5
Recorded
The change and who approved it, on record
How quickly a change ships depends on its size; most rule changes are small increments.