“It’s the quality and the calibre of the leads as well, people that we would have never got in front of are phoning us: big clients, it’s fantastic.”
Rachel Hosking, Gasket Guy
Digital prototyping, what it is and what you get
Digital prototyping is a short, focused build that turns a messy idea into something tangible. Not a slide deck, not a theoretical brief, a working first version you can use.
This is for the moment when you can feel there is a better way to do something, but the shape is still unclear.
You might have a clunky internal process, a customer journey that could be improved with a digital tool, or a spreadsheet that has become mission-critical.
The aim is not to launch a finished product in a week. The aim is to make the idea real enough to understand, test, and make better decisions.
What you get:
- a clearer view of cost, risk, and opportunity before committing to a full build
- a working prototype you can use and test
- a clear scope for version one, and what is not in version one
- a shortlist of next steps, prioritised
Book a free 30 minute chat
Practical, no-nonsense digital advice. No jargon, no pressure, just (hopefully) some ideas you can action.
How a prototype sprint works
A prototype sprint is a short, focused collaboration designed to get to a usable first version quickly.
We do not start with a long specification. We start with the problem, the users, and the workflow.
Most of the value comes from shaping the right first version. The build is quick, but the judgement is the point.
What this looks like in practice:
- A kick-off session to define the problem, users, and success criteria
- A simple version one scope, what is in, what is out
- Rapid build with frequent check-ins, so you can steer it while it is being made
- A review session to test what works, what feels clunky, and what is missing
- A next-step plan, rollout, bigger build, or stop
What we need from you:
- One decision maker who can unblock priorities
- Access to the people who live with the process, not just the people who report on it
- Quick feedback loops, so we do not build in the dark
From idea to working prototype, a live build example
If you have any doubts about how quickly an MVP can be produced then check out our article on how we built an app with the room at a recent 1 hour live seminar.
We got the room to help create the brief for an event companion app.
The question was simple. If you had an app in your pocket for today’s networking event, what would it help you do better?
People shared ideas, we gathered them, shaped them into features, and built the first version during the session. By the end, the app was deployed and people in the room could open it on their phones.
The point is not that we can build something quickly. The point is that the best prototypes come from shared context.
Your knowledge, your audience insight, and your process are what turn a generic tool into something useful.
“The process was inspiring. The Vu team brought energy, insight and creativity that genuinely lit a spark in us.”
Prototype sprint pricing, example packages
We keep this flexible, because prototypes vary. These packages are here to show what typically fits, and what changes the scope.
| Package | Typical timeline | Best for | What you get |
|---|---|---|---|
| Prototype sprint, from £3,000 + VAT | 1 to 2 weeks | Making an idea real enough to test | kick-off and problem framing, version one scope, working prototype, review session, next-step roadmap |
| Prototype plus testing, from £5,000 + VAT | 2 to 4 weeks | Reducing risk before you scale | prototype sprint plus user testing, iteration, clearer technical brief, rollout options and priorities |
| Prototype to MVP, from £10,000 + VAT | 4 to 8 weeks | Moving from prototype to real use | prototype sprint plus pilot build, light integrations where needed, internal rollout support, measurement plan |
Notes
- This is not a finished enterprise-grade system from day one.
- The goal is a usable first version, plus clear decisions about what comes next.
- If you want one budget to include third-party costs, hosting, licences, or tooling, we can include that, or ring-fence it separately.
What you can expect to be delivered
Depending on the scope, you may come away with a working prototype and a clearer understanding of what it should become.
Typical outcomes
- A functional version one you can use and show to others
- A tested workflow, with the clunky bits highlighted
- A clearer technical brief for a bigger build, if needed
- A prioritised list of next-step features
- A clearer view of cost, risk, and opportunity
- A stronger case for internal buy-in, because people can see and use the thing
Two ways rapid prototyping can help
Rapid prototyping tends to land in one of two camps. Improving how your business works, or improving what your customers experience.
Improve how your business works
Some prototypes are about saving time, reducing admin, and making internal work less painful.
Examples include internal dashboards, workflow tools, approvals and handovers, knowledge capture, project visibility, and turning a spreadsheet into a usable internal tool.
This is often where the return is clearest. You already know the process. The sprint helps test whether a better system could save hours, reduce errors, or improve consistency.
Improve what your customers experience
Other prototypes add a digital layer to your service.
That could mean a portal, a self-serve tool, an interactive advice experience, a member area, or an app that makes a service more useful, personal, or scalable.
The sprint helps you explore whether the digital layer adds real value, and what version one needs to do to prove it.
What affects price and timeline
Prototype work gets more complex when there are lots of stakeholders, lots of data, or lots of systems involved.
The main factors are:
- How many workflows the prototype needs to cover
- How much data needs cleaning or modelling
- Whether you need integrations with existing systems
- How many feedback loops you want, and how quickly you can review
- How many users need to test it, internal teams, customers, or both
If you are not sure what level you need, start with a prototype sprint. It is usually the fastest way to turn an idea into something you can test and make decisions on.
“Vu encouraged us to think beyond the day to day content planning, helping us find the opportunities where we are not doing something that we actually could be.”
Where your why fits in the process
Some prototype ideas need more than a build. They need clarity on what the product is, who it is for, and what problem it solves in the the world.
Without this, it is easily replicable and likely to have a short shelf life.
That is where Whyso fits.
Whyso brings strategy, creative, and technical together, in a simple sequence, purpose, presence, practice. That work helps sharpen positioning, narrative, identity, and voice, then turn it into a system your team can actually use.
How it connects to rapid prototyping
- Before the sprint: to clarify purpose, audience, and message, so the prototype solves the right problem
- Alongside the sprint: to shape naming, language, and interface decisions as the first version takes shape
- After the sprint: to turn a successful prototype into a coherent product, brand, and rollout plan
Why Choose Vu?
Message first
We start with the problem, the users, and what would make the tool genuinely useful. That clarity shapes the prototype, so you do not end up building something impressive that solves the wrong thing.
Built with you
This is not a handover. We work in short cycles with quick feedback, so decisions get made while the prototype is being built, not after it has gone off track.
Practical judgement
Speed is useful, but judgement is the difference. We focus on version one that teaches you something valuable, then we decide what to build next, based on evidence.
Values-led delivery
We build for performance, accessibility, and a lighter footprint. Practical digital choices matter, and we make them part of the process, not an afterthought.
Ready to test an idea?
You do not need a full specification to start. Bring us the problem, the opportunity, or the process that feels harder than it needs to be.
We will help you shape a version one that is real enough to test, so you can make a confident decision about what to build next.
Or read our take on why judgement matters before speed, the most dangerous thing you can do with AI is get better at what you already do
Book a free 30 minute chat
Practical, no-nonsense digital advice. No jargon, no pressure, just (hopefully) some ideas you can action.
FAQs
Most prototype sprints run over a few weeks. Longer timelines usually mean more stakeholders, more workflows, more data, or more testing.
A working prototype is a functional version one you can use, click through, and test. It is not a finished enterprise system secure enough for all your data, nor is it a slide deck or visual.
Internal dashboards, workflow tools, portals, self-serve tools, interactive resources, event companion tools, and proof-of-concept versions of new digital products.
Yes. We often prototype workflow automation before committing to a full build or buying a platform. The sprint helps you test the workflow and define what the system actually needs to do.
Yes. If a spreadsheet has become mission-critical, we can prototype a lightweight tool that keeps the logic, improves usability, and reduces risk.
Sometimes, if we are best placed to do so, or we can help you find who is. The sprint gives you a clear decision point. The next move might be a bigger build, a pilot rollout, more testing, or stopping because you have learned what you needed.
One decision maker who can unblock priorities, access to the people who live with the process, and quick feedback so we do not build in the dark.
An MVP is usually a product release. A prototype sprint is earlier. It is designed to make the idea testable, learn quickly, and reduce the risk of building the wrong thing. The next step afterwards might well be an MVP…
Yes, where it genuinely helps. AI can speed up parts of delivery, but it does not replace the thinking work. We focus on usefulness, accuracy, and whether the tool supports how people actually work.
Prototype sprints typically start from £3,000 + VAT. Cost changes with scope, pace, data complexity, integrations, stakeholder load, and how much testing you want.
Let’s Make a Start
