Ask the bank for a six-week delay to rebuild production-grade before go-live, but only if internal QA hits 99.9% pass rate by week 4 and the bank signs a written addendum confirming acceptance.
- AStart on bank's date with demo as is, harden during pilot2.3
- BAsk for six-week delay to rebuild for production before go-live8.6
- CDon't do it2.4
- DKeep doing what you do now, ignore the pilot0.9
- Confidence
- 9/10
- Support for the plan
- 8.4/10
- Votes
- 6 endorse, 2 endorse with an amendment
- Spread on the pick
- 1 point
Why the board landed here
- A failed pilot with missing audit logs, fallback, and QA is a one-way door, reputation loss with this bank and future banks is irreversible because enterprise AI reliability is table stakes, not differentiating. Wickman seat
- The £60k pilot is purely a reference; its standalone value is negligible versus the £180k+ follow-on pipeline, so losing it destroys the whole business model. Buffett seat
- A six-week delay can be framed as competence if led with the bank’s risk (e.g., audit integrity), not your own unpreparedness, and only if backed by internal QA pass rates ≥99.9% and a camcorder-style plan showing ownership. Thiel seat
- Founder time is the scarcest capital, shipping a shaky demo guarantees fire drills, not learning; rebuilding now buys back 6x founder hours at £62.50/hour versus £150+ later. Martell seat
- In enterprise AI, no one checks output, so if the first demo fails audit or fallback, the bank assumes all output is garbage, and judgment errors are costly and non-retryable. Thiel seat
The minority report
“A demo that breaks under audit isn’t just bad—it’s zero users. You have to make something people want.”
For this view to be right: That the bank will tolerate a broken demo if fixes are fast and visible, this is false in enterprise AI where audit/fallback are table stakes, not features.
Conditions
- Bank signs a written addendum accepting a six-week delay only if production-grade audit logs, fallback, and QA pass rates are delivered before go-live, and the £60k fee is not voided or penalized.
- Internal QA passes at 99.9% on answer quality, audit, and fallback recovery by week 4, tested against real bank data (not synthetic).
- Founder records and shares a camcorder-style plan (per Martell) with one number (99.9% QA pass rate), outcome, and handoff to lead engineer, with lead engineer present, before calling the bank.
- If internal QA pass rate <99% by week 3, pause the ask and rebuild or walk.
- Founder confirms no penalty clauses bind the startup for delay.
- If bank refuses written confirmation before week 1 ends, walk away.
What to do next
- Day 1 Founder and Integrator (or lead engineer) sign off on rebuild plan with weekly QA scorecard (e.g., QA pass rate) and camcorder-style plan recorded with lead engineer present.
- Day 2–3 Ship rebuilt system to internal QA suite; run full test suite against real bank data; capture pass rates; if <95%, pivot to Option C or reshape.
- If ≥95% by week 2, Day 3 Call bank’s technical lead and project lead separately with same ask framed as 'quality assurance', lead with bank’s audit risk, not your own.
- If bank confirms in writing, Day 4 Lock addendum with 99.9% QA threshold and production-grade requirement.
- Week 4 Rebuild complete; QA sign-off recorded; lead engineer certifies system readiness.
- Cheapest test
- Run a full internal QA pass on audit/fallback/answer quality by week 2; if pass rate <95%, pivot to Option C.
- Kill criteria
- If internal QA pass rate <95% by week 2, or bank refuses written confirmation before week 1 ends, pivot to Option C.
- Revisit
- Revisit if bank delays beyond six weeks or insists on 'hardening during pilot', then pivot to Option A only if QA pass rate ≥99.9% by week 2 and bank signs addendum waiving penalties.