Masha

Step 1 — initial email

Subject: Source data, not a rented list

Hi {Name}, We build outbound from source data: company filings, hiring signals, tech-stack changes. Not from a rented list. For a seed-to-Series-B SaaS company, that means three to five buyer cohorts with a distinct angle for each, live in under two weeks. Right now you're probably covering SDR work yourself between founder calls. Pipeline scales with your personal hours, and every week that stays unfixed is another board update explaining flat numbers. Our Sending Engine runs $3K/month: target cohorts built from your market evidence, evidence-backed sequences, managed deliverability. A junior SDR costs $85K loaded and takes a quarter to ramp. This doesn't. Send me your website and I'll come back with the three cohorts I'd target first and the angle for each. Best, Masha

Step 2 — follow-up

Hi {Name}, Around month three of a first SDR hire, most seed-stage founders notice the same pattern: they're writing the sequences, rebuilding the list, and joining calls that should have closed without them. The hire was supposed to buy back selling time. It consumed it instead. Fully loaded, that experiment costs $8–10K a month — salary, tooling, and the founder hours you'll never invoice. By ramp, you've spent a quarter doing two jobs badly. We run the whole outbound operation — sourcing, copy, deliverability, inbox management — for $3K a month, live in under two weeks. You sell; we keep conversations arriving. The engine is AI-native, which is how quality holds at that price. Send me your ICP and current close rate, and I'll put together a one-page map of the cohorts we'd target and the volume to hit your next pipeline number. Best, Masha

Step 3 — follow-up

Hi {Name}, Here's something I keep seeing at seed-stage SaaS companies that surprises me: the outbound budget gets approved, runs two months, and then the CFO asks one question nobody prepared for — "show me which revenue came from those emails." Not "how many meetings." Not "what's the open rate." Which dollars. Most agencies can't answer that. They report meetings booked and reply rates, which at your stage is like reporting gym check-ins when the board asked about muscle. The useful test is simpler: can you trace a line from a specific sequence to a specific signed contract, within one quarter? If not, the spend is a rounding error that dies at the next board meeting. We build outbound that passes that test. The Sending Engine runs source-backed targeting — every contact traced to a buying signal, every sequence written to survive a skeptical reader's four-second scan — so when the CFO asks, you hand over a pipeline report with names, dates, and deal stages. Not impressions. Revenue conversations. If you'll share your current cost-per-meeting or your target CAC, I'll send back a one-page model showing what traced pipeline looks like at your number. Best, Masha

Step 4 — follow-up

Hi {Name}, At seed stage, the outbound bottleneck is almost never volume. It's that your ICP is still a hypothesis with a logo attached. One anchor customer, a strong belief about who else looks like them, sequences built on that belief. Three weeks later the replies are too noisy to separate a messaging miss from a targeting miss, so you adjust copy, not the list. The loop repeats. The founders who break out usually do something unscalable first: personally write to 30 people who don't match the assumed ICP, just to see who bites. The pattern in those replies is worth more than three months of sequences against the original list. Is this matching what you see, or has your targeting already survived contact with real buyers? Best, Masha

Step 5 — follow-up

Hi {Name}, You haven't replied, and I'd rather ask than keep guessing from my side. Maybe you just closed a round and every hour goes to product. Or the budget sits with your board until next quarter, or this simply lands with the wrong person. A line or two — even "not my call" — tells me something real, and it changes what we build and who we build it for. Best, Masha

Step 1 — initial email

Subject: Distribution is the bottleneck, not your model

Hi {Name}, Your model isn't the bottleneck. Distribution is. We built a $200 AI Market Scan for exactly this. It segments your addressable market from source data: hiring signals for the problem you solve, competing-tool purchases, budget location. You get a target-cohort map and buyer-title cloud. Not a guess, a map. Most applied-AI teams demo to anyone who takes the call and wonder why conversions are random. The scan tells you which three cohorts can say yes this quarter, and the Sending Engine ($3K/month, managed inboxes and deliverability) puts evidence-backed sequences in front of them. Tell me what your model does in one sentence and I'll tell you which cohort I'd hit first. Best, Masha

Step 2 — follow-up

Hi {Name}, The first three design partners for an applied-AI product almost always come from the founder's network. The next seven require a motion the founding team has never run: reaching hundreds of companies in use cases they haven't named yet, with an introduction specific enough to get a technical buyer to block an afternoon. Most teams stall at that transition. They demo well, but the 600-send-a-day machine with warmed inboxes and verified contacts doesn't exist yet — and building it in-house means months of hiring and tooling while the funding clock runs. We build that machine for you. The AI Market Scan segments your addressable market for $200 — you pick which cohort answers, and we turn on a Sending Engine that keeps qualified conversations arriving while you stay in the product. Tell me what your model does and who you've sold to so far, and I'll sketch the three adjacent use cases most likely to produce your next design partners. Best, Masha

