06-reference/research

solo fde contract structures

2026-06-07·research-brief·source: deep-research
fdecontractspricingrisk-reversalsolo-vs-studio

Contract Mechanics for a Solo FDE: Stage the Risk Down a Ramp — Fixed-Fee Pilot → Milestone-Staged Retainer, with Outcome-Based Kept as Optional Upside, Never the Backbone

The question

Verbatim: "What contract structures (outcome-based, retainer, milestone) let a solo forward-deployed AI engineer de-risk the buyer while protecting margin, and how do buyers perceive solo vs. studio for agent-deployment work?" Context: the FDE cluster has settled the positioning (solo-as-feature) and the price band ($15K/mo retainer); this brief fills the remaining gap — the actual contract plumbing underneath the offer. Deepens [[2026-05-30-solo-vs-studio-fde-buyer-perception]] and [[2026-05-31-fde-scoping-pricing-vs-ai-consultant-framing]].

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Recommended contract shape: a two-stage risk ramp where each stage de-risks the buyer further while the structure — not a contingency bet — protects margin. Stage 1 is the already-decided paid fixed-fee pilot ($2K-$5K, ≤2-3 weeks), governed by a one-page SOW with a written, agreed success bar, a fixed-scope money-back guarantee ("delivered to the agreed spec by the agreed date, or refunded"), and 100% fee-credit into the retainer on conversion. This is the buyer's headline de-risk: small dollars, short window, guaranteed, and free to proceed. It is cheap for RDCO to guarantee precisely because the scope is tiny and the window is short — the guarantee is a high-trust signal a solo can afford that a studio rarely matches at the individual level. Stage 2 converts to the 90-day-minimum retainer at $15K/mo, but billed as milestone-staged releases inside the term rather than one upfront lump: month-one (or a kickoff deposit) up front to seat the engagement, then releases tied to shipped production artifacts, each with a 5-business-day acceptance window (silence = auto-accept), documentation + working-code handoff as a standing line-item deliverable, a change-order clause so every new ask re-prices scope and time, and a kill-fee/cancellation clause (e.g., 30 days' notice or pay-for-work-completed-to-date). The retainer floor is the margin backbone; the milestone staging is the buyer's exposure cap; the change order is the scope-creep firewall.

On outcome-based: keep it as optional, capped upside layered on top of a guaranteed floor — never the backbone, and never pure. The evidence is clear that pure contingency hands a solo all the execution and attribution risk with no bench to absorb a miss and a cash-flow profile that can't survive a 30-90 day unpaid verification window. If a buyer pushes for skin-in-the-game beyond the guarantee, offer a hybrid: the full $15K/mo retainer floor stays, plus a small success kicker (10-25% of a single, pre-agreed, attributable metric the buyer signs off on as caused by the build), capped at a defined ceiling, and only where a clean baseline exists. For most first data/agent engagements the outcome is a step removed from revenue (a reliable pipeline, a working eval harness, a deployed agent), so attribution is contestable and the kicker should be the exception, not the default. The money-back guarantee on the pilot already gives the buyer the de-risk that outcome-based promises, without exposing solo margin to a metric RDCO doesn't fully control.

The solo-vs-studio answer, in contract terms. Buyers read a solo as senior-does-the-actual-work (the studio's biggest grievance, "senior pitch, junior delivery," is structurally impossible solo) — a feature for a deep single-discipline build. The lone liability is bus-factor/continuity, and every neutralizer is a contract clause RDCO offers unprompted: milestone staging caps exposure at any single point; the money-back guarantee caps downside on the trial; code-plus-documentation handoff as a standing deliverable means the buyer is never stranded; and for a genuinely nervous first enterprise buyer, offer third-party milestone escrow proactively (Escrow.com-style, funds release per accepted milestone). Offering these before they are asked for flips the script: the solo stops being the risky default that needs excusing and becomes the operator confident enough to put the downside in writing. The studio buys safety with a bench the buyer pays for; RDCO buys it with structure the buyer keeps.

Net contract recipe: paid fixed-fee pilot (guaranteed, credited) → 90-day-min retainer at $15K/mo, milestone-staged with 5-day acceptance windows, change-order + kill-fee clauses, code+docs handoff as a deliverable, escrow offered on request, and outcome-based confined to an optional capped kicker on a pre-agreed attributable metric. Keep it build-shaped; the whole structure degrades the moment it becomes an open-ended seat.

Open follow-ups

Related

Sources

Vault:

Web (accessed 2026-06-07):