The 3-Part Outbound Doc: What You Do, What You See, What You Offer

Why outbound docs beat resumes in 2026

Resumes are optimized for ATS parsers, not humans. In 2026, 38% of developers work fully remote and most B2B roles never hit job boards, so a resume alone cannot prove fit. An outbound doc flips the script by showing you already audited their stack and can ship a specific outcome in two weeks.

If you have applied to 50+ roles and heard nothing, you are not broken. The system is. Job boards push you through Greenhouse, Lever, or Workday filters that rank by keyword overlap, not shipping ability. One viral post on Reddit’s r/jobsearchhacks about a “their nouns” doc showed why: after 200+ ATS applications with zero callbacks, the author switched to mapping employer language and adding one targeted bullet. Result: three interviews in ten days.

For developers chasing B2B contracts, the math is worse. The 2025 Stack Overflow Developer Survey shows 38% fully remote and 10% freelance or self-employed, yet most global contracts are filled via referral or direct outreach before they ever become a public req. An outbound doc for developers replaces volume with proof. You are not asking for permission to be screened. You are showing a CTO you already looked at their product and have a plan.

This is why the classic resume + cover letter fails for B2B. Cover letters explain motivation. CTOs want risk reduction. The outbound doc answers the only question that matters: can you ship this specific thing in their stack without creating more work for their team? That is also how you escape the ATS black hole that eats React and Node.js profiles every day.

Resumes go to ATS filters. Outbound docs go to CTO inboxes.

What the outbound doc for developers actually is

The 3-part outbound doc is a single page split into three blocks that map to trust. What You Do establishes relevance in two lines, What You See proves you did homework on their product, and What You Offer turns insight into a low-risk, fixed-scope trial that a CTO can say yes to.

Think of it as a teardown, not a biography. The original r/jobsearchhacks framework was built for generic roles: show you understand the company’s pain, then position yourself as the fix. For developers pitching B2B, we adapt it with code-level specifics.

1. What You Do — proof in their nouns

This is not your title. It is two lines that mirror their stack and outcome. Bad: “Senior Full-Stack Developer with 8 years experience.” Good: “Ship Next.js 14 + tRPC performance fixes. Last quarter: cut LCP from 4.2s to 1.1s for a $2M ARR SaaS.”

Use their exact nouns. If they say “Next.js App Router, Prisma, Postgres, Vercel,” you say the same. This is the lesson from that “their nouns” doc — ATS and humans both filter by vocabulary. List one framework chain you own, one metric you moved, and one environment you have shipped in, like B2B SaaS or Laravel + Livewire monoliths.

2. What You See — three observations they cannot ignore

This is where 90% of cold pitches die. Most devs write “I love your product.” A CTO hears nothing. Instead, record a 60-second Loom scrolling their app and name three specific, non-obvious observations.

• Product or UX gap: “On /pricing, the annual toggle resets on refresh. State is not persisted in URL search params.”
• Tech or performance signal: “Your marketing site ships 2.3 MB of client JS. No dynamic import for the testimonial carousel. Lighthouse shows 67 performance.”
• Business or hiring signal: “You are hiring for two frontend roles mentioning Framer Motion migration. Your changelog shows that migration stalled in March.”

You do not need access to their private repo. Public signals are enough: network tab, source maps, job descriptions, changelog, GitHub issues. The goal is to prove you looked. That is what cold outreach templates that get replies all have in common — a trigger observation, not flattery.

3. What You Offer — a scoped trial they can buy

Stop offering “full-time availability” or “10 hours a week.” Offer a concrete two-week win with a price anchor and a clear deliverable. This de-risks you for B2B.

• Scope: “Fix pricing state + ship dynamic imports for 3 marketing pages. PRs with tests, Vercel preview links, and LCP before/after.”
• Timeline: “10 days, async, Slack overlap 13:00–16:00 CET.”
• Price anchor: “Fixed €2,400 for the sprint, or $65/h B2B via Deel. No commitment after.”
• CTA: “If useful, I can send the Loom teardown today. Want me to?”

This structure borrows from proven B2B cold email frameworks — hook with relevance, prove with observation, close with low-friction ask — but rewritten for developers who sell outcomes, not hours.

What You See: 3 specific observations from their live product with Loom proof.

How to build your developer outbound doc in 45 minutes

You can build a high-signal outbound doc in 45 minutes using their public stack, a quick Loom, and a tight scope. Start with LinkedIn and their repo, pull three observations, match each to a past ship, then package a two-week sprint with a price range and a calendar link for maximum reply rate.

