MOD.04 // OPERATOR_FILE
Carried the number. Built the engine. Now building the machine.
I'm Agnishwar. Most people call me AB.
I've spent over a decade on both sides of B2B SaaS revenue. I closed $5M+ across 100+
enterprise deals, selling compliance and legaltech SaaS to CXOs and the kind of
multi-stakeholder buying committees that treat a signature like a hostage negotiation —
at Unilever, Siemens, Tata Group, Mahindra, Vodafone, P&G, L&T, and Brookfield.
Then I built the GTM engine from the inside: positioning, competitive battlecards, and
enablement that lifted competitive win rate by 40% and supported $5M+ in new ARR at CleverTap.
For the past year I've been rebuilding how I operate — AI as the core operating layer for
revenue and GTM work, not a productivity add-on you bolt on and forget. Agentic workflow
design, prompt architecture, and tool orchestration across Claude, ChatGPT, and Gemini,
instead of politely asking a chatbot for help.
The point isn't the tooling. It's the combination: quota-carrying sales instinct, GTM
systems fluency built from the inside, and AI-native build capability most operators in
sales or marketing don't have. It's the difference between describing what AI should do
for a revenue team and having built it, shipped it, and measured what it changed.
agentic_workflows
enterprise_saas_sales
gtm_systems
sales_enablement
competitive_positioning
prompt_architecture
cxo_selling
product_marketing
