Thirty days is enough to understand the current system, test one meaningful improvement, and establish a useful review rhythm. It is not enough to redesign everything, which is precisely why the boundary encourages focus. Pricing communicates value, shapes demand, funds service quality, and influences which customers a business is equipped to serve.
Week one: understand reality
Pricing decisions drift when they are based only on cost markups or competitor lists rather than willingness to pay and delivered value. Begin by observing the work as it happens and separating symptoms from the conditions that repeatedly create them.
Identify the customer outcome that best explains why one segment values the offer more than another. Speak with the people who perform the work, receive its output, and handle its exceptions so the current picture reflects reality rather than policy alone.
Weeks two and three: test a better way
Capture the emerging approach in a pricing architecture that links segments, value metrics, packages, guardrails, and approval rights. The artifact should make the next decision easier, not become documentation maintained for its own sake.
Keep the first change small enough to reverse and specific enough to evaluate. Give one person clear ownership, make constraints explicit, and agree on when the team will inspect the result.
Week four: decide what to sustain
Use realized price, conversion, discount depth, retention, and contribution margin to understand progress from more than one angle. A measure belongs in the review only when a meaningful change would prompt a question, decision, or action.
End each review by recording what the team learned, what it will change, and what remains uncertain. Durable improvement comes from repeating that loop with discipline rather than launching a larger program.
