Lo-Fi Prototype Builder

Make the idea concrete enough to test.

A prototype does not need to be real software or a manufactured device. Early on, the job is to create something specific enough that users, buyers, engineers, or advisors can react to it.

Use this page to generate a prompt for turning a clinical problem and solution into a functional requirements document, PRD, spec sheet, fake front-end, wireframe, device concept image, or user-testing plan.

Build the prompt

Fail fast with a smaller, cheaper version of the idea.

Choose the type of solution, the prototype you want, and the assumption you need to test. The generated prompt asks the LLM to create a practical artifact and a feedback plan, not just a prettier version of the idea.

Generated prototype prompt updates as you type.

Your preferred LLMThe prompt works best with a model that can write specs, HTML, and image-generation prompts. Solution typePick the closest category; uncertainty is useful signal. Prototype artifactSelect the thing you want the LLM to help create first. Riskiest assumption to testThe best prototype tests one risky assumption at a time. Problem being solvedDescribe the painful clinical workflow or patient-care problem. Proposed solutionDescribe what the product might do in plain language. Target userSeparate the person using the product from the person buying it if possible. Workflow settingInclude site of care, timing, handoffs, EHR context, patient state, or environmental constraints. Feedback you want to collectState what you need to learn from users, buyers, engineers, or advisors. Constraints and risksInclude anything that should shape the requirements or prototype.

How to use the prototype

Run a Plan-Build-Measure-Learn loop.

PlanBuildMeasureLearn

01PlanChoose one risky assumption.

02BuildCreate the smallest artifact.

03MeasureCollect real reactions.

04LearnRevise, pivot, or stop.

SynthesizeHow does that change our risk model?

AssumptionWhat must be true?

PrototypeWhat can users react to?

SignalWhat did you observe?

Plan the one assumption you need to test before the project gets more expensive. Build the smallest artifact that makes the idea understandable: a fake front-end, wireframe, device image, storyboard, or spec. Measure reactions from users, buyers, engineers, and advisors, then decide what to change, test next, or stop.