One GitHub login away.
Opening shortly.
One GitHub login away.
Opening shortly.
For competition teams at the final stage
Judges — like all of us — decide through stories. The winning ones are carried by evidence: asserted numbers read as pitch, tied numbers make your story unbeatable. This is the guide for your last stage: upload your Stripe / bank CSV and GCP billing export, walk out with a judge-ready cash-basis P&L on the competition's evidence shape — every total equal to the sum of its own monthly column — plus a Viability Report your numbers can actually defend. We name gaps; we never plug them.
Deterministic parsing first; Gemini for the messy tail. Every number traceable to a source row.
The success state looks like this: a green tie-out banner over your own P&L, an in-band RateCard verdict beside it, and every uncomputable metric named instead of hidden. That artifact is what survives a judge's reconciliation.
The list-price anchor below is recomputed component by component — it is not a marketing number. See the arithmetic.
The one artifact every team already has. Pick it or paste it; the mock judge returns a scorecard with file citations, organized by the three judging criteria. Sign in with GitHub to unlock.
One click, then pick your repo — private repos included. Your GitHub token stays on the server, session-scoped with a short expiry; it never reaches this page and is never stored in your scan.
GitHub: signed in as
Skipping the repo? Fine — the CSV paths in step 2 work on their own. Every card below carries ONE evidence-source chip: detected (in code) · estimated (modeled, assumptions shown) · declared (your edit) · measured (artifact attached) — and reconciled is earned only when independent sources agree.
Attach, don't type: paste CSV text or choose files. Any subset works. Every total equals the sum of its own monthly column; every source row is accounted for. Rows we can't classify go to a review list you resolve with explicit marks — declared, never inferred. Sign in with GitHub to unlock.
Revenue from team members, family, related entities or pre-existing relationships must be disclosed separately per the competition rules. Declaring it here is what makes your arms-length line defensible.
Defaults to the competition's May–Aug 2026 window. Rows dated outside it are excluded from every total and listed separately — never silently dropped. Widen it to see your full history.
Describe your agents; everything is computed from your declared parameters and your generated P&L. Uncomputable metrics are named, not hidden. Sign in with GitHub to unlock.