SYS/CASE
Digital product creation · Prototyping · 2026
BAO (docAgency) — from a medical-practice project to a bank file in 34 screens
By Mathieu Milon, AI engineer growth & CRO · Published
La Boîte à Outils turns the creation or takeover of a medical practice into a presentation file — in hours, not weeks. Single collection, location analysis (public data), budgets, bank PDF, reverse schedule.
34 screens · 10 PRDs
Context
docAgency supports practitioners who create or take over a medical practice. Putting the bank file together — location, budgets, financing plan, reverse schedule — takes weeks and a lot of back-and-forth.
Problem
Turn a single collection of information into a complete presentation file — location, budgets, financing, reverse schedule — in hours rather than weeks, without multiplying tools or re-entry.
Approach
Two journeys (create / take over), 13 steps plus a location analysis and an export. A PRD written per step, then a static HTML prototype that materialises the target product: collection, data propagation between steps, budget recalculation, preview and print of the file.
data.js
Dummy data & calculations
bao-dossier.js
Persistence & propagation
bao-export.js
Preview & bank PDF
Scoping & PRD
Two journeys — create or take over — and 13 steps, plus a location analysis and an export. A PRD is written per step before any screen: the product decision is scoped first, the interface follows.
Scoping in detail
10 PRDs cover the journey, scoped with the GSD method — the same one that then scopes the proto.
Screens
34 static HTML screens materialise the target product: collection, data propagation from one step to the next, budget recalculation, file preview.
Clickable prototype in detail
data.js holds dummy data and calculations, bao-dossier.js localStorage persistence and propagation between steps: the proto is walked through for real, it is not just looked at.
Bank export
bao-export.js produces the preview and print of the file. That is the deliverable that matters for the bank — location, budgets, financing plan, reverse schedule gathered in a single PDF; the rest of the journey exists to produce it.
Tools
- HTML / Tailwind
- JavaScript
- CARTO/OSM maps
- localStorage persistence
- GSD method
Where AI comes in
PRDs written and audited with agents (consistency audits 15–20 July 2026), screens generated from the PRDs then corrected by hand; AI speeds up the spec and the proto, it does not replace the bank file.
Results
13
steps (create + take over)
34
HTML screens
10
PRDs written
| Deliverable | Quantity |
|---|---|
| HTML screens | 34 |
| Journey steps | 13 |
| PRDs written | 10 |
Axis: number of items delivered. Guided journey in 13 steps, PDF export for the bank file.
Takeaway
- 1
A PRD per step before the screen: we scope the product decision before drawing the interface, never the other way around.
- 2
The proto is the contract with the client: clickable, it aligns everyone far better than a spec document.
- 3
The PDF export is the real feature: it is the deliverable that matters for the bank, everything else exists to produce it.
Visuals
Prototype home screen: 34 screens, journey index Step 1: create or take over, the choice that orients the journey
Related expertise: Prototyping, SaaS, AI engineering.
A similar project?
Let's talk about your next engagement
A funnel, a product or an extract to analyse: book a 30-minute call, written scoping within 48h.