06-reference/concepts

fde asymmetric edge rdco positioning

2026-05-13·concept·status: canonical-pattern·source: Founder synthesis (iMessage 2026-05-13 02:30-02:46 ET) + Ray expansion·by Ben Wilson (founder framing) + Ray (asymmetry articulation)
fdeforward-deployed-engineerpositioningasymmetric-edgeproductization-gapsmb-disciplinecustomer-zeromacsanity-checkpalantir-playbookharness-engineering

FDE Asymmetric Edge: RDCO's Positioning Against the Enterprise Playbook

Why this is in the vault

Forward Deployed Engineers (FDE) are crystallizing as the load-bearing function in enterprise AI rollouts. Three frontier labs (OpenAI DeployCo, Anthropic partnership programs, Google's hundreds-of-engineers AI service) plus the application-layer giants (Palantir, Box, phData, Blitzy) are running the same playbook simultaneously. Founder is about to join phData full-time as an FDE-shape role. The question this doc answers: if RDCO plays the same game as the enterprise FDE shops, RDCO gets crushed by their bench + balance sheet. So what game does RDCO play instead?

This is the canonical positioning frame for RDCO services going forward. MAC, Sanity Check, the multi-agent skill pipeline, the bet stacks, and any future client-facing surface all derive from the four asymmetries named here.

The frame

Big FDE shops play the $200k+ enterprise end. RDCO plays the $5k-$30k artifact-and-template end. Different game, same discipline. The discipline transfers because the underlying work (evals, change management, data setup, harness deployment, agentic tuning) is the same. The scale differs by 10x. The pricing differs by 10x. The cost-structure differs by 10x. The customer differs entirely.

The founder operates inside both worlds simultaneously. phData W-2 is the enterprise playbook lived from the IC seat. RDCO is the SMB-scale productized version built from the lived experience the IC seat provides. This combination, alongside RDCO's customer-zero operation of its own AI-COO (Ray), is the moat nobody else in the FDE-as-thesis conversation can claim.

The four asymmetries

The advantages flow from playing a different game, not from being better at the same game.

1. Productization gap

Enterprise FDE shops cannot productize their artifacts. The constraint is structural:

A solo operator inside the playbook can extract the GENERIC SHAPE of the load-bearing artifacts (MAC matrices, eval suites, data-setup playbooks, change-management runbooks, agentic-tuning loops) that work across clients, anonymize, and ship as info-products + open-source patterns. The enterprise sells engagement-hours; RDCO sells artifact templates. Different revenue mechanic; different cost structure; different customer.

2. SMB-scale with enterprise-discipline

The enterprise FDE engagement size floor sits at $200k+ ARR because the procurement + compliance + legal + security-review apparatus has fixed overhead. That apparatus does not exist at SMB scale. A solo operator can run the SAME discipline (evals, MAC, change management, harness deployment) at $5k-$30k engagement size because:

Ships faster (no procurement gate) and cheaper (no bench). The discipline is identical; the operational shape is built for a different scale point.

3. Public synthesis voice

Big FDE shops cannot publicly tell you what works because:

The Sanity Check seat is structurally available to RDCO precisely because phData lawyers cannot run it. Lived-experience synthesis from inside the enterprise FDE playbook is the highest-trust voice in the conversation and is uncopyable by anyone not inside the playbook. The founder occupies this seat the moment he starts at phData.

Editorial guardrails (no derivative pieces per feedback_no_derivative_sanity_check_pieces) keep the synthesis honest. RDCO's no-derivative rule is the discipline that turns "I work at phData" into "here is the original re-frame nobody else could write."

4. Customer-zero operating moat

Big FDE shops have no in-house pet-COO. They cannot dogfood the deliverables they sell because their internal operations run on legacy systems. RDCO operates as its own customer-zero: Ray (the AI-COO) is the live deployment that the founder runs on his own life and business simultaneously while seeing what big FDE shops ship in client engagements and where they leave value on the table.

The intersection (founder of AI-COO substrate) × (lived-experience-as-FDE-IC at phData) is the strongest single moat in the wave. Nobody else in the FDE-as-thesis conversation can simultaneously claim:

The customer-zero moat compounds with each phData engagement. Every artifact the founder produces for phData clients teaches him something about the generic shape that RDCO can productize. Every engagement deepens the public-voice authority. Every passing month, the moat widens.

What this implies for RDCO services

MAC. The 2026-05-11 ARCHIVE call on MAC-as-retainer (Notion decision 2026-05-11-board-backfill-mac-warm-network-pick) stands as a correct read of the retainer math at the time. The shape implied by this positioning frame is different: MAC ships as an info-product (the productization-gap asymmetry) with a clear retainer-tier upgrade path for clients who outgrow the info-product but cannot afford the $200k+ enterprise FDE engagement. The upgrade-path retainer is NOT the same as the original retainer pitch; it is a different shape that did not exist before this positioning frame crystallized.

Sanity Check. SC v3 lands as the synthesis voice. Each piece draws on at least one of: (a) lived phData engagement (anonymized + generic-shape only), (b) RDCO customer-zero operating experience (Ray + bet stacks + investing project + harness-engineering build), (c) the 1500-year intellectual lineage Atkins surfaced. The discipline is no-derivative; the original re-frame is built from the four-asymmetry seat.

The multi-agent skill pipeline (shipped 2026-05-12). The pipeline is itself an FDE-artifact productization. Each domain workflow (/build-website-discovery, /build-mac-test-suite, /build-sanity-check-article, etc.) is a productized version of work that would cost $200k+ as an enterprise engagement. The pipeline is RDCO's mechanism for taking phData-engagement learnings and shipping them at SMB scale.

The bet stacks (Squarely, MAC, Sanity Check, RDCO umbrella). Each bet is an instance of the productization-gap asymmetry applied to a specific market segment. The bet-stack YAML pattern formalizes the productization shape.

Pricing. RDCO operates in the $5k-$30k artifact range. Above $30k, RDCO defers to phData or the enterprise FDE shops. Below $5k, RDCO ships as info-product (one-time purchase, no engagement). Inside the $5k-$30k band, RDCO sells templated engagements: artifact + light coaching + handoff.

What this implies for founder time allocation

phData is the lived-experience-acquisition phase. Founder cycles inside phData are not lost to RDCO; they are the input that makes RDCO's positioning possible. The optimization is NOT to minimize phData time. The optimization is to extract maximum signal per phData engagement back into RDCO's productized artifacts.

Practically, this means:

What this implies for the FDE wave commentary

If/when the founder lands a Sanity Check piece in the FDE wave, the shape is: "Running the inverted ladder from inside the FDE seat." Substance:

The piece's distinctiveness is the four-asymmetry seat: no other writer in the wave can simultaneously claim all four. The piece writes itself once founder has cycles to land it. Until then, this concept doc is the substance.

Cross-references to surfaces this should touch

Related