StackAuditThese are the questions ops managers ask in the first call. I've answered them here so we can skip the preamble.
"How do I know which tools to cut?"
Every renewal season, the same conversation: "Do we actually use this?" Nobody knows. Finance is guessing, ops is guessing, and the vendor is auto-renewing.
From 41 tools → 14, saving $178k annually
Three project management tools. Two note-taking apps. A video platform nobody had logged into since 2023. The hard part wasn't finding the waste — it was getting buy-in from the team that adopted each tool in the first place.
Ops team, Austin TX
Usage data doesn't lie. Gut feelings do.
I pull 90-day active-user reports from every tool in your stack, cross-reference against seat counts, and map each tool to a job-to-be-done. If two tools do the same job, one goes. If a tool has no job, it definitely goes.
Inventory
Full stack census from SSO logs, credit card statements, and IT shadow IT scan
Usage audit
90-day active user rate per tool — not logins, actual feature engagement
Overlap map
Every tool plotted against the job it does — duplicates surface immediately
Cut recommendation
Ranked list with migration path for anything being replaced, not just deleted
Data hygiene before migration. Always.
A CRM migration that moves dirty data is just dirty data in a new house. I run a data audit first — finding duplicates, empty required fields, and custom properties nobody uses — before a single record moves. The migration is the last 20% of the project.
Data audit
Duplicate contacts, incomplete records, orphaned deals, unused custom fields
Field mapping
Every field in the old CRM mapped to its destination — gaps documented before migration
Stakeholder interviews
Sales, CS, and marketing each have opinions on what matters. Capture them before, not after.
Staged migration
Test migration on 10% of records. Validate. Then run full migration with rollback plan in place.
"What happens to our CRM data when we migrate?"
You've been in HubSpot for three years. Or Salesforce. Or a custom Airtable build that made sense at the time. The data is messy, the custom fields are worse, and nobody wants to own the migration.
HubSpot → Attio in 19 days, zero data loss
The COO had been handed a 4,200-contact HubSpot instance with 89 custom properties, 31 of which were blank across 95% of records. We deleted the noise, mapped what remained, and ran the migration over a weekend.
Fractional COO engagement, Chicago IL
"Will the automations hold after you leave?"
Every consultant builds automations. Most of them are a house of cards — Zapier chains with no error handling, Make.com scenarios with hardcoded IDs, and zero documentation for the next person who has to touch it.
If I can't hand it off, I didn't build it right.
Every automation I build gets a plain-English runbook, a test trigger procedure, and an alert when it breaks. I also audit your existing automations before I build new ones — most stacks have 15 automations and 8 of them are doing nothing or duplicating each other.
Automation census
Full inventory of active Zaps, Make scenarios, and native integrations — including the ones nobody remembers building
Break analysis
Which automations have error logs? Which haven't fired in 60 days? Which are silently failing?
Rebuild with error handling
Every automation gets a failure path, not just a success path. Errors alert Slack, not a dead inbox.
Runbook documentation
Plain English. What it does, what triggers it, what to check when it breaks, who to call.
Or download the Stack Comparison Template — no email required.
The checklist that runs before every engagement.
47 questions across stack coverage, automation health, and data hygiene. Takes 20 minutes to fill out. Saves months of guessing.
Or download the Stack Comparison Template — no email required.
Three types of engagement.
One clear outcome each.
Project-based. No retainer required. Scope is fixed before work begins.
Stack Audit
From $8,500Full census of your SaaS stack, usage analysis, overlap map, and a ranked cut list with migration paths. Deliverable: a decision-ready report your CFO can act on.
CRM Migration
From $14,000Data audit, field mapping, stakeholder interviews, staged migration, and a 30-day post-migration support window. No dirty data in a new house.
Automation Rebuild
From $6,500Full inventory of existing automations, break analysis, rebuild with error handling, and plain-English runbooks for every workflow.
I was handed a spreadsheet of 43 passwords on day one. Six weeks later, we had 12 tools, clean data, and automations that actually work on a Monday morning.
Priya Raghunathan
Fractional COO · Series A fintech, San Francisco
We'd been paying for Salesforce for two years and using maybe 20% of it. The audit surfaced $140k in annual waste. We migrated to Attio in three weeks and haven't looked back.
Marcus Webb
VP Operations · B2B SaaS, 55 employees, Austin
Our Zapier stack had 34 active Zaps. 11 were doing nothing. 6 were silently failing. The rebuild took 10 days and I can actually explain how it works to a new hire now.
Daniela Fuentes
Head of RevOps · Series A marketplace, Chicago
Get the SaaS Audit Checklist.
47 questions. Free. No sequences. Work email only.
Or download the Stack Comparison Template — no email required.