sales-proposal

Buyer & stakes

DesignSystem — an honestly-declared PLANNED product-domain stub (owner founder, T2): a declaration, not a live domain. domains/design-system.xml:6-6

Reaves Labs Site — the site anatomy node; every page is a projection FROM it, never edited directly. domains/reaveslabs-site.xml:9-9

Lives in ~/RLL, git-tracked, brain-indexed; the pattern repeats for every product and system node. domains/reaveslabs-site.xml:16-16

GTM Model — a revenue domain node; decks, PRD sections, CRM seeds, and outreach templates project FROM it. domains/gtm-model.xml:12-12

All deal economics (tranches, 60-month RBF, tiers, pricing $7/$10/$15) live in investment-terms.xml — never restated here. LLC structure is a FEATURE: pass-through losses flow to investors; membership units + notes work cleanly; C-corp convert available later (~$8-15K) if a SAFE/QSBS investor requires it. domains/gtm-model.xml:49-49

Buyer & stakes for Sales proposal. Customer ask centers on a Sales proposal for GCBC. Offer answered to a buyer’s needs. You get: A yes/no document. Raw ask: Build a Sales proposal for GCBC.

Detail for Buyer & stakes: this Sales proposal stays locked to a Sales proposal. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Sales proposal appears in the working lines, not only the title.

