Skip to content
Notifications
Clear all

Check out my ugly but effective spreadsheet for GRC implementation cost tracking.

4 Posts
4 Users
0 Reactions
55 Views
(@karina23)
Estimable Member
Joined: 4 months ago
Posts: 50
Topic starter   [#8065]

Hello everyone,

I’ve been lurking here for a while, reading through all the fantastic threads on implementation timelines and vendor evaluations. As someone who handles IT procurement, I’ve been tasked with helping to oversee the financial side of our upcoming ServiceNow GRC implementation. One thing I kept hitting my head against was getting a clear, unified view of all the costs—not just the obvious license fees.

Everyone talks about TCO, but when I asked our implementation partner and internal teams for a consolidated view, everything came in different formats: slides, emails, rough estimates in meetings. I needed a single source of truth to track everything against budget, so I built a spreadsheet.

It’s not pretty—I’m no UX designer—but it’s been incredibly effective for me. I wanted to share my structure to get your feedback and see if I’m missing any major cost buckets that could come back to haunt us later.

My core philosophy was to track costs by phase and by cost type, and to separate one-time from recurring expenses. Here’s the basic layout:

**Sheet 1: Implementation Phase (One-Time Costs)**
* Partner Professional Services (broken down by Discovery, Design, Configuration, Testing, Deployment)
* Internal Resource Costs (FTE allocation for our project team, calculated at a burdened rate)
* Training & Enablement (developer training, admin training, end-user training materials)
* Environment Setup Fees (any dev/test/prod setup charges from ServiceNow or the partner)
* Initial Data Migration & Integration (cost for any tools or extra services to load initial data)

**Sheet 2: Annual Recurring Costs**
* ServiceNow GRC Subscription Fees (by production instance, broken down per module if possible)
* Partner Support & Maintenance Retainer (if applicable)
* Internal Admin & Support FTE (ongoing burdened cost for our team)
* Annual Training Refresh / New Hire Training
* Community & Support Portal Fees (any premium support plans)

**Sheet 3: "Hidden" or Often-Forgotten Cost Buckets**
* Security & Compliance Reviews (cost of internal audit or security team time to vet the platform)
* Change Management & Communications (creating guides, running sessions)
* Contingency Buffer (I have a column for this, currently set at 15% of total implementation)
* Exit Strategy Considerations (data extraction cost estimates, contract termination clauses analysis)

For each line item, I have columns for:
* Vendor/Internal
* Budgeted Amount
* Committed Amount (from SOW/contract)
* Actual Spent (updated monthly)
* Variance
* Notes (with links to contract sections or SOWs)

My big questions for the community, based on your experiences:
* What cost categories did you overlook initially that showed up later?
* How did you handle tracking the internal FTE costs? Did you use fully burdened rates or just salary?
* For those who have gone through a renewal, were there any cost elements that spiked unexpectedly that I should build into my recurring sheet?
* Has anyone built a similar tool and found a better way to visualize the data for stakeholders?

I’m particularly paranoid about missing something that would affect the long-term TCO or complicate an exit strategy later. Any insights from your own vendor evaluations and contract negotiations would be invaluable.



   
Quote
(@danm)
Honorable Member
Joined: 4 months ago
Posts: 452
 

Totally get the need for a single source of truth, I do the same thing for project tracking. Your sheet structure sounds solid. One cost bucket I almost missed in a past project was the internal team's time for training and UAT - not just the partner's training delivery. It can blow out if you don't track those hours.

Would you also track any potential costs for custom integrations? I've seen those creep in mid-project when a team realizes they need a specific data feed into GRC.

You mentioned a Sheet 2 for recurring costs - is that where you're handling stuff like annual license increases and internal admin support?



   
ReplyQuote
(@kubernetes_tinker_99)
Estimable Member
Joined: 8 months ago
Posts: 56
 

Love the phase-by-phase breakdown, that's smart. A cost bucket I'd add to your one-time sheet is "platform readiness." If you're deploying to a private cloud or a locked-down VPC, you often need extra networking, security groups, or even a new Kubernetes cluster just to host the platform. Those infra costs can be sneaky and often fall outside the partner's SOW.

On the recurring side, don't forget about the cost of *maintaining* custom integrations. Every time ServiceNow or the source system does a major update, someone's gotta test that data feed. That's usually an internal team's time, and it adds up year over year.

Could you share a sanitized screenshot of the structure? Always looking to steal good ideas for my own tracking sheets 😄


#k8s


   
ReplyQuote
(@auditlog)
Honorable Member
Joined: 7 months ago
Posts: 454
 

The phase-by-phase breakdown is a great start. I always push to map those phases directly to the vendor's statement of work. If your SOW has a line for "Phase 2 - Build & Test," you need a matching line in your sheet. That's how you catch scope drift early, when the partner's weekly status report shows hours being logged against a task that wasn't in the original cost column.

One thing I'd add to Sheet 1 is a column for cost classification, separate from the phase. Was it capital expenditure or operational expense? It doesn't change the total, but getting that wrong during booking can create a huge mess for the finance team and auditors later, especially for those platform readiness items user380 mentioned.


Logs don't lie.


   
ReplyQuote