Home โ€บ Blog โ€บ The Maestro ยท Part 18
The Maestro ยท Part 18 ยท Phase 4 ยท ๐Ÿ’ผ Founder hat

The Scorecard

Eighteen months ago Gopala wrote down an idea, its hypotheses and the conditions that would kill it. Now he grades himself against them. This final part compares the plan with what happened, line by line, with a script; checks the runway and the path to break-even; asks which of Part 1's hypotheses held; lists what he would do differently; and sketches what comes next: Maestro-2, a larger team, and the localised and frontier-scale versions of this story the site will tell later.

FL
FrontierAGI Team
๐Ÿ’ผ Founder๐Ÿ”ฌ Researcher๐Ÿ“Š Analyst๐Ÿ’ป Coder
โš ๏ธ How to read this (as of 30 Oct 2026) Plan figures come from the scripts in earlier parts. scorecard.py and runway.py were run (real output below); every outcome they grade is the scenario, and revenue growth is our assumption. Gopala and his company are a teaching story; nothing here reports a real company's results. Disclosure: Claude, made by Anthropic, helps write this site.

1. Mission log: month 18

Week 78 ยท The review
  • Writes scorecard.py and runway.py; reviews the plan with investors and the two new hires.
Week 78 ยท Decisions
  • Raises a seed extension or series A in month 22โ€“24 (section 5); approves Maestro-1.1 work; defers Maestro-2.

2. Plan vs outcome

scorecard.py ยท Python 3, no dependencies; scenario outcomes
"""scorecard.py โ€” plan vs outcome after 18 months (Part 3's plan vs the story).

Plan numbers are from earlier parts' scripts; outcomes are the SCENARIO.
A line is green within 10% of plan, amber within 25%, red beyond.
"""
ROWS = [  # name, plan, outcome, unit, higher_is_better
    ("Training compute spent", 8.1, 8.4, "$M", False),
    ("Main run duration", 31.4, 32.5, "days", False),
    ("Months to first partner use", 4, 4.5, "months", False),
    ("Months to Maestro-1 release", 13, 13.5, "months", False),
    ("Release-set improvement over Maestro-0", 4.0, 5.1, "points", True),
    ("Loop updates approved by the gate", 12, 7, "updates", True),
    ("Paying customers at month 18", 12, 9, "customers", True),
    ("Monthly burn", 318, 352, "$k", False),
]

def rag(plan, out, hib):
    d = (out - plan) / plan if hib else (plan - out) / plan
    return "G" if d >= -0.10 else ("A" if d >= -0.25 else "R")

def main():
    counts = {"G": 0, "A": 0, "R": 0}
    for name, plan, out, unit, hib in ROWS:
        r = rag(plan, out, hib); counts[r] += 1
        print(f"[{r}] {name:40s} plan {plan:7.1f} {unit:9s} outcome {out:7.1f}")
    print(f"green {counts['G']}, amber {counts['A']}, red {counts['R']}")

if __name__ == "__main__":
    main()
$ python3 scorecard.py # outcomes are the story's, plans from Parts 3โ€“12 [G] Training compute spent plan 8.1 $M outcome 8.4 [G] Main run duration plan 31.4 days outcome 32.5 [A] Months to first partner use plan 4.0 months outcome 4.5 [G] Months to Maestro-1 release plan 13.0 months outcome 13.5 [G] Release-set improvement over Maestro-0 plan 4.0 points outcome 5.1 [R] Loop updates approved by the gate plan 12.0 updates outcome 7.0 [A] Paying customers at month 18 plan 12.0 customers outcome 9.0 [A] Monthly burn plan 318.0 $k outcome 352.0 green 4, amber 3, red 1

The 18-month scorecard (scenario)

Green: within 10% of plan4 lines
Amber: within 25%3 lines
Red: worse than 25%1 line

Real output of scorecard.py on the story's outcomes.

3. Did the hypotheses hold?

Hypothesis (Part 1)EvidenceVerdict (scenario)
H1 ยท Skills transfer: retrieving verified skills raises success on new held-out tasksPart 2 small-scale results; retrieval in production agents with a library well past 1,000 skillsHeld, modestly
H2 ยท Folding skills into weights beats the same compute on generic code dataRelease-set gain of Maestro-1 over Maestro-0 (Part 12)Partly held; hard to separate from the new base model
H3 ยท The gate catches bad changesGamed and regressing updates rejected (Part 11); injected bad skills caught in red-team tests (Part 13)Held, at a cost in speed
The moat: verified data competitors cannot downloadLibrary of ~2,200 skills, partner agreementsToo early to tell

4. The kill criteria, revisited

5. Cash, runway and break-even

runway.py ยท Python 3, no dependencies; scenario revenue
"""runway.py โ€” cash after 18 months and the path to the next raise.

Starts from the $20M seed (Part 3). Spend by phase from the story's
Mission Control; revenue from SCENARIO customers growing per month.
"""
RAISE = 20.0
SPENT_18M = 12.6                 # $M, scenario total through month 18
BURN = 0.352                     # $M per month after month 18 (scenario)
REV_M18 = 0.11                   # $M monthly revenue at month 18 (scenario)
GROWTH = 0.12                    # monthly revenue growth (assumption)