Here is the exact workflow senior contractors use to get 20–30% reply rates, not the 2% most job board spam gets.

Step 0: Pick one target, not ten

Choose a company with public traction, a visible Next.js or Laravel or Python stack, and a hiring signal. A recently posted frontend role, a “We are rebuilding onboarding” blog post, or a founder complaining about performance on LinkedIn are perfect triggers. Skip companies with no public surface to audit.

Step 1: 15 minutes — stack reconnaissance

Open their site with DevTools. Check package.json via source maps, Wappalyzer, or /_next/static chunks. Look at their careers page for nouns. Look at their GitHub org for stale PRs. Write down exact tools: “Next.js 14, Tailwind, Prisma, PlanetScale, Clerk.” That list becomes your What You Do vocabulary.

Step 2: 15 minutes — write What You See

Record a Loom, no editing. Script: “Hey, I was looking at because. Noticed three things.” Show the bug, show the network waterfall, show the job description mismatch. Keep it under 90 seconds. Then transcribe the three bullets into the doc. Link the Loom at the top of the doc.

Step 3: 10 minutes — write What You Offer

Match each observation to a past ship. Example mapping table:

Observation	Your Proof	Offered Fix
Pricing toggle resets	Fixed similar state bug for SaaS X	Persist in URL + test
2.3 MB client JS	Cut bundle 68% for SaaS Y	Dynamic import + audit
Framer Motion stall	Migrated 40 components at Z	Ship 10 components in sprint

Keep scope narrow. A two-week sprint beats “I can do anything.” CTOs buy specific fixes, not general availability.

Step 4: 5 minutes — format for CTO scan

One page, plain Google Doc or Notion, no columns, no icons. Title: “For — in 10 days.” Structure:

1. What You Do — 2 lines
2. What You See — 3 bullets + Loom link
3. What You Offer — scope, timeline, price anchor, calendar link

Export as PDF with selectable text. Do not use images of code. That breaks ATS and search if they forward it, and it signals junior.

Want to see how matching actually works behind the scenes? Our direct pitch templates break down how VectorMatch’s 3-Gate funnel screens tags, then vector similarity, then LLM reasoning — the same logic you should use manually until you automate it.

Map each observation to past proof and a 2-week fix.

Where to send it and how to track what works

Send the doc where CTOs actually read, not where ATS lives. That means direct email found via GitHub or company domain, a LinkedIn DM with the Loom attached, and a follow-up that adds one new observation. Track opens, reply rate, and trial conversion to iterate weekly.

Do not upload it to Lever or Greenhouse. That defeats the purpose. The outbound doc is for bypassing forms.

Channel 1: Email to the decision maker

Find the CTO or VP Engineering via LinkedIn or their GitHub commits. Use a tool like Apollo or hunter.io to guess the work email, or DM them asking for the best email to send a 60-second teardown. Subject: “Teardown: 3 quick wins for /pricing.” Body: 40 words max, link to doc and Loom, no attachments. Attachments kill deliverability.

Channel 2: LinkedIn with context

Do not pitch in the connection request. Connect with a note: “Saw your post on. Noticed a small bug on pricing. Happy to share a Loom if useful.” After they accept, send the doc. This two-step approach doubles reply rate versus cold pitching on connect.

Channel 3: Follow-up with new value

One follow-up, 48 hours later, with one new observation. Not “bumping this.” Example: “Also noticed your blog images are not lazy-loaded. I shipped that for and cut LCP 0.8s. Added it as an optional extra in the doc.”

Track in a simple sheet: company, observation, date sent, opened, replied, call booked, trial closed. After 20 sends, you will see patterns. Most devs find that Next.js performance teardowns reply 2x more than generic “I can help” offers. That data is gold for landing remote B2B contracts consistently.

If manual outbound feels like a second job, that is because it is. VectorMatch automates the reconnaissance part: tag screening filters for your real stack, vector similarity finds hidden B2B roles that match your past ships, and LLM reasoning writes the pitch in the hiring manager’s nouns. You still own the Loom, but you skip the ATS lottery.

The outbound doc for developers works because it replaces generic motivation with specific proof. What You Do shows you ship their stack, What You See shows you already audited them, and What You Offer turns insight into a buyable two-week win. Build one in 45 minutes, send it direct, track replies, and iterate. That loop beats any ATS hack.