Test the technical unknowns before the project starts.
A proof of concept answers one specific technical question before the project starts: Will the interface hold up? Is performance good enough? Does the planned technology fit? It takes two to six weeks and starts at €5,000.
The intro call takes 30 minutes and is free.
A proof of concept, or PoC, is a hands-on demonstration that an idea or concept is technically feasible.
In software development, we build only the part where the project could fail and test it under real conditions. That way, risks show up at the start of the project, not shortly before go-live.
A PoC is deliberately unfinished. The interface is rough and the feature set is small. At the end you get the answer to a question defined up front: Does this work, yes or no?
Can the core function be built with the planned technology at all?
Does the system respond fast enough with realistic data volumes?
Does data exchange work with the systems already in place?
Will the chosen structure also support full development later on?
Technical problems surface in the first few weeks, not after months.
A wrong turn in a PoC costs a fraction of what it would cost in a running project.
You decide on the overall budget based on test results.
A working demonstration convinces people more than a slide deck.
A PoC pays off when a single technical question decides the whole project. When the technology is well known, it just costs time.
For an existing system, the Software Audit is usually the better first step: two weeks, fixed price of €3,000 to €6,000.
For a configurator, that might be 3D rendering with real plant data. For a catalog, search across a large assortment. For an integration, the interface to the ERP.
PoC code is written to answer the test question, not to run in production. Whether parts of it carry over into full development is something we decide together with you at the end.
The answer to the test question is yes, no, or yes under certain conditions. You also get the material you need to decide on the overall budget.
Measured against the criteria we set before the start. If the answer is no, that's a result too: you know after weeks instead of months.
Response times, data volumes, behavior under load or interface test results, depending on what was tested.
One you can demo to management and business teams. We hand over the prototype and the source code.
A list of open issues for full development and an effort range based on what was actually built in the PoC.
Four steps in two to six weeks. The test question and the criteria are set before we write the first line of code.
Together we define which question the PoC answers and how we measure the result.
We build the critical functions and test them with real or realistic data.
We compare the results with the criteria from the start and write them up.
We walk you through the results. You decide what happens next.
A PoC starts at €5,000. The price depends on how complex the test question is, how many technologies are involved and how quickly you need the result.
Project complexity
Technology areas
Estimated price range
€7,500 to €12,500
A rough guide, not a quote. We give you the price for your project after the intro call.
Together we define the test question and the criteria the result will be measured against.
The critical functions run and can be demonstrated.
What has to be solved before go-live, and where are the open issues?
An effort range for full development, based on what was built and measured in the PoC.
Three questions that are often still open before a software project starts, and that a PoC answers.
Several frameworks or technologies are on the table for a new project. The PoC builds the same core function with each candidate and shows which one fits.
A third-party system needs to send or receive data. The PoC tests whether the connection is feasible and how quickly the interface responds.
The application has to handle many simultaneous users. The PoC measures behavior under load before the actual development starts.
Two examples from our own projects are right below, under success stories.
Plant engineering · 3D configurator
Industrial plants were to be configured in 3D in the browser, with large data volumes and high performance requirements.
Analyzed web technologies, ran performance tests and chose the technology stack: React, Three.js and WebGL.
In 2018 the MVP with the core functions, in 2019 extensions and data compression.
Audio software · SaaS
VST audio plugins were to run in a cloud environment so musicians could master their tracks online.
First tests with the VST SDK and audio processing via Node.js.
In 2020 the SaaS platform with Nuxt and NestJS, in 2021 the launch in three world regions.
Four questions for a first take. They don't replace a conversation, but they show whether one is worth having.
Are you planning a technically complex project?
Is there uncertainty about technical feasibility?
Is the budget for the overall project above €50,000?
Do several technologies or systems need to be integrated?
In the intro call we work out whether a proof of concept is the right answer, what it should test and what price range to expect. The call takes 30 minutes and is free. We work in English and German.
Jens Bohl Founder and Managing Director
Platforms, integrations, and hosting and operations
projekt@onveda.de+49 2173 2972 20