Matvey Zakharov
RU

Every order is “special”

Routine configurations and delivery paths are not separated from genuine custom work. Each order is handled as a new exception, so more sales require more custom coordination.

Routine orders bypass individual review

The same 480-order sample. Routine orders sent for individual review: 384 → 0.

Before
Accepted orders480
Is there a reusable configuration?

Standard route0

Individual review480
Routine orders in individual review: 384
After
Accepted orders480
Is there a reusable configuration?

Standard route384

Individual review96
Routine orders in individual review: 0
Genuine custom work keeps its own route. Arrows show routing rules; numbers count orders.

See which revenue needs custom work

The same orders and amounts. Inner level: route. Outer level: whether the work scope is explicitly priced.

Before
Scope explicitly pricedScope not separately priced
Scope not separately priced: RUB 17,370,600
After
Scope explicitly pricedScope not separately priced
Scope not separately priced: RUB 421,500
Sector area represents revenue. Each level has the same total. No profit increase is assumed.
SOLUTION

Standardization & exception design.

  1. Compare customer requirements, quotes and delivery records to distinguish recurring configurations from work that needs a separate estimate.
  2. Define scope, pricing and delivery for standard options, and who estimates extra work before a commitment to the customer.
  3. Check new orders: standard work follows a reusable route; custom work has an agreed scope and price.

What an engagement produces

  • A catalogue of standard order configurations
  • Pricing and delivery rules
  • Criteria for genuine exceptions
  • A process for estimating and approving custom work
  • Setup in your tools, or oversight if you set it up yourself

Rules, thresholds, scripts and automation logic are engagement deliverables and are not published here.

Find out whether this is actually your constraint.

Explore another problem