Custom Tables and the Licensing Line
Custom tables are how teams extend ServiceNow beyond the out of the box modules, and in some agreements a custom build that grows past a threshold triggers a separate licensing line. Because the tables are created by technical teams mid project, the charge is often discovered only at renewal, so the move is to define coverage and price before you build at scale.
Key takeaways
- Custom tables extend ServiceNow on the Now Platform beyond the standard modules.
- Some agreements treat heavy custom application use as a separate licensable category with its own charge.
- The charge surprises buyers because the tables are built by technical teams during projects, not procurement.
- Inventory your custom builds, clarify what existing licensing covers, and agree the threshold and price up front.
What is a custom table on ServiceNow?
A custom table is a data structure your teams create on the Now Platform to support an application or process that the out of the box modules do not cover. Custom tables are the normal way organisations extend ServiceNow, from a bespoke request workflow to a full department application. They are powerful and widely used, which is exactly why their commercial treatment matters more than buyers often realise.
The key point is that not all custom use is treated the same way in every agreement. A handful of supporting tables behaves very differently, commercially, from a large custom application built and operated at scale. The line between extension that is covered and custom build that is separately licensable is where the surprise lives.
Why do custom tables create a separate licensing line?
Because some agreements treat heavy custom application use as a distinct licensable category, so a build that grows beyond a defined threshold can trigger an additional charge. The logic on the vendor side is that a large custom application is its own workload rather than a light extension of the modules you licensed. Whether that applies to you depends entirely on the wording of your specific agreement and the scale of what your teams have built.
The reason this lands as a surprise is organisational. Custom tables are created by developers and platform teams during projects, focused on solving a business need, while the licensing implication sits with procurement and is rarely in view at build time. By the time the renewal arrives, the estate has grown, and the question of what is covered surfaces with a number attached. The fix is to connect the two functions before the build, not after.
How do you control custom table licensing?
Inventory what you have built, clarify what your existing licensing covers, and agree the threshold and price before you build at scale. The work breaks into clear steps.
| Step | What it answers | Why it protects you |
|---|---|---|
| Inventory custom tables and applications | What exists and how heavily each is used | You cannot negotiate a build you have not measured |
| Map builds against your agreement wording | Which custom use is covered and which is separately licensable | Removes ambiguity the vendor would otherwise resolve in its favor |
| Define the threshold and the price up front | The point at which a charge applies and what it is | Turns a renewal surprise into a planned, known cost |
| Set governance for new custom builds | Who approves a build with a licensing implication | Stops uncontrolled growth from creating the next surprise |
Negotiating clarity is the goal here, not a discount on a surprise. A defined threshold and a defined price, agreed before the work, is worth far more than the strongest argument made after the estate has already grown past the line.
What do you ask for at the table?
Ask for clear contractual language on what custom use your licensing covers, a defined threshold for any additional charge, and a price for crossing it that you agree in advance. Treat custom table licensing the same way you would treat any consumption based line: get it written down, get it priced, and make it predictable. Vagueness in the agreement always resolves toward the vendor, so the buyer interest is precision.
Then protect the commercial outcome with the same discipline you apply across the deal. Cap any uplift on the custom licensing line at 3 to 5 percent CPI indexed alongside the rest of the contract. Lock the agreed price at SKU level so a repackaging cannot reset it mid term. Secure the right to reduce or retire custom builds and have the licensing follow, so decommissioning an old application actually lowers the bill rather than leaving a stranded charge.
The expensive custom table is the one nobody priced before it was built. Define coverage, threshold, and price up front, and the licensing line stops being a surprise.
What does this look like in practice?
Consider an indicative example. A buyer approaching renewal discovers that platform teams have built a sizeable custom application on the Now Platform over the past two years, well beyond a few supporting tables. The vendor raises the custom application as a separately licensable workload, with a charge attached, and the buyer is hearing about the commercial implication for the first time.
Rather than negotiate from the back foot, the buyer inventories every custom build, maps each against the agreement wording, and separates genuine large applications from light extensions. They agree a clear threshold and a fixed price for the application that crosses it, decline charges on builds that fall within existing licensing, and set governance so any future build with a licensing implication is approved deliberately. They cap uplift at CPI and lock the price. In this indicative example the custom line becomes a known, bounded cost rather than an open ended renewal surprise.
Your next step
Custom table licensing sits alongside seat discipline as the two big ServiceNow levers. For the full method, read the SaaS Negotiation Guide, and for the commercial page on this vendor see ServiceNow negotiation. To control the seat count that drives the bill, read Fulfiller License Discipline, and for the levers in any deal, see The Discount Levers in Every SaaS Deal.
Download guide: SaaS Negotiation Guide, or take the full tactic library in The Vendor Tactics Field Guide.
Common questions
What is a custom table on ServiceNow?
Why do custom tables create a licensing line?
How do I control custom table licensing?
Last reviewed March 2026. Market figures cited are published industry data; figures labelled indicative are directional.