Home โ€บ Blog โ€บ The Maestro, Season 2 ยท Part 1
The Maestro, Season 2 ยท Part 1 ยท Phase 5 ยท ๐Ÿ’ผ CEO hat

The Second Raise

Season 1 ended at month 18 with Maestro-1 shipped, nine paying customers, $7.4M in the bank and an honest scorecard. Season 2 opens with the decision that shapes everything after it: raise a Series A now, from strength, to pay for a team, a second model and a product that can survive frontier labs. This part follows Gopala from the first investor email to the signed term sheet: the numbers investors ask for in 2026, the data room built from Season 1's records, the deck, the funnel, three term sheets compared line by line with a script, and why he took the one that did not have the highest valuation on its face.

FL
FrontierAGI Team
๐Ÿ’ผ CEO๐Ÿ“Š Analyst๐Ÿค Negotiator๐Ÿ”ฌ Researcher
โš ๏ธ How to read this (as of 2 Nov 2026) investor_metrics.py and series_a.py were run (real output below). Every customer, offer, investor and valuation is the story's scenario; market benchmarks are cited and marked โš ๏ธ when they come from secondary sources. Gopala and his company are a teaching story; nothing here is investment or legal advice, or a report of a real company. Disclosure: Claude, made by Anthropic, helps write this site.

1. Mission log: months 18โ€“22

Week 79 ยท The decision
  • Reads the month-18 scorecard with the two Season 1 hires and the seed investors; decides to raise in months 20โ€“22, not wait for break-even.
Week 82 ยท The data room
  • Turns Season 1's records (run ledger, evaluation reports, gate decisions, model card, release check) into a data room.
Week 86 ยท The process
  • Contacts 64 funds over three weeks; 22 first meetings, 9 partner meetings (scenario).
Week 91 ยท Term sheets
  • Three term sheets; compares them with series_a.py; signs offer A at month 22.

2. Why raise now, not later

3. What investors ask for in 2026

investor_metrics.py ยท Python 3, no dependencies; scenario customers
"""investor_metrics.py โ€” the numbers a Series A investor asks for, from the
story's month-18 customer table (SCENARIO data, not a real company).

Monthly recurring revenue (MRR) per customer at month 6 of their contract
and now; serving cost from Part 15's $1.17 per million tokens.
"""
# name, MRR $k 12 months ago (0 = not a customer yet), MRR $k now, tokens (billions) per month
CUSTOMERS = [
    ("partner-A", 9.0, 14.5, 2.0), ("partner-B", 8.0, 12.0, 1.7), ("partner-C", 6.0, 10.0, 1.4),
    ("pilot-D", 4.0, 3.0, 0.4),   ("E", 0, 16.0, 2.2), ("F", 0, 14.0, 1.9),
    ("G", 0, 14.0, 1.9), ("H", 0, 13.5, 1.8), ("I", 0, 13.0, 1.8),
]
PRICE_PER_M_TOKENS_COST = 1.17      # $ serving cost per million tokens (Part 15)
OTHER_COGS_K = 21.0                 # $k/month: support, integrations, eval runs for customers (scenario)
BURN_K = 352.0                      # $k/month net burn at month 18 (Part 18)
NET_NEW_ARR_K = 12 * (110 - 46)     # ARR added over the last 12 months, $k (scenario)

def main():
    mrr = sum(c[2] for c in CUSTOMERS)
    tokens_cost = sum(c[3] for c in CUSTOMERS) * 1000 * PRICE_PER_M_TOKENS_COST / 1000
    gm = 1 - (tokens_cost + OTHER_COGS_K) / mrr
    old = [c for c in CUSTOMERS if c[1] > 0]
    nrr = sum(c[2] for c in old) / sum(c[1] for c in old)
    top3 = sum(sorted((c[2] for c in CUSTOMERS), reverse=True)[:3]) / mrr
    print(f"MRR now            ${mrr:6.1f}k   ARR ${mrr * 12 / 1000:.2f}M")
    print(f"serving cost       ${tokens_cost:6.1f}k/month for {sum(c[3] for c in CUSTOMERS):.1f}B tokens")
    print(f"gross margin       {gm:6.1%}")
    print(f"net revenue retention (12-month cohort of {len(old)}): {nrr:.0%}")
    print(f"top-3 customer share  {top3:.0%}")
    print(f"burn multiple      {BURN_K * 12 / NET_NEW_ARR_K:.1f}x  (net burn / net new ARR)")

if __name__ == "__main__":
    main()
$ python3 investor_metrics.py # scenario customer table MRR now $ 110.0k ARR $1.32M serving cost $ 17.7k/month for 15.1B tokens gross margin 64.8% net revenue retention (12-month cohort of 4): 146% top-3 customer share 40% burn multiple 5.5x (net burn / net new ARR)

The month-18 numbers an investor sees first (scenario)

$1.32MARR (9 customers)
64.8%gross margin after serving
146%NRR, 4-customer cohort
40%top-3 revenue share
5.5ร—burn multiple

Real output of investor_metrics.py on the story's customer table.

4. The data room: Season 1's records, reused

From records to a data room

๐Ÿ“’Run ledgerPart 10: cost, days, failures
๐Ÿ“Eval reportsPart 12: intervals, not points
๐ŸšฆGate logPart 11: approved and rejected
๐Ÿ“œRelease checkPart 14: GO with evidence
๐Ÿ—‚๏ธData roomone folder per question

The records Season 1 needed for safety and compliance became the evidence for the raise.

5. The deck, slide by slide

The story the deck tells

๐Ÿ˜ŸProblemprivate code, no trust
๐Ÿ’กInsightverified skills + gate
๐Ÿ“Proofbeats open baseline
๐Ÿ’ตTraction$1.32M ARR, 9 customers
๐Ÿ—บ๏ธPlanteam, Maestro-2, platform
๐Ÿ™‹Ask$60M, 30 months

Each step leads to the next question an investor would ask.

6. The process: a funnel, not a meeting

The investor funnel (scenario)

Funds contacted64
First meetings22
Partner meetings9
Diligence5
Term sheets3

Scenario numbers; a narrow funnel is normal for a Series A.

7. A term sheet, in plain words

8. Three offers, compared with a script

series_a.py ยท Python 3, no dependencies; scenario offers and burn
"""series_a.py โ€” three Series A term sheets compared on dilution and runway.

Cap table after the seed and every offer are the story's SCENARIO numbers.
Post-money valuation = pre-money + new money; the option-pool top-up is
taken from the pre-money (the usual 'pool shuffle'), so founders pay for it.
"""
CAP = {"Gopala": 0.66, "seed investors": 0.25, "option pool": 0.09}   # after the seed (scenario)
CASH_M = 7.4                                                          # month 22: cash before the round
# name, new money $M, pre-money $M, pool target after the round
OFFERS = [("A: big fund", 60, 240, 0.12), ("B: strategic", 45, 255, 0.10), ("C: small, fast", 30, 150, 0.10)]
BURN = {22: 0.42, 26: 1.10, 30: 3.40, 36: 1.95}                       # $M/month: team growth (hiring_plan.py), Maestro-2 run months 30-35 (scenario)
REV0, GROWTH = 0.137, 0.08                                            # $M/month at month 22, growth (assumption)

def round_table(new, pre, pool):
    post = pre + new
    inv = new / post
    shuffle = max(0, pool - CAP["option pool"] * (1 - inv))   # extra pool, carved from pre-money holders
    old = 1 - inv - pool
    scale = old / (CAP["Gopala"] + CAP["seed investors"])
    return post, inv, CAP["Gopala"] * scale, CAP["seed investors"] * scale, pool, shuffle

def runway(new):
    """Month when cash falls below 9 months of burn: the latest safe start for the next raise."""
    cash, rev, m, low = CASH_M + new, REV0, 22, CASH_M + new
    while m < 72:
        b = [v for k, v in BURN.items() if m >= k][-1]
        if cash < 9 * (b - rev): return f"low ${low:4.1f}M  raise again by month {m}"
        cash -= max(0, b - rev); rev *= 1 + GROWTH; m += 1; low = min(low, cash)
        if rev >= b: return f"low ${low:4.1f}M  break-even at month {m}"
    return "beyond month 72"

def main():
    print(f"{'offer':16} {'post $M':>7} {'new inv':>7} {'Gopala':>7} {'seed':>6} {'pool':>5}  runway")
    for name, new, pre, pool in OFFERS:
        post, inv, g, s, p, sh = round_table(new, pre, pool)
        print(f"{name:16} {post:7.0f} {inv:7.1%} {g:7.1%} {s:6.1%} {p:5.0%}  {runway(new)}")
    print("pool shuffle in offer A costs Gopala "
          f"{(CAP['Gopala'] * (1 - 60 / 300) - round_table(60, 240, 0.12)[2]) * 100:.1f} points")

