Home โ€บ Blog โ€บ The Maestro, Season 2 ยท Part 18
The Maestro, Season 2 ยท Part 18 ยท Phase 8 ยท ๐Ÿข CEO hat

Enterprise Adoption

Engineers loved the pilots. Then the security teams arrived, and deals that looked certain went quiet for months. This part follows the company's first year of selling to large enterprises: a funnel that loses most of its value in one stage, a ten-item questionnaire, and the discovery that the most persuasive sales material was the paperwork written for the EU.

FL
FrontierAGI Team
๐Ÿ’ผ CEO๐Ÿค Sales๐Ÿ” Security
โš ๏ธ How to read this (as of 4 Nov 2026) Gopala's company is a teaching scenario. deal_cycle.py and security_review.py were run (real output below). Conversion rates, durations, contract values and the questionnaire status are scenario numbers; the questionnaire items are the kind enterprise security teams commonly ask AI vendors. Ideas from the owner's startup notes are labelled. Disclosure: Claude, made by Anthropic, helps write this site.

1. Month 44: the deal that went quiet

๐Ÿ“– The story

Daniel Okafor had sold enterprise software for fifteen years, and he knew the sound of a deal going quiet. The pilot at the logistics company had been the best they had run: three teams, four weeks, sixty percent of Maestro's changes merged. The engineering director had sent a thank-you note.

Then the security questionnaire arrived. Two hundred and twelve questions. Daniel forwarded it to Arjun with a single line: We need this back in ten days or we lose them.

It took twenty-three. They did not lose the logistics company, but they lost three others that month in exactly the same place.

๐Ÿ”ฌ In plain words: enterprise sales cycle Large companies buy software in stages. Engineers test it in a pilot. A security review checks how it handles data, access and incidents. Procurement negotiates the contract. Each stage can stop the deal, and they happen one after another, so a good product can still take most of a year to sell.

2. The map: from a first meeting to a signature

๐Ÿ•ธ๏ธ Where enterprise deals are won and lost

or click any node

The funnel across the top, the questionnaire underneath, and trust as the thing every stage is really testing.

3. The funnel

deal_cycle.py ยท Python 3, no dependencies; scenario rates
"""deal_cycle.py โ€” why enterprise revenue arrives late.

A funnel of enterprise opportunities moves through pilot, security review,
procurement and rollout. Each stage has a conversion rate and a duration.
Rates, durations and contract sizes are SCENARIO assumptions.
"""
STAGES = [("first meeting -> pilot", 0.40, 4), ("pilot -> security review", 0.65, 8), ("security review -> procurement", 0.70, 10), ("procurement -> signed", 0.80, 8)]

def main():
    n, weeks = 100.0, 0
    for name, r, w in STAGES:
        n *= r; weeks += w; print(f"{name:32} {r:4.0%}  {w:2} wk   {n:5.1f} of 100 left, week {weeks}")
    acv = 420_000
    print(f"\n{n:.1f} signed per 100 opportunities after {weeks} weeks; ${n * acv / 1e6:.1f}M ACV at ${acv / 1e3:.0f}k each")
    print(f"security review alone takes {STAGES[2][2]} of {weeks} weeks and loses {1 - STAGES[2][1]:.0%} of deals")

if __name__ == "__main__":
    main()
$ python3 deal_cycle.py # 100 opportunities through four stages first meeting -> pilot 40% 4 wk 40.0 of 100 left, week 4 pilot -> security review 65% 8 wk 26.0 of 100 left, week 12 security review -> procurement 70% 10 wk 18.2 of 100 left, week 22 procurement -> signed 80% 8 wk 14.6 of 100 left, week 30 14.6 signed per 100 opportunities after 30 weeks; $6.1M ACV at $420k each security review alone takes 10 of 30 weeks and loses 30% of deals

100 opportunities, 30 weeks

First meeting100
Pilot40
Security review26
Procurement18.2
Signed14.6 ยท $6.1M ACV

Real output. Security review takes 10 of the 30 weeks and loses 30% of the deals that reach it.

4. The questionnaire

security_review.py ยท Python 3, no dependencies; common questionnaire items, scenario status
"""security_review.py โ€” what enterprise security teams ask, and the gaps.

Items common in enterprise security questionnaires for AI vendors, with the
status at month 42 and weeks to close each gap. Status and weeks are SCENARIO.
"""
ITEMS = [("SOC 2 Type II report", "in progress", 16), ("SSO / SCIM", "done", 0), ("audit logs of every agent action", "done", 0),
         ("data residency (EU region)", "gap", 10), ("no training on customer code by default", "done", 0), ("customer-managed keys", "gap", 8),
         ("model card + EU AI Act status", "done", 0), ("agent permission scopes per repo", "done", 0), ("pen-test report (last 12 months)", "gap", 6),
         ("incident response SLA", "done", 0)]

def main():
    for n, s, w in ITEMS: print(f"{n:42} {s:12} {('+' + str(w) + ' wk') if w else ''}")
    gaps = [i for i in ITEMS if i[1] != "done"]
    print(f"\n{len(ITEMS) - len(gaps)} of {len(ITEMS)} ready; {len(gaps)} open; longest {max(g[2] for g in gaps)} weeks (run in parallel)")

if __name__ == "__main__":
    main()
$ python3 security_review.py # ready, in progress, gaps SOC 2 Type II report in progress +16 wk SSO / SCIM done audit logs of every agent action done data residency (EU region) gap +10 wk no training on customer code by default done customer-managed keys gap +8 wk model card + EU AI Act status done agent permission scopes per repo done pen-test report (last 12 months) gap +6 wk incident response SLA done 6 of 10 ready; 4 open; longest 16 weeks (run in parallel)

Ten questions every security team asked

Ready (6)SSO/SCIM ยท audit logs of every agent action ยท no training on customer code ยท model card + EU AI Act status ยท permission scopes per repo ยท incident SLA
In progress (1)SOC 2 Type II report: 16 weeks
Gaps (3)EU data residency (10 wk) ยท customer-managed keys (8 wk) ยท pen-test report (6 wk)

Real output. All four open items run in parallel; the longest is SOC 2 at 16 weeks.

๐Ÿ“– The story

Hana noticed it first. Half the questions that took Arjun longest were already answered, in documents nobody in sales had seen: the model documentation and evaluation report written for the AI Act, the incident process, the record of every change the gate had approved or refused.

Daniel turned them into a single trust pack: a forty-page PDF and a live page showing the gate's decisions. The next security review took six weeks instead of ten. We spent two million dollars on compliance, Gopala said at the board meeting, and it turned out to be our best sales asset.

5. Sandbox: fix the security review

๐ŸŽฎ Sandbox: fix the security review

Same funnel as deal_cycle.py; other stages fixed. Scenario numbers.

6. Five mistakes

7. Delegation box

๐Ÿ™‹ Gopala himself
  • The trust pack and what it promises
๐Ÿค– AI agents
  • Drafting questionnaire answers from existing documents
  • Keeping the trust page current
๐Ÿค Bought, rented or borrowed
  • SOC 2 auditor
  • External penetration testers

8. Budget and risk tracker

ItemStatus after Part 18Note
Enterprise funnel14.6% to signature30 weeks
Security review6 of 10 readytrust pack cuts it to ~6 weeks
SOC 2In progress16 weeks
TrustEvidence-ledgate record public to customers

9. The series

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

VerdictEnterprise deals are won in the pilot and lost in the security review. The company's fastest fix was not a new feature but a trust pack built from documents it already had for the EU and the gate. Next: which numbers actually show that customers get value.

10. Reading the numbers

Primary / standard
Enterprise security questionnaire topics (common industry practice: SOC 2, SSO, data residency, encryption keys, penetration tests).
Secondary โš ๏ธ
None in this part.
Our assumptions
Rates, durations, contract values, questionnaire status and story events are the scenario. Owner's notes (Rauch) are a summary, not a transcript.