ServiceNow is hired to take IT requests, track incidents and run approvals. Many companies use a small corner of it. Below: how to find out which corner, what a narrow replacement would cover and must not copy, and what to settle before you cancel.
A request system gathers habits. People submit things there, approvers expect them there, and a couple of other tools send tickets to it. Each connection is small, and together they make it feel like part of the plumbing.
It is also bought for a larger job than most teams grow into. The company keeps paying for the platform while using a few forms and an approval chain, and nobody has written down which parts matter.
Only alternatives we have checked. An open-source project is listed with the license its repository reports, on the date shown; one whose license could not be read as a single standard id is not offered as open source. Read the license guide before running any of them.
| Alternative | Kind | License | Read from |
|---|---|---|---|
| A request tracker for the handful of request types IT really gets | Custom build | — | Written for the one job |
A request system is a set of forms, rules and records. Most companies use a small part of it, and the first piece of work is to write down which part. If it is five request types and one approval chain, a lighter tool can do that job. If it is also your configuration database and your change-control record, it is a platform, and replacing it is a project.
We rate this one hard. The software is not the difficult part. The difficult part is the connections and the records that other people rely on. The realistic path is a narrow build, or a lighter existing tool such as Jira, for the daily requests, while the contract runs to its end.
Samples are made up and are not ServiceNow's prices. Type in the figures from your own invoice or order form.
Build a small tool or keep paying for one: the cost of each over your horizon and the month the build breaks even.
Paid seats against seats in use: what the idle ones cost a year, and what you save by right-sizing at renewal.
Arithmetic only, not tax, accounting or legal advice. Check the figures against your own order form.
Move the requests people actually make first, keep the old system read-only for lookups, and end the contract only when nothing depends on it.
Export a year of tickets and count them by request type. List the types that make up almost all of the volume and the ones nobody has used.
For each type, write who requests, who approves, what happens next and how it is closed. This document is the specification of the replacement.
List every other system that creates tickets or reads them: monitoring, HR, email. Each is a connection to rebuild or retire.
Run one request type, such as software access, in the replacement for two weeks. Compare what it records with what the old system would have.
Move the remaining types one at a time. Keep the old system in read-only mode, with no new tickets, so old cases can still be looked up.
Take the full export of tickets, attachments and approvals. Check counts against the system, and store the export under access control.
After a full month with no new tickets in the old system, end the contract inside the notice window and confirm the end in writing.
The realistic version is a narrow tool written from scratch for the request types your company actually has. It is not a clone of ServiceNow. It copies no code, screens, branding, wording or workflows from the product, and it makes no attempt to reproduce the platform.
Tickets are a place where employee names and sometimes personal details end up, so the tool needs the same access control and retention rules as any HR-adjacent system. Keep the asset and configuration records, security tooling and anything the contract or an auditor depends on in a system built for them. A small build sits beside the long-term system of record. It does not replace it.
Run the vendor report for QuickBooks Online or Xero, then open the free audit.
General information, not legal advice. See cancelling without penalties. Last reviewed Oct 25, 2026. Product names belong to their owners and are used only to identify them.
Send us the export and see which lines are worth a second look. A connected version is planned. ServiceNow is one of the lines worth a look.
Worked example. Type over it.
Result
| Year | Buy, cumulative | Build, cumulative |
|---|---|---|
| 1 | 9,000.00 | 8,040.00 |
| 2 | 18,000.00 | 10,080.00 |
| 3 | 27,000.00 | 12,120.00 |
Undiscounted, and it leaves out the vendor's price rises and your own overruns. A tool built for one job is not the whole product: list what you would lose before you count the saving.
Worked example. Type over it.
Result
“In use” is your call: last sign-in in the past 30 or 90 days from the vendor's admin report. A seat for someone on leave is not idle.