pricing-sheet

Drivers & horizon

The declared revenue target for the teacher storefronts is five hundred dollars per site, and progress against it is reported only from a session that actually returned its totals, never from an estimate. domains/finance-ops.xml:182-182

Checkout prices never come from the request: the client sends only a product and an interval, and the function looks up the price in a generated map, so a visitor cannot name a price of their own. domains/finance-ops.xml:183-183

The finance view of GCBC reports only measured Stripe figures and founder-ratified prices, and an unreachable payment surface is reported as unmeasured with exit code three, never presented as a reading of zero dollars. domains/finance-ops.xml:188-188

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

Drivers & horizon for Pricing sheet. Customer ask centers on a Pricing sheet for GCBC. Tiers, discounts, margin after delivery. You get: What you charge. Raw ask: Build a Pricing sheet for GCBC.

Detail for Drivers & horizon: this Pricing sheet stays locked to a Pricing sheet. 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 Pricing sheet appears in the working lines, not only the title.

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

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

Unit economics

GCBC Individual is priced at 299 dollars per month, the founder-ratified price recorded in the offer node, and the Stripe price and product behind it were read back from the live API and verified active. domains/finance-ops.xml:173-173

GCBC Professional is priced at 2,499 dollars per month, the founder-ratified price recorded in the offer node, with its Stripe price and product read back from the live API and verified active. domains/finance-ops.xml:174-174

GCBC Elite is priced at 4,999 dollars per month, the founder-ratified price recorded in the offer node, with its Stripe price and product read back from the live API and verified active. domains/finance-ops.xml:175-175

Measured monthly recurring revenue for GCBC on 2026-09-24 was zero dollars, read from Stripe in read-only mode by check-subscription-lifecycle with the revenue flag, using only the prices the checkout map lists under gcbc products. domains/finance-ops.xml:176-176

One paid one-time beta checkout session exists and it grossed zero dollars, so no beta revenue has been collected; the beta is a single payment for ninety days that does not renew and has nothing to cancel. domains/finance-ops.xml:178-178

Unit economics for Pricing sheet. Customer ask centers on a Pricing sheet for GCBC. Tiers, discounts, margin after delivery. You get: What you charge. Raw ask: Build a Pricing sheet for GCBC.

Detail for Unit economics: this Pricing sheet stays locked to a Pricing sheet. 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 Pricing sheet appears in the working lines, not only the title.

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

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

Cash & runway

D57 triple required on every payment (known gap: tax-accrual daemon not yet emitting per-accrual); historian flags missing attribution; live-file truth over stale sources — flag rather than serve wrong data. domains/finance-ops.xml:15-15

Monarch BALANCES CSV export (programmatic login DEAD, HTTP 405 — CSV is the live runway path) · Stripe charge.succeeded · Plaid feed (19 accounts) · Coinbase JWT portfolio · Notion bills DB · budget.json. domains/finance-ops.xml:11-11

Every subscription plan starts with a seven-day free trial, and no card is collected until the trial converts, because the checkout session is created with payment method collection set to if required rather than always. domains/finance-ops.xml:179-179

Annual pricing is withdrawn: no annual price, annual button or annual Stripe price is offered on any page until the founder ratifies one again; every tier is sold monthly. domains/finance-ops.xml:180-180

Cash & runway for Pricing sheet. Customer ask centers on a Pricing sheet for GCBC. Tiers, discounts, margin after delivery. You get: What you charge. Raw ask: Build a Pricing sheet for GCBC.

Detail for Cash & runway: this Pricing sheet stays locked to a Pricing sheet. 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 Pricing sheet appears in the working lines, not only the title.

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

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

Pricing & margin

Zero missed bills · zero untracked tax events · daily budget report delivered by 06:00 PT · variances escalated before they compound. domains/finance-ops.xml:18-18

GCBC is licensed per person for Individual and per organization for Professional and Elite, pay monthly or take the annual license, and it is never priced per seat under any plan the offer node sells. domains/finance-ops.xml:184-184

Renewal is disclosed beside every price on the live page, and property P21 verifies in a real browser that each buyable tier states renewal at exactly the price the offer node declares for every interval it sells. domains/finance-ops.xml:185-185

Pricing & margin for Pricing sheet. Customer ask centers on a Pricing sheet for GCBC. Tiers, discounts, margin after delivery. You get: What you charge. Raw ask: Build a Pricing sheet for GCBC.

Detail for Pricing & margin: this Pricing sheet stays locked to a Pricing sheet. 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 Pricing sheet appears in the working lines, not only the title.

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

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

Plan vs actual

Source stale/evicted → flag, never serve; failure fallback = halt discretionary pay; circuit-open (5 fails / 60s) publishes an incident report and surfaces to the founder queue. domains/finance-ops.xml:16-16

Six GCBC subscriptions have ever been created and all six are canceled; all six were on the Individual monthly price, so there is no active subscriber and no recurring revenue to report for any tier today. domains/finance-ops.xml:177-177

Teacher storefront revenue could not be read on 2026-09-24 because the TPT, Classful and Gumroad sessions had all expired, and the rule is that a surface which cannot report is red, never counted as zero. domains/finance-ops.xml:181-181

Bill-pay provenance triples required; tax-accrual daemon not yet emitting D57 on every accrual domains/finance-ops.xml:142-142

Plan vs actual for Pricing sheet. Customer ask centers on a Pricing sheet for GCBC. Tiers, discounts, margin after delivery. You get: What you charge. Raw ask: Build a Pricing sheet for GCBC.

Detail for Plan vs actual: this Pricing sheet stays locked to a Pricing sheet. 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 Pricing sheet appears in the working lines, not only the title.

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

Operating note for Plan vs actual: next action is concrete for a Pricing sheet — who does what, by when, and what “done” looks like for this Pricing sheet. Category spine “Plan vs actual” is mandatory; skipping it is a refuse, not a soft omit.

Bound to your ask

FinanceOps — the live finance domain node: identity, inputs, outputs, agents, states, authority, and propagation for the cash spine. domains/finance-ops.xml:6-6

Every GCBC price quotes the founder ratification of 2026-09-03, and no product price may change without a new founder ratification recorded in the offer node, which is the single place prices are allowed to live. domains/finance-ops.xml:186-186

GCBC money is read from Stripe and not from a storefront, because GCBC is sold only through the reaveslabs.ai checkout function, whose webhook records each paid session with its amount, currency and product. domains/finance-ops.xml:187-187

Bound to your ask for Pricing sheet. Customer ask centers on a Pricing sheet for GCBC. Tiers, discounts, margin after delivery. You get: What you charge. Raw ask: Build a Pricing sheet for GCBC.

Detail for Bound to your ask: this Pricing sheet stays locked to a Pricing sheet. 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 Pricing sheet 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 Pricing sheet for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Pricing sheet 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 Pricing sheet — who does what, by when, and what “done” looks like for this Pricing sheet. Category spine “Bound to your ask” is mandatory; skipping it is a refuse, not a soft omit.