STAGE 01 · DISCOVERY

Validate the clinical need

Prove that the problem is frequent, important, and poorly served before committing to a product architecture.

Typical horizon0–3 months
Common capitalFounder capital · grants · incubators
Illustrative spendOften $10K–$100K
RECOGNIZE THE STAGE

How to know you are here

A recurring clinical or operational problem has been observed
The affected patient, clinician, and workflow can be named
The team has not yet committed to a final technical solution
READINESS LENSES

What must be managed together

Evidence

Structured interviews, workflow observation, burden and frequency estimates.

Regulatory

Preliminary device classification, predicate, and intended-use scan—no submission yet.

Capital

Founder capital · grants · incubators. Often $10K–$100K.

ACTION PLAN

Priorities for the next 90 days

  1. 01

    Interview clinicians, patients, operators, and economic buyers

  2. 02

    Map the current workflow and quantify the failure or burden

  3. 03

    Write a one-page problem statement and intended-use draft

  4. 04

    Define objective continue, pivot, and stop criteria

BEFORE YOU ADVANCE

Required outputs

  • Validated clinical-need brief
  • Stakeholder and workflow map
  • Intended use v0.1
  • Early classification and predicate memo
WATCH FOR

Common failure modes

  • Building a solution before validating the problem
  • Confusing the user with the buyer
  • Claims that exceed the evidence or intended use
THE DECISION GATE

Is this a real, important, solvable clinical problem with an identifiable user and buyer?

Do not advance because time or money has been spent. Advance when the evidence supports the decision.

Next stageShape and select the concept

NEED A COMPANY-SPECIFIC ROADMAP?

Turn this orientation into a milestone plan.

SECUIA can connect product, evidence, regulatory, usability, and financing decisions around your actual technology.

Call SECUIA