mkdir
$

The outbound engine that books your buyers.

mkdir runs your outbound end to end: prospecting, warmed domains and mailboxes, email + LinkedIn sequences, and an AI reply agent that books decision-makers straight onto your calendar.

Wired into your GTM stack

HubSpotClayApolloInstantlyVectorn8nOpenAISlack
inbox · re: your distributor onboarding
> prospect · vp opstue 9:42 am

This is actually timely, we are rebuilding this exact process this quarter. Can you send over some times for next week?

> mkdir agenttue 9:51 am

Great to hear. Tuesday 10:30 am or Wednesday 2:00 pm (your time) both work, calendar link below if something else suits better.

classifiedpositive
response9 min
outcomebooked · wed 2 pm

✓ meeting on your calendar. no rep touched this thread.

> the problem

Your SDRs are working leads by feel.

Five thousand raw leads in a spreadsheet. No consistent scoring, no prioritization, no idea which fifty actually fit ICP. Reps guess, pipeline lags.

Most B2B teams don't need another SDR. They need the engine that turns a raw list into booked meetings: prospecting, warmed sending infrastructure, sequences, and an AI agent working every reply. That is what mkdir runs for you.

90%+inbox placement, monitored daily
< 1 hrAI reply to every positive lead
8 wksengagement to show the best results
Explore the outbound engine →
Targeted prospects5,000 contacts
Outreach goes liveEmail + LinkedIn
Replies worked by AI< 1 hour
Meetings bookedOn your calendar

one managed motion, list to calendar

> work

GTM engines and RevOps systems we've shipped

> gtm engineering

GTM Lead Processing Pipeline

The problem

A B2B AI sales SaaS had raw lead lists from every channel, website visitors, LinkedIn engagement, conference exhibitors, Clay enrichment. No consistent scoring, no prioritization, no way to know which 50 of 5,000 leads actually fit ICP. SDRs were working leads by feel.

The solution

Six-step Python pipeline that takes any raw lead CSV and outputs a campaign-ready file: 278 industry labels normalized to 50 canonical, 100-point ICP score (industry, title, size, revenue, tech, geo), hard filters, automated product research, 9-signal account prioritization, and a sequencer-ready export with merge fields populated.

5,000 raw

Tiered A→D

leads scored, ranked, ready to work

minutes

from raw CSV to campaign-ready

PythonClayVectorLemListApollo
1 / 6
> why mkdir

Built for B2B sales teams. By someone running the engine.

01 /

GTM engineers, not generalists

ICP scoring, account research, signal-driven outbound, built by someone who runs the GTM engine, not just connects apps.

02 /

Your stack, not ours

HubSpot, Clay, Apollo, Instantly, n8n, we build inside what you already pay for, no migration tax.

03 /

Zero behavior change for SDRs

Reps get a tiered queue and pre-filled briefs. They keep working in the tools they know, the system runs underneath.

04 /

Project-based, paid on delivery

Defined scope, fixed timeline, shipped output. No retainers to figure things out.

Varun Bagrodia

Varun Bagrodia, founder

GTM engineer. Previously financial risk at Credit Suisse, MEM (Finance) from Duke. You work directly with Varun on every engagement.

linkedin →
> frequently asked

Common questions

What is mkdir?+

mkdir runs managed outbound for B2B sales orgs: prospecting, warmed sending infrastructure, email and LinkedIn sequences, and an AI agent that works every reply until a meeting lands on your calendar. Under the hood it is a GTM engineering practice: ICP scoring, account research, and the CRM plumbing that ties it together.

How is this different from hiring a GTM engineer?+

A full-time GTM engineer is a $150k-$200k commitment with undefined scope and no shipped output for months. mkdir is project-based: defined scope, fixed timeline, and a working system in production. Prove the work first, then bake it into payroll if you want to.

What does a typical engagement look like?+

Three phases: a one-week GTM Audit that maps your funnel and identifies the highest-leverage builds; a Build & Deploy phase with a custom timeline (usually 2-6 weeks per project); and an optional monthly Retainer to maintain and extend the engine as your team grows.

How is this different from Zapier or Make?+

Zapier and Make connect apps with linear if-this-then-that triggers. mkdir builds branching, AI-decisioned workflows that score leads on a 100-point ICP model, research accounts at depth, extract structured data from transcripts and PDFs, and run end-to-end without human review on the steps that don't need it.

What tools does mkdir work with?+

HubSpot, Clay, Apollo, Instantly, Vector, n8n, Python, OpenAI (GPT-4o), Slack, Fireflies, Sybill, Google Slides, Google Sheets, Gmail, and Serper API. We build inside whatever stack you already have rather than asking you to migrate.

$ mkdir meetings

Meetings on your calendar, without hiring more SDRs.

Book a free 30 minute consultation. We will map your funnel and show you exactly what the engine would do with it.

Book a call