Automation is attractive because it promises scale without more labor. Leads routed instantly. Follow-ups triggered automatically. Opportunity updates synchronized across systems. Summaries generated without manual work. All of that can help. But automation only improves what the underlying system already knows how to do. If the underlying process is unclear, automation spreads confusion faster.
That is why the first serious catch-up GTM move is almost always foundational. Before the company automates more of the workflow, it needs to decide what the workflow actually is.
Start with ownership. Which accounts belong to whom? How are house accounts handled? When does an inbound lead stay with marketing, when does it pass to sales, and when does it go back? What happens if service teams identify a commercial opportunity? Which manager owns disputed territory decisions? These questions sound basic because they are basic. They also produce a lot of hidden friction when they are unresolved.
Then move to stage definitions. Many companies have sales stages that are nominally documented but not operationally useful. One rep uses stage two to mean "intro call done." Another uses it to mean "qualified and pursuing." A manager uses it to mean "has enough signal to forecast lightly." If stage language does not map to observable buying evidence, the pipeline becomes a social negotiation rather than a system.
Next is data hygiene, but not in the sterile sense. A lot of data-hygiene programs fail because they act as if the job is to make the CRM pretty. The real job is to make the CRM reliable enough for management and automation. Which fields matter for routing, forecasting, segmentation, and follow-up? Which fields should be required? Which fields should die because nobody uses them? What should happen when data conflicts across systems? Hygiene should be designed around actual operating decisions.
Another foundation issue is contact and activity truth. If the company wants better sales execution, it needs to know whether customer interaction history is legible. Can a new rep understand the account without hunting through private notes and inboxes? Can a manager inspect deal momentum from the system instead of from rep narration alone? Can marketing or service teams see enough context to coordinate intelligently? If not, automation will keep tripping over partial context.
Quoting and handoff logic also belong in the foundation layer. Many underbuilt companies suffer from messy quoting paths, discount exceptions, or branch-specific workarounds that live outside the main system. That is not just a finance problem. It shapes sales behavior, cycle time, and trust in the operating process. If the quote path is unreliable, the company will struggle to standardize downstream reporting and follow-up.
There is also a management foundation. A lot of GTM systems look weak because no one is using them to inspect work consistently. Reps update fields when they have to. Managers ask for pipeline cleanups before forecast meetings. Operations teams chase missing values. That creates a bursty compliance culture instead of a living operating system. Before adding more automation, the company needs a baseline inspection rhythm that reinforces the few things that actually matter.
The good news is that foundational repair does not always require large capital projects. Some of it is definitional. Some of it is process cleanup. Some of it is field reduction. Some of it is deciding that only a small number of status transitions matter. Some of it is training managers to ask for evidence rather than anecdotes.
In practice, a strong foundation layer usually includes six elements. Clear account ownership. Observable stage criteria. A limited set of required fields. A reliable activity surface. A sane quote or commercial exception path. And manager inspection routines tied to those definitions. That is enough to make later automation safer and much more valuable.
This is also where people often underestimate the value of deletion. Underbuilt systems accumulate forms, fields, stages, dashboards, and custom workflows because every past problem left residue. Cleaning the foundation often means removing things, not adding them. A smaller set of trusted controls can do more for operating quality than another layer of complexity.
AI and automation can still help at this stage, but in a narrow way. They can surface missing fields, summarize activity, draft notes, flag duplicates, or suggest next actions. They should not be asked to compensate for unresolved ownership rules or bad process design. If people do not agree on what stage three means, an AI assistant will not save the forecast.
The practical order matters. Define the few decisions the system must support. Strip down the fields and stages to those decisions. Clarify ownership and handoffs. Train managers to inspect against that structure. Then automate the parts that are repetitive, low-risk, and already legible.
Foundations can feel unglamorous because they do not produce a flashy transformation slide. But this is where the compounding starts. Once the company can trust its account ownership, stage movement, activity record, and basic workflow controls, almost every downstream improvement gets easier. Reporting improves. Coaching improves. Handoffs improve. Automation becomes less dangerous. AI becomes more useful. The system begins to deserve the data it is collecting.
One useful rule is to refuse workflow automation for any step the team cannot explain simply. If the routing logic takes ten minutes to describe, the company probably does not understand it well enough to automate it.
Another useful rule is to design fields and stages for inspection, not for fantasy completeness. If a field never changes a decision, remove it or make it optional. Underbuilt companies do not need more admin burden disguised as data quality.
Evidence note: this post uses local context from the Revenue Operations and GTM Engineering series, plus public CRM/admin references such as https://trailhead.salesforce.com/.
This is part 2 of 10 in Catch-Up GTM for Mid-Market and Traditional-Industry Companies.