Pricing software: Who will choose it? its roadmap in two years?
November 16, 2026
Purchasing pricing software also means committing to a specific path. It is important to distinguish between features currently in production and promises of future integration, and to understand who decides how to allocate investments among the vendor’s products.
The role of pricing experts in decision-making says a lot about the product's future. Maintenance, migrations, and support must be specified in the contract—not just promised.
When choosing pricing software, we compare what each solution can do today. But we’re committing to it for several years, and the solution will evolve during that time.
This article is intended for pricing, sales, and procurement departments. It explains how to verify, before signing a contract, that your business needs will remain a priority for the software vendor following an acquisition, a change in ownership, or an expansion of its product offerings.

You're buying a solution—and its future trajectory as well
A pricing software roadmap is a list of the updates the vendor commits to delivering—and, most importantly, the order in which they will be delivered. It determines what you’ll have in two years.
When making a choice, we compare what the solution can do today. That's only natural: it's what we can demonstrate, test, and quantify.
But a pricing contract lasts for several years. During that time, your challenges evolve: new channels, new rules, and new competitive pressures.
The solution will also evolve. The question is who will decide in which direction, and whether your priorities will still factor into that decision.
Distinguishing between what exists and what is promised
A sales presentation often combines three elements: what’s currently in production, what’s in development, and what’s being considered. All three are presented with the same confidence.
"Available" means in production at a comparable customer site
A feature is considered available when a customer of similar size and industry uses it on a daily basis. A prototype, a demonstration using sample data, or a pilot version do not count as such.
The surest way to decide is to test it using your own data. That's the whole point of a well-defined pricing proof of concept (POC).
Convergence Announced Following an Acquisition
When a software company acquires other software companies, it almost always announces a move toward convergence: a unified platform, a common interface, and shared data.
This project is real, but it takes time and ties up our teams. Until it's finished, two products will coexist, and one of them will eventually receive less attention.
Ask for a date, a scope, and a client that has already migrated. Without these three elements, convergence remains merely an intention.
Who decides how to allocate investments among products?
For a publisher specializing in a single title, the question rarely arises: pricing is the product. For a publisher with multiple titles, every euro spent on development is allocated among them.
An acquisition, a change in ownership, or an expansion of the product offering can shift this trade-off. The module that was once the publisher's pride and joy may become just one line among many in a portfolio.
CIOs at large companies report that their primary software vendor sets the timeline and terms for system upgrades. 76% feel they have very little leverage in negotiations.
(Origina, Censuswide survey of 2,018 CIOs and IT decision-makers at large companies (United States, United Kingdom), May 2026, published in October 2026)
This power dynamic exists with all suppliers. It becomes more pronounced when your tool is no longer at the center of the developer's strategy.
So let's ask the question straight out: What percentage of revenue and R&D headcount does pricing account for? And who, within the leadership, advocates for its roadmap?
Do pricing experts have a say in the matter?
A useful roadmap is developed with people who know the business: the hierarchy of rules, regulatory constraints, and the realities of a pricing committee.
When these profiles are sidelined in favor of purely technical or financial considerations, the solution follows the platform’s priorities, not those of its users. The business context is the first thing to be lost.
Ask who writes the specifications for new pricing features, and how many of those people have actual experience in the field. Also ask how customer requests are escalated and prioritized.
The role of the expert does not disappear with automation; it simply shifts. We discussed this in relation to the pricing manager in the age of AI.
What You Need to Get in Writing
A roadmap is not a contractual commitment. Certain points, however, can and should be.
First, maintenance: How long will the version you purchase be supported, patched, and updated? Next, migrations: If the vendor switches platforms, who will bear the cost and manage the timeline?
Of the CIOs surveyed , some have paid, over the past three years, for an upgrade mandated by a software vendor that they believed would reduce performance, reliability, or value for the company.
(Source: Censuswide survey of 2,018 CIOs and IT decision-makers at large companies (United States, United Kingdom), May 2026, published in October 2026)
Finally, support. Pricing software works alongside your teams: training, rule configuration, and skill development. Ask who will be supporting you, and what happens if that team changes.
If you've already had experience with a first tool that didn't catch on, these points are even more important. We discuss this in our article on how to switch pricing tools without repeating the same mistakes.
Intentions matter less than track record. What a publisher has delivered to its customers over the past two years is a better indicator of what it will deliver tomorrow than its presentation for the year.
Ask for a list of recent versions and what specific changes they've brought for the pricing teams.
How AI Is Changing Roadmaps
AI has inflated the roadmaps of every publisher. Autonomous agents, conversational assistants, automated recommendations: every presentation heralds a new wave of them.
The criteria for evaluation are the same as for any proposal, with one additional requirement. A price recommendation must be able to be explained, line by line, to a committee or a supplier.
So ask which AI features are in production, what data they’re based on, and how they justify their recommendations. We go into more detail on this topic in our article onthe explainability of price recommendations.
A serious AI roadmap also outlines what it won't do. An agent that decides your prices on its own isn't necessarily a step forward, as the rise ofagentic pricing shows.
Questions to Include in Your Request for Proposals
These questions apply to all publishers, including Booper. They build on the questions raised in our first article in this series:Does your next publisher really need to do everything?
| Question to Ask | What the answer should show |
|---|---|
| Which of the features presented are currently in production at a comparable client? | Industries, customer sizes, and go-live dates |
| What percentage of your R&D budget is allocated to pricing? | An order of magnitude, and its change over three years |
| Who decides on the pricing roadmap? | Qualified individuals with professional experience |
| How long will our version be supported? | A term specified in the contract |
| If you switch platforms, who pays for our migration? | Explicit financial support, or a quantified commitment |
| What happens to the team that supports us in the event of a buyout? | Commitments to continuity, not verbal assurances |
No answer can guarantee the future. But the clarity—or the hesitation—with which an editor responds speaks volumes about the place they have in mind for you.
The answer lies not in promises, but in the organization: who develops, who oversees, and for which clients.
Choosing a pricing platform also means choosing the conditions under which your business will grow. To understand how this choice fits into the bigger picture of your project, read our guide to selecting and implementing a pricing tool.
Last article in the series:Can your publisher follow through on its promises?
Would you like to compare the publishers' roadmaps?
Our experts help you distinguish between what’s available and what’s promised, based on your own pricing challenges.
Let's discuss your choice of publisherFrequently Asked Questions About a Pricing Editor's Roadmap
This is the list of updates a publisher plans to release, along with the order in which they will be released: new features, integrations, platform changes, and AI enhancements.
It generally has no contractual value, but it determines what you'll be getting in two or three years. That's why it's important to understand who writes it, what criteria are used to evaluate it, and what the publisher has actually delivered in the past.
A feature is considered available when a customer of comparable size and industry uses it on a daily basis in a production environment. A prototype, a demonstration using sample data, or a pilot version are not sufficient.
Ask for sectors, deployment dates, and, if possible, a contact person. The most reliable test is still one that demonstrates value using your own data, with success criteria established before you begin.
An acquisition can provide resources, but it often shifts priorities. The acquired product becomes part of a portfolio, where each development budget is allocated among several software projects.
The most common effects include a planned transition to a common platform, mandated migrations, and changes in staff.
Before signing, ask what is planned for your version, who will bear the cost, and what guarantees the continuity of your support.
Because a useful roadmap is developed with people who know the business: the hierarchy of rules, regulatory constraints, and the realities of a pricing committee.
When these profiles are overshadowed by purely technical or financial considerations, the product ends up prioritizing the platform's needs over those of its users.
Ask who writes the specifications for the pricing functions, and how many of those people have actually worked in the field.
Three commitments warrant a specific clause: the maintenance period for the purchased version, support for migrations if the vendor changes platforms, and the continuity of support.
A roadmap is always just a guideline, but these three points can be included in a contract. They protect your project from changes in the publisher’s strategy, whether those changes result from an acquisition, a new shareholder, or an expansion of the product offering.
Apply the same criteria as you would to any feature promise: which features are in production, for which customers, and since when. Add a requirement specific to pricing: explainability.
A price recommendation must be justifiable to a committee or a supplier.
Ask what data the models are based on, how they explain their recommendations, and who has the final say. A thorough roadmap also specifies what the AI will not do.
The floor price is the price below which a sale cannot be finalized without approval. Together with a target price and a ceiling price, it forms a range that guides the negotiation without locking it in.
The sales rep retains their autonomy, the company maintains its margin, and sales that fall below the threshold become transparent. AI helps set these thresholds by customer segment, provided that the sales rep understands where they come from.
The history shows what price was listed. Traceability shows who decided it, when, on what basis, and with what approval.
It is used to provide evidence during an audit, to justify a price to a supplier, a franchisee, or management, and, above all, to link each decision to its outcome. With AI, it distinguishes between what the machine suggests and what a human decides.
A vague pricing policy works as long as a human makes decisions on a case-by-case basis. When automated, it applies a set of priorities that no one has chosen, across the entire catalog and with every recalculation.
Conflicting objectives, implicit rules, and exceptions that have become the norm must be resolved beforehand. With AI, the stakes are even higher: a poorly defined objective is optimized with formidable precision.
