The BUILD project mode: our method for creating business tools

Building a digital product shouldn't start with six months of specifications. Our approach favours short cycles.

BUILD 01 — The problem

Describe the problem in one sentence. Example: “Our teams spend hours manually consolidating data from several marketplaces to know each product's profitability.”

If the problem can't be clearly stated, it's probably too early to build.

BUILD 02 — The current workflow

Document what happens today. Who? What? With which tool? How many times? How long? To produce what?

BUILD 03 — The target workflow

Remove useless steps before automating them. This is fundamental. Automating a bad process simply creates a faster bad process.

BUILD 04 — The MVP

Determine the essential features. The MVP must allow you to verify a hypothesis. Not to immediately replicate mature software.

BUILD 05 — The prototype

Give the product a shape. Navigation. Screens. Actions. Information. Workflows. Users must be able to understand how it works before everything is developed.

BUILD 06 — Development

Build the product in functional blocks. Each cycle must produce something testable.

BUILD 07 — Usage

Measure: time saved; actions performed; errors avoided; usage rate; frequency; features used.

BUILD 08 — Iteration

Keep what brings value. Change what creates friction. Remove what isn't used. Add only what usage justifies.

Build small. Learn fast. Improve continuously.