Skip to content

Revenue chosen on the Entry board, calculated before OPEX - #60

Merged
sa-anyan merged 1 commit into
mainfrom
e1/revenue-setup
Nov 13, 2026
Merged

sa-anyan merged 1 commit into
mainfrom
e1/revenue-setup

Conversation

@sa-anyan

Copy link
Copy Markdown
Owner

Why

Founder direction: keep the stage order, but replace the free-text Revenue Box with explicit choices on the Entry page. That way the Revenue stage is never ambiguous, and the OPEX lines that are a share of revenue are complete when OPEX runs.

Changes

  • Entry card "How does this project earn money?". The user picks:
    • the sold M&E stream;
    • optionally, the component actually sold, from the stream's parsed components;
    • the product name, price, unit and currency;
    • the operating days and hours.
  • Set-up endpoint. POST /assessments/{key}/revenue-setup (revenue/setup.py) writes the sales lines and the authorising Revenue Box sentence, then approves them through the existing revenue checks. An unpriced item stays unapproved.
  • No pipeline change. The existing economics run (CAPEX, revenue, OPEX, financial) already runs revenue before OPEX. Administration, distribution and sales, R&D and royalties are therefore calculated.
  • Revenue page notice. Changing revenue changes the revenue-based OPEX lines (VCOP), total OPEX and the cash flow. FCOP is unaffected.

Verified

  • Through the UI, on a copy of the founder's Team 8 study:
    • the set-up saved and was approved: "We sell Fungal biomass (stream 14) at 1.2 USD per kg";
    • revenue was 1.71M USD in year 1;
    • OPEX was complete at 837k per year (712k fixed, 125k variable), with the revenue-based lines filled;
    • financial ran.
  • Backend: 4,641 passed, including a new set-up test.
  • Frontend: tsc passes and node tests are 56/56.

🤖 Generated with Claude Code

Founder direction: keep the stage order; replace the free-text Revenue Box
with explicit choices on the Entry page so the Revenue stage is never
ambiguous and revenue-based OPEX lines are complete when OPEX runs.

- Entry card "How does this project earn money?": the user picks the sold
  M&E stream, optionally the component actually sold (from the stream's
  parsed components), product name, price and unit, currency and operating
  hours. POST /assessments/{key}/revenue-setup (revenue/setup.py) writes the
  sales lines and the authorising Revenue Box sentence and approves them
  through the existing revenue checks; an unpriced item stays unapproved.
  Fills missing assumption date and schedule basis; a missing financial
  schedule is returned as a question.
- No pipeline change: the existing economics run (CAPEX, revenue, OPEX,
  financial) already runs revenue before OPEX, so administration,
  distribution & sales, R&D and royalties are calculated.
- Revenue page notice: changing revenue changes the revenue-based OPEX lines
  (VCOP), total OPEX and the cash flow; FCOP is unaffected.

Verified on a copy of the founder's Team 8 study through the UI: set-up
saved and approved ("We sell Fungal biomass (stream 14) at 1.2 USD per kg"),
revenue 1.71M USD year 1, OPEX complete 837k/yr with the revenue-based lines
filled, financial ready. Backend 4,641 passed; frontend tsc and 56/56.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
flowvalue-ai Ready Ready Preview Nov 13, 2026 12:34pm UTC

@sa-anyan
sa-anyan merged commit 7d04643 into main Nov 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant