Skip to content
dvnt.io

Resources · glossary

Proof of concept

A small, deliberately incomplete piece built to test one risk: whether something can be done at all. It is not the first version of the product.

Also called
  • proof of concept
  • PoC
  • feasibility study
  • technical spike
  1. 01

    How it differs from an MVP

    An MVP reaches users and is meant to earn money or gather information from the market. A PoC answers a technical question (is this integration possible, can this volume of data be processed in an acceptable time), and once it has answered, it usually goes in the bin.

  2. 02

    When it's worth doing

    When the project rests on one assumption that, if proven wrong, wrecks the whole budget. A week spent testing the integration with a warehouse system is cheaper than finding out after three months that the system doesn't expose the data you need.

  3. 03

    The main trap

    Growing the PoC into a product. It was built without tests, without security and without thought for maintenance, because that was the point. Bolting more features onto it is the most expensive route to a system nobody wants to touch.

  4. 04

    How to close it

    With a question agreed up front and a deadline agreed up front. A PoC without a written success criterion can run for as long as you like, because there is always one more thing to check.

In practice

Related terms

  • MVP (minimum viable product)The smallest version of a product that genuinely solves a user's problem and lets you check whether anyone will use it. Not a prototype, and not a version stripped of quality.
  • Build vs buyThe decision between building your own solution and buying a ready-made one. It is settled on costs over time and on whether the process is the company's advantage or just a necessity.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.