Where does a pricing team's time really go: the actual distribution
October 9, 2026
Pricing decisions account for only a small portion of a pricing team’s week. The rest is spent on preparation, coordination, formatting, justification, and corrections. This work is real, and it takes time away from what creates value.
The order of correction is: eliminate, then automate, then delegate. A tool first reduces the amount of preparation required; coordination and justification only improve if decision-making processes also change.
Ask a pricing manager: How much time do you spend deciding on a price? The off-the-cuff answer is about half a week.
Then ask them to reconstruct their past week, time slot by time slot, and the number plummets.
In between, there’s everything that doesn’t have a name: compiling data extracts, following up, fixing a corrupted file, explaining for the fourth time why this price is what it is. This work is invisible because it doesn’t appear in any of the objectives.

The Work That Has No Name
A job description for a pricing manager outlines the following responsibilities: defining pricing policy, determining market positioning, and managing margins.
A typical week in the life of a pricing manager looks quite different: files, follow-ups, meetings, and explanations.
The discrepancy is not a sign of poor organization. It is structural and stems from a specific characteristic of pricing: it is a function that has almost none of its own data.
Sales data falls under management control, purchasing terms under the buyers, inventory under supply chain management, competitor reports under a service provider, and the product database under a third-party system.
Deciding on a price, therefore, requires gathering information before thinking, and gathering information costs more than thinking.
This lack of strategic direction goes beyond the issue of time alone, as our article on companies that truly manage their pricing demonstrates.
Why This Time Remains Invisible
Because it isn't included in any annual goals or metrics. No one is evaluated based on the number of hours spent consolidating data extracts; everyone is evaluated based on profit margin.
Preparatory work is therefore seen as a natural prerequisite—just like turning on a computer—rather than as a burden that can be measured and reduced.
It also remains invisible because it is fragmented. Three-quarters of an hour here, twenty minutes there: none of these moments seems significant on its own. It is their cumulative effect that is significant, and that cumulative effect can only be seen if one measures it deliberately.
The Five Tasks That Take Up the Week
1. Data Preparation
Extract, reconcile, verify, correct obvious discrepancies, and reconstruct a comparable scope from one month to the next. This is the most labor-intensive and thankless task: it starts over exactly the same way every cycle, and it leaves no trace of value.
When done in a spreadsheet, this process quickly reaches its structural limits, particularly when it comes to monitoring competitors' prices.
Operational teams find a spreadsheet error every week, and 22% find one every day. Each error triggers a new cycle of verification and correction.
(DOSS, study published on May 14, 2026)
This figure does not specifically pertain to pricing. It explains why preparation is never finished: part of the time is spent verifying what has already been prepared.
2. Coordination
Follow up with a buyer regarding a missing requirement, wait for approval, request an incomplete competitive analysis, or mediate a disagreement between two departments.
This position has a unique feature: it cannot be streamlined through tools alone, because it involves organizational and decision-making processes.
3. Formatting
Turning an analysis into a presentable document, adapting the same content for three different audiences, reworking a slide because the scope changed the day before.
This position grows along with the number of governance bodies, and it is the first to balloon when an organization adds a committee.
4. The Justification
Explaining why a particular price was set to a buyer, a store manager, or sales management is a legitimate and necessary task. The cost of doing so depends entirely on one thing: the system’s ability to reconstruct the decision-making process.
When you have to retrace this path manually for each question, justifying your decision becomes a part-time job. This is exactly the challenge described in our article on explaining a pricing decision.
5. Correction
Manually correct what the system has suggested incorrectly. Each repeated correction highlights knowledge that the tool lacks, and we’ve devoted an entire article to this topic: business context is not data.
Until it is formalized, the team re-enters it manually, week after week.
The other 5 parts of the series “Managing an AI Pricing System”
- ROI of a pricing solution: time savings or increased profit margins?
- Rule Debt: What Happens to a Pricing Engine After 18 Months
- The business context is not data
- Developing an In-House Pricing Tool: The True Cost of a Build
- Reversibility: What do you get back if you switch to a different pricing solution?
Measuring its actual distribution rather than estimating it
Before correcting anything, we need a number. Subjective estimates are misleading in this regard: we remember the decisions, not the twenty minutes spent piecing a file back together. Fragmented tasks are almost always underestimated.
A brief assessment—covering regular weeks, broken down by major categories, and involving the entire team—is sufficient to provide a rough estimate. The goal is not to conduct cost accounting.
The division of responsibilities differs significantly between a leader and a manager, and it is this difference that indicates where action is needed. It directly informs the discussion on how to structure a pricing organization.
The two key figures to take away
The first is the decision-making component: the percentage of time spent analyzing, simulating, and making decisions. This is the indicator of the function's health.
The second is the recurring portion: the percentage of time spent on tasks that are identical from one cycle to the next. This is where the potential lies, because tasks that repeat identically are the ones that become automated most easily.
These two figures serve another, often more immediate purpose: they turn a request for resources into a demonstration.
A team that simply asks for additional staff rarely gets its way; a team that demonstrates that the bulk of its weekly workload is recurring will be taken seriously.
Eliminate, automate, delegate: in that order
The order is more important than the measurements themselves, and in practice it is almost always reversed.
1. Delete
For every recurring task, the first question is “What happens if we stop doing it?”, long before “How can we speed it up?”.
A weekly report that three people received but only one actually opened; a metric that had been generated out of habit since a reorganization long ago; a committee whose agenda is empty half the time.
This item is consistently underestimated, and it is the only one with a cost of zero.
Automating a pointless task is the worst possible outcome: it makes the task permanent, since no one has any reason to question it anymore.
2. Automate
Only then, starting with data preparation, which is the most time-consuming and routine task.
The order of priority is evident from the measurement itself: frequency multiplied by duration, starting with what is most stable from one cycle to the next.
The "justification" feature deserves special mention because it automates the process in an unexpected way: not by generating explanations more quickly, but by enabling the system to provide them on its own, so that the buyer can find the answer without having to go through the team.
Booper reports a 70 to 90 percent reduction in pricing preparation time for teams using the platform. This figure refers to just one of the five tasks, and should be interpreted as such.
Illustrative example: If preparation accounts for 40% of the week, reducing it by 80% frees up about one-third of the total time. Coordination, formatting, and justification remain unchanged as long as the decision-making processes do not change.
How automation of order fulfillment is changing things at a group we're working with.
One price per store group, revised every six weeks.
The group used to manage several retail chains using Excel and manual processes. Now, prices are linked, simulated in batches, and applied by store group. Each pricing cycle starts from its own baseline.
- Issue
- Manage multiple franchise locations, each with its own pricing.
- What Has Changed
- Reference linking, batch simulations, suggested prices by store cluster.
by price cycle, simulated in batches across all retail chains.
Pricing Management · Multi-brand franchise group. Case study written by Booper based on an actual client project; the client has been anonymized.
Our position: A proposed tool that promises to free up the team without affecting committees or approval processes only delivers on part of its promise. The rest depends on the organization.
3. Delegate
Finally, because delegating a task doesn't make it disappear from the organization—it simply shifts it elsewhere. This makes sense when the task requires less expertise than it currently requires, not when the goal is simply to free up time on someone's schedule.
What a team does with the time it saves
This is the part that almost no one prepares for, and it’s what determines whether the whole effort was worth it. Unplanned free time fills itself up on its own, and it fills up with whatever screams the loudest—that is, the day’s urgent tasks.
Three Profitable Pricing Strategies
- Simulate before deciding. Testing three scenarios rather than just going with the first one is exactly what a team that’s behind schedule never has time to do—and yet that’s where the difference in margin comes into play.
- Measure after making a decision. Review the decisions from the previous quarter to verify their actual impact. Without this feedback loop, a team will consistently repeat its mistakes.
- Challenge the rules. Reexamine legacy constraints rather than working around them—which ties into the system review described in the “rule debt” of a pricing engine.
The recommended wording
Saving time is not an end in itself, and that is also why it should not be confused with the return on investment of a pricing project, as we explain in detail in “Time Savings vs. Margin Gains.”
A team that is freed from preparation does not yield any results in and of itself. It yields results if, and only if, someone has decided in advance what the team would do with that time. That decision is made before the project begins, not after.
See also in this feature
- The Booper Solution: Pricing Training
- Pricing Rollout: Successfully Managing Change in the Workplace
- Why Pricing Decisions Should Never Be Left to a Single Person
- Pricing Alerts: The Right Thresholds, the Right Workflows—Without Overwhelming Your Teams
- Implementing and Maintaining a Pricing Policy Over Time: Governance, Exceptions
FAQ
By measuring actual time spent over a typical few weeks, rather than relying on self-reported estimates: fragmented time (follow-ups, file reconciliation, data formatting) is almost always underestimated.
Just a few key positions are enough for the entire team: the workload of a manager is completely different from that of an administrator, and it is this difference that indicates where action is needed.
Five key tasks stand out. Data preparation: extracting, reconciling, verifying, and establishing a comparable scope.
Coordination: following up, waiting for approval, mediating between departments. Formatting committee materials, which becomes more time-consuming as the number of committees increases.
Justification, which involves explaining a price to a buyer or store manager, and whose cost depends on the system's ability to reconstruct the decision-making process.
And the manual correction of recommendations—each repeated correction indicating knowledge that the tool lacks.
Because it owns almost none of its own data.
Sales are managed through management control, buyers' purchasing terms, supply chain inventory, a service provider's competitor reports, and the product catalog of yet another system.
Setting a price therefore requires gathering information before it can be analyzed, and gathering that information often costs more than the analysis itself. This is a structural characteristic of the role, not a failure in the organization of any particular team.
No, and the order of operations matters more than the measurements themselves. The first question for every recurring task is “What happens if we stop?”, not “How can we speed it up?”.
Reports that no one opens and committee meetings with no items on the agenda are consistently underestimated, and eliminating them is the only measure that costs nothing.
Automating a pointless task is the worst possible outcome: it makes the task permanent, since no one has any reason to question it anymore. The proper order, therefore, is to eliminate, then automate, then delegate.
You have to decide this before the project, not after: free time that isn't planned for fills up on its own with the day's urgent tasks. Three approaches really pay off in terms of pricing.
Simulate before deciding—by testing several scenarios rather than implementing the first one—which is something a team that’s struggling never does. Measure after deciding—by reviewing the decisions from the previous quarter to verify their actual impact.
And challenging outdated rules rather than working with them, which requires a periodic review of the fleet.
Above all, it reduces data preparation: Booper claims a 70 to 90 percent reduction in pricing preparation time.
Coordination, formatting, and justification will only improve if decision-making processes also change, or if the tool can trace the path of a recommendation.
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.
