Home › Topics › Monitoring Licensing Models and Hidden Costs › Hidden-Costs Checklist

The Hidden-Costs Checklist


The first monitoring quote I signed off said one number. The purchase order said the same number. For about a month I believed that was the cost. Then the other numbers arrived. A module I had assumed was included. A support renewal nobody had mentioned. A database that turned out to need its own license, a consultant for the setup, and a second login for my colleague. None of them were secret. Every one was somewhere in the paperwork, or in the documentation, or in a sentence a salesperson had said in passing while I was watching the demo. They were hidden only in the sense that nobody had a list.


This guide is that list. It walks through the costs that commonly appear after signature for monitoring software. It explains where each one tends to hide in a quote. It gives you the question that surfaces it. And it puts the whole thing into a checklist table you can take to your next quote. You will also learn how to read a quote line by line, which is a small skill that pays for itself the first time you use it.


This is not a guide to estimating the cost of monitoring. The worksheet for that already exists in the total cost of ownership guide, and this checklist feeds into it. Nor is any item here a vendor being sneaky. Modular products have modular pricing, and a quote answers the question it was asked. The failure is on the buyer's side when nobody asks, and the fix is simply to ask.


In this guide

  • Why costs hide
  • The software lines you did not see
  • The recurring lines
  • The people lines and the infrastructure lines
  • Where each item hides in a quote
  • When each cost first appears
  • Asking the questions well
  • The checklist table
  • Reading a quote line by line

Why costs hide


A quote is written to answer the question the buyer asked. If you asked "how much for monitoring a hundred devices?", the quote answers that and nothing else. The items you did not ask about are not in it. And the absence of a line is not the same as the item being free. This is the first rule of reading quotes: "not mentioned" is not "included."


The second reason is time. A quote is a snapshot of the first purchase. Costs that begin later are naturally outside the snapshot. These include the renewal of support and the storage the database will need after a year of history. They also include the upgrade project when the next major version arrives. The third reason is the word optional. Many quotes have a section of optional lines, and optional means "you can decline this," which is true. But it does not mean "you will not need this." Probes for your second site are optional in the same way that a second shoe is optional.


Once you accept those three reasons, the hiding places become predictable, and predictable is all a checklist needs.


The software lines you did not see


Add-on modules

Monitoring products are built from modules, and the base license usually covers device health: up/down, interface status, CPU, memory, disk. The features that impressed you in the demo are often separate. They include flow analysis (who is using the bandwidth), and configuration management (backing up and comparing device configs). They also include advanced reporting (scheduled and customizable reports), network maps beyond the basic auto-generated view, and application and log monitoring. Another is an API (application programming interface, the doorway other programs use to talk to the tool) for automation. Each may be an edition feature, a module with its own unit count, or simply included. The demo does not tell you which. Ask: "For each feature we saw, is it in the edition quoted, a separate module, or not available?" Then keep the answer.


Probe and collector licenses

A probe (or collector, or remote poller) is the piece of the monitoring system that lives at another site or segment. The central server is quoted; the probes for the warehouse, the branch, and the isolated lab network may not be. A quote tends to cover the building the salesperson visited. Some products include a number of probes, some license them individually, and some count each as a device. Ask: "How many sites and segments will we need probes for, and how are probes licensed?"


High-availability licenses

If you want the monitoring system itself to survive a server failure, you may need a second server instance. The second instance may need its own license, a special "standby" license, or a clustering feature that is only present in a higher edition. Ask: "If we run a redundant pair, what do we need to license for the second node?"


The second admin seat, and the seats you forgot

Some products license console users. The quote may include one administrator. You will want at least two. Nobody should be the only person who can log into the monitoring system. You will also want read-only access for the help desk, plus perhaps an account for the wall display and one for an integration. Ask: "How many named or concurrent users are included, and how are read-only and service accounts counted?"


The recurring lines


Maintenance and support as a separate line

