Growing companies add go-to-market tools one at a time: a CRM, then an email tool, an enrichment provider, a scheduler, a call recorder, a chat widget, a proposal tool, a few AI assistants. Each made sense when it was bought. Two years later, nobody has a full list, several tools do the same job, some are paid for but unused, and data moves between them in ways nobody fully understands. A tech stack audit brings this back under control. This article explains how to run one: building the inventory, checking usage and overlap, mapping data flows, and deciding what to keep, consolidate, renegotiate or remove.
Step 1: build the inventory
Start with finance, not memory. Pull every recurring software charge from card statements, accounts payable and expense reports for the last twelve months, because tools bought on individual cards are often missing from official lists. Add tools on free plans that hold company data, since they carry risk even without cost. For each tool, record the name, what it does, the owner, the team using it, the number of seats or plan tier, annual cost, renewal date, notice period and contract terms. Group tools by function, such as CRM, marketing automation, enrichment, sales engagement, conversation intelligence, scheduling, chat, analytics, customer success and billing.
Step 2: check usage
For each tool, find out how much it is actually used. Most tools have an admin view showing active users and last login. Compare active users with paid seats. Look at whether the key features are used, not just whether people log in: a sales engagement tool where nobody runs sequences, or a conversation intelligence tool where nobody reviews calls, may have users but little value. Ask the owners and a sample of users what they use the tool for and what would happen if it disappeared. Tools with low usage and no clear answer are candidates for removal.
Step 3: find overlap
Overlap is common because many tools have expanded beyond their original purpose. CRMs now include email sequences, meeting scheduling, forms, chat and basic enrichment. Marketing automation platforms include landing pages and social scheduling. Look for functions covered by two or more tools: two enrichment providers, a separate scheduler when the CRM has one, a standalone form tool alongside the CRM's forms. For each overlap, compare the capability actually needed, not the full feature list. Often the built-in feature in a core platform is good enough and removes an integration as well as a licence.
Step 4: map data flows
Draw how data moves between tools: which system creates a contact, which updates it, where activities are logged, where lead source is set, and which system is the source of truth for each type of data. Note every integration and whether it is native, middleware-based or custom code, and who maintains it. Broken or duplicated data flows cause many reporting problems: two tools writing different values to the same field, a sync that silently stopped, or enrichment overwriting data entered by reps. Mapping the flows often reveals the real cause of reporting disputes.
Step 5: check ownership and security
For each tool, confirm that the company owns the account rather than a former employee or agency, that someone current is an administrator, and that access is removed when people leave. Check which tools hold personal data of customers and prospects, where that data is stored, and whether the vendor's terms meet your data protection obligations, including India's Digital Personal Data Protection Act where it applies. Tools that nobody owns and that hold personal data are a risk even if they cost nothing.
The audit sheet
Use one row per tool. The decision column is the output of the audit.
| Column | What to record |
|---|---|
| Tool and function | Name and the job it does |
| Owner and users | Accountable owner, teams, active users vs paid seats |
| Cost and contract | Annual cost, renewal date, notice period, tier |
| Usage of key features | Which features are used and how often |
| Overlap | Other tools covering the same function |
| Integrations | Systems it reads from and writes to, and how |
| Data and security | Personal data held, admin, account ownership |
| Decision | Keep, consolidate, renegotiate or remove, with date |
Making decisions
For each tool, choose one of four outcomes. Keep: well used, clear value, no better alternative in the stack. Consolidate: the function is covered adequately by a core platform, so migrate and remove the tool. Renegotiate: valuable but over-licensed or on the wrong tier, so reduce seats or change plan at renewal. Remove: little use and no clear value. Put renewal dates on a calendar with reminders well before the notice period, because most savings depend on acting before auto-renewal. Plan migrations carefully, especially where historical data matters, and communicate changes to users with a date and a replacement.
Keeping the stack healthy
After the audit, keep the inventory as a living document owned by RevOps. Agree a simple rule for new tools: before purchase, the requester checks whether an existing tool covers the need, names an owner, confirms how it will integrate and where its data will live, and adds it to the inventory. Review the inventory before each major renewal and run a full audit annually. The tech stack duplication inspector on this site gives a quick first view of where overlap is likely.
Running the audit as a project
An audit for a growing company usually takes a few weeks of part-time effort, and it goes faster with a clear owner and a fixed timeline. In the first week, RevOps builds the inventory from finance records and sends a short questionnaire to each tool owner about purpose, usage and integrations. In the second week, RevOps checks admin consoles for usage, maps the main data flows and identifies overlaps. In the third week, the findings are reviewed with sales, marketing, customer success and finance leaders, and decisions are agreed for each tool. Migrations and cancellations are then scheduled against renewal dates. Present the results in terms leadership cares about: annual cost that can be saved or avoided, risks reduced such as unowned tools holding personal data, and reporting problems that the cleaner data flows will fix. That framing makes it easier to get agreement for consolidation, which often means asking a team to give up a tool they like.
AI tools and the stack
AI assistants and agents have added a new category of tools, often bought by individuals on monthly plans and connected to the CRM, email or call recordings. They deserve the same audit as any other tool, with extra attention to data. Check which AI tools have access to CRM records, emails or call transcripts, what the vendor's terms say about using that data, and whether access is granted through personal accounts that will not be removed when someone leaves. Many core platforms now include AI features for summarising calls, drafting emails or scoring leads, so check for overlap with standalone tools. Where AI tools are genuinely useful, bring them under company accounts with a named owner, and add them to the inventory so that their cost and data access are visible.
Common audit findings
Some findings recur across companies. Seats still paid for people who have left. A second enrichment or data provider bought by one team while another already had one. A scheduler, form builder or chat tool duplicating a feature already included in the CRM plan. Integrations built by a former employee or agency that nobody now maintains. Free trials that converted to paid plans on a personal card. And at least one tool holding customer data that no current employee administers. None of these is unusual, and fixing them is usually straightforward once they are visible.
FAQ
A review of every sales, marketing and customer tool for cost, usage, overlap, data flows and ownership, ending with a keep, consolidate, renegotiate or remove decision for each.
Fully once a year, with a lighter check before each major renewal. Keep the inventory updated whenever a tool is added or removed.
Start with finance: card statements, accounts payable and expense reports for the last twelve months. Then add free tools that hold company or customer data.
Often for core functions, because built-in features remove integrations and licences. Keep specialist tools where they clearly outperform and are well used.
RevOps, with an accountable owner named for each tool and a rule that new tools are checked against the existing stack before purchase.