Cloud & Enterprise IT
Cloud Cost Management
Visibility and controls for cloud spending, aligned to budgets and fiscal years.
What this covers
Cloud bills grow quietly. Idle resources, oversized instances, unattached storage, and untagged experiments add up. HQT establishes the practices, often called FinOps, that keep spending visible and tied to the departments that incur it.
Typical activities
- Tagging standards and enforcement so every resource maps to a department or program
- Budgets, alerts, and monthly reporting by cost center
- Rightsizing and scheduling of non-production environments
- Reserved capacity and savings plan analysis
- Storage tiering and lifecycle policies
- Chargeback or showback models suited to public-sector accounting
What you receive
A cost management framework, dashboards, a savings backlog with estimated impact, and a monthly review cadence agency finance staff can run.
Considerations for public agencies
Public budgets are appropriated annually and often cannot absorb variable monthly bills without controls. We design reporting that fits budget cycles and supports encumbrance and grant accounting.
Signals to check before scoping this work
Each of these can be checked against your own invoice and console, without a benchmark or an industry average.
- The monthly invoice arrives as a handful of summary lines, and attributing it to departments, programs, or grants takes a manual spreadsheet.
- Spending is tracking above the appropriated line item, and variances get explained after the close rather than forecast before it.
- A migration finished and environments are still sized for cutover rather than steady-state operation.
- Data transfer, logging, backup, and snapshot charges appear on the bill and no one can account for what generates them.
- Reserved capacity or savings plans are in place, but no one owns the renewal and expiration dates.
- A grant-funded workload shares infrastructure with general-fund workloads, with no written basis for splitting the cost.
- Finance asks what a named system costs to run, and the answer has to be rebuilt by hand from the console each time.
What a sound implementation looks like, and how a weak one shows
A sound implementation settles allocation when a resource is created rather than reconstructing it after the fact: resources without an owner fail provisioning or land in a holding account someone is accountable for. Forecasts arrive on a schedule finance can reconcile against fund, organization, and object codes in the accounting system. Each savings item names an owner, an effort estimate, a performance risk, and the invoice line where the saving should appear. Commitment purchases carry recorded terms, utilization, expiration dates, and a written reason the capacity was bought.
Weak implementations have recognizable symptoms. Dashboards run under credentials only the vendor holds. Savings are counted against public list rates rather than the effective rates the agency actually pays. A cleanup runs with no guardrail behind it, so the same idle volumes and orphaned snapshots reappear as new work is built. Rightsizing is done from average utilization without asking program staff about peak periods such as tax deadlines, open enrollment, or elections. An allocation formula is published that no department accepts, and it degrades into a report nobody opens. Tagging rules are written but never enforced in templates or pipelines.
What to specify when you procure this work
- Require the provider's detailed billing export at resource and hourly granularity, delivered into storage the agency owns, so the underlying data outlives the engagement.
- State that the engagement does not change your reseller or partner of record. Cost work should not become an argument for moving a billing relationship, particularly where your rates come through a cooperative or statewide agreement.
- Define the savings baseline in writing: effective rates after existing discounts, a stated measurement window, and evidence taken from invoices rather than from a tool's projection.
- Treat percentage-of-savings compensation carefully. If you use it, cap it, define the baseline precisely, and set an end date, since it creates pressure toward reductions program staff never agreed to.
- Require the allocation method and its supporting data to be documented well enough for an auditor or a grants office to follow a charge back to the bill it came from.
Measuring whether it worked
Agree on the measures before the work starts. Useful ones include the share of spend attributable to a department, program, or fund; forecast accuracy, meaning month-end actual against the prior forecast, watched over several cycles; savings visible on an invoice, tracked separately from savings merely identified; commitment coverage and utilization; and how long it takes to answer a routine cost question from a department head. Where the workload supports it, a unit measure such as cost per case, per permit, or per transaction says more than the total does. One caution on targets: in a growing environment this work often bends the growth curve rather than cutting the absolute bill, so judge the result against what the workloads were asked to carry, not against last year's total alone.
Working with HQT on this
HQT scopes this kind of work as a fixed-price or time-and-materials engagement with a written statement of work, named staff, and a defined acceptance process. We are candid about what we can take on and prefer a well-run project to an oversized one. Contact us to discuss a requirement, a draft scope, or an upcoming solicitation.
Frequently asked questions
What is the difference between cloud cost management and a one-time cleanup of unused resources?
A cleanup removes waste that already exists and is finished when the resources are deleted. Cost management is the standing arrangement that decides who owns a cost before it is incurred and who reviews it after, so idle volumes, oversized instances, and forgotten snapshots do not quietly accumulate again as new projects are built. The difference shows up on later invoices rather than the next one, which is why a cleanup with no ownership behind it tends to drift back toward where it started.
Can we commit to reserved instances or savings plans if our budget is appropriated one year at a time?
Often yes, though the structure matters more than the headline discount. Providers commonly offer one-year and three-year commitment terms, with payment options ranging from all upfront to monthly with no prepayment, so a one-year commitment paid monthly produces a level charge that sits inside an annual appropriation more comfortably than a large prepayment does. Whether a longer commitment counts as a multi-year obligation under your charter, code, or non-appropriation rules is a question for your finance office and counsel before the purchase, not after it.
Should we use chargeback or showback for cloud costs?
Showback reports each department's share without moving money, and it is usually the place to start, because the numbers have to be trusted before anyone will pay against them. Chargeback also needs a billing mechanism your finance structure already supports, such as an internal service fund or an interdepartmental transfer, along with a published rate method and a way to dispute a charge. If a department cannot reproduce its own number from the report it receives, chargeback tends to generate appeals rather than changes in behavior.
Do we need a third-party cloud cost tool, or are the native tools enough?
The major cloud providers include cost analysis views and a detailed billing or usage export, and for a single provider with consistent tagging those are often enough. Third-party platforms tend to be worth their license when you run more than one provider, need allocation logic the native tools cannot express, or want reporting shaped to your fund and object codes. Whichever you choose, keep the raw billing export flowing into storage your agency controls, so your cost history does not live only inside a tool you may later replace.
How do we allocate shared cloud costs to grant-funded programs?
Direct-charge what can be attributed to a single program, then allocate the shared remainder on a written basis you apply consistently, such as measured usage, user counts, or storage consumed. Decide the method before the period you are charging for, apply it the same way across programs and periods, and keep the billing data that supports it. Where federal awards are involved, the cost principles in 2 CFR Part 200 generally require a cost charged to an award to be allocable to that award and adequately documented, so settle the approach with your grants and finance staff rather than inside the IT shop.