Free IT ticket analysis
Find out how much of your IT queue can run on its own
Move the sliders for a first estimate, then send us a ticket export and we work out the real figure for free.
491 hours back a year
9.4 hours a week · Stepwork works on 72% of your tickets
Hours a month still done by hand
- By hand
- Returned
Month
Starts from a real analysis of 1,923 IT tickets. Hours are modeled.
Fine-tune the estimate
Change any group or use case. The sliders above scale what you set here.
Where the tickets sit
Select a group to edit its use cases.
Access and identity
265 hours back a year
- Other app and license requests39 hrs a year
One intake routes by app to a flow for each: statistics, spreadsheets, file storage, dashboards, the ERP. License files go out from a shared folder.
Procedure70% of the time removed - Onboarding bundles for new hires and contractors112 hrs a year
Reads names and tools from the ticket, gets approval, then creates each person's accounts across the 5 to 8 systems they need and closes the ticket.
Procedure75% of the time removed - Issue tracker and wiki access20 hrs a year
Reads the project or space and access level, asks the owner in chat, changes the group or role, replies and closes.
Procedure85% of the time removed - Source repository access15 hrs a year
Reads the repository and access level, asks the repository owner in chat, grants the permission, replies and closes.
Procedure85% of the time removed - MFA resets, unlocks, and password resets14 hrs a year
Requested from chat. After an identity check, resets the factor or unlocks the account, including engineering tools and the vendor VPN.
Procedure85% of the time removed - AI coding tool seats9 hrs a year
Invites the user to the team after approval. A monthly run lists inactive seats to reclaim.
Flow + procedure90% of the time removed - Chat guests, shared channels, email groups and aliases11 hrs a year
Invites guests, extends guest expiry, creates shared channels, and manages groups, aliases and forwarding.
Flow + procedure80% of the time removed - Microsoft 365 and Teams licenses10 hrs a year
Checks free seats, assigns the license in the Microsoft 365 admin center, and sends sign-in steps.
Flow + procedure80% of the time removed - PLM and requirements tool accounts10 hrs a year
Creates the user, sets the role and project, and transfers licenses in each tool's web admin.
Flow + procedure70% of the time removed - Cloud console access requests5 hrs a year
Adds the user to a pre-approved group or policy after approval. New policies stay with an engineer.
Procedure with approval50% of the time removed - VPN access setup4 hrs a year
Adds the user to the VPN group or creates the vendor VPN account, then sends the client setup guide.
Procedure75% of the time removed - Linux server accounts and folder permissions5 hrs a year
Creates the directory user and adds groups or sudo rules. Folder permission changes stay manual.
Flow + procedure50% of the time removed - Offboarding and access removal11 hrs a year
After approval, deactivates the account, removes source control, wiki and VPN access, reclaims paid seats, and logs each removal for audit.
Procedure80% of the time removed
Build order
310 hours back in year one
- Month 2Hardware requests5 hrs a month back
- Month 3Inbox and alert triage3 hrs a month back
- Month 4Self-serve identity resets1 hr a month back
- Month 5Access requests11 hrs a month back
- Month 6Onboarding and offboarding10 hrs a month back
- Month 7Scheduled reviews and reports7 hrs a month back
- Month 8Infrastructure changes2 hrs a month back
- Month 9VPN and endpoint triage2 hrs a month back
Lowest effort is built first, starting in month 2. Nothing is saved until a procedure is live, so year one returns less than a full year.
Each use case has a handling time and a share of that time Stepwork removes. The starting minutes are estimates, because the export they came from had no time logged.
This starts from one company's mix of tickets. For your own mix, book your free analysis and send us an export.
How it works
Three steps, and the first is a CSV export
Book a call and export your tickets
Six to twelve months as a CSV, from any helpdesk.
We sort every ticket
Each one goes into a use case, matched to the flow or procedure that can run it.
You get the report
What Stepwork can run, what stays with your team, and the hours that come back.
Your service desk
Works with the service desk you have
Keep your service desk. Let the tickets run.
ServiceNow
Jira Service Management
FreshserviceManageEngine ServiceDesk Plus
Zendesk
The ticket starts the run
A webhook fires when a ticket is created or changes status.
The work happens in the app
Stepwork signs in and does the steps, whether or not the app has an API.
The ticket gets the answer
The run adds a note with what changed and resolves the ticket.
Your helpdesk automates about half. Stepwork works on the other half.
Serval, Ravenna, Console, and other AI-native helpdesks resolve requests through APIs. Stepwork runs the ones with no API to call, in the app's own screens.
- About 50%Automated through APIs
- 22%Repeatable, with no API to call
- 28%Needs a person
About 50% is what Serval's customers report (source). The rest of the split comes from the analysis the estimator starts from.
FAQ