First Principles / Field guide 02 / October 2026

DevTools GTM, channel by channel.

How companies like PostHog, Harness, Rippling, Supabase, Grafana and Tailscale actually use SEO, content, outbound, events, launches and other channels — with practical templates to try the same thing.

13 channelsReal company examples13 copyable worksheets23 original links

The important distinction: SEO is about being found at the right moment. Technical content is about being worth reading. Research gives people something to cite. Outbound starts conversations that won't happen on their own. They work together, but they are not the same job. This guide keeps them separate so you can build each one properly.

A note about evidence. These are documented company practices and reported examples. They do not prove that a single channel caused a company’s revenue growth. The “How to do it” sections are suggested adaptations, not claims about the companies’ internal playbooks.

01 — See an example

What a real company published, shipped or ran. Every example links to the source.

02 — Follow the steps

A practical workflow, not a general marketing framework.

03 — Copy the worksheet

Replace the placeholders and create your own version.

Channel playbooks

Pick the channel you want to build.

Don't start every channel. Pick one route to near-term demand and one that compounds over time.

01 · Capture intent

SEO & search

Be there when someone is actively choosing a tool.

Read playbook →

02 · Build trust

Technical content

Make something an engineer would save even without buying.

Read playbook →

03 · Create authority

Original research & benchmarks

Publish something the market can cite, not just another opinion.

Read playbook →

04 · Create pipeline

Outbound & account-based GTM

Find a buyer with an urgent problem; send a relevant reason to talk.

Read playbook →

05 · Create momentum

Product launches

Use one shipped feature to reach the right communities in several formats.

Read playbook →

06 · Build ecosystem

Developer community & DevRel

Give people a place to learn, build and contribute before selling.

Read playbook →

07 · Borrow trust

Partnerships & integrations

Show up inside a stack your buyer already trusts.

Read playbook →

08 · Earn credibility

Customer stories & advocacy

Make successful customers useful to the next buyer.

Read playbook →

09 · Start conversations

Webinars, workshops & events

Make the session worth attending even if nobody buys.

Read playbook →

10 · Convert users

Free product, trial & adoption

Let an individual get value before they need a buying committee.

Read playbook →

11 · Own distribution

Email & owned audience

Build a way to reach interested practitioners again.

Read playbook →

12 · Build trust

Founder & engineer-led social

Publish the work and opinions of people who actually build the product.

Read playbook →

13 · Test efficiently

Paid search, ads & sponsorships

Use paid reach to test a known message—not to invent positioning.

Read playbook →

Where to start

Where should a small team start?

A practical starting order. The right mix depends on your product’s adoption model, customer economics and the proof you already have.

First 2 weeks

1Interview the last five buyers or lost deals.
2Write one competitor/migration page.
3Create one 50-account outbound cohort with a real trigger.
4Choose one customer result you can verify.

Weeks 3–4

1Publish the technical guide an engineer would share.
2Run outreach and a small working session.
3Connect relevant articles to a trial, demo or assessment.
4Measure intent and qualified opportunities, not just visits.

Weeks 5–6

1Improve the best page and rewrite the worst message.
2Reuse customer proof in sales and email.
3Test one partner or community distribution opportunity.
4Double down on the motion showing real progression.

One good rule: A channel is not “working” because it generates attention. Look for a chain of evidence: relevant person → useful interaction → evaluation or activated usage → revenue opportunity.

Sources

Original reading list

Company-written posts, operator interviews, event pages, customer cases and filings. Keep these links with the work when you adapt a framework.

Prefer companies?

The same lessons, told company by company.

Ten company playbooks →