I built a shared AI discovery partner for 18 founder teams and rolled it out in two weeks. It held every customer interview, knew every team's business, and coached them on their own evidence. Founders kept it. Coaches rebuilt their workshops around it. I presented it at the GCEC annual conference in October 2026.
Nobody holds 50 interviews in their head. By week two, founders forget what early customers said. Coaches only hear what founders choose to report. By the time coaching happens, the signal has been interpreted twice.
Out-of-the-box AI made it worse. Founders were already using ChatGPT and Claude, but every chat started from zero. They spent their time re-explaining the venture instead of learning from it.
We needed an AI that already knew every team: the business, the method, and what the team learned yesterday.
"We really need to create a centralized mind within our own team just so we can really be on the same page with our understanding of the problem and therefore our vision of the solution."
— Founder, AgoraThe Hardest Design Problem
The hardest problem here was never the AI. It was the range of people who had to use it.
The cohort ran from founders who had been building AI products for years to founders who had never opened a terminal. A system that only works for the top of that distribution is a perk for the already capable. So I set the least technical founder as the design target and let everyone else inherit the same system.
Three decisions followed from that one constraint.
Technical founders run Claude Code in the terminal, connected to Notion over MCP. Everyone else uses Claude in the browser with the Notion connector. Same workspace, same skills, same outputs, different door in.
Duplicate a Notion template, drop in a config file, run one command. Nothing else stands between a founder and a working system.
Claude reads the team's context, initializes it if empty, and installs any missing skills before the founder types a word. A founder's first interaction is a working system, not an empty prompt box.
The result was near-universal adoption across the cohort with almost no technical issues. For a two-week program where every hour counts, the reliability was a design outcome, not an accident.
How It Works
Each team gets a Notion workspace: the Discovery Records Manager with every interview, a versioned Business Model Canvas, workshop outputs, the written methodology, and a Context Log. Claude reads it through MCP. Storage and reasoning stay separate, so every answer traces back to a source.
Ten custom skills turn the Institute's discovery methodology into one-command workflows. /discovery-ladder maps a team's evidence for one customer and one problem. /customer-journey drafts a journey from the team's own interviews. /interview-feedback shows founders, quote by quote, where they led the witness or started pitching. Skills live as Notion pages that Claude installs, so one update reaches every team.
The AI never tells founders what to do. It never validates, never celebrates, and never offers next steps unprompted. It surfaces evidence and flags contradictions, the same way our coaches coach instead of consult.
The methodology itself, the Discovery Ladder and its scoring rubrics, was developed by my colleague at the Institute. My job was to build the system that runs it.
Tools and Stack
The software was the easy part. The work was adoption.
I built, tested, and rolled the system out in about two weeks. It was live on day one of the sprint. I trained all 50 founders and every coach myself. The cohort ran from founders who had built AI products for years to founders who had never opened a terminal. I designed for the second group.
This was the second AI system I took to full adoption at the Institute. The first was the Leslie coaching copilot. The lesson carried over: skeptics become advocates when the system makes their own work better, not when you tell them it will.
We surveyed founders at the end of the sprint. 36 responded.
One team shows what the record is for. Counterpart, an app for actors, checked claims from an industry meeting against their own interviews. 18 of 50 customers had independently mentioned a fear of AI. They repositioned. An ad written in their customers' own words drew about 60 trial signups.
"It called me out on my initial reluctance to dig in when I heard people identify pain points."
— Founder, SoundMeshI ran this as an experiment, so here is what failed.
Trust came down to two questions: does it cite its sources, and does it behave the same way twice?
The pilot ran on Notion and Claude, configured by hand. That works for about 10 to 20 teams. It breaks at scale. I'm now leading the move to a proper application that scales across our programs, starting with the open Bootcamp funnel of 600 to 800 teams. The same record serves us as operators: we can select teams on their evidence instead of their pitch.