VesterosConsulting

Rapid Prototyping

From business problem to something you can test

Rapid prototyping means building a working version of an idea quickly enough to learn from it before committing to a large build. It can be an internal tool, a B2B or B2C product, an AI-enabled workflow, a customer-facing service, a proof of concept or an MVP tested with the people who would actually use it.

The problem we usually meet

Ideas stall in documents. A requirement list circulates, everyone reads it differently, and the decision waits for a bigger budget round.

Meanwhile the underlying problem is still handled in a spreadsheet that three people maintain in slightly different ways.

Who this is for

You do not need an existing product, technical team or finished specification. Sometimes the starting point is simply a problem worth solving or an idea worth testing.

  • Founders and entrepreneurs who have an app, platform, service or product idea and want to turn it into something people can actually try.
  • Product and innovation teams exploring a new product, feature, service or business model before committing to a full build.
  • Internal teams that have outgrown spreadsheets, manual processes or disconnected tools and want to test a better way of working.
  • Organisations considering a larger technology investment and wanting evidence before committing more time and budget.
  • Teams exploring AI-enabled products or workflows that need to test whether AI adds meaningful value in practice.
  • Leaders who need to show an idea rather than describe it, whether to customers, users, colleagues, investors or decision-makers.

What we help with

  • Turning an early idea or business problem into a clear concept that can be tested.
  • Defining what the prototype, PoC, MVP or pilot actually needs to prove.
  • Building lightweight internal tools, dashboards, portals and workflow applications.
  • Prototyping B2B and B2C digital products, services, platforms and product features.
  • Building AI-enabled products and workflows where AI has a useful role rather than being added for the sake of it.
  • Testing with real users, customers or stakeholders and capturing what we learn.
  • Defining what would be required to take a validated concept further.
  • Recommending whether to build further, change direction or stop.

Internal · B2B · B2C

What we prototype

Internal teams, business customers and consumers all have ideas worth testing. The format changes. The question stays the same: does this actually work for the people it is for?

Internal

  • Internal tools
  • Operations tools
  • Dashboards
  • Knowledge interfaces
  • Portals
  • CRM-style tools
  • Workflow tools
  • AI assistants and agents

B2B

  • SaaS concepts
  • Enterprise tools
  • Customer portals
  • New product concepts
  • Features
  • AI-enabled B2B products

B2C

  • Consumer web applications
  • Marketplaces
  • Digital services
  • AI-enabled consumer experiences
  • Product concepts

Prototype, PoC, MVP or pilot?

The words get used interchangeably. They mean different things, and the difference decides what you build.

Prototype
A working version used to explore the experience, workflow or concept.
Proof of concept
A focused build used to test whether an important assumption or capability works.
MVP
A deliberately limited version that delivers enough value to be used and learned from.
Pilot
A controlled real-world implementation with a defined group, workflow or environment.

Not every engagement passes through all four. Many stop after one, and that is often the point.

A prototype people can use beats another slide deck about what might work.

How an engagement runs

  1. 01

    Frame

    Agree the problem, the users and the question the prototype must answer.

  2. 02

    Sketch

    Outline the workflow and the smallest version that is still useful.

  3. 03

    Build

    Produce a working prototype quickly, not a polished product.

  4. 04

    Test

    Put it in front of real users and observe what actually happens.

  5. 05

    Decide

    Recommend whether to continue, change direction or stop.

What you can expect to end up with

  • A working prototype people can use, not a slide deck about one.
  • Documented findings from real use, including what did not work.
  • Clear requirements for a larger build, if a larger build is justified.
  • A defensible decision either way, reached in weeks rather than quarters.

Tools and methods we work with

  • Low-code and modern web application platforms
  • Lightweight CRM, dashboard and portal patterns
  • AI-enabled workflow components
  • User testing and structured feedback
  • Requirements definition from what was learned

What if it works?

A successful prototype is often the beginning of the next decision, not the end of the project.

If testing shows that the idea is worth taking further, we can help define the requirements, priorities and next stage of development. Where production engineering, security, infrastructure or other specialist technical expertise is needed, we can bring in the right expertise from our wider partner network.

The goal is not to keep a prototype alive forever. It is to learn enough to make a good decision about what comes next.

When a prototype is not the answer

If a proven product already covers the need, prototyping is an expensive way to reach the same conclusion. If the problem is unclear, the honest first step is workflow discovery rather than a build. And a prototype is not a production system: we label it as a prototype and describe what would be required to run it for real.

Frequently asked questions

What is rapid prototyping in a business context?

It is building a working version of a solution quickly, so people can use it and give grounded feedback. The goal is learning and decision-making, not shipping a finished product.

How long does a prototype take?

It depends on the scope, but the point is to work in weeks rather than quarters. If a prototype cannot be produced quickly, the scope is usually too large and needs to be cut down.

Is a prototype production-ready?

No, and we do not describe it as such. A prototype is built to answer a question. Turning it into a production system requires decisions about security, data handling, support and ownership, which we can help define.

What happens after the prototype?

You get a recommendation based on what happened during testing: continue and harden it, change direction, or stop. Stopping early with evidence is a legitimate and often valuable result.

Related

Have something you want to test?

You do not need to know whether it should become a prototype, PoC, MVP or pilot. Bring us the problem or idea and we will work out what needs to be learned first.

Discuss an idea→

30 minutes · Online · Complimentary

Something else on your mind? See every way to start