Revenue tech stack
The revenue tech stack is the set of systems the revenue process runs on, and more importantly the integration topology connecting them.
The tool list is the least interesting part. What determines whether the stack works is the topology: which system is authoritative for each entity, which direction each sync runs, and where transformation happens. Two companies with identical tool lists can have completely different reliability depending on those answers.
Accumulated tools and bidirectional syncs can make field history difficult to explain. The response is not consolidation for its own sake: state authority by decision scope, preserve legitimate snapshots and derived copies, and make every write path observable.
Where it breaks
Four systems bidirectionally sync the same field and the last writer wins nondeterministically.
Related terms
- System of record
- A system of record is the designated authoritative source for a given entity or field, the one place where, if two systems disagree, this one is right.
- Revenue data model
- The revenue data model is the set of objects, relationships and required fields that every revenue-facing process reads from and writes to.
- Single source of truth
- A source-of-truth designation names the authority for one object, field, event, artifact, role, or decision within a stated scope and effective period.
- Change control
- Change control is the governed process for proposing, reviewing, releasing and recording modifications to the revenue system, its fields, definitions, automations and stage criteria.
Field notes on this
- You just inherited RevOps. Start with a charter.
Being told to "own revenue operations" is not a mandate. Until authority is written down, every decision you make is reversible by whoever objects loudest.
- Why four teams report four different revenue numbers
A reconciliation problem may be definitional, technical, or both. Test the metric contract before buying another data platform.