Make the difficult product decision before paying to build the entire product.
Discuss a project
A prototype should answer a question, not imitate a finished product. I define what needs to be learned, choose the smallest useful fidelity and put the important flow in front of the people who can challenge it. That may be a clickable interface, a technical proof or a working slice of the product. Grantix includes documented first-stage interface prototypes; the MoyChay case shows a separate discovery and test-environment engagement that stopped before a production rebuild.
A booking application with per-boat pricing, two-way Google Calendar synchronization and Bitrix24 integration. Developed but not publicly launched.
Per-vessel calendar integration
A WordPress / WooCommerce test environment and specifications for a proposed store migration. The original engagement stopped before production redevelopment.
WordPress and WooCommerce test environment
A written decision to test, target audience and realistic success criteria
The few journeys or technical assumptions that need evidence first
A clickable, coded or technical prototype at the right level of fidelity
Findings, unresolved risks and a recommended scope for the next stage
I identify the decision the prototype needs to support and what would count as useful evidence.
I select wireframes, a clickable design, a coded flow or a technical test according to the risk being tested.
I build the smallest credible version and review it with the relevant users or decision-makers.
I document findings, limitations and the scope of a possible next release.
One core user journey as a clickable prototype
This price covers the starting scope described above. I confirm a quote after reviewing your brief and existing systems. Third-party fees are separate.
Send a brief on WhatsAppFor development work I deliver, I correct defects in the agreed scope reported within 90 days of launch. New features, changes by others and third-party outages are separate work.
Usually not. Its purpose and fidelity are agreed at the start. If a coded prototype can be reused, I still review its architecture, accessibility and tests before treating it as production work.
Yes. A focused journey or integration test often answers the decision better than a complete interface mockup.
You receive the agreed prototype or test environment, plus the findings and next-stage recommendation. The discovery work remains useful even if you choose another implementation partner.
Tell me where your product stands. I'll give you a direct view of the options and what I can take on.