What belongs in a revenue tech stack inventory?

Every system touching revenue data, including the spreadsheets that function as systems. If something drives routing, forecasting or reporting, it is infrastructure regardless of what it is built in.

How do you decide what to consolidate?

Not by count. Look for two tools in one category holding the same data, tools with no named administrator, and tools whose cost exceeds their use. Overlap is a data-consistency problem before it is a cost problem.

What is the most common tech stack failure?

Not too many tools — unowned ones. A system with no named administrator will not be configured deliberately, patched, or reviewed, and nobody will notice when it breaks.

How often should the stack be audited?

Annually, and after any acquisition or major system change. The list drifts continuously because adding a tool is easy and removing one requires knowing what depends on it.

Tech Stack

The set of systems a revenue team operates, and — more importantly — how they relate to each other.

What actually matters about it

Not how many tools there are. Three questions decide whether a stack is manageable: which system is authoritative for each object, who can change each system's configuration, and what happens when a connection between them fails.

Include the spreadsheets

A shared sheet driving routing, forecasting or commission is infrastructure. Treating it as a document is why it has no owner, no backup and no change control — and why it is usually the most fragile thing in the stack.

Building the inventory

Get the list from finance, not from memory. Card statements and vendor invoices find the tools nobody mentions, which are exactly the unowned ones.
Record a named administrator for each — the person who can change configuration. Blanks here are the finding.
Record cost, user count and contract term, so renewal decisions are made before auto-renewal rather than after.
Record the number of integrations. A heavily connected tool cannot be removed without work regardless of how little it is used.

What the inventory reliably surfaces

Tools with no administrator — unmanaged spend and unmanaged risk in one row.
Two systems in one category, which means the same data exists twice with no stated authority.
Annual contracts with low utilisation, discoverable only before the renewal date.
The gap between total tooling cost and what leadership believes it is — usually the finding that gets the audit taken seriously.

RELATED TERMS

Systems of Record

The set of systems that each hold authoritative data for part of the business, and the map of which owns what. The architectural decision underneath every reporting question.

Revenue Architecture

The deliberate design of how offerings, motions, systems and data fit together to produce revenue — as opposed to the arrangement that accumulated by default.

Integration Layer

The connections moving data between systems, and the rules governing direction, timing and conflict.

Single Source of Truth (SSOT)

The declared authority for a given piece of data — the system whose value wins when two systems disagree. Correctly applied it is decided per field, not per system.

COMMON QUESTIONS

What belongs in a revenue tech stack inventory?: Every system touching revenue data, including the spreadsheets that function as systems. If something drives routing, forecasting or reporting, it is infrastructure regardless of what it is built in.
How do you decide what to consolidate?: Not by count. Look for two tools in one category holding the same data, tools with no named administrator, and tools whose cost exceeds their use. Overlap is a data-consistency problem before it is a cost problem.
What is the most common tech stack failure?: Not too many tools — unowned ones. A system with no named administrator will not be configured deliberately, patched, or reviewed, and nobody will notice when it breaks.
How often should the stack be audited?: Annually, and after any acquisition or major system change. The list drifts continuously because adding a tool is easy and removing one requires knowing what depends on it.

Learn how to apply this: CRM Admin 101

Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.

See the course