Case study
Self-Service Tagging App for FinOps Accuracy
How SquareShift built a self-service tagging portal that standardized product, project, subscription, and account metadata for accurate FinOps reporting.
A global semiconductor and enterprise software company was flying blind on its own cloud spend.
It ran cloud infrastructure across multiple business units on manual tagging with no shared system of record, so it needed a self-service way for business units to tag their own resources and trust the numbers.
Tags standardized through self-service tagging. Product metadata entries centralized in one portal. Replaced manual, ad hoc tagging across business units.
Key servicesHow SquareShift delivered it.
The challenge
A global semiconductor and enterprise software company ran large-scale cloud infrastructure and metadata systems across multiple business units — and FinOps governance ran on manual tagging. Every business unit tagged its own products, projects, subscriptions, and accounts by hand, with no shared system of record.
That gap showed up downstream: FinOps reports were only as accurate as the last manual tagging pass, and integration issues across platforms made the numbers hard to trust.
What we delivered
SquareShift built a self-service FinOps portal so business units tag their own products, projects, subscriptions, and accounts directly, with approval workflows keeping every change governed instead of ad hoc.
The portal integrates through APIs and Google Cloud Functions, with automated syncs to connected systems like Klera, so metadata updates propagate without a manual re-entry step.
The payoff
The portal is now the system of record for FinOps tagging: it holds 3,000+ product metadata entries and 17,000+ tags, entered and maintained by the business units that own them.
Automated syncs keep FinOps reporting fed by current tags instead of a stale manual export — closing the accuracy gap that started this engagement.
Tagging accuracy never comes from a policy memo — it comes from self-service workflows with an approval step, so business units govern their tags instead of chasing them down.
Data Engineering Practice Lead, SquareShift
Where this work sits