How I help / Design it
Prototypes and demos. See it before you build it.
I build clickable demos and technical proofs that answer a specific question early: will people understand this flow, and can the systems involved actually do what the plan assumes?
Often part of a focused discovery · £3,000 for one defined process
Prototypes, at a glance.
Clickable demo
A realistic, clickable version of the screens and flow. People can try it, react and point at what is missing.
Technical proof
A small working test of the risky part, such as a connection, a data source or an automation step, before anyone commits to it.
Why do it
A cheap question now beats an expensive surprise later. A demo also helps everyone picture the same thing.
What happens next
The findings feed a solution plan. A delivery quote reuses them, so the same discovery work is not charged twice.
When a demo is worth it.
Written requirements leave room for interpretation. Ten people can read the same specification and imagine ten different screens.
A prototype gives everyone the same picture. A technical proof tests the assumption the whole plan rests on. Both are small on purpose: they answer a question, then make way for the real build.
Stakeholders disagree
A clickable flow turns a debate about words into a conversation about something people can see and try.
A risky dependency
Test the integration, data or automation step that would sink the project if it did not work.
A decision needs support
A demo helps decision-makers understand what they are being asked to fund.
How I build them.
Name the question
Agree what the demo or proof must answer, and who will judge the result.
Build the smallest useful version
Only the screens or steps needed to answer the question. No polish where it does not matter.
Try it with real people
Put it in front of the people who will use or approve the real thing. Note what works and what confuses.
Write down what you learned
Findings, open questions and the recommended next step, so the result outlives the demo.
Part of focused discovery.
Focused discovery covers one defined process and up to four of my working days. You receive a clear problem statement and solution plan, with a technical proof or clickable demo when it helps answer the question.
Discovery is a standalone paid engagement. Any delivery is quoted separately using its findings, so the same discovery work is not charged twice. A full fixed build quote follows once scope, dependencies and acceptance criteria are clear.
Focused discoveryDesign and build in one pair of hands.
I do UI, UX and graphic design, including freelance work on 99designs, and I build software myself as external / fractional CTO at Kona Libre. A prototype from me is designed with the real build in mind.
A useful next step
What would you like to see working?
Tell me the idea and the question you need answered. The first 30-minute conversation is free.
You’ll speak directly with me about the problem, the fit and a sensible next step.
Opens your email app with a few prompts.
hello@richardzoltantoth.com
Online meetings worldwide.
No VAT added — I’m not VAT registered.
View the full engagement terms.