01
For technical products, buying intent shows up in developer behaviour, GitHub activity, package installs, docs usage, CLI runs, long before it shows up in a CRM. Whoever captures that signal first owns the pipeline.
Positioned today as The Technical GTM MeshAn engineer finds a tool and installs it. The team adopts it quietly. The org evaluates. Only at procurement does the CRM see anything.
Stage 1
Engineer discovers, installs, pulls, clones
Stage 2
Team adopts quietly through docs, CLI and trials
Stage 3
Org evaluates, still invisible to sales
Stage 4
Procurement surfaces, the CRM finally sees it
Built on what engineers do, not what titles claim. Proprietary, behavioural, compounding.
2023–24
Developer-intent detection. Signal collection from open source, docs and packages.
2025
Audiences, scoring and prioritisation. Activation into CRM and outreach.
2026
Reo Agents and Reo MCP, 2Bn tokens in month one. The Agent Intent Gateway captures what AI agents ask when they evaluate a product.
02
This is a category-led content engine, not a blog. The positioning is deliberately narrow, GTM for technical buyers and nothing wider, and every property carries the same prefix. Content is treated as the layer that builds the category, not as lead-gen support for sales.
Ranks for adjacent problems buyers already search for, then leads them to the bigger reframe. See How to monetize your OSS, the DevRel Guide, and Why 90% of Developer Content Fails.
Content teaches plays that require the product’s infrastructure. The need gets created without the product being sold. See the playbook Identify Developers Opening Issues & Comments on your Competitor GitHub Repositories.
Co-creating with recognised DevTool operators transfers that authority. See the DevGTM Ecosystem hub and the Unstructured.io session on converting OSS signals into pipeline.
If DevGTM becomes the category language, competitors have to play on Reo’s terms. DevGTM Blog, Playbooks, Academy, Signals Guide, Modern DevGTM Newsletter.
Six pillars visible from outside.
Why generic intent data fails for developer-first companies.
Playbooks, a 120+ signal framework, and the DevGTM Academy.
Launch posts for Audiences, Tech & Hiring Signals, MCP and Agents.
DataHub, $1.01M pipeline per quarter. Unstructured, 40% of pipeline.
Three distinct voices: category and vision, technical credibility, commercial execution and hiring.
DevGTM Ecosystem partners, webinars, a podcast, and the Reo × Claude Builder Challenge.
The numbers Reo.Dev publishes about its own go-to-market.
Generic B2B intent becomes developer-specific intelligence.
The chain
03
The LinkedIn page is not the channel. It is an aggregator.
Only 1 of the last 11 posts on the company page was original, an employee spotlight. Everything else was a repost. The restructure started five to six months ago.
This is deliberate. LinkedIn suppresses company pages and rewards personal profiles, so the entire broadcast function has moved onto people and the page just collects it.
CEO on category narratives and provocative POVs. Co-founders on product depth, podcasts and demos. Marketing on launch teasers and campaigns.
A fictional “Co-CEO” with its own account runs humour and product disguised as memes.
DevTools GTM experts who reinforce Reo’s positioning.
Repeated narratives suggest these talking points are seeded, not purely organic.
DevGTM Academy graduates and customers supplying social proof and community-generated content.
Comment “Agent” produced 47 comments against 53 reactions, deliberately optimising for reach and lead capture over vanity engagement.
Executives are consistently among the first reactors, which builds early post velocity.
#ReoLaunchMonth, #AgentGTM and DevGTM used consistently to compound the category.