Lean doesn’t mean fewer people. It means growing without adding operational headcount at the same rate. Before hiring, check whether the work exists because the business is growing or because data, systems and processes can’t keep up. Fix those first, automate what repeats, and hire for judgment and specialist expertise.
Key takeaways
- Not every hire is about growth. I talked with Allie Kelly at Revenue Brew about the difference between needing more people to grow revenue and needing them because systems and processes can’t keep up.
- Fix the data before automating it. Consolidating more than 25,000 duplicate account records after a CRM migration gave one B2B software client reliable segmentation and routing, with no AI involved.
- Experienced people are still needed for judgment. AI can take on research, reporting, data entry and routine admin, but sales judgment, customer relationships, commercial decisions and complex technical work still need people.
Lean doesn’t mean fewer people. It means getting more out of the people you have, without adding headcount every time the business grows. There’s a difference between needing more people to grow revenue and needing more people because your systems and processes can’t keep up.
I recently spoke with Allie Kelly at Revenue Brew about how companies are building leaner GTM teams, where AI fits in, and where people still matter.
Why growth keeps meaning more headcount
For years, revenue organizations have added people to manage growing complexity: more systems, more data, more reporting and more manual processes. We see it across our clients: years of CRM customization, duplicated data, disconnected systems and temporary workarounds that have become permanent jobs.
Someone is fixing leads routed to the wrong rep. Someone is reconciling reports that don’t match. Someone is manually building territories because the CRM doesn’t have a reliable account hierarchy. Rather than fixing what’s creating the work, companies hire more people to manage it.
Fix the work before automating it
AI and automation can change this, but only if companies address the underlying problems. For one B2B software client, we consolidated more than 25,000 duplicate account records following a CRM migration. Leads were attaching to the wrong accounts, and marketing couldn’t reliably distinguish customers from prospects. Fixing the data meant better segmentation, more accurate routing and less manual correction.
Another client couldn’t see how revenue rolled up across parent and subsidiary accounts. We’re rebuilding their account hierarchy so the team can plan territories and allocate coverage without extensive manual analysis. The hierarchy comes first. For a supply chain technology company, identifying 2,732 ultimate parent hierarchies is what let us redesign 37 territories in five weeks.
Neither project started with AI. Both started with understanding why the work existed in the first place. Once those problems are fixed, automation becomes far more useful.
What work actually needs people?
AI can handle more of the research, reporting, data entry and routine administration that consumes people’s time. But sales judgment, customer relationships, commercial decisions and complex technical work still need experienced people.
That raises the bar for everyone. As I told Revenue Brew, it’s no longer okay to say you haven’t used a tool. You don’t need to be an analyst, but you do need to be comfortable with data and AI.
What it costs to build is changing too. A media company we work with relied on specialized analytics resources for reporting, and new reports could take days or weeks. We built them a reporting application with AI coding tools in about seven weeks. AI made the build faster. But understanding the data, diagnosing issues and fixing the underlying CRM problems still took deep technical expertise.
That changes the decision between buying another system, building something specific to the business, or hiring someone to manage the work. And the expertise to build it doesn’t have to be a full time hire.
Before adding headcount, look at the work
Before hiring, I’d ask:
- What work is taking up the team’s time?
- What could be eliminated or automated?
- Where do we genuinely need human judgment or specialist expertise?
This is also how we approach our work at Lean Layer. We fix the underlying data and systems, automate repeatable processes and bring in specialists where needed, rather than expecting companies to hire every capability internally. The goal is to grow without operational headcount increasing at the same rate, rather than to run with as few people as possible.
Read the full Revenue Brew article.
Frequently asked questions
What does a lean GTM team mean?
A lean GTM team gets more output from the people it has, so headcount does not have to grow at the same rate as revenue. It does not mean running with as few people as possible. It means removing the work that exists only because data, systems or processes are broken, and putting people on the work that needs judgment.
Why do revenue teams keep adding headcount as they grow?
Because complexity grows with them: more systems, more data, more reports and more manual processes. Temporary workarounds for duplicate records, bad routing or a missing account hierarchy turn into permanent jobs, and companies hire people to manage the problem rather than fixing what creates it.
Should we fix our CRM data before adding AI?
Yes. Automation applied to duplicate accounts, wrong routing or a broken hierarchy repeats those errors faster. Cleaning the data first, for example consolidating duplicate account records after a migration, gives better segmentation and routing on its own, and makes any automation built on top of it more useful.
What work still needs people on a revenue team?
Sales judgment, customer relationships, commercial decisions and complex technical work. AI can take on more of the research, reporting, data entry and routine administration, which raises the bar for everyone else: team members need to be comfortable working with data and AI tools, even if they are not analysts.
What should I ask before hiring another operations role?
Ask what work is taking up the team’s time, what of it could be eliminated or automated, and where you genuinely need human judgment or specialist expertise. The specialist expertise does not have to be a full time hire.