A quote for machine monitoring rarely lands as one number. It lands as a handful of line items, a per-machine rate, a hardware charge, sometimes an install fee, sometimes a minimum you don’t hit until you ask, and the total depends entirely on how those pieces are structured. Two vendors quoting what looks like a similar rate can land very differently once you add up what each one actually counts. This is a walk through the models you’ll run into, what each one is billing for, and what a real quote adds up to using Spall’s own pricing structure as the worked case.
Per machine pricing
This is the most common model, and the easiest to compare across vendors on its face: a monthly rate multiplied by the number of machines connected. The part worth reading closely is what counts as a machine. A control with a full data connection, cycle counts, program name, alarm state, run signal, usually costs more than a machine sensed only through a clamp or analog input reading run and stop. If a vendor quotes one flat per-machine number regardless of connection depth, ask whether a sensed-only machine is really priced the same as a fully connected CNC, because that’s an unusual thing for a rate card to ignore.
Per machine pricing also tends to step down as you add machines. A rate that holds for the first ten and drops after that rewards a real rollout, beyond a single pilot. Worth asking directly where that break sits and whether it’s automatic or something you have to negotiate into.
Per site or per plant pricing
Some vendors charge a flat rate per facility regardless of machine count, sometimes with a machine cap built in. This model favors a dense floor: fifty machines in one building cost the same as five. It disadvantages a small site, since you’re paying for capacity you may not use. It’s less common in machine monitoring specifically than in broader plant software, where the unit of value is the site’s overall operation, not a specific asset count. A monthly minimum works the same way even inside a per-machine model. It puts a floor under a very small deployment so a two-machine pilot doesn’t undercut what it costs the vendor to support it.
Per user pricing
Charging by dashboard seat is standard in general business software and uncommon in machine monitoring, for a specific reason: the value here comes from the machines being watched, not from how many people are logged in to watch them. A plant manager, three supervisors, and a maintenance lead all looking at the same floor shouldn’t cost five times what one person looking at it costs. If a vendor’s model charges per seat, ask what happens when you want to add the whole shift to a wallboard view, because a seat-based model can turn a good habit, more eyes on the same floor data, into a reason not to.
Hardware bundles
Almost every real deployment needs a physical device on the machine network, a gateway or edge box that reads the controllers and sends data out. How that gets billed varies more than the software rate does. Some vendors sell the hardware outright as a separate capital purchase. Some fold it into the monthly rate as a lease. Some charge a one-time kit price that includes the install labor for that device, which is the cleaner model to compare against, because it tells you up front what getting a gateway physically working costs, once, instead of spreading an ambiguous markup across years of subscription.
Ask specifically whether the hardware price includes the labor to install it, or whether that’s billed separately by the hour or the day. A kit price with install bundled in is a single number you can compare directly against a competitor’s kit-plus-day-rate combination.
Activation and install fees
Some vendors charge a separate fee just to turn a connected device on, on top of the hardware and the monthly rate, sometimes framed as onboarding or activation. This is worth asking about explicitly and worth being suspicious of when it’s vague. A one-time fee tied to a specific deliverable, a complex install that needs an extra technician day on site because of unusual network topology or an older control, is a real cost. A flat activation fee charged on every account regardless of what work it represents is closer to a second subscription fee wearing a different name. Ask what the fee buys, specifically, before agreeing to pay it.
What Spall’s own structure looks like
Spall’s rate card follows the same shape. The current numbers are on the product page. The recurring rate is per machine, monthly, with a lower rate that kicks in once a plant crosses ten machines on the account. A machine sensed only through a clamp or analog input, instead of a full control connection, runs at its own flat monthly rate, lower than a fully connected machine. A plant-wide monthly minimum puts a floor under a very small deployment. The gateway is priced as a one-time kit that includes that gateway’s install day, with a separate day rate for any additional install work a complex site needs beyond that. Every deployment starts as a line pilot or a plant pilot, each a fixed machine and gateway count over thirty days, credited in full against the subscription if the plant continues past the trial. An annual prepay option applies a discount off the monthly total, and a larger deployment moves to quoted volume pricing above a certain machine count.
There’s no separate activation fee anywhere in that structure. The gateway kit price already covers the install day for that gateway, and because every deployment starts as a credited pilot, the hardware cost spent finding out whether the system works becomes part of what a plant would have paid anyway if it continues. The current numbers behind each of these line items are published on the pricing section of /product/, the one place they’re kept up to date, not restated here where they’d eventually drift out of sync.
The four numbers to add up for any quote
Whatever vendor you’re evaluating, the total cost of a real deployment comes down to four things, and a quote that’s hard to compare usually has one of them buried. First, the recurring rate, per machine, per site, or per user, multiplied by your actual count, not a rounded estimate. Second, the hardware cost, whether it’s upfront, amortized, or bundled, and whether install labor rides along with it or shows up as its own line. Third, any one-time fee outside the hardware, activation, onboarding, training, and specifically what deliverable it’s tied to. Fourth, any minimum or floor that applies regardless of count, which matters most for a small deployment that might otherwise look cheaper than it turns out to be.
Add those four together for a twelve-month projection, not a monthly snapshot, because a low monthly rate with a heavy one-time fee reads very differently over a year than the same math spread the other way. A vendor who can hand you those four numbers cleanly, without you having to extract them from a sales call, is telling you something about how they price. A vendor who can’t is asking you to trust a total you can’t actually verify.
Quick recap
- Per machine pricing is the most common model, watch what counts as a machine and where the rate steps down
- Per site pricing favors a dense floor and costs a small site more per machine actually watched
- Per user pricing is rare in this category for a reason, the value is the machines, not the headcount viewing them
- Hardware can be billed outright, leased into the subscription, or bundled as a kit price with install included, ask which
- A one-time activation fee should be tied to a specific deliverable, not charged as a second subscription in disguise
- Add up the recurring rate, hardware, one-time fees, and any minimum over twelve months before comparing two quotes