def main():
    cash = RAISE - SPENT_18M
    print(f"cash at month 18: ${cash:.1f}M of ${RAISE:.0f}M")
    rev, m = REV_M18, 18
    while cash > 0 and m < 60:
        m += 1; rev *= 1 + GROWTH; cash -= max(0, BURN - rev)
        if rev >= BURN:
            print(f"break-even on monthly burn at month {m} with ${cash:.1f}M left"); break
    else:
        print(f"cash runs out at month {m}")
    for g in (0.06, 0.09, 0.12, 0.15):
        cash, rev, m = RAISE - SPENT_18M, REV_M18, 18
        while cash > 0 and rev < BURN and m < 80:
            m += 1; rev *= 1 + g; cash -= BURN - rev
        print(f"  growth {g:.0%}/month: {'break-even' if rev >= BURN else 'out of cash'} at month {m}")

if __name__ == "__main__":
    main()
$ python3 runway.py # scenario revenue and burn cash at month 18: $7.4M of $20M break-even on monthly burn at month 29 with $6.0M left growth 6%/month: break-even at month 38 growth 9%/month: break-even at month 32 growth 12%/month: break-even at month 29 growth 15%/month: break-even at month 27

Months to break-even by monthly revenue growth (scenario)

6% a monthmonth 38
9% a monthmonth 32
12% a monthmonth 29
15% a monthmonth 27

Real output of runway.py; growth rates are assumptions.

6. Try the runway

Runway after month 18 (our model)

7. Where the money went

Spend through month 18 by phase (scenario, $M)

Phase 0 ยท idea$0.01M
Phase 1 ยท machine$0.95M
Phase 2 ยท model$5.3M
Phase 3 ยท proving$1.1M
Phase 4 ยท shipping$5.2M

From Maestro Mission Control (scenario figures).

8. What he would do differently

9. Ten lessons from wearing every hat

10. What comes next

The next 18 months (plan)

๐Ÿ”Maestro-1.1More loop cycles, new task types to beat saturation
๐Ÿ’ฐRaiseMonths 22โ€“24, to fund Maestro-2
๐Ÿ—๏ธMaestro-2Larger MoE; near the EU 1e25 FLOP presumption (Part 14)
๐Ÿ‘ฅTeam of ~15Separate safety, security and research leads

Plans, not results.

11. The numbers he will report from now on

MetricWhySource
Solved tasks per monthValue deliveredProduct telemetry (Part 16)
Cost per solved taskMargin and pricingServing and sandbox costs (Part 15)
Accepted-change rate with intervalQuality as clients see itPilots and production (Part 12)
Verified skills per cycleHealth of the flywheelLoop records (Part 17)
Gate approval rateSpeed of improvementGate log (Part 11)
Error-budget burnReliabilitySLO dashboards (Part 17)
Runway in monthsSurvivalFinance (runway.py)

12. What the job looks like now

13. If you are building something like this

14. The risk register at month 18

RiskStatusNext step
Flywheel saturationWatch: gains per cycle smallNew task types; track skills per cycle
Competition from large labsHighDepth in client repositories, trust evidence
Customer concentrationMedium: three partners are a large share of revenueBroaden pilots
Regulatory changeLow today; rises with Maestro-2 scaleRe-run ai_act_check.py before training
Key personReducedSecond gate reviewer, documented processes
Compute pricesMediumRenewal options and a second provider (Part 4)

15. The investor update, in five lines

16. Seven founder mistakes the scorecard caught

17. Delegation box

๐Ÿ™‹ Gopala himself
  • The scorecard and the decisions it drives
  • Fundraising
  • The research agenda for Maestro-2
๐Ÿค– AI agents
  • Assembling the scorecard data from every system
  • Drafting the investor update
  • Scenario analysis on growth and burn
๐Ÿค Bought, rented or borrowed
  • Investors and advisers for the review
  • The first two hires running operations
  • Counsel for the next financing

18. Budget and risk tracker

ItemStatus after Part 18Note
Spend to date~$12.6M of $20M (scenario)Through month 18
Scorecard4 green, 3 amber, 1 redLoop updates behind plan
Runway$7.4M; break-even ~month 29 at 12% growthOur model
Strategy riskWatchFlywheel slower than pitched
Cash riskLowRaise planned from strength
Competition riskHighLarger labs ship agents too

19. The series

The Maestro: 18 parts in five phases

Verdict
  • Eighteen months, eighteen parts, every hat: an idea tested small, a machine rented and verified, a model trained from scratch, proved and approved, and products shipped to paying clients.
    • The scorecard is honest: the plan held where it was built from arithmetic and slipped where it relied on hope.
    • That is the Maestro series.
    • Thank you for reading; see it all on Maestro Mission Control.

20. Reading the numbers

Primary / standard
Plan figures from earlier parts' scripts (budget.py, failure_budget.py, evaluation and gate scripts).
Secondary โš ๏ธ
None in this part.
Our assumptions
All outcomes, revenue, growth, burn, spend by phase, hires and plans.