Can your pricing editor Will he be able to fund his promises all the way through?
November 16, 2026
A publisher's stability does not depend on its size, but on whether its resources match its promises. A roadmap funded by money that has yet to be received remains a gamble.
Before signing, you need to understand how the publisher is funded, verify the continuity of its teams, and obtain written commitments regarding service, data backup, and data restoration.
Pricing software calculates prices every day that determine your profit margin. Choosing it also means placing your trust in the software provider’s ability to fulfill its commitments throughout the duration of the contract.
This article is intended for pricing, finance, and procurement departments. It provides practical insights into the issue of funding a software vendor: R&D, support, service continuity, and data recovery.

You entrust your profit margin to a publisher for several years
The strength of a pricing software provider lies in its ability to fulfill its commitments throughout the entire term of the contract: to develop, maintain, support, and provide service, without relying on any uncertain event.
Pricing software isn't just a peripheral tool. Every day, it calculates prices that determine your margin, your pricing image, and your compliance.
Its reliability is therefore just as important as its features. A brilliant but unstable editor poses a risk to your business—not just to your project.
It's not a matter of size. A large corporation can discontinue a product, while a small team can last twenty years. What matters is the balance between resources and promises.
Understanding How the Publisher Is Funded
A publisher funds its development and day-to-day operations in two ways: through its revenue or through outside capital. Both models are valid.
The first moves at the pace of its customers. The second can move faster, but it depends on investor confidence and their timeline.
The relevant question isn't "Are you profitable?" It's "Do your current revenues cover the service you're selling me, and do your investments depend on future funding?"
Distinguish between available resources and expected funding
An ambitious roadmap comes at a cost. If that cost depends on an announced fundraising effort, a hoped-for initial public offering, or a partner still under discussion, the promise is conditional.
The market has recently shown that these conditions are not always met. Promising companies have had to downsize their teams, sell themselves in a hurry, or shut down.
Number of startup closures in one year in the United States: 966 in 2024, compared to 769 in 2023, among Carta’s client companies.
(Carta, data reported by TechCrunch, January 2025)
These figures are not directed at any specific publisher. They serve as a reminder that a development plan financed with future funds remains a gamble—and that this gamble is, in part, yours.
In-house development is no exception to this logic: it, too, requires sustainable resources, as we quantified in our article on the true cost of an in-house pricing tool.
Acquisitions, integrations, client projects: juggling it all at once
A software company that grows through acquisitions must fund three initiatives at once: acquiring new companies, integrating the acquired products, and continuing to serve its existing customers.
Everyone draws on the same scarce resources: developers, project managers, and subject-matter experts. When there’s a shortage of money or staff, one of the three slows down—and it’s rarely the first one.
Ask how the teams are divided among these projects, and what the plan is if the schedule slips. Questions about the publisher's roadmap are closely related to those about funding.
Team Continuity and Service Commitments
Your project relies on people: the team that configured your rules, the team that responds to incidents, and the team that knows your history. Their stability is part of the service.
Consider staff rotation, how your configuration is documented, and how knowledge about your project is shared. A project that depends on a single person is vulnerable, regardless of the software vendor.
As for the contract, service commitments must be specified in writing: availability, response times, and restoration times. And there must be consequences if these commitments are not met.
Recover Data and Resume Operations
The final guarantee covers the worst-case scenario: a service outage, a sale, or a failure. What happens to your data, your rules, and your price history in that case?
Only executives would be able to continue using their primary AI provider without interruption if its service were to stop tomorrow. For 47%, at least one key function would cease to operate.
(Zapier, Centiment survey of 542 U.S. business executives, January–February 2026)
You need to know where your data is hosted, how often it is backed up, and how long it takes to restore the service. You also need to know in what format you can retrieve everything, and how long that will take.
We provide details on the assets to be recovered, rules, trade-offs, and product matching in our article on the reversibility of a pricing solution.
We apply these questions to ourselves. Our clients' data is hosted in France by OVHcloud on dedicated servers for each client, with daily backups to a remote location.
Our commitments are public: data loss limited to 24 hours, service restoration within 8 hours as standard, and data deletion 60 days after the end of the contract. Details are available on our data security and compliance page.
How AI Is Changing the Cost of Delivering on Its Promises
AI has driven up the cost of developing pricing software. The models require computations, prepared data, and rare profiles, and these costs accrue every month.
A publisher that promises cutting-edge AI must therefore be able to fund it over the long term—not just demonstrate it. Ask where the models are running, who’s paying for the computing power, and what happens if those costs rise.
Your choice of hosting also affects your sovereignty, as we explain in our article onon-premises vs. cloud-based AI for pricing software.
Questions to Include in Your Request for Proposals
These questions apply to all publishers, including Booper. They are a continuation of a series that began with “Does Your Next Publisher Really Have to Do Everything?”
| Question to Ask | What the answer should show |
|---|---|
| Do your recurring revenues cover your operating costs? | A clear response, supported by figures or documentation |
| Does your roadmap depend on future funding? | What has already been funded, and what has not yet been funded |
| How are your teams divided between clients and integrations? | A description of the organization, with named contacts |
| What service commitments are specified in writing, and what are the penalties? | Availability, wait times for treatment, and recovery times |
| Where is our data, and how can we retrieve it in the event of a system shutdown? | Hosting, backups, format, and turnaround time |
| Has your business continuity plan been tested? | The date of the last test and its results |
A reputable publisher can easily provide an answer, backed up by supporting documents. Hesitation on these matters is, in itself, an answer.
A commitment funded by existing resources binds the publisher. A commitment funded by anticipated resources also binds your project.
Choosing a pricing platform also means choosing the conditions under which your business will grow. To assess the expected return on these investments, read our article on the ROI of a pricing solution.
The final installment in the series:Subscription, usage, or results—who bears the risk?
Would you like to ask Booper these questions?
We address each of these points one by one, with supporting documentation: hosting, service commitments, reversibility, and support.
Ask us your questionsFrequently Asked Questions About the Reliability of a Pricing Editor
Start by understanding its business model: Does its recurring revenue cover its operating costs, or does it rely on outside capital to move forward? Both models are valid, but they entail different levels of commitment.
Next, ask what parts of the roadmap are already funded and which ones depend on future funding.
Back this up with verifiable information: customer retention, team stability, written service commitments, and a tested disaster recovery plan.
Yes. Size doesn't determine stability: a large corporation can discontinue a product, while a small team can last a long time. A young company often brings responsiveness and strong industry expertise.
The question is whether its resources match its promises.
A startup that funds its service through its own revenue and includes a contractual guarantee of data portability poses less risk than a larger company whose roadmap depends on a hoped-for round of funding.
It all depends on what is specified in the contract. Without a reversibility clause or a recovery plan, access to the service and data may be interrupted—sometimes abruptly.
To protect yourself, you need to know where the data is stored, how often backups are performed, the format and timeframe for data recovery, and what happens in the event of a transfer of ownership or bankruptcy proceedings.
These points are negotiated at the time of signing, not when problems arise.
A disaster recovery plan, or DRP, describes how the publisher restores service following a major incident: an infrastructure outage, a cyberattack, or the loss of a data center.
It establishes two benchmarks: the maximum amount of data you are willing to lose, and the maximum recovery time. A disaster recovery plan is only effective if it is tested regularly. Ask for the date of the last test and what the results showed.
At a minimum: an uptime rate, a response time for incidents based on their severity, a recovery time, and consequences if these commitments are not met.
When choosing software to calculate your prices, consider the frequency of backups, the hosting location, the terms for data return at the end of the contract, and the continuity of the team supporting you.
These commitments must be included in the contract or its appendices.
Because AI has made the development and operation of pricing software more expensive. The models require computation, prepared data, and specialized expertise, and these costs accrue every month.
A publisher that promises advanced AI must therefore be able to fund it over the long term. Ask where the models are run, who pays for the computing power, and what would happen if that cost increased. The answer will tell you whether the promise is sustainable.
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.
