SMYS 5 | From Account List to Monitoring Universe: Building the Prioritization Layer
Why the scored list is not the outbound trigger, and how Umar Farooq Adam built the scoring, monitoring, and signal architecture that finds the right 300 accounts every month in a TAM of 150,000
👋 Hi, it’s Rick Koleta. Welcome to GTM Vault - a breakdown of how high-growth companies design, test, and scale revenue architecture. Join 26,000+ operators building GTM systems that compound.
Enterprise account lists are too long to work and too short to ignore. The TAM is mapped. The named accounts are assigned. Reps still spend their week researching the wrong 50 companies because nothing in the system tells them which five to actually open today. This is not a coverage problem. It is a prioritization problem masquerading as one.
In episode five of Show Me Your Stack, Umar Farooq Adam walks through how he solves it at a Global Systems Integrator pushing hard into EMEA on the back of sovereign cloud trends and cloud repatriation. The client has a TAM of more than 150,000 enterprise accounts. They reach out to 300 of them every month. The system Umar built is what decides which 300.
Umar started as an inside sales rep for APAC at Hitachi. He did not wait for someone to build better tooling. He built account research automations to improve his own selling, got pulled into a global pilot, increased lead quality by 60%, and compressed weeks of manual research into two days. He now runs GTM programs globally at Hitachi Vantara and consults IT MSPs and ISVs on automating GTM at gtmstudio.xyz. His stack is Clay, HubSpot, Chili Piper, Outreach, and the Power Platform with the rest of the M365 suite. The unusual part is not the tools. It is how he wires them together inside an enterprise where the data lives in Salesforce, the workflows live in Microsoft, and the motion has to land in both without breaking either.
The Client Problem: Project-Based Selling Into a Commodity Signal Window
Systems integrators do not sell on subscription. Every deal is a project. There is no recurring revenue base to expand against, no predictable renewal motion to anchor outbound timing. The buying window opens when a customer’s infrastructure is aging, their vendors are consolidating, or their cloud workloads are ready to move. The GSI’s job is to be present the moment that window opens, not six months after the deal was already decided.
The sovereign cloud trend and the cloud repatriation window in EMEA created a specific version of this problem. A large cohort of enterprise accounts are evaluating moves from cloud-heavy infrastructure back toward on-premises solutions, driven by data sovereignty regulation, cost repatriation, and one specific structural event: a major mainframe supplier is going end of life. There were three players providing mainframe systems. One is closing that business. The accounts still running those systems need to move, and they need a systems integrator to help them do it.
The window is real. The signal is public. The problem is that 150,000 enterprise accounts fit the rough profile, and the GSI does not have 40 sales reps making 200 dials a day. They have a tight outbound function and a need to be surgically right about which 300 accounts deserve time this month.
Before this system, they were spending £300,000 a year with a specialized research firm in London to answer that question manually.