06-reference/research

fde capture vs create demand

2026-05-30·research-brief·source: deep-research
fdedemand-genpositioningsanity-checkseo

FDE Capture-vs-Create: Is There Latent Search Demand for "Forward Deployed" Data Services?

The question

"FDE capture-vs-create demand: is there existing search demand for 'forward deployed' data services?" — feeds the founder's live decision on whether the planned Sanity Check FDE term-claim piece is a capture-existing-demand SEO play or a create-the-category move (different content strategy, different success metric).

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The load-bearing call: on current evidence this is a create-the-category move, not a capture-existing-demand SEO play. The distinction the founder is deciding between resolves cleanly because every retrievable signal points to supply-side heat with no measurable buyer-side search demand. The term "forward deployed engineer" / "FDE" is salient among the people who want to hire FDEs or build FDE-led startups — it is not (yet) the phrase a data-team buyer types into a search bar when they have a pipeline problem and a budget. A capture play only works when buyers are already searching the term; the proxies say they are not, and the buyer-intent phrasings return near-empty. Treating the Sanity Check piece as an SEO capture play would optimize for a query that does not have buyer volume behind it.

What that implies for the piece's framing: write it as category-creation / demand-education, not as a keyword-targeted SEO landing page. The job of the piece is to teach a data-team buyer that "the embedded, forward-deployed delivery model" is the thing they actually want — to attach RDCO's name to the concept BEFORE buyers have a search habit for it, so RDCO is the brand they recall once the habit forms. This is a planting-a-flag move (consistent with the baseline's "the data-qualified term is open"). It rides a real and rising supply-side wave, which is the legitimate reason to move now rather than wait: the term is accruing salience fast, and being the first data-specific claimant is cheaper today than after an incumbent claims it.

The success metric must change accordingly. Do NOT measure this piece by organic search traffic or keyword ranking in the first 1-3 months — that metric assumes a capture play and will read as failure even if the piece succeeds at its actual job. Measure it instead by: (1) category-attachment signals — inbound/referral mentions, operator/VC reshares, citations that pair "RDCO" with "forward deployed for data"; (2) brand-recall and direct/branded-search lift over a longer horizon (6-12 months) as the term matures; (3) qualified-conversation starts attributable to the piece. SEO/organic capture becomes a LATER, lagging metric once (if) buyer search demand materializes — worth instrumenting from day one as a leading indicator of the category tipping from create to capture, but not the launch scorecard.

Evidence-strength caveat, stated plainly: this recommendation is directionally well-supported but rests on proxies, not a measured search-volume figure. The single highest-value thing that would harden or overturn it is one real Google Trends / keyword-tool reading on "forward deployed engineer" and the data-qualified variants. If that reading came back showing meaningful and rising buyer-side volume, the call would shift toward a hybrid (create-led, capture-instrumented). On what is retrievable today, create-the-category is the right default.

Open follow-ups

Sources