A proof of concept is taking the theory behind your idea and testing its feasibility. It’s one of the most critical stages of product development and often the earliest stage for securing funding (Technology Readiness Levels 3 and 4). This guide will help define a proof of concept, how to create one, why it’s important and how to transition from a proof of concept to a prototype.

What is a proof of concept?

A proof of concept aims to verify that your idea is feasible and will function in the real world. The proof of concept should address the following questions: 

• Problem identification: what are you trying to solve?
• Goals: what are your measurable objectives?
• Basic features: what are the core functionalities of the device? 
• Stakeholder involvement: what external input is required?

How to create a proof of concept

Research and define the scope

The first step is conducting research and defining the project’s scope. You should already have a theoretical foundation for your innovation and proposals for its potential applications (TRL 1 and 2).  However, this stage focuses on the problem your idea is solving, the current market landscape and the technical requirements you’ll need to meet. Following this research, you can begin your plan for validating your ideas, such as methodology and expected outcomes, to keep things as simple as possible.

What does a successful proof of concept look like?

With a clear project scope, you can begin to outline your success criteria. You want to have realistic and measurable outcomes. Remember, a proof of concept is not a finished product. A successful proof of concept is confirmation that your idea works or, if it doesn’t, understanding why it doesn’t work, what needs to change and how to do this. It should consist of small-scale and low-risk experiments to test your theory.

Left: Smart Gas proof of concept. Right: Prototype.

Build your solution 

It’s time to put your plan into action. Here is an example of one of our projects, Push to Talk, at its proof of concept stage.

The idea behind Push to Talk was to develop a device that could easily allow people to converse by pushing a button. It required us to create two things: software and a physical device. Our initial focus was fitting the technology into an enclosure (hardware) no bigger than an alarm clock. This was to ensure we could fulfil our goal of having a button that would look discreet in someone’s home.

For the software, we needed to prove that users of the device could press a button, and a phone call would trigger. To trial this, we created four Push to Talk devices which would radio back to a laptop running our software. The program would take two presses and trigger a call for the phone numbers assigned to each device. After successfully trialling this, we knew we could send data from a device to the internet without needing Bluetooth, mobile data, Wi-Fi or broadband. 

The proof of concept device (left) is simple and looks very different to the finished product (right). However, the crucial difference is that the proof of concept devices were low-cost and allowed us to verify our idea. Spending time and money on the device’s aesthetics shouldn’t be a key focus at this early stage.

Testing and feedback

Following the build of your proof of concept, it’s crucial to test it. Our Push to Talk device was tested in-house, but depending on your device and use case, you may have to collaborate with industry partners to provide expertise and resources for testing. It should be a controlled testing environment that simulates real-world conditions. Here, you monitor and collect data to evaluate the proof of concept’s performance, identify any issues and refine and improve your design. 

Document findings

Documenting your findings is vital for immediate progress and long-term success. Recording what works and what doesn’t throughout the process offers a clear foundation for advancing to the next stage. Documentation is equally critical for stakeholder communication, as it provides a transparent explanation of your design choices, decisions and the rationale behind them. The challenges you encounter are also valuable to record, as they reveal potential pitfalls and opportunities for improvement. 

Why is a proof of concept important?

Risk reduction: The goal is to test feasibility without committing significant resources. Identifying challenges earlier allows you to address potential issues before they escalate, minimising wasted time and effort. Early discovery of obstacles may also reveal the need for significant redesigns, which are far easier to manage in the early stages.

Informed decision-making: A solid proof of concept should provide insights to guide your next steps.  Even if the idea is viable, the process may reveal unexpected costs or complexities. The data collected will help you evaluate whether to proceed, adjust the approach, or return to the drawing board. 

Stakeholder confidence: If you aim to secure funding, especially for pre-seed founders, investors are strongly influenced by how well a startup has executed things such as developing its MVP [Sifted]. A well-crafted proof of concept demonstrates the viability of your idea and showcases your ability to deliver results. It strengthens your credibility and creates trust among investors, increasing the likelihood of securing their support.

Transitioning from proof of concept to prototype 

Transitioning from a proof of concept to a prototype is an exciting milestone but requires careful evaluation and planning. Start by reviewing the results of your proof of concept to ensure it meets all the success criteria. Thorough documentation of these results is essential, especially if you plan to secure funding for your prototype. You should also identify improvements, additional features, and the materials or tools needed for the next stage. 

Conclusion

A proof of concept lays the foundation for the success of your project. Ultimately, the goal is to fail fast. Learning what doesn’t work is just as valuable as discovering what does. Embracing this process is a step towards innovation, helping you validate ideas and effectively reduce risks. 

At DefProc, we support innovators in bridging the gap between concept and commercialisation. Whether you need help refining your ideas through workshops or a comprehensive roadmap to bring your proof of concept to a market-ready product, we’re here to help.