Per-Asset Pricing Traps

Most SMB tools are priced in a way that looks reasonable when you sign up and punishing by year three.

The pattern goes by many names — per-seat, per-asset, per-check, per-integration, per-endpoint — but the shape is the same: you pay more as you use the tool more. Which sounds fair. Until you realise the tool you use more is the tool you bought because it worked, and you're being penalised for the outcome the vendor was hoping for.

This isn't always predatory. Sometimes per-asset pricing is the only structure that makes sense for a vendor's cost base. But it's worth understanding when you're walking into the trap and when it's actually benign.

The classic case: monitoring

Per-domain pricing in domain monitoring is the purest example. A tool charges $5/month per monitored domain. At 3 domains you're paying $15/month — completely fine. By the time you're at 30 domains (which happens faster than people expect), you're paying $150/month for what is, architecturally, the same service.

We've written the indignant version of this argument in per-domain pricing is a scam. The broader version is that the same dynamic plays out across almost every category of SMB tooling.

Where per-asset pricing bites

It's not always obvious at sign-up. Some things to watch for:

Per-seat tools you'll hire into. A team-collaboration tool at $10/seat is reasonable for 5 people. For 25, you're paying $250/month and the tool isn't 5x more valuable. It's the same tool. You just have more mouths using it.

Per-check monitoring. Tools that charge per "check" or per "probe" penalise you for having checks at short intervals or on more services. You end up making architectural decisions (fewer checks? longer intervals?) to control the bill, which defeats the point of the tool.

Per-integration automation. Workflow tools that charge per external connector. By the time your business is integrated with your CRM, your billing system, your email provider, your analytics, and your internal tools, the integration count is 20+. At $20/integration/month, you're paying more for the plumbing than for the tool.

Per-endpoint security. Endpoint protection priced per device. Fine when you have 10 laptops. Less fine when you have 40 plus a bring-your-own-device policy that nobody's tracking carefully.

Per-seat on tools most people rarely open. This is a favourite. A tool everyone technically needs access to but uses maybe once a month. You're paying the seat cost on people who'd struggle to tell you what the tool does.

The sign-up math vs. the long-run math

Per-asset pricing almost always looks good at the low end. Vendors aren't stupid — they set the unit price to feel cheap for the customer they're acquiring today.

The trap is that you're usually not evaluating the price you'll pay. You're evaluating today's bill. You adopt a tool at 3 assets for $30/month and think "great, I'll save that as an expense." Two years later you have 30 assets and a $300/month bill, and the switching cost is high because the tool is wired into your workflow.

The discipline is to run the math at 3x and 10x your current scale before signing up. If the bill at 3x scale is something you'd grit your teeth through, but 10x scale is genuinely painful, consider a flat-rate alternative even if it's more expensive today.

When per-asset pricing is actually fair

To be fair to vendors: some categories really do scale cost linearly with usage.

Outbound communications. Email sending, SMS, physical mail. The vendor's cost per message is real; charging per message makes sense.

Transactional processing. Payment gateways, bank transfers, identity verification calls. Real per-unit cost downstream.

Heavy compute or storage. Video processing, large data analytics, CDN bandwidth. Genuinely resource-intensive.

In these categories, per-asset pricing is honest. The vendor isn't inventing a billing dimension — they're passing through actual unit cost.

Per-asset pricing becomes predatory when the vendor's underlying cost is largely flat but the pricing is variable. Domain monitoring is the archetypal example. Checking 100 domains is not meaningfully more expensive for the vendor than checking 10. The per-domain price exists because it's a good way to extract value from growing customers, not because it reflects cost.

How to evaluate a pricing page

A few questions that tell you what you're looking at:

1. Does the vendor's cost scale linearly with the billing dimension? If not, the pricing is extractive rather than reflective.
2. What happens at 10x? Not 2x. Ten times your current usage. If the answer makes you wince, that's your real price.
3. Is there a flat-rate alternative in the category? Often there is, and the flat-rate tool is cheaper at anything beyond the smallest scale.
4. Can you negotiate off the per-unit structure? Enterprise sales will often flat-rate a customer at high volume. SMBs rarely ask; they just absorb the bill.

Switching costs are real

The reason per-asset pricing works as a trap is that switching later is expensive. You've integrated the tool. Your team knows it. Your runbooks reference it. Moving to a flat-rate competitor requires time and risk.

Which is why catching this at evaluation matters. Signing up for a per-asset tool when a flat-rate alternative exists in the same category is a decision to pay more later in exchange for slightly lower cost today.

This connects to the broader question of monitoring on the cheap versus DIY. Flat-rate vendors often sit in the middle of that spectrum — not free, not enterprise, but structurally aligned with the economics of a growing small business. They're the ones you want in your stack because their pricing doesn't punish your growth.

The pillar view

The complete guide to boring IT for SMBs treats pricing traps as one of a handful of structural forces that determine whether ops spend stays reasonable as the business grows. This piece is the deep dive. The short principle: flat-rate for tools you'll grow into, per-use for tools whose vendor cost genuinely scales with usage, and a willingness to audit your own bill quarterly.

The tools that cost $30/month five years ago are rarely still $30/month today. The difference between a company that notices and one that doesn't is a few hours per quarter. It's one of the higher-ROI ops tasks available. Our own flat-rate pricing on Site Watcher ($39/month, unlimited targets) and Email Deliverability Checker ($39/month, unlimited domains) exists for exactly this reason — the bill doesn't scale with your success.