Skip to content
Japanese Industrial Manufacturer — Industrial Products DivisionStarted with a Craft Sprint →

New-business exploration in one app, with a record of every decision and AI that drafts but never decides

The division's new-business team kept its candidate list, research and meeting notes in personal spreadsheets and email, so the reasons behind each decision were lost. We framed the exploration loop, designed one app to run it from long-list to lean canvas to field notes, and proved it in a Craft Sprint: AI drafts and proposes, and nothing changes until a person approves. It is now in trial and moving to a production build.

0

changes applied by AI without human approval

10days

From first specification to a live demo for the division's executives

Client
Industrial products division of a Japanese manufacturer
Users
New-business exploration team
Scope
Craft Sprint prototype · Trial build · Production build
Timeline
Jul 2026 sprint → Sep 2026 trial → production build
Team
Consultants, full-stack engineers
9

Screens covering the loop, from long-list and voting to portfolio and decision log

4

Evidence levels (fact, counterpart opinion, hypothesis, hearsay); only facts can mark a hypothesis verified

6

AI functions: theme drafts, consumables scoring, Go/Pivot/Kill judgement, next-action advice, revenue hypotheses, field-note diffs

20–40sec

For AI to draft a new theme from a name and a one-line note

The challenge

Good ideas were found, but the evidence and the reasons got lost

The division looks for new businesses in a fixed cycle. It builds a long-list of themes, agrees a short-list, tests each one on a lean canvas and goes out to meet universities, potential customers and partners. Each step lived in a different file.

What the team learned on visits rarely made it back into the hypotheses in a structured way. Six months later, nobody could say why a theme had been dropped.

Scattered information

Candidate lists, research notes and meeting minutes sat in personal spreadsheets and email, so no one had the full picture.

Inconvenient evidence buried

The more a team wanted a theme to work, the easier it was to skip negative customer feedback or competitor news.

Slow to start

Background research on each new candidate took days, so the long-list stayed short.

Our approach

Frame the loop, prove it in a sprint, then harden it with real users

One rule shaped every design decision: AI never overwrites data. Everything it produces is a draft or a proposed diff. A person approves, edits or rejects each item, one by one, and there is no bulk-approve button. Evidence that is not a fact cannot promote a hypothesis to verified. The server enforces this when an item is decided and again when it is applied.

EXPLORE · SELECT VERIFY IN THE FIELD Long-listAI draft · vote · short-list Lean canvas9 blocks · Go / Pivot / Kill Field notesminutes from visits AI diff proposalsquoted ·counter-evidence first Human approvalone item at a time Only fact-level evidence can mark a block verified Approved changes update the canvas and the decision log; the loop repeats with every visit
AI writes only drafts and proposed diffs. A change reaches the lean canvas after a person approves it, and the server refuses to mark a hypothesis verified on anything weaker than a fact.

Craft Sprint

Jul 2026
  • Lean canvas tool turned into a local app with AI judgement
  • Long-list, field notes and AI diff proposals added
  • Tested on real meeting notes, then a live demo to executives

Trial build

Aug – Sep 2026
  • Database-backed app hosted in Japan with sign-in and admin-issued accounts
  • Voting, short-list, portfolio, signals and decision log
  • Architecture and security overview for the client's information-security review

Trial

Sep 2026 →
  • Users try it freely on sample data that can be reset at any time
  • Per-user usage tracking to guide the next stage
  • Feedback on screens and functions goes straight into the backlog

Production build

Next
  • Migration to Cloudflare Workers
  • Real themes and minutes; the reset function switched off
  • Security hardening as required, such as IP restriction and MFA
The impact

The exploration cycle now runs in one place, with a record of every decision

BeforeCandidates, research and minutes spread across personal files
SolutionOne app from long-list to Go/Pivot/Kill judgement
ResultEveryone sees the same, current state of every theme
BeforeDays of desk research before a new candidate could be discussed
SolutionAI drafts market, needs, technology fit, market size and growth, marked 'AI draft, unverified'
ResultA first draft in 20–40 seconds; people check and correct it
BeforeNegative feedback from visits easily overlooked
SolutionField notes become proposed diffs, each quoting the source text. Counter-evidence is listed first
ResultWeaknesses in a hypothesis surface before the team commits to it
BeforeNo record of why a theme was adopted or dropped
SolutionDecision log of who decided what, when and why, with before and after
ResultTeams can still explain past decisions after people change
BeforeOff-topic insights from visits lost
SolutionRouted as signals (new opportunities) or leads for existing businesses
ResultCaptured in the same record as the exploration itself, instead of in personal notes
AI can draft and propose in seconds. What the team needed was a tool that keeps judgement with people and still shows them the evidence they would rather not see.
Engagement Lead, Taira Promote
What's next

From trial to a production platform

After the trial, the app moves to a production build on Cloudflare Workers and the team starts entering real themes and minutes. The same rules carry over: AI drafts and proposes, people approve, and every decision is logged.

Step 1

Real data

Switch off the sandbox reset, issue accounts in stages and start building up real themes and field notes.

Step 2

Production platform

Rebuild the runtime on Cloudflare Workers, with security controls such as IP restriction and MFA to match the client's requirements.

Step 3

From Go to project

Connect themes judged Go to the division's process for turning them into funded projects.

Platforms & partners
Node.jsExpressPrismaPostgreSQL (JSONB)Anthropic Claude APIVanilla JSAWS ECS FargateAmazon CognitoAmazon RDSCloudflare Workers (planned)

Facing a similar challenge?

Tell us about it in a few lines. We will come back with a practical first step, usually within a week.