Test your business idea quickly and cost-effectively with rapid prototyping

As a decision-maker, building a prototype may seem like a significant investment. What if the product never reaches the market? Would that money be wasted? The reality is that with off-the-shelf components and open-source platforms, you can minimize both time and costs. And even if the idea never becomes a final product, rapid prototyping remains a fast and affordable way to refine your business strategy and make better decisions.

Bent Bisballe Nyeng is a Senior Embedded Solution Architect at Mjølner. We asked him about the benefits of rapid prototyping and how to get started.

How to Test a Business Idea with Rapid Prototyping

So, you want to test a business idea using rapid prototyping? Well, the obvious answer is to call Mjølner! Jokes aside, at Mjølner, we follow a three-phase approach to rapid prototyping, where we assess at each stage whether to proceed or not.

We apply a “Fail Early” strategy, identifying errors and challenges as soon as possible—so we can learn from them quickly. The goal is to minimize risk, reduce costs, and improve the prototype before too many resources are spent on a failed idea.

Phase 1: Technological Feasibility

At this stage, we focus on assessing the technology rather than optimizing every detail. Factors like power consumption are less important. We use standard components to avoid expensive custom solutions. The goal is to quickly determine whether the chosen technology is viable.

Phase 2: Refinement and Optimization

Here, we take a more detailed approach, evaluating each component alongside the software. Can we adjust parameters to lower power consumption? Software often plays a key role in this phase. The objective is to qualify and refine the prototype before moving forward.

Phase 3: Pre-Production Prototype

Now, we start working towards a production-ready prototype. This advanced prototype closely resembles the final product in design, functionality, and materials. It is used to test and validate the production process before scaling up to mass production.

The strength of our approach is that the testing phase carries low risk. We stay in close collaboration with the customer throughout the process, continuously assessing whether to move forward or halt development if necessary.

By failing early, learning fast, and iterating efficiently, we help businesses turn ideas into reality – without unnecessary risk.

Why use rapid prototyping in embedded? 

Starting a large project from scratch can be an expensive and risky endeavor. It often requires significant investments in both time and resources before you even know whether the solution works as expected.

An effective way to minimize this risk is to carry out a rapid prototyping process before committing to the entire project. A rapid prototype allows you to quickly test ideas, validate concepts, and identify potential challenges – all without a major financial investment.

Here are some good reasons for using rapid prototyping:  

1. Faster Time-to-Market 
   With rapid prototyping, you can test and improve ideas quickly. This means that your company can bring products to market faster than competitors, gaining a strategic advantage in industries with rapid technological development.
   
   
2. Lower Development Costs
   Instead of investing in custom-developed hardware and software from the start, standard components can be used to test concepts. This saves money and reduces the risk of misinvestments in failed ideas.
   
   
3. Better Decision-Making
   A physical prototype makes it easier to assess the potential of a product. It can be difficult to understand an idea solely from a PowerPoint presentation—but a functioning prototype provides a concrete foundation for strategic decisions.
   
   
4. Early Feedback from Users and Costumers
   With a quick prototype, you can test the product idea directly with potential customers, making it easier to tailor the solution to market needs. This means fewer iterations later in development and a product that hits the mark.
   
   
5. Lower Risk by Failing Early 
   By identifying and solving errors early in the process, you avoid bigger and more expensive problems later on. It’s all about testing, learning, and adjusting quickly before investing too much in a solution that might not work.

Can You Give a Concrete Example of an Embedded Rapid Prototype?

We were recently contacted by a client who wanted to use technology to improve the level of service in rehabilitation. They found that their physiotherapists often visited patients who had not completed their prescribed exercises. This led to wasted time and less effective rehabilitation processes.

The solution was a physical device that can be mounted on an exercise bike or a patient’s leg and, using machine learning, determines whether the user is running, standing, or cycling. With Long Range (LoRa) technology, we can wirelessly transmit small data packets over long distances with very low power consumption.

One of the client’s key requirements was minimal battery maintenance—physiotherapists should not have to constantly replace batteries. The goal is for the small device to function for several years on a single battery.

The device integrates into an existing network that physiotherapists already use, providing them with an operational overview and allowing them to focus on their core tasks instead of unnecessary travel. At the same time, it was crucial that the technical solution respects the privacy of patients. The focus is on nudging rather than surveillance, ensuring that the collected data serves as a basis for constructive dialogue between patients and physiotherapists.