06-reference/research

fde equity kicker retainer pricing shape

2026-07-31·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
fde-pricingequity-compensationphdata-constraintscontract-mechanicsrdco-positioning

The equity-kicker question is built on two premises that do not hold, and the real gate is a clause nobody has read

The question

Verbatim: "Does the equity-heavy FDE comp norm open a retainer-plus-equity-kicker pricing shape for early-stage data-team clients, and does that conflict with the phData W-2 / single-client-concentration guardrails?"

Follow-up from the 2026-05-27 FDE-pricing brief, carried forward unresolved through three subsequent briefs. Context: the founder is W-2 at phData (started 2026-05-26, DSA + Technical Account Lead), Florida-based; RDCO is the side entity.

Answer first

No, and do not spend more on this shape. Three findings, in descending order of how much they should change behavior:

  1. The "phData W-2 / single-client-concentration guardrail" has no source. It is a citation loop. The phrase originates in the 2026-05-27 brief's open-follow-up section and is re-cited as an established constraint by [[2026-05-31-fde-scoping-pricing-vs-ai-consultant-framing]], [[2026-06-02-fde-retainer-band-pricing]], and [[2026-06-07-solo-fde-contract-structures]] without any of them ever sourcing it. A vault-wide grep finds no phData document, offer letter, or note establishing such a rule. The only real "single-client concentration" discussion in the vault is [[2026-04-15-commoncog-career-moats-confession]], where it describes Mammoth Growth at ~60% of RDCO revenue as a risk of the 1099 path. Taking the phData W-2 was the resolution of that risk, not the source of it. The compound phrase fused two unrelated things and then hardened into fact across four briefs.

  2. The FDE comp norm provides no "cover" for a vendor equity kicker. The equity-heavy finding is real but is a fact about employment compensation. The report that establishes it explicitly does not cover contractor or consulting engagements (see below). A client's willingness to grant equity to an employee they hire says nothing about a vendor's pricing shape, and the "FDE buyers already expect equity in the picture" line from the parent brief is an inference the underlying data does not support.

  3. The binding constraint is a different, unread clause, and it gates far more than the kicker. [[2026-04-16-client-reporting-automation-one-pager]] (line 102) has carried this open item since April: "Moonlighting clause check — phData's employment agreement may restrict outside consulting work. Need to read it before any client pitch goes out." That gate blocks all paid RDCO client work, cash or equity. Debating the kicker while the base retainer is ungated is optimizing the wrong layer.

Recommendation: drop the equity-kicker thread. Keep the standing cash-only shape from [[2026-06-07-solo-fde-contract-structures]]. Convert the four propagated "check the guardrail" follow-ups into one founder action: read five named clauses (listed below). That is a document read, not a research task.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The honest verdict is that this pricing shape is not worth pursuing, and the more valuable output of the question is the citation failure it exposed. Four briefs across five weeks treated "the phData W-2 single-client-concentration guardrail" as a known constraint. It never was. It was a question mark in an open-follow-ups section that got re-cited as a premise, which is exactly the laundering failure mode the founder catalogued in feedback_workflow_agent_output_integrity (status: proposal read as live fact). The chain is worth retiring explicitly rather than quietly, because three downstream briefs currently carry a constraint that does not exist.

On the merits, even granting a permissive employment agreement, the trade is poor for a side thread. An early-stage advisory-scale grant is small, illiquid, and years from any liquidity event, while the costs land immediately: a §83(b) decision on a 30-day fuse, a 409A-dependent valuation, annual K-1 or reporting overhead, and a standing ownership interest that persists after the engagement ends. Set that against RDCO's actual bottleneck, which [[2026-06-28-productized-consulting-scalable-anchor-transition]] names as founder attention rather than capital. A kicker consumes attention and adds zero throughput. The cash retainer is the right instrument and it is already specified.

The genuinely useful reframe concerns which clause bites. The instinct is to worry about moonlighting, but for equity specifically the sharper exposure is a conflict-of-interest clause. Cash for a one-off engagement is a transaction that closes. Equity converts it into an ongoing ownership position in a third party, and if that client is, becomes, or competes with a phData customer or prospect, that position is a textbook disclosable interest that will surface on any annual COI attestation. Equity does not merely inherit the moonlighting risk; it creates a distinct and longer-lived one. That is a reason to prefer cash independent of what the agreement turns out to say.

Where the answer depends on the signed agreement, it depends entirely. These are the five clauses to check, by their usual headings:

  1. Outside Activities / Outside Employment — is prior written approval required, or only non-interference with duties? Approval-required is the common posture at consultancies and would gate the retainer itself.
  2. Conflict of Interest — does it prohibit, or merely require disclosure of, a financial or ownership interest in a customer, vendor, partner, or competitor? This is the clause that bites hardest on equity.
  3. Proprietary Information and Inventions Assignment (PIIA) — scope test: does it assign inventions "relating to the Company's business" regardless of when or where conceived, or is there a carve-out for work on own time without company resources? A broad version puts RDCO methodology at risk, cash or equity.
  4. Non-solicitation of customers/clients — separate from non-compete and often survives where a non-compete would not.
  5. Corporate opportunity — whether business opportunities arising through the role must be presented to phData first.

Note that Florida law does not help here. The CHOICE Act governs non-competes and garden leave only; ordinary outside-activity and COI obligations are contractual, and the agreement's own text controls.

Why this is in the vault

It retires a fabricated constraint that four FDE-pricing briefs ([[2026-05-27-forward-deployed-engineer-pricing-rdco-framing]], [[2026-05-31-fde-scoping-pricing-vs-ai-consultant-framing]], [[2026-06-02-fde-retainer-band-pricing]], [[2026-06-07-solo-fde-contract-structures]]) currently treat as real, and it redirects the open item from a pricing debate to the concrete unblocking action for RDCO's entire paid-services line: reading five named clauses in the phData agreement, an item open since 2026-04-16.

Open follow-ups

Related

Sources

Vault

Web (fetched and read in this run unless marked)

Follow-ups

  1. In publicly-available US employment agreements at comparable data/AI consulting firms (SEC-filed exhibits, published handbooks), what is the modal text of the "outside activities" and "conflict of interest" clauses, and which formulations actually prohibit holding an ownership interest in a client versus merely requiring disclosure? This is researchable from public filings, is not covered by any existing brief, and gates RDCO's entire paid-services line rather than just the equity question.

(Second candidate withheld: an E&O / advisor-liability question was considered and cut, since it is downstream of a pricing shape this brief recommends dropping.)