Pavilion argues that modern GTM teams should narrow their ICP and build proprietary account data before adopting more technology, because automation amplifies the quality of the underlying strategy, targeting, and data.
Revomnis take
Revomnis take Pavilion is right that modern GTM teams should narrow the ICP and build proprietary account knowledge before adding automation. Technology can make a precise strategy faster and more consistent. It can also make a weak strategy produce mistakes at industrial speed. Failure mode The usual failure is to buy tools as a substitute for market definition. Enrichment fields become the ICP, AI-generated summaries become research, and workflow complexity creates confidence. The system can process thousands of accounts while nobody can explain which ones should actually receive outreach. Operating rules 1. Narrow the commercial problem first. Define the segment, account conditions, buyer role, problem, proof, and exclusions. Automation should not begin until these choices are explicit enough to govern a record. 2. Build proprietary classification, not just a larger database. Capture the attributes, signals, objections, reply patterns, and meeting outcomes that matter specifically to the client’s offer. The advantage comes from better judgment, not access to the same public data as everyone else. 3. Automate stable decisions before ambiguous ones. Data normalization, enrichment, routing, deduplication, and reporting are usually safer. Account inclusion, message claims, exception handling, and important replies require stronger evidence and often human review. 4. Keep email + LinkedIn under one control model. Automation should coordinate account state, stakeholder coverage, cadence, and stop rules across both channels. More tools should not create more independent motions. 5. Scale only after the narrow model works. Validate qualified replies, held meetings, sales acceptance, infrastructure health, and coherent objections within the segment. Expansion should follow evidence, not unused tool capacity. How Revomnis applies it Revomnis builds the strategy and execution layers together. We define and classify the audience, establish managed infrastructure, coordinate email + LinkedIn, handle replies, qualify conversations, and show the client why each account entered the system. Automation supports the engine, but the operating logic remains visible and accountable. Decision test / what good looks like A good automated system can explain why an account was included, which rule applied, what message path followed, and what outcome changed the model. If removing the tools would leave the team unable to describe the strategy, technology is concealing the absence of one.