Getting Your Pricing Structure Actually Right
A Price Foundation Diet is what I call the habit of stripping your pricing down to its raw components and rebuilding it from scratch instead of tweaking percentages on a broken model. Most people skip this. They adjust margins, add a discount tier, move a feature from premium to pro, and call it optimization. It doesn't work because the underlying structure is usually misaligned with how the market actually buys. Here is what it involves in practice: I tried running this on a SaaS client last year with a flat per-seat model that had eight feature tiers. We spent three weeks redoing the cost floor because their "premium" tier was subsidizing support costs for the "starter" tier without anyone realizing it. The workaround was pulling actual ticket duration data by tier from Zendesk and back-calculating the true delivery cost. That changed everything about how we structured the pricing.
When you audit a Price Foundation Diet properly, you are usually surprised by how many businesses are running negative margin at the top tier because of untracked overhead. That is not a marketing problem. It is a structuring problem.
How to Run a Price Foundation Diet Audit
Start by exporting your last 90 days of billing data. Filter for active paying customers only. Exclude trials and cancelled accounts. Put each customer into their tier and label them by acquisition channel. Next, pull support metrics by tier. Average ticket volume, average resolution time, and escalation rate. Multiply resolution time by your loaded support labor cost. That gives you real cost per customer per month, not the theoretical number from your accounting software. Then compare gross margin per tier after you include the support cost. You will likely see that your best margin is not where you think it is. I ran this exercise for a mid-market platform once and discovered the $29 tier was actually more profitable than the $79 tier after support costs were accounted for. The fix was moving two high-support features into the mid-tier and renaming it to match the actual use case rather than the feature count.
Get the Full Details
This process usually takes about four to six hours for a small product with under 5,000 customers. Larger setups can stretch it to a full workweek depending on data availability.
Common Pitfalls I Keep Seeing
The biggest mistake is assuming your competitors' pricing is the right reference point. It isn't. Competitor pricing is lagging indicator data. It tells you what other people who already made these decisions are charging. It does not tell you what your cost structure or value perception should be. Another one is tier stacking without a cap. If your pricing page lists every feature in every tier, nobody understands what they are buying. I had a client who removed half the feature comparisons from their pricing page and saw a 14 percent increase in conversion within six weeks. The reduction in decision fatigue mattered more than the visible feature density. A third issue is anchoring to your own historical pricing. If you raised prices once in 2022 and haven't revisited the model since, you are likely leaving money on the table or pricing out segments you should be capturing. I recommend a full foundation diet at least once every 18 months for products in growth mode.
When a Price Foundation Diet Won't Help
This method breaks down in markets where pricing is driven almost entirely by commodity factors — raw materials, wholesale margins, or regulated fee structures. If your product is a physical good with thin margins and no differentiation, rebasing your pricing architecture will not move the needle. In those cases, you are better off focusing on supply chain efficiency or channel negotiation. It also fails when your customer base is too small to extract meaningful support cost signals. If you have fewer than 200 paying customers, the variance in ticket volume and resolution time will be too noisy to rely on. In that scenario, manual outreach to a representative sample of 20 to 30 customers gives you cleaner data than analytics alone.
What to Do After the Audit
Once you finish the foundation diet, draft a pricing memo before you change anything. List the current tier structure, the calculated margin per tier, the identified misalignments, and the proposed changes with expected impact. Get sign-off from finance and product before updating the pricing page. Skipping this step is how I have seen companies accidentally cut revenue by implementing a "better" model on paper that broke in production. After the memo is approved, roll out changes in a single release window. Do not A/B test pricing tiers against each other in a way that confuses existing customers. If you must test, use a silent cohort of new signups only. Track net revenue retention for 60 days after launch. If NRR drops below 98 percent, you have a segment pricing problem, not a conversion problem. Revisit the cost floor for the affected tier and adjust accordingly.
