A cost audit of every tool your store pays for — what each one costs per order, where two subscriptions do one job, and what you already own that does the same thing.
Screenshot goes here: the verdict list — keep, cut, renegotiate, replace
public/assets/ankka-home/ → set productShot
Every tool was a reasonable decision on the day it was bought. The bill is what happens when nobody re-reads those decisions.
Six ways an ecommerce stack gets expensive without anyone deciding it should:
Stacks grow by addition. The analytics app, the reporting app and the dashboard app all answer the same question — and all three renew every month.
Apps that bill a cut of orders or GMV get more expensive exactly as you succeed, whether or not they do more work for you.
Plans get chosen at peak and never revisited. The event, session or SKU ceiling you are paying for is often several times what you use.
Something got bought to answer one question in one meeting. The question was answered eighteen months ago. The seat is still billing.
Agencies roll off, staff move on, and per-seat plans do not notice. Nobody owns the licence list, so nobody cancels.
The switching decision has a date attached and the date passes silently. Knowing the renewal calendar is half the leverage in any negotiation.
Invoices on one side, your own data on the other. Nothing here rests on a vendor's marketing page:
One list of what you pay for, what it costs monthly and annually, which card it bills to, and when each contract renews.
Subscriptions are quoted per month; stores earn per order. Both numbers go in the report, so cost sits next to the volume it serves.
Login and usage evidence where the tool exposes it, and the reports it feeds. A tool nobody has opened since spring is a finding.
Capabilities are mapped across the stack, so duplicate coverage shows up as a picture rather than a hunch.
GA4, BigQuery, Tag Manager, Search Console and your store admin cover more than most stacks assume. Where they do, the report says so — and what it would take to move.
Migration effort, data you would lose, contract lock-in and the risk of the change — because a saving that costs three developer weeks is not a saving.
The shape of the report — an illustration of the four verdicts, not a customer's bill:
2 of 3
A paid analytics suite, a dashboard product and a reporting app all report the same funnel. One is enough; the other two renew monthly.
Illustration · overlap map, not a customer bill
4× headroom
The plan ceiling was chosen during a launch. Actual volume has sat well under it for a year, and the next tier down covers it with room.
Illustration · plan ceiling vs. measured volume
Already paid for
The subscription exists to produce one report. The same numbers are in your GA4 export and BigQuery, which you are already paying for.
Illustration · capability mapped to owned stack
Worth it
Not everything is waste. Tools that carry real load are named as keepers, with the reason — so the list survives the next budget round.
Illustration · usage evidence attached
A list of subscriptions, or the invoices, or read-only access to the billing inbox — whatever is least work for you. Renewal dates matter as much as prices.
Each tool is matched against what your data shows it does: what it feeds, who opens it, and which questions it is the only source for.
Keep, cut, renegotiate or replace — one line each, with the monthly number, the reasoning, and what switching would cost.
Renewal dates go on a schedule. Agents flag the next one before it lands, so the decision is made by you and not by the calendar.
First 10 customers
$49/ month
Locked in for life.
Read-only connections. Your data stays in your own accounts.