maganjot singh

← back to portfolio

gtm plan

an intelligence and distribution system for AI security, not a traditional sales playbook.

iit patna · maths and computing

air 5095 · jee advanced 2023

cracked one of the toughest exams in the world at 17

unfair advantage

the network I have is what you need.

I already operate in the environments Oximy needs

I'm already close to:

founders
operators
engineers
AI builders
startup ecosystems
IIT networks
fast-moving product teams

Inter IIT Tech Meet gave me access to companies and a network across all 23 IITs. Real relationships, not just campus visibility.

How I'd build GTM for Oximy

I wouldn't approach this like a traditional sales process.

I'd approach it like building an intelligence and distribution system around AI security.

The goal early on is not “scale outreach.”

The goal is:

understand where AI adoption is happening fastest
identify where security pain already exists
get into the right conversations early
build trust with technical teams
create repeatable systems around that

Most AI companies are still figuring things out internally.

That's the opportunity.

the plan

five phases. one system.

phase 1 - first 2–3 weeks

Build the signal map

I'd start by building a live ecosystem map around companies actively deploying AI.

Not random lead lists.

Actual signal.

What I'd track

startups shipping AI features
companies hiring AI infra/platform/security roles
teams talking about governance/compliance
startups scaling internal copilots or agents
AI-native SaaS companies
infra-heavy engineering orgs
founders publicly discussing AI workflows

Regions

SF startups
NYC AI ecosystem
India AI-native SaaS
remote-first AI companies

What this creates

Instead of blind outbound, we know:

who's moving fast
who's under pressure
who probably already has security gaps
who recently raised
who's scaling too quickly for their current infra

That becomes the foundation for everything else.

phase 2 - weeks 3–6

Build outbound that doesn't feel like outbound

Most outbound fails because it's generic.

Especially with technical buyers.

I'd focus on:

contextual outreach
company-specific observations
AI workflow discussions
infra/security pain points
founder/operator-level messaging

Not:

“Hey, just checking if you're interested in AI security.”

That gets ignored instantly.

The messaging should feel like:

someone who understands their stack
understands their velocity
and understands what breaks when AI adoption scales too fast

Channels

LinkedIn
X/Twitter
email
founder circles
Reddit signal monitoring
engineering communities
warm intros through operators and alumni networks

The objective isn't volume.

The objective is:

book high-quality conversations consistently.

phase 3

Win the meetings

This is probably where I'm strongest.

If I can get someone on a call, I can usually move the conversation somewhere meaningful.

Not because I “sell aggressively.”

Because I adapt fast in live conversations.

I'm good at:

reading what people actually care about
simplifying technical ideas
asking the right questions quickly
making conversations feel collaborative
understanding operational pain in real time
creating trust without sounding scripted

A lot of enterprise GTM dies before the meeting.

I think my advantage starts once the meeting begins.

Honestly, doubting that is fair.

Get on a call with me and see.

phase 4 - weeks 6–10

Build narrative and ecosystem presence

Most AI security companies sound identical online.

Too much jargon.

Too much fear marketing.

Too little real operator insight.

I'd help position Oximy around:

real AI adoption problems
operational security gaps
governance friction
velocity vs safety tradeoffs
lessons from teams shipping AI fast

Content style

Not polished enterprise fluff.

observations
breakdowns
short operator insights
ecosystem analysis
technical GTM content
"here's what we're seeing" style narratives

The goal is to become recognizable inside:

AI founder circles
infra communities
engineering ecosystems
startup operators

phase 5 - long-term

Turn GTM into infrastructure

Long-term, GTM shouldn't depend on brute-force outreach forever.

I'd help build:

outbound systems
CRM workflows
lead intelligence pipelines
content loops
meeting feedback systems
referral loops
automated follow-ups
account research systems
ecosystem relationship maps

Because eventually:

distribution itself should become infrastructure.

That's already how I think.

Why I fit this

I don't come from a polished enterprise background.

I come from environments where:

ambiguity is normal
systems are broken
timelines are unrealistic
and execution matters more than presentations

At Saturn Labs, I worked across:

operations
hiring
product execution
backend systems
rapid iteration

Sometimes the gap between idea and deployment was less than a day.

At Inter IIT Tech Meet 14.0, I led execution across:

23 IITs
2000+ participants
₹1Cr+ operations
multiple external partners and internal teams

That experience trained me to:

operate under pressure
coordinate chaos
make decisions quickly
and keep moving when things stop being organized

I also think deeply about distribution.

TRXND came from a simple belief:

most products don't fail at the build. they fail at distribution.

So I've spent time building:

content engines
outbound systems
lead pipelines
narrative systems
Reddit intelligence tooling
marketing infrastructure
account orchestration systems

Because I don't see GTM as “sales.”

I see it as systems design.

And even though I'm based in India, I don't think modern GTM is geography-bound anymore.

The buyers may be in SF.

But the leverage now comes from:

intelligence
positioning
communication
systems
speed
consistency
relationship building online

Most founders don't need another generic SDR.

They need someone who:

thinks like an operator
understands technical environments
communicates naturally
learns fast
builds systems
creates momentum
and can execute independently

That's the lane where I fit naturally.