ORIGINAL APPROACH
Fill everything in first.
Organisation, employees, equipment, work centres, items and integrations. Only then comes the first order.
A LOT OF EFFORT BEFORE THE FIRST RESULT
PRODUCT & TECHNOLOGYLet a small manufacturer see the product’s value before getting tired of setting it up.
ORDER #0048 / NEW
Customer: Sever · Dispatch: 28 October
The order is on schedule.
Next step: hand the plan to the foreman. Everything else can be configured later.
CONTEXT
Smena brings together orders, operations and capacity for small manufacturers. Its main user is an owner or foreman who keeps the plan in a spreadsheet and discusses changes in messages.
The concept explores a specific tension: accurate planning needs data, but a new user has no reason yet to spend time entering it. Value has to come first.
PRODUCT DECISION
We defined first value precisely: the user sees a plan for their order, understands the sequence of work and can discuss the deadline with the foreman. Creating an account is not that result.
ORIGINAL APPROACH
Organisation, employees, equipment, work centres, items and integrations. Only then comes the first order.
A LOT OF EFFORT BEFORE THE FIRST RESULT
CHOSEN SCENARIO
Add one order, choose operations from a short template and get a draft plan. Refine settings as needed.
ORDER → OPERATIONS → PLAN
DECISION LOGIC
We set working parameters for the design: a segment, a path to value and viable economics. These are initial model assumptions that need validation with real users before investment.
01 / WHO WE START WITH
The first segment is small make-to-order manufacturers. Capacity planning is a recurring need, and the owner or production manager makes the buying decision.
02 / WHERE USERS DROP OFF
In the initial model, 72% of users understand the offer and 49% reach their first plan. This gap sets the focus for validation.
We test the first steps: creating an order, choosing operations and viewing the finished plan.
03 / IS IT WORTH FIXING?
4.4×
The modelled scenario allows investment in activation. Before scaling acquisition, we need to validate margin, customer lifetime and implementation cost.
CAC ₽4,200 · LTV ₽18,600 · payback 3.8 months
04 / WHAT WE DO NOT KNOW YET
Working confidence estimate:
27 / 100
This is the central untested assumption. If the first plan requires an implementation specialist, we need to shorten the workflow itself, not just remove a few fields.
05 / WHAT WE DO NEXT
Test the workflow with one real order: enter the inputs, choose operations and get a plan without prompts from the moderator.
we expect:
activation ↑ · retention ↑ · payback ↓
DESIGN → ENGINEERING
A short first workflow does not mean stripping down the future product. Separate what is essential for the first decision from what can be refined along the way.
01 / INTERFACE
One main workflow per screen, clear defaults and a saved draft. Users always know what is done and what remains.
02 / ARCHITECTURE
The first order is created manually or imported from CSV. Reference data, roles and accounting systems are connected separately and do not block the first plan.
03 / ANALYTICS
The events order_created, operations_confirmed and plan_viewed trace the path to value. Errors and requests for help are analysed at each step.
NEXT VALIDATION
Next, owners and foremen try the workflow with their own orders. We observe where they need a prompt, how clear the plan is and whether they are willing to use it at work.
The criterion is not click speed but whether someone can get a usable result independently. If they cannot, we revisit the workflow and the quality of the plan. New features come after first value is validated.
/ YOUR NEXT MOVE
We will examine the journey, economics and constraints, then identify which change is worth testing first.