Repository navigation
Revenue chosen on the Entry board, calculated before OPEX - #60
Merged
Merged
Conversation
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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
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.Verified
tscpasses and node tests are 56/56.🤖 Generated with Claude Code