Loading
It hears about things last. A starter is agreed in HR and IT finds out the day before; a leaver is processed on their last day and access closes the following week if somebody remembers.
And the request queue is email, so there is no catalogue, no clock and no way to say what the team is absorbing.
Joiners and leavers come from the personnel record in Nest: onboarding opens the access request with the role's requirements on it, and offboarding closes access across every product in one action.
Other requests run from a service catalogue — a defined list with expected turnaround — rather than free text.
It does not deploy software, manage endpoints or discover devices. It holds the service relationship and the asset record beside the tools that do.
And it will not stop people messaging you directly. It gives that message somewhere to become a ticket.
Incidents, problems and changes are separate lifecycles, so a recurring fault becomes a tracked problem rather than a monthly irritation.
And load is reportable against the requests that caused it, which is how internal IT stops being invisible in budget conversations.
Yes, from Nest, with the role's access already scoped.
Yes, across every product, in one action.
Yes, with defined requests and expected turnaround.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.