Evidence for Buyer & stakes: where a number or rule is stated, it must be re-checkable against your ask (“Build a Sales proposal for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Sales proposal could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Buyer & stakes: next action is concrete for a Sales proposal — who does what, by when, and what “done” looks like for this Sales proposal. Category spine “Buyer & stakes” is mandatory; skipping it is a refuse, not a soft omit.

Offer & scope

Your company, compiled. Ask it anything and get the line the answer came from. domains/reaveslabs-site.xml:36-36

Reaves Labs & Learning builds products people learn with, tools we build and run, and engagements you can hire us for — across Education, Finance, AI & Engineering, and Life Skills. domains/reaveslabs-site.xml:37-37

Deterministic AI. We use the components that make modern AI work — retrieval, structure, learned representations — without the sampled step that guesses. Every answer is computed and cites its source; every build is a compile, not a generation. domains/reaveslabs-site.xml:39-39

Two tracks, one adventure: Math (the prerequisite) unlocks Financial Literacy. 72 free modules, K-12, mastery proven not assumed. domains/reaveslabs-site.xml:74-74

The digital network that controls and coordinates your physical robots, plus the platform to build them — with a human always in the loop. domains/reaveslabs-site.xml:191-191

Offer & scope for Sales proposal. Customer ask centers on a Sales proposal for GCBC. Offer answered to a buyer’s needs. You get: A yes/no document. Raw ask: Build a Sales proposal for GCBC.

Detail for Offer & scope: this Sales proposal stays locked to a Sales proposal. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Sales proposal appears in the working lines, not only the title.

Evidence for Offer & scope: where a number or rule is stated, it must be re-checkable against your ask (“Build a Sales proposal for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Sales proposal could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Offer & scope: next action is concrete for a Sales proposal — who does what, by when, and what “done” looks like for this Sales proposal. Category spine “Offer & scope” is mandatory; skipping it is a refuse, not a soft omit.

Proof & sources

The stub stays honest (planned, never asserted active) and the founder makes the quarterly activation call on true information. domains/design-system.xml:18-18

Declared in the manifest as status="planned"; no live spec/state yet (honest, not a dangling ref). domains/design-system.xml:66-66

Homepage projects 1:1 from the contract with the gate green; a visitor understands what the company does AND that GCBC is the franchise product, in one screen; every other product reads as coming-soon without a claim it cannot carry; careers elevated per signed intent. domains/reaveslabs-site.xml:21-21

Every answer names the file and line it came from; every refusal names the contract line that broke. It is a property of the architecture, so it cannot regress, and a sampled model can never offer it about itself. domains/reaveslabs-site.xml:41-41

Answers are retrieval plus verbatim citation — no inference cost and nothing to hallucinate. As token economics tighten, an answer that costs nothing to generate and cannot be invented is a lasting cost and trust advantage. domains/reaveslabs-site.xml:42-42

Proof & sources for Sales proposal. Customer ask centers on a Sales proposal for GCBC. Offer answered to a buyer’s needs. You get: A yes/no document. Raw ask: Build a Sales proposal for GCBC.

Detail for Proof & sources: this Sales proposal stays locked to a Sales proposal. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Sales proposal appears in the working lines, not only the title.

Evidence for Proof & sources: where a number or rule is stated, it must be re-checkable against your ask (“Build a Sales proposal for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Sales proposal could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Proof & sources: next action is concrete for a Sales proposal — who does what, by when, and what “done” looks like for this Sales proposal. Category spine “Proof & sources” is mandatory; skipping it is a refuse, not a soft omit.

Objections & next step

If any surface or report treats this domain as operating, flag it as a violation. If ownership of the informal duty becomes ambiguous, escalate; if authority is uncertain, route to the founder queue (D57). domains/design-system.xml:16-16

Stages are stated honestly: in development means in development. GCBC is the only product available today; nothing else on this page is for sale or claims an outcome yet. domains/reaveslabs-site.xml:274-274

Product KB nodes (products/xml/*.xml via kb-ref) · founder directives (brand icons 2026-07-16) · state/decisions (Reaves Academy domain cutover 2026-07-15). domains/reaveslabs-site.xml:612-612

LOAD failures from declared origins are tolerated (environmental DNS filters/ad-blockers); undeclared origins still fail. Post-CNAME the try-demo trigger flips per the 2026-07-15 decision record. Hidden sections (rll-city) are declared hidden, not deleted. domains/reaveslabs-site.xml:19-19

Nothing in this list is for sale, and none of it has a date. When one of them can be verified the way GCBC can, it gets a name and a price on this page. domains/reaveslabs-site.xml:639-639

Objections & next step for Sales proposal. Customer ask centers on a Sales proposal for GCBC. Offer answered to a buyer’s needs. You get: A yes/no document. Raw ask: Build a Sales proposal for GCBC.

Detail for Objections & next step: this Sales proposal stays locked to a Sales proposal. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Sales proposal appears in the working lines, not only the title.

Evidence for Objections & next step: where a number or rule is stated, it must be re-checkable against your ask (“Build a Sales proposal for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Sales proposal could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Objections & next step: next action is concrete for a Sales proposal — who does what, by when, and what “done” looks like for this Sales proposal. Category spine “Objections & next step” is mandatory; skipping it is a refuse, not a soft omit.

Close criteria

D58 measurement integrity: reported as planned, never asserted active; the denylist forbids claiming the domain operates before it is built. domains/design-system.xml:15-15

Homepage projects 1:1 from the contract with the gate green; visitors understand the company; Reaves Academy demos reachable as the live proof; careers elevated per signed intent. domains/reaveslabs-site.xml:610-610

verify-projection.mjs renders index.html and proves every declared section present and no undeclared top-level section[id]; product stages stay honest (demo vs coming-soon); undeclared third-party origins fail the gate. domains/reaveslabs-site.xml:18-18

~$150K revenue-based financing converting to equity, tiny teams selling to US PreK-12 — near-perfect structural match. Track down by name. domains/gtm-model.xml:242-242

Close criteria for Sales proposal. Customer ask centers on a Sales proposal for GCBC. Offer answered to a buyer’s needs. You get: A yes/no document. Raw ask: Build a Sales proposal for GCBC.

Detail for Close criteria: this Sales proposal stays locked to a Sales proposal. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Sales proposal appears in the working lines, not only the title.

Evidence for Close criteria: where a number or rule is stated, it must be re-checkable against your ask (“Build a Sales proposal for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Sales proposal could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Close criteria: next action is concrete for a Sales proposal — who does what, by when, and what “done” looks like for this Sales proposal. Category spine “Close criteria” is mandatory; skipping it is a refuse, not a soft omit.

Bound to your ask

Founder decides whether to activate this domain or keep brand/UI inside product surfaces. domains/design-system.xml:78-78

Emit activity log + health (GREEN/YELLOW/RED) to the historian chain; push blockers to the steward and the founder queue. domains/outreach.xml:140-140

Report the primary KPI trend up the chain; close or escalate every open task in the domain. domains/outreach.xml:141-141

Status + blockers + KPI delta delivered to the founder queue; nothing requires the founder during daily ops except escalations. domains/outreach.xml:149-149

Bound to your ask for Sales proposal. Customer ask centers on a Sales proposal for GCBC. Offer answered to a buyer’s needs. You get: A yes/no document. Raw ask: Build a Sales proposal for GCBC.

Detail for Bound to your ask: this Sales proposal stays locked to a Sales proposal. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Sales proposal appears in the working lines, not only the title.

Evidence for Bound to your ask: where a number or rule is stated, it must be re-checkable against your ask (“Build a Sales proposal for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Sales proposal could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Bound to your ask: next action is concrete for a Sales proposal — who does what, by when, and what “done” looks like for this Sales proposal. Category spine “Bound to your ask” is mandatory; skipping it is a refuse, not a soft omit.