Build Candidate · Sample

Dental pre-authorization is ready for a bounded product build.

The validation gate has been passed for this prototype scenario. That does not mean “build the platform.” It means the opportunity has earned a small, testable product build tied to a real pilot.

01 · Build decision

What changed?

ProblemRepeated and material

Target users consistently describe the workflow as painful enough to change.

BuyerPractice owner identified

The economic buyer understands the cost of the workflow and is willing to test a solution.

Pilot pullEnough demand to test

At least three clinics are willing to continue into a bounded pilot.

DecisionBuild candidate

Move from clickable prototype to a small pilotable product. Do not broaden scope yet.

02 · MVP scope

Build only what the pilot needs

Case intake for patient, procedure and payer context
Payer requirement checklist with missing-item visibility
Simple status board for pending, blocked and approved cases
Follow-up reminders and stalled-case escalation
Basic aging and bottleneck reporting

Explicitly out of scope

Not nowFull PMS replacement

Integrate around the existing system instead of trying to replace it.

Not nowAutonomous insurance agent

Do not add high-complexity AI automation before the workflow itself proves value.

03 · First pilot

Build for three clinics, not for the market

Pilot cohort3 independent dental clinicsEnough variation to expose workflow differences without expanding scope too early.
Timebox10 business daysShort enough to force learning and prevent premature feature expansion.
Buyer checkpointPractice owner reviewConfirm measurable value and whether the workflow is worth paying for.

Pilot success metrics

Workflow useTeams use it on real cases

Not demo clicks. Actual pre-authorization cases enter the workflow.

Time savedLess manual chasing

Capture baseline vs pilot follow-up effort where practical.

Operational pullUsers ask to keep it

Continued use or requested improvements matter more than compliments.

Commercial pullOwner will discuss paid continuation

Move from “interesting” to a concrete price conversation.

04 · Production readiness

What still blocks a real launch?

Data handlingPatient/privacy scope must be decided

Do not introduce real PHI into the pilot until the product, security and compliance model is intentionally designed.

IntegrationsPMS/payer integrations are not yet earned

Start with the smallest workflow that can prove value without deep integration.

PricingPaid conversion still must be proven

A pilot request is not the same as willingness to pay.

DistributionRepeatable acquisition not yet proven

Founder-led outreach can validate the wedge before investing in scalable GTM.

05 · Founder operating plan

Your next 30 days

Week 1: finalize pilot workflow and three clinic commitments
Week 2: build only the five MVP capabilities above
Week 3: run live pilot with daily issue capture
Week 4: measure value, test pricing, decide continue / change / stop
Build Candidate status

Proceed to a bounded pilot build.

This is not production authorization. The product has earned a small build whose purpose is to generate commercial evidence.