With a perpetual license (bought once, used indefinitely), the software is paid for once and maintenance (updates plus support) is bought per term. A first-purchase quote may include the first term of maintenance in the headline, may list it separately, or may leave it for the renewal quote. Support also comes in tiers: business hours versus around the clock, email versus phone, response-time commitments. The tier quoted is not always the tier you assumed. Ask: "Is maintenance included in this quote, for how long, at which support tier, and what does the renewal look like?" With a subscription, the same question becomes: "Which support tier is included in the subscription?"


Database licensing for a commercial backend

Every monitoring tool stores its history somewhere. Some ship with a built-in database. Some use an open-source engine. Some require, or perform much better with, a commercial database engine that is licensed separately. That license is from the vendor of that database, not the vendor of the monitoring tool. A monitoring quote will not include a database it does not sell. Free-of-charge editions of commercial databases often have size or performance limits that a monitoring workload can reach. Ask: "Which databases are supported, which one do you recommend for our size, and is that database included, free, or licensed separately?"


Harbourview Clinic signed for a monitoring platform whose quote carried a note reading "database engine to be provided by customer". The clinic provided the free edition of a commercial database because it was already on the server. It ran beautifully for eleven months. Then it reached its size limit on a Tuesday afternoon. From that point the history stopped being written while the live status carried on looking perfectly healthy. The database was licensed by a different vendor, on a different approval cycle. The monitoring vendor pointed out, quite correctly, that the note had been there all along. The clinic lost a month of capacity history and gained a policy. The notes are read before the summary, by two people, one of whom has to say the word "database" out loud.


Storage growth

Monitoring history grows every day. Sensors times polling frequency times retention equals disk, and disk is bought by you. The first year fits on the server you had; the second may not. This is not a license cost, but it is a cost that follows the license count. Ask: "What is the storage growth per sensor at our polling interval, and what retention does the default configuration keep?"


The people lines and the infrastructure lines


Training

Some products are learnable from the documentation; some expect a course. Training may be a line in the quote, an optional line, a separate catalog, or included with a support tier. Also count the internal cost: the hours your team will spend learning the tool are real, even if they are not on any invoice. Ask: "What training is included, and what does the vendor recommend for a team our size?"


Professional services for setup

A day or two of vendor help to install, discover, and configure the first alert rules is common for larger products. That help is sometimes required to keep the support entitlement valid. It appears as "implementation," "onboarding," "quick start," or "jump start." It may be genuinely valuable; it is still a line. Ask: "Is any implementation service required or recommended, and is it in this quote?"


Integrations

Connecting monitoring to your ticketing system, chat platform, on-call tool, or log platform may be a built-in connector, a paid connector, or a small custom project. The other side may also charge: the ticketing platform's API access may need its own license tier. Ask: "Which of our systems have built-in integrations, and which would need a module or custom work?"


Upgrade projects

Minor updates install in an afternoon. Major versions are projects: a test environment, a backup, a maintenance window, re-validation of alert rules, and sometimes a database migration. A major version arrives with a changelog, a migration guide, and occasionally a new unit of measurement. Some vendors charge for migration assistance. Some major versions change the licensing model. In that case, a renewal after an upgrade is quoted in new units. Ask: "How are major upgrades delivered, what typically changes, and has the licensing model changed across recent major versions?"


The server, the test instance, and the network

The monitoring system needs a machine to run on and a place for its probes; those are yours to provide. A test or lab instance for trying upgrades may need its own license, or may be allowed under a non-production clause. Polling traffic across WAN links (the wide area network, meaning the links between your sites) is small per sensor and not small in total. Ask: "What are the hardware requirements at our size, and is a non-production instance permitted under the license?"


Where each item hides in a quote


