Skip to main content
GullySystem

MVP and Proof of Concept Development

MVP and proof of concept development builds a small first version that tests the assumption most likely to be wrong. Real users try it before the full budget is committed.

Proof of concept, or a first product

The two are different builds. One answers whether a thing can be done at all, and the other answers whether anybody wants it.

Proof of concept

A throwaway build that settles a technical doubt, such as whether a machine reading can be captured at all.

Minimum viable product

A real product with fewer features, used by real customers.

A pilot

One branch or one dealer runs it for an agreed period before anybody else sees it.

What gets cut, and what stays

Features can be cut. Logins, backups and the data model are kept, because a first version passes its shortcuts on to every later one.

Cut: settings and variations

One workflow is fixed in code until someone needs a second.

Cut: reports nobody asked for

An export to Excel covers most early reporting.

Keep: logins, backups, data model

Shortcuts here carry into each later version. They are costly to undo.

After the first version

There are two outcomes. Either people use it and the build continues, or they do not, and that is learned before the full budget is spent.

Watch what people do

Usage shows which screen opens daily and which one nobody has touched since the demo.

Decide before adding

The next release comes from what gets used, not from the original wish list.

Replace the shortcuts

Some early code is meant to be thrown away once the shape has settled.

FAQ

Frequently asked questions

What does an MVP and proof of concept build include?

The smallest set of screens that lets someone finish a real task, plus logins, a sound database and a way to see what gets used. Everything else waits.

Can it be shown to investors?

Yes. A working screen with real data shows more than a deck does, as long as nobody claims it does more than it does.

Do we throw it away later?

Not usually, provided the data model was done properly. Screens get replaced as you learn. The database and core rules carry into the full product.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements