Pricing: Pricefx, Revionics, build, or implement. Where each path wins.

To put data-driven pricing into a mid-size chain, there are three paths. Buy an engine like Pricefx or Revionics. Build internally. Hire someone who implements.

The question “which engine is best” is the wrong one. The engines are serious. The right question is who will operate price when the year-end promotion gets tight.

The three paths, as cost shapes

The difference is not in the feature list. It is in the shape of the cost and the responsibility that remains afterward.

Buy a platform. Recurring annual license, high, predictable. Pricefx, Revionics, SAS, and DemandTec compete for the same budget pocket. It turns on fast and brings pricing science built in. The criterion is the product’s, and you fit the operation to the engine, not the other way around.

Build internally. Cost in a data science and pricing engineering team. Variable, slow, and it becomes a permanent house responsibility. It makes sense for those with scale who want price as a proprietary edge.

Hire an implementer. Project cost, fixed by scope. The internal team keeps the engine and the runbook at the end. It builds against your data, with your KVI list and your elasticity, and leaves.

The decision tree

The deciding condition is operational: who owns price on the next big promotion, a year from now?

• If the answer is “the engine vendor”, buy the platform.
• If it is “the consultant”, you did not finish buying, and you will pay at every recalibration.
• If it is “my team, with criterion and rules written before the code”, you want an implementer.

The trap in each path

The platform fails when the license is expensive and the team still prices by eye, because nobody trusts an engine they do not understand. The build fails when pricing becomes an ownerless project and the key person leaves with the knowledge. The implementer fails when the pricing criterion stays vague and the work stretches.

The defense, on any path, is the same: the KVI list and elasticity measured before the engine. Without that, any of the three prices the wrong item with confidence.

What the choice decides

Take the pricing decision on your desk. Ask the team which of the three paths you assumed last time. Almost always nobody chose; it drifted to whatever felt safest in the meeting.

Tell me the shape of the problem, chain size and category. In one hour I will send back which path fits, with no bias. If it is a platform, I will point you to the three names that show up in pricing RFPs. If it is an internal team, the profile to hire. If it is an implementer, the next conversation is the two-week Diagnóstico, which ends with criterion, timeline, and cost signed before the code.