if __name__ == "__main__":
    main()
$ python3 series_a.py # scenario offers; growth 8%/month assumed offer post $M new inv Gopala seed pool runway A: big fund 300 20.0% 49.3% 18.7% 12% low $23.6M break-even at month 57 B: strategic 300 15.0% 54.4% 20.6% 10% low $ 8.6M break-even at month 57 C: small, fast 180 16.7% 53.2% 20.1% 10% low $26.5M raise again by month 32 pool shuffle in offer A costs Gopala 3.5 points

Gopala's ownership after each offer (scenario)

A ยท big fund, $60M49.3%
B ยท strategic, $45M54.4%
C ยท small, fast, $30M53.2%

Real output of series_a.py. He starts at 66% after the seed.

9. Try it: dilution and runway

Series A calculator (our model, same rules as series_a.py)

10. The strategic investor trap (scenario)

Scenario
  • Offer B's cloud credits were worth about $8M at list prices, which made its headline look better than A's. Gopala's counsel pointed out that the credits expire in two years and only apply to one provider.

11. The decision and the new board (scenario)

Scenario
  • Gopala signs offer A at month 22: $60M at $240M pre-money, $300M post. After the round he owns 49.3%, the seed investors 18.7%, the new investor 20% and the employee pool 12%.

12. What the $60M buys

Use of funds over 30 months (scenario, $M)

๐Ÿ‹๏ธ Maestro-2 compute reserve ยท $24Mthe run in months 30โ€“35, or a stronger open base if Phase 7 says so
๐Ÿ‘ฅ Team ยท $22M36 hires from hiring_plan.py (S2 Part 2)
๐Ÿ’ฌ Serving and infrastructure ยท $6Mmore customers, more replicas
๐Ÿ“ฃ Go-to-market ยท $4Msales, solutions engineering, marketplace listings
๐Ÿ›ก๏ธ Safety, evaluation and compliance ยท $2.5Mred teams, external evaluations, legal for the EU line (Phase 7)
๐Ÿงฏ Buffer ยท $1.5Mfor things nobody planned

The allocation is the story's plan; Phase 7 may move the compute line.

13. What could go wrong after the money lands

RiskEarly signResponse
Burn ahead of planPeople cost above hiring_plan.py by 10%Freeze non-critical hires for a quarter
Growth below 8%/monthTwo months of slow bookingsRe-run series_a.py; move the Maestro-2 decision
Customer concentrationTop-3 share above 40%Prioritise mid-size regulated customers
Board misalignmentPressure to loosen the gateIndependent director and the written gate rule

14. Eight fundraising mistakes Gopala avoided (or nearly made)

15. Delegation box

๐Ÿ™‹ Gopala himself
  • The raise: story, deck, investor meetings and negotiation
  • Choosing the board and the independent director
  • What will not change (the gate rule)
๐Ÿค– AI agents
  • Building the investor tracker and data-room index
  • Running investor_metrics.py and series_a.py variants
  • Drafting answers to diligence questions for him to check
๐Ÿค Bought, rented or borrowed
  • Counsel for the term sheet and the financing documents
  • An adviser who has raised a Series A in developer tools
  • The seed investors' introductions

16. Budget and risk tracker

ItemStatus after Part 1Note
Cash after the round$67.4M (scenario)Month 22: $7.4M + $60M
OwnershipGopala 49.3% ยท seed 18.7% ยท Series A 20% ยท pool 12%From series_a.py
Board3 seats: CEO, investor, independentSeed lead as observer
Execution riskWatch36 hires to make
Cash riskLowLowest cash $23.6M through Maestro-2
Expectation riskWatchARR expected to roughly triple

17. The series

The Maestro, Season 2: 23 parts in five phases (Season 1: 18 parts)

VerdictThe second raise is won with Season 1's records rather than with a pitch: the evidence that convinced customers and regulators also convinced investors. Gopala picked the offer that funds the plan without a forced raise in the middle of training, read ownership after the pool shuffle rather than the headline, and wrote the gate's independence into the financing. Next: who to hire, and in what order.

18. Reading the numbers

Primary / standard
Carta data on dilution; the NVCA model legal documents for standard terms.
Secondary โš ๏ธ
AI gross-margin benchmarks (ICONIQ, Bessemer) and Series A medians as relayed by secondary sources โš ๏ธ.
Our assumptions
All customers, offers, valuations, funnel numbers, burn and growth are the story's scenario; the calculator is our model.