Quotes have a structure, and each hiding place has a habit. The summary at the top carries the headline number and is designed to be read alone; it is where "not mentioned" lives. The line items beneath it name products by SKU (a stock-keeping unit, a catalog code) and a description. Module names, probe packs, and user packs live here. So does the word "optional," often as a separate column or a separate block. The footnotes and assumptions are the most honest part of any quote and the least read. The phrases "customer to provide database," "standard support," "one-time," "per site," and "subject to master agreement" all appear here. Finally, the quote points to documents it does not contain. One is the master agreement (the legal terms, including audit and true-up rules). Another is the price list (where the next band's boundary is written). The third is the support policy (what each tier actually promises).


A useful habit is to read a quote in reverse: footnotes first, then line items, then the summary. Reading the summary last stops the headline from shaping how you read everything else. Read all of the footnotes. Yes, the one in the smaller font as well.


Tip: watch for four small words in a quote or a proposal: "available," "supported," "compatible," and "optional." Each is true and each is silent on cost. "Flow analysis is available" means it exists somewhere in the catalog. "Clustering is supported" means it works when licensed. Every time one of these words appears, add a row to your checklist and ask whether the thing is in the quote.


When each cost first appears


Hidden costs have a schedule. Some show up during installation, some at the first renewal, and some only when the network or the team changes. Knowing the schedule helps in two ways. It tells you which items to settle before signing (the ones that appear early). It also tells you which to write into the budget for later (the ones that appear at renewal or on growth). The table below is the rough order in which a small team meets them.


ItemUsually first appearsRecurs?
Database backendAt installation, or when a free edition of the database reaches its limitYes, if licensed separately
Implementation servicesAt installationNo
TrainingIn the first weeks, when the team is learning the consoleSometimes, for new staff
Admin and user seatsThe first time a colleague needs their own loginYes, with the license
IntegrationsWhen the help desk asks for alerts as ticketsDepends on the connector
Add-on modulesThe first time someone asks who is using the bandwidth, or for a config backupYes, with the license
Probes / collectorsWhen the second site or an isolated segment is addedYes, with the license
Storage growthAfter the first months of history have accumulatedYes, as retention grows
Maintenance / supportAt the first renewalYes, every term
High-availability nodeAfter the first outage of the monitoring server itselfYes, with the license
Test instance and upgrade projectAt the first major versionYes, per major version

Notice that the items at the top of this table are the ones you can settle before signing, because they are part of the first purchase. The items at the bottom are the ones that belong in next year's budget line, and the year after. A quote covers the top of the table; your checklist has to cover the bottom.


Asking the questions well


The questions in this guide work best asked together, in writing, before the quote is final. Put them in one email, numbered. And ask for the answers to be either written into the quote itself (as lines, notes, or assumptions) or attached to it. Written answers do three things that a phone call cannot. They survive the departure of the salesperson. They become part of the record you will use at renewal. And they force precision. "Flow analysis is available" on a call becomes "Flow Analysis Module, licensed per exporter, not included in this quote" on paper. That is the sentence you actually needed.


Be pleasant about it. You are not accusing anyone of hiding anything; you are doing the buyer's half of the job. And a good account manager will recognize the questions as the sign of a customer who will still be a customer in a few years. I once sent the list in the wrong tone and received the entire master agreement by return, which did, technically, answer every question. If an answer comes back vague, ask once more, more specifically. If it stays vague, note that too. How a vendor handles a list of plain questions before the sale is a fair preview of how they will handle a support case after it.


The checklist table


Take this table to every quote. The last two columns are yours to fill in. A row with "no" in the third column and "no" in the fourth is a cost you have not yet seen.


ItemAskFound in quote?Included?
Flow analysis moduleEdition feature, module, or unavailable? What unit does it count?[ ][ ]
Configuration management moduleIncluded or separate? Per device?[ ][ ]
Reporting and mapsWhich reports and map types are in the edition quoted?[ ][ ]
API and automationIncluded, gated by edition, or a module?[ ][ ]
Probes / collectorsHow many sites need one; how are they licensed?[ ][ ]
High-availability nodeWhat does the second node need?[ ][ ]
Admin and user seatsHow many included; read-only and service accounts?[ ][ ]
Maintenance / supportIncluded for how long, which tier, renewal mechanics?[ ][ ]
Database backendWhich is recommended at our size; licensed separately?[ ][ ]
Storage growthGrowth per sensor at our interval; default retention?[ ][ ]
TrainingIncluded, optional, or separate catalog?[ ][ ]
Implementation servicesRequired, recommended, or optional?[ ][ ]
IntegrationsBuilt-in, module, or custom for each of our systems?[ ][ ]
Major upgradesDelivery, migration help, licensing changes?[ ][ ]
Test / non-production instancePermitted under the license, or separate?[ ][ ]
Server hardwareRequirements at our size; whose cost?[ ][ ]

Reading a quote line by line


Here is a fictional quote, stripped of money so that only the structure remains. It is the kind of document a small team receives for a mid-size network with two sites. Read it, then read the annotations.


Line  Description                                      Qty   Unit        Term
----  -----------------------------------------------  ----  ----------  --------
1     Monitoring Platform, Standard Edition,
      band up to 250 devices                            1    license     perpetual
2     Maintenance & Support, Standard tier, initial      1    per year    1 term
3     Remote Probe                                      1    license     perpetual
4     Flow Analysis Module, up to 5 exporters (opt.)    1    license     perpetual
5     Implementation Package, 2 days remote (opt.)      1    service     one-time

Notes:
 a. Database engine to be provided by customer.
 b. Additional administrator accounts available.
 c. Pricing per current price list; subject to master agreement.

Line 1 is the headline, and it tells you three things beyond the count. One is the edition (so check which features are gated above Standard). Another is the band (so find the next band's boundary in the price list). The third is the perpetual term (so maintenance is a separate, recurring decision). Line 2 confirms that: the initial maintenance term is quoted, and the renewal is not. Ask for the renewal mechanics now, while you have leverage, rather than at the first renewal, when you have none.


Line 3 quotes one probe. You have two sites, and the central server covers one. That is correct today. If the third site opens next year, the probe is a new purchase, so note it in your growth plan. Line 4 is marked optional, which is how you learn that flow analysis is a module rather than an edition feature. You also learn that the module's unit is exporters. Five exporters covers a core and an edge at each site with one spare; count your flow-capable devices before deciding. Line 5 is the professional services line; optional here, and worth asking whether the support tier assumes the platform was implemented by the vendor.


Note a is the database line that never appears as a line. You are providing the engine, so either the built-in option is adequate for your size or you are licensing something separately. Note b is the second admin seat, phrased in the gentlest possible way. Note c points at the two documents that contain the true-up, audit, and band rules; request both before signing. In under ten minutes, a five-line quote has produced six questions, and every one of them is cheaper to ask today than to discover later.


When you have two or more quotes, resist comparing their headlines. Two headlines that differ by a probe and a support tier are not two prices for the same thing. They are two different things. First normalize them. Use the same device and sensor counts, the same term length, and the same support tier. Use the same set of modules, the same number of probes and seats, and the same assumption about who provides the database. Ask each vendor to re-quote against that common specification if their first quote does not match it. Only then do the numbers mean the same thing, and only then are they ready for the worksheet.


Where to go next


You now have the list nobody gave you: the modules, the recurring lines, the people lines, and the infrastructure lines. You also know where each hides and the question that surfaces it. Fill in the checklist for every quote. Then carry the answers into the worksheet in the total-cost guide. That puts the comparison between candidates on the whole cost rather than the headline. None of these costs was ever hidden from a buyer who asked, and you now know exactly what to ask. The next guide in Monitoring Licensing Models and Hidden Costs, Negotiating Renewals Without Being a Jerk, is where these questions turn into a professional conversation. And Tracking Licenses and Usage keeps the answers current after you sign.


Put this into practice with SysPeep Monitor

One way to shorten this checklist is to choose a tool whose quote has fewer lines to hide things in. SysPeep Monitor runs as a single Windows service. It can use a built-in database or one you already operate. It supports remote probes and high-availability clustering from the same web console. Pricing is on the site, and the free trial lets you confirm what you would actually need before anyone writes a quote.

Download Free TrialLearn About SysPeep