Skip to content
Notifications
Clear all

Procurement asking: Real-world annual upkeep costs beyond the license?

5 Posts
5 Users
0 Reactions
61 Views
(@chloem)
Reputable Member
Joined: 4 months ago
Posts: 231
Topic starter   [#22184]

Our security team is pushing hard for a ThreatConnect PO, and procurement has come back with a tough but fair question: "What's the real annual cost of ownership *after* the initial license fee?" They want to budget for upkeep, not just the sticker price.

I'm helping to build the business case, and I know from our marketing automation platforms that the SaaS subscription is often just the entry ticket. I'm particularly curious about the ongoing resource investment.

Based on your experience, what are the tangible, recurring costs we should factor in? I'm thinking along these lines:

* **Essential Staffing:** How many FTE hours per week are needed for routine maintenance, playbook updates, and indicator management? Is a dedicated analyst realistic, or is it more of a shared duty?
* **Integration & Data Pipelines:** Costs for ongoing maintenance of feeds (like TI feeds, SIEM, EDR). Are there often consulting fees for custom integration work post-implementation?
* **Training & Certification:** Is annual re-training or new analyst onboarding a significant line item? Do you find value in the paid training vs. building your own internal program?
* **Infrastructure & Overhead:** If on-prem or private cloud, what are the typical annual costs for hosting, scaling, and security compliance? Any surprises with data storage growth?

We're trying to avoid the classic trap of a tool that becomes a cost center because we underfunded its operation. Any insight into what proportion of Year 1 costs tend to repeat annually would be incredibly helpful.



   
Quote
(@crm_hopper)
Honorable Member
Joined: 8 months ago
Posts: 472
 

Procurement's asking the only smart question in the room. With CRMs, the license is just your entry fee to a world of hidden costs.

For staffing, a dedicated analyst is a fantasy. It'll be a shared duty that somehow consumes 20 hours a week of your team's time just for basic upkeep and indicator management. Playbook updates? That's a part-time job masquerading as a "weekly task."

Integration maintenance is a consulting fee bonanza. Every TI feed or SIEM connection that hiccups means another call to a partner, and those hours stack up fast by the end of the year.

Paid training is usually a racket. Building your own program saves cash but costs you in elbow grease and ramping up new hires. The real annual cost is the morale hit from maintaining another clunky platform.


CRM is a necessary evil


   
ReplyQuote
(@ci_cd_plumber)
Honorable Member
Joined: 7 months ago
Posts: 512
 

You're on the right track, but missing the biggest hidden cost: data storage and egress if you're running on-prem or in a private cloud. Those telemetry and log volumes will balloon and you'll pay for it every month.

On staffing, a dedicated FTE is overkill. It's a shared duty that will consume 15-20 hours weekly across two people for reliable coverage. If you treat it as an "as needed" task, the platform decays and your initial investment is wasted.

For training, skip the vendor's annual recertification unless it's mandated. Build a runbook and internal demo instance instead. The real cost is the friction every time someone new needs to touch it.


Build once, deploy everywhere


   
ReplyQuote
(@cost_optimizer_88)
Reputable Member
Joined: 7 months ago
Posts: 372
 

Everyone's fixating on staff hours and training, but they're missing the infrastructure elephant in the room, especially if you're on the "bring your own cloud" plan. Your *Infrastructure & Overhead* line is where budgets silently hemorrhage.

The license fee gets you the software. Then you pay your cloud provider for the compute to run it, the storage for the exploding log and indicator volumes, and the data egress every time you query an external feed or sync with your SIEM. This isn't a flat fee, it scales directly with usage. If your threat intel feed starts pumping out more data, your AWS or Azure bill feels it immediately. Call it a "success tax."

Building your own internal training program is smart, but you'll need a dedicated sandbox instance to do it. That's another full dev/staging environment running 24/7, duplicating all those compute and storage costs. It's never just the license.


pay for what you use, not what you reserve


   
ReplyQuote
(@cloud_ops_amy_2)
Reputable Member
Joined: 9 months ago
Posts: 274
 

Good call on the sandbox for training, that's a non-negotiable. The friction cost is real, but I've seen teams skip it to save on dev environment compute, which just pushes the cost into slower incident response later.

On the storage and egress point, you're spot on. The scaling isn't linear, it's more like a step function. Once you cross a throughput tier in your cloud account, the unit cost for egress can jump. It's easy to model flat data growth and miss that cliff.

Your 15-20 shared hours is the right ballpark in my experience, but that assumes your team already has the context. If they're learning from scratch, double that for the first quarter.


terraform and chill


   
ReplyQuote