How a 4-Week Design Sprint Resolved 25+ Technical Unknowns for a Dental Clinical-AI Startup

A pre-launch dental clinical-AI startup, founded by a practicing oral surgeon, came to Mindbowser with a clinical problem and more than 25 open technical questions. In four weeks we settled the AI architecture, intake approach, data-source strategy, product design and development scope, before development started.

Book a Design Sprint Call
Customer Focus

Pre-launch dental clinical-AI startup, founded by a practicing oral surgeon

Scope

4-week design sprint: AI architecture, intake approach, rules engine, product UI, data sources and development scope

Stack

Vertex AI, Google Cloud, JSON rules engine, Figma

Status

Sprint complete, fixed-scope SOW signed

Outcomes

Architecture, design and scope settled before development

Every major architecture and product decision was made during the sprint, so development starts against a fixed scope instead of open questions.

25+

Technical questions resolved before development started

50+

Sprint deliverables, including wireframes, prototypes, user stories and design documentation

~12

Medical and professional data sources mapped and evaluated for API availability

6 weeks

From first call to signed fixed-scope SOW

The Problem

A clear clinical problem, no settled technical approach

The founder understood the clinical need. The architecture, data strategy and scope still had to be decided, and every one of those calls needed to land before development so nothing would be reworked later.

01
Fragmented patient histories

Patients can arrive with fragmented or incomplete medical histories, while dentists need to identify relevant risks quickly during clinical workflows.

02
No model architecture selected

General-purpose LLM or specialized dental SLM, fine-tuning or prompt engineering: none of it was decided.

03
Licensing, data sources, hosting and ownership unverified

Licensing, data-source API availability, hosting and model ownership were all open among the 25+ questions.

04
Fixed-scope risk

The engagement needed clear boundaries on what the platform would and would not include, with potential scope-creep areas identified before development began.

The Tech Stack

Vertex AI inference on Google Cloud, with a JSON rules engine deciding what gets checked and the LLM writing the explanation.

  • Vertex AI
  • Google Cloud
  • JSON rules engine
  • Figma
  • Clinical data-source APIs
What We Built

Architecture, product design and scope, decided in four weeks

A general-purpose LLM governed by structured clinical rules

We evaluated specialized dental SLM approaches against a general-purpose LLM governed by structured clinical rules, then selected Vertex AI for cloud inference.

  • JSON rules engine: structured clinical rules determine what needs to be checked
  • The LLM generates the narrative explanation for the dentist
  • Vertex AI selected for cloud inference on Google Cloud
  • Hosting and ownership evaluated, with the architecture built around founder-owned IP

Have a clinical problem and an open architecture question?

We run design sprints that settle model choice, data sources and scope before development starts.

Book a Design Sprint Call

Let’s #Transform Healthcare,# Together.

Partner with us to design, build, and scale digital solutions that drive better outcomes.

Location

Global Tech Teams LLC, 525 Washington Blvd, Industrious at Newport Tower, Jersey City, NJ 07310, United States.

Contact

+1 408 786 5974
contact@mindbowser.com
BOOK A QUICK CONSULTATION

Have a Healthcare Project in Mind?

Let’s discuss your goals, workflows, and next steps in a focused consultation call.

Calendar icon Schedule a Call

Contact form