Step 3 — follow-up

Hi {Name}, You've probably fielded four or five outbound-agency pitches this quarter. They all say the same thing: "we'll book you meetings." And you didn't reply, because at your stage a meeting is not the unit of progress — a design-partner conversation with someone who can say yes to your model this month is. The difference is targeting, not volume. The expensive way to learn this is six months of founder-led sends to whoever your CRM suggests, discovering your real ICP somewhere around the third pivot. By then the category narrative belongs to whoever got there first. The cheap way is to segment the market before you send a single sequence — know which 40 companies have the use case, the budget authority, and the timeline to say yes now. We run that segmentation as the first step, not the upsell. Source-backed contact data, verified against the buying signals that actually exist for applied-AI buyers — not generic title scraping. Then the Sending Engine runs the sequences: written by someone who has read your model card, not a template with your logo swapped in. Tell me what your model does in one sentence and who you think buys it. I'll send back three segments you haven't considered, with the reasoning for each. Best, Masha

Step 4 — follow-up

Hi {Name}, The design partners in applied AI are going to startups with worse models but better proof-of-work: a named pilot, a specific integration story, a reference who'll take a call. The buyer's CTO stopped evaluating capability and started evaluating survival risk. The question behind the question is no longer "does it work" but "will you exist in twelve months." Most founders I talk to are still building their outreach around the capability pitch because that's the story they know best. The buyer moved. The pitch didn't. Is your segment still buying on what the model does, or has it shifted to who survives? Best, Masha

Step 5 — follow-up

Hi {Name}, I haven't heard back, and honestly I'd rather ask than keep guessing. Maybe the model ships before GTM becomes the bottleneck, or inbound from the AI cycle already fills your calendar, or the budget is runway you can't justify spending yet, or this simply sits with your Head of GTM. A line or two — even "not my call" — tells me something real, and it changes what we build and who we build it for. Best, Masha

Step 1 — initial email

Subject: Pangle, Snap, Aviasales: the 500 accounts I couldn't reach

Hi {Name}, I ran SDK adoption and yield partnerships at TikTok Pangle, Snap, and Aviasales/Momondo. Supply-side, demand-side, programmatic. Your partnerships team covers the top 20 accounts. The other 500 are going cold, and that's where fill rate and incrementality actually live. Our Sending Engine sources verified contacts across your counterparty base, writes variants in your language (yield, not "synergy"), and sorts replies into your pipeline. $3K/month, managed inboxes and deliverability. Tell me whether supply or demand is the tighter bottleneck and I'll sketch the first 50 contacts I'd source. Best, Masha

Step 2 — follow-up

Hi {Name}, Most AdTech outbound fails at the first sentence, not the tenth follow-up. The partnerships lead at a mid-size publisher can tell in four words whether the sender has ever looked at a header-bidding wrapper — and most haven't. That credibility gap is why your team's hit rate on new supply or demand conversations stays low even when the list is good. The counterparty base is fragmented and skeptical; they've been pitched by every SSP, DSP, and measurement vendor with a deck. The ones who answer are the ones who speak yield, fill rate, and incrementality without a glossary. We write those introductions. The engine sources verified contacts across your long tail, drafts outreach in the language your counterparties actually use, and sorts replies so your partnerships team walks into warm conversations instead of cold ones. Name the side you're trying to grow — supply or demand — and the geographies that matter, and I'll send back a map of the counterparties your team hasn't reached yet. Best, Masha

Step 3 — follow-up

Hi {Name}, Your partnerships team covers maybe 40 accounts well. Your addressable supply base — the publishers, apps, and CTV inventory that could meaningfully move fill rate — is closer to 2,000. The 1,960 in between don't churn. They never start. No first email, no SDK conversation, no yield comparison on their desk. That silence is expensive in a way that doesn't show up in a pipeline report, because there's no lost-deal stage for a conversation that never happened. The fill rate you report is the fill rate of the 2% you reached. The other 98% is not "no" — it's "never asked." And your competitors' partnerships teams are not reaching them either, which means the first credible email wins. We source and verify the long-tail contacts your team doesn't have bandwidth to find — app developers, mid-tier publishers, CTV inventory holders — then run sequences in the language they actually respond to: yield uplift, incrementality, SDK integration timelines. Not generic "partner with us" blasts. Masha built this playbook on Pangle and Snap supply; the engine runs it at a volume no four-person team can match. Name your supply type and the geographies where fill is thinnest. I'll send back a coverage map showing how many verified contacts sit in that gap. Best, Masha

Step 4 — follow-up

Hi {Name}, The three platform logos on the partnership deck get the board's attention. The yield model runs on the 200 mid-tier publishers and apps nobody on the team has time to call. Every partnerships lead I talk to calls it a relationship business, and they're right about how deals close. But the constraint isn't closing. It's that the long tail never gets a first conversation. The teams that grow fill rate aren't better at relationships. They're better at reaching publishers before the next SSP does. The relationship takes care of itself once someone picks up. Does your long tail already have a first conversation, or is it still waiting? Best, Masha

Step 5 — follow-up

Hi {Name}, You haven't replied, which is fine, but I'd rather ask than keep guessing. Maybe your partnerships team already runs both supply and demand origination and doesn't need outside help. Maybe the conference circuit and existing Rolodex cover enough of your deal flow that cold outbound feels like the wrong motion. Or the budget is locked for the year, or this sits with your CRO and never crossed their desk. A line or two — even "not my call" — tells me something real, and it changes what we build and who we build it for. Best, Masha

Step 1 — initial email

Subject: 10,000 developers on the free tier, zero enterprise logos

Hi {Name}, Most PLG companies discover the enterprise ceiling the expensive way: a board meeting where someone asks why 10,000 developers are on the free tier and zero logos are on the enterprise slide. The fix isn't building an SDR pod. Your culture is product-led for a reason, and a cold-calling team won't survive two quarters. What works is a temporary, outsourced engine that finds the VPs Engineering and CTOs with actual budget, warms them with evidence-backed sequences, and hands you conversations, not a CRM full of cold leads. Our Sending Engine does exactly that: source-backed targeting (economic buyers, not random engineers), managed inboxes and deliverability, $3K/month. It runs alongside your self-serve motion without touching it. Send me your pricing page and I'll map the five enterprise accounts that look like your next expansion cohort. Best, Masha

Step 2 — follow-up

Hi {Name}, A VP Engineering with 200 engineers and a $400K annual tools budget is the buyer your next revenue stage runs on. That person has never seen your name outside a GitHub thread, and your self-serve funnel — the one that built your first $2M — will never surface them. The friction isn't product. Your developers love it. The friction is that nobody on your team has run a conversation that starts with a procurement checklist and ends with a master service agreement. Building that motion in-house means hiring SDRs into a culture that flinches at the title. We run it outside your culture. The engine identifies the economic buyers at your target accounts — not random engineers, the people who sign — sources verified contacts, and writes introductions that earn a first meeting without making your team cold-callers. Share your pricing page and the account sizes you want to reach, and I'll map the enterprise titles at those companies who haven't heard from you yet. Best, Masha

Step 3 — follow-up

Hi {Name}, Here's something I keep seeing in PLG companies that surprises the sales team when they first map it out: the person who adopted your product — the developer who starred the repo, pulled the API key, wrote the internal Slack post — is almost never the person who signs a $120K annual contract. Your champion has influence. Your champion does not have budget authority. And the VP Engineering who does have budget authority has never heard your product described in terms she cares about: risk reduction, compliance posture, total cost against the alternative. The gap between those two conversations is where enterprise pipeline goes quiet. Your marketing speaks to developers. Your docs speak to developers. Your sales deck, if you have one, was built for a demo to an engineer. The VP who needs to justify the spend to a CFO gets none of that — and she is not going to raise her hand in a contact-us form to ask for it. We find those economic buyers — VP Engineering, CTO, Head of Platform — at companies where your product already has organic adoption, and we open the conversation in their language: governance, procurement readiness, what the rollout looks like for 200 engineers. Not a feature tour. A business case, delivered by someone who has read your docs and can speak to the architecture without dumbing it down. Tell me which accounts already have organic users. I'll map the economic buyers sitting above them and send back the first three conversation starters. Best, Masha

Step 4 — follow-up

Hi {Name}, "We should do enterprise." That sentence has been in your planning doc for three quarters. The product is ready, the VP Engineering buyers exist, the budget is real. What's missing isn't a target list. It's that your team spent three years building a culture where selling is something other companies do, and reaching out first feels like betraying the thing that made the product work. The PLG companies that actually cross over don't fix the culture first. They treat the first enterprise conversations as a temporary bridge, run by someone outside the core team, so the product identity stays intact while the revenue line opens. Is the upmarket move already in motion on your side, or still in the planning doc? Best, Masha

Step 5 — follow-up

Hi {Name}, I haven't heard back, and I'd rather ask than keep guessing at the reason from my side. Maybe PLG growth still covers the number and enterprise feels like a distraction you can defer. Maybe the engineering culture makes cold outreach to a VP feel like the wrong language entirely, or you've already hired an AE and are building the motion in-house. Or this sits with your new Head of Sales and never reached them. A line or two — even "not my call" — tells me something real, and it changes what we build and who we build it for. Best, Masha