When building software products or solutions, it is of critical importance to define early enough the target output — in terms of both functionality and ‘production readiness’. This is a practical guide to help you define a ‘prototype’, versus a ‘proof of concept’ and a ‘minimum viable product’ — and avoid costly misunderstandings.