> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 0007 revenue based label

# User-facing label: "Established Funding" → "Revenue Based"

Status: accepted

Date: 2026-07-09

Operator-visible copy that today says **Established Funding** (or "Established") for the MCA / SBA / BLOC family is renamed to **Revenue Based** in Phase 9e. Workflow / code identifiers stay `established_funding` until a later cleanup.

## Decision

1. **Phase 9e** renames all operator-facing strings for this product family to **Revenue Based** (card titles, approve/confirm dialog, coaching copy, queue/CRM labels, help text in-app). The screenshot surface that currently reads "ESTABLISHED FUNDING" becomes "REVENUE BASED" when MCA / BLOC / SBA rows are split (ADR-0003).
2. **Code and persisted ids stay** for Phase 9: `established_funding` workflow primary, `evaluateEstablished`, `establishedSubVariant`, related schema fields. Glossary documents the split: UX label = Revenue Based; machine id = `established_funding`.
3. A later optional cleanup may rename identifiers; that is out of scope for Phase 9 (wide churn, no operator value).

## Context

Product language is shifting away from "Established" toward revenue-based products (MCA, BLOC; SBA questionnaire-gated). Phase 9e already rewrites the Established card (three rows, Coming Soon SBA CTA, per-product reasons) — bundling the label rename avoids a second pass over the same UI.

## Considered options

* **A — Phase 9e label rename; keep code ids (accepted).**
* **B — Separate label-only PR before Phase 9** — rejected; same surfaces get touched again in 9e.
* **C — Defer rename entirely** — rejected; operators would see a redesigned card still titled Established.

## Consequences

* Mintlify / help docs that say "Established Funding" should be updated in the same Phase 9e PR or an immediate follow-up doc PR — do not leave public docs on the old name after the app ships.
* AI prompts / narration that say "established" for operator-facing prose should use "revenue based" where the audience is the operator; internal coaching path codes may keep `established_*` until the id cleanup.
* Glossary: CONTEXT.md → "Revenue Based (UX label)". System reference: `docs/design/underwriting.md` §7.