Two weeks for a design tool
A marketing lead needs a design tool for three people on her team. She opens a ticket. Someone in IT logs into the license tool, or a spreadsheet, to see whether there are free seats. There aren’t, so procurement gets involved, and the purchase needs a director’s sign-off because it is over the threshold. Once the seats are bought, a technician pushes the install from Intune and closes the ticket. Two weeks have passed. One of the three has started using a personal account in the meantime.
The work in that chain is small. The waiting comes from the handoffs, and the cost comes from the guesswork: organizations buy seats they already own because nobody checked, and keep paying for seats nobody opens.
What the request looks like now
- The marketing lead picks the title in the catalog and adds her three people.
- Kinetic asks the license tool how many seats are free. Two are.
- Two installs go ahead. Approved, licensed titles don’t need a manager’s approval unless you want one.
- For the third seat, Kinetic opens a purchase request with the vendor, SKU and cost center already filled in and routes it by cost: under your threshold to the manager, over it to a director.
- When approved and bought, the install is sent to the right tool for the device: Intune for cloud-managed laptops, SCCM for on-premises machines, Jamf for Macs, or the RMM for endpoints an MSP manages.
- Kinetic waits for the install result, updates the ServiceNow ticket if one exists, and writes the seat assignment back to the license tool.
Getting seats back
The same workflow runs in reverse. On a schedule, Kinetic pulls last-use data, asks people with idle seats whether they still need the software, and releases the seat if they don’t. Offboarding releases every seat the departing employee held.
For MSPs
Service providers run this per client: each client has its own catalog, approval rules and deployment tool, but the workflow is built once. Adding a client is a matter of connecting their tools and setting their policies.
From here most teams add device lifecycle management, which uses the same catalog and approvals for hardware, or broaden the catalog into a full IT service catalog.