Define the Core Transaction and Its Boundaries

What it means

The company can describe one repeatable customer, offer, sales path, delivery method, quality standard and economic logic without immediately disappearing into exceptions. This does not require the company to eliminate every variation. It requires management to distinguish the core transaction from useful customization and from accidental custom work that prevents learning. The team should know what ordinary business looks like, what it promises, how it is sold, how it is delivered and what economics make it acceptable.

What it requires

This milestone matters because Stable companies often have enough success to hide how much variation exists. Revenue can come from several adjacent customer types, bespoke projects and special-case offers. Each may be attractive on its own, but the aggregate can make the business difficult to teach. The first Repeatability milestone is therefore clarity about what the company intends to reproduce.

Why it matters

The milestone is strong when the company can point to a recognizable standard path and classify variation deliberately. The founder and team can say which work is core, which variation is strategically useful, which exceptions are experiments and which requests should be declined. That creates a stable object for the rest of the organization to improve.