# Can you build a prototype before we commit to a full product?

Canonical URL: https://newphysician.org/can-you-do-this/prototype-before-full-build/

Yes. A prototype should answer a decision, not merely look finished. It can test whether users understand a workflow, whether an integration is feasible, or whether a proposed service is worth building. Those are different experiments and need different levels of fidelity.

What a solution might involve

Choose the uncertainty first. For a usability question, build an interactive path using clearly labeled sample data. For technical feasibility, test the difficult integration directly. Record the observations and the decision they support before expanding into production engineering.

What needs care

A convincing demonstration is not automatically production-ready. Authentication, audit history, recovery, accessibility, and operational ownership can be absent from a prototype. The handover must identify those gaps so a sales demo does not quietly become a critical system.

How we would judge whether it works

The agreed question has an observable answer. The team can explain what was tested, what remains unknown, and what must change before real customer information or production traffic enters the system.

Likely engagement

Rapid Build: $1,500 to $3,000. This is a likely starting tier, not a quote. Scope, access, dependencies, and responsibility for operation need agreement first.

Discuss Rapid BuildWhat to send first

Tell me which decision is blocked and what result would make you proceed, change direction, or stop.

Send me the messy version.

Experience and scope

Selected builds documents the currently authorized public proof. This page describes a proposed approach, not a claim of a completed client engagement in this exact workflow.

Related problems

Can you turn a small idea into a working digital product?

Can you help finish a digital build that has stalled?



[Send me the problem](https://newphysician.org/send-me-the-problem/)