About
About Aslam
I started by trying to find customers for my brother's food business, a family business. No sales
background, just business books, Alex Hormozi, a real problem and pressure to solve it. The job was simple to state: get customers.
Manual lead research (Google, Scribd PDFs, UK Trade Info) turned into Apollo and Clay. I used Clay at
first only for email verification, later for list building and then full workflow orchestration. The
databases turned out to lack coverage for a fragmented ICP, so I moved to reverse-engineering
competitors' distributor networks, and then to agents. That gap pushed me into custom data sourcing, ICP design, qualification, signal
research, automation and agentic workflows. At the same time, I got increasingly interested in the
strategy and motion behind the systems, not just the execution.
That led me into freelance GTM work, and into structured learning through Clay University, Apollo
Academy, Maven and the Clay Outbound Orchestration Foundation.
What that learning covered: Clay's Outbound Orchestration Foundations Cohort 1 went through ICP segments
built with signals, persona and messaging in mind, TAM, validating segments, stating assumptions, testing
messages and running discovery calls, then signals, enrichment, segmentation, workflows, webhooks,
Claygents and outreach drafting in Clay. n8n's Foundations Pathway (n8n101, n8n102 and n8n103) and Quickstart covered building and scheduling
workflows, data mapping, sub-workflows, API calls, webhooks, error handling and the AI Agent node with
tools and memory. This is learning; not all of it is applied in client work yet.
I didn't start as a traditional software engineer. I learned and built by starting with a commercial
goal, understanding the conditions the business was working within, and finding or building the
system that made the goal achievable. That's still how I work.