Pricing an audit needs a model that separates the product's scope from assumptions about buyer behavior. The earlier notes compared $129, $149, and $497 examples from the 2026 catalog. Those examples are useful for sensitivity calculations, with the period and assumptions attached.
The offer a buyer can purchase comes from the current product page. A historical price test does not establish a universal threshold for an unfamiliar audience.
Compare equivalent scopes and traffic
Write down the deliverable, fulfillment cost, refund terms, acquisition channel, and purchase rate for each scenario. A packaged tool and a reviewed custom diagnostic have different costs and buyer expectations. Comparing their headline prices alone leaves those differences out of the decision.
The old $49, $129, and $249 alternatives asked whether the buyer understood the diagnostic and could decide from the page. A higher price might need more evidence of scope, and a lower one might still fail if the promise is unclear. Those are testable propositions for the audience and offer.
Keep assumptions separate from results
Use modeled purchase and refund rates while planning, then replace them with measured values as data arrives. Record the traffic source and observation window. A small number of sales can make the apparent rate move sharply without a change in buyer behavior.
Track net receipts and variable delivery cost as well as revenue. A higher price can support a different scope, but it also changes what must be explained and fulfilled. Keep referrals and later upgrades as separate measured outcomes until they are established for the cohort.
Decide what to test
If the page is losing buyers, inspect the traffic quality, scope, sample output, payment flow, and price together. Write a hypothesis before changing one of them. A controlled comparison on comparable traffic provides better evidence than treating a three figure price as a psychological rule.
Retain the original scope description with the result. When the product or delivery process changes, mark the old comparison as historical so its rate is not presented as current evidence for a different offer.
A dated pricing model and a measurable payback test
The original entry price decision compared $49, $129, and $249 in early 2026. Those were alternative prices for one offer. The concerns were whether the page made the diagnostic's scope clear, whether a buyer needed a conversation, and whether delivery left enough margin. Treat those concerns as hypotheses to test on comparable traffic. A price alone does not tell you who will buy or refund.
For a six week buyer payback target, divide the price by six and compare it with the weekly benefit the buyer can actually realize. A hypothetical $129 purchase needs $21.50 of weekly benefit over that period before considering implementation cost. At $149, the weekly figure is about $24.83. The diagnostic still has to identify something useful, and the buyer still has to make an effective change. Improved attribution visibility by itself is not additional revenue.
In the seller's model, record the same inputs for each price:
net receipts per visitor = price * purchase rate * (1 - refund rate)
contribution per visitor = net receipts per visitor - variable cost per visitor
For illustration, 100 qualified visits at $149 and a 3 percent purchase rate produce $447 before refunds and delivery cost. At $497 and a 1 percent purchase rate, the figure is $497. With assumed refunds of 2 percent and 10 percent respectively, those become $438.06 and $447.30. These assumptions show why headline revenue alone cannot choose the price. They are not measured rates from this site.
Run sensitivity checks on purchase rate, refund rate, acquisition cost, and fulfillment cost. Compare the same traffic source and a defined period. Track upgrades separately, after enough time has passed for the next purchase to occur, so projected lifetime value does not rescue a weak first sale on paper.
The current tracking catalog is different from the old $129 and $497 examples. As reviewed in October 2026, the CAPI Leak Report is $149, the Tracking Truth Map is $750, and the Attribution Teardown is $1,500. Each has a different scope. Keep historical calculations dated and use the current product page for what a buyer can purchase.
If abandonment increases, inspect the promise, sample output, payment errors, and traffic mix before attributing the change to price. A $97 alternative or a higher price can be tested, but the earlier notes did not supply a controlled result establishing either as the correct next move.