Honest timeline: elasticity-based pricing in one category, 10 to 16 weeks

Implementing elasticity-based pricing in one category takes 10 to 16 weeks, if the history has real price variation. With no past variation, there is no way to estimate elasticity, and the timeline becomes however long it takes.

The timeline number hides the most important condition. Elasticity is estimated from moments when price changed and sales reacted. A category that never moved its price has nothing to estimate.

The realistic range

10 to 16 weeks, one category, a small team. The range assumes a history with observable price changes, clean sales, and a KVI list already defined.

If the category was priced on the same ruler for years, add a controlled-experiment phase to generate variation. That adds weeks and requires stomach from leadership.

What “data in reasonable shape” means here

This is where the project lives or dies. Reasonable means concrete things.

• Price history with real variation, not a constant price for two years.
• Clean sales, separated from shelf-out and from the neighbor’s promotion effect.
• A competitor price map, at least on the comparison items.
• KVI defined by behavior, not by the inherited list.

Three of the four, the range holds. Less than that, double the first phase.

The phases

Diagnóstico: 2 weeks, choose the category and write the margin and traffic criterion. Implementação: 8 to 12 weeks, model estimating elasticity per SKU and proposing price, with commercial validating. Operação: quarterly, the internal team running the engine.

What moves the timeline by 50%

Three decisions, and you can see all three.

• How many categories. One proves it; three become an unfocused project.
• Whether price variation exists in the history, or has to be created.
• Whether commercial joins the criterion, or receives the price and ignores it.

The week-one criterion

The number that decides is not the estimated elasticity. It is category margin without losing KVI traffic, measured on sales, compared against the baseline. Margin that rises while traffic collapses is not a win; it is the customer leaving slowly.

Take the pricing project on your roadmap. In ten seconds, name the three indicators that say whether it is working. Stalled? Then the project has a hope, not a criterion.

Send me the three candidate indicators your pricing project will measure. In one hour I will send back which predict healthy margin and which predict traffic in flight. If the shape confirms, the two-week Diagnóstico ends with a one-page document, three indicators, three ranges, three triggers, that the squad holds for the rest of the Implementação.