Audit type
User adoption diagnostic
If half the paid seats have not been used in thirty days, the application is not ‘under-trained’. It is usually the wrong shape for the job, too slow on a phone, or already replaced by a side channel. An adoption diagnostic starts from that suspicion.
We sit with the people who should be in the CRM and the people who have quietly left it. We look at last-activity dates, empty required fields, and the moment in a call when someone says they will ‘update it later’ and does not.
The write-up names friction by role. It may recommend fewer required fields, a simpler mobile path, or an honest decision that a team should not be forced into the CRM at all. It will not recommend a motivational poster.
What is in the engagement
- Login and last-activity patterns by role (from exports you provide)
- Interviews with people who avoid the CRM and people who live in it
- Screen-level friction: required fields, duplicate entry, mobile use
- Recommendations that do not assume more training is the only answer
Fees are informational. We confirm the figure after the scoping call, against the size of the organisation and the state of the file. Payment is by invoice; there is no online checkout.