EgressMap — per-tenant API cost burn map for accounting app builders

1. One-liner

Shows an accounting-integration builder which connected client is eating their Xero and QuickBooks read allowance — before the overage lands.

2. Trend signal — why now?

For fifteen years, reading data out of Xero and QuickBooks was free. In nine months, both platforms turned that read path into a metered utility. That is the whole idea.

Xero. Announced 4 December 2025, effective 2 March 2026, mandatory for every app by 1 July 2026. Pricing is tiered on egress — gigabytes of data flowing out of GET responses, measured monthly per app. Starter is free but capped at 5 connections (a test rig, not a business). Core is A$35/mo for 50 connections and 10 GB. Plus is A$245/mo for 1,000 connections and 50 GB. Advanced is A$1,445/mo. Overage is A$2.40/GB. Writing into Xero stays free and unlimited; only reads are billed.

Intuit. Same move, eight months earlier. The Intuit App Partner Program launched 28 July 2025 with a 100% discount on variable API fees through 31 October 2025, and full variable fees from 1 November 2025. The free Builder tier allows 500,000 read operations per month and then blocks further requests. Paid tiers run $300/mo to $4,500/mo with overage on top. Writes free, reads metered. Identical architecture.

The ecosystem reaction was not polite. Accountants Daily ran the headline “‘All you can eat Xero data buffet’ comes to abrupt end.” Alex Lacota, co-founder of the balance-sheet reconciliation app RecHound, calculated his annual bill at A$17,340 — up from approximately nothing. Dext’s chief product and technology officer Stephen Edginton wrote on LinkedIn: “It’s a shame there was zero discussion ahead of such abrupt changes. These costs will ultimately be paid by end customers as another tax – which many businesses will struggle with.” Codat told its own customers to go “review your datasets’ sync frequency in the Codat portal” — an admission that the sync-based model it sells is now structurally expensive.

Here is the mechanic that makes this a product rather than a news story. Egress is billed at the app level, but it is generated at the tenant level. A builder with 400 connected client organisations gets one aggregate number. The bill is driven by a handful of outlier tenants — the accounting firm with 90,000 invoices, the client whose historical sync never got throttled, the org that reconnected and triggered a full backfill. The builder cannot see which. Xero’s developer portal offers a usage tab showing consumption against tier allowance; it does not tell you which connected organisation or which endpoint produced it. So the only lever a panicking builder can pull is the blunt one: cut sync frequency globally. Truto’s guidance spells out the trade — going from 15-minute to 4-hour syncs cuts egress 94% and makes every customer’s data up to four hours stale.

That is the gap. Everyone sells the builder advice on how to reduce egress. Nobody sells them the answer to whose egress it is.

Provenance:

• Signal 1 (demand): Xero developer pricing shift — tiered egress billing effective 2 March 2026, mandatory 1 July 2026, A$2.40/GB overage; developer quoted at A$17,340/yr, ecosystem calls it a “rug pull” — https://truto.one/blog/xero-api-pricing-changes-2026-costs-tiers-and-how-to-minimize-egress/ and https://www.accountantsdaily.com.au/technology/21986-all-you-can-eat-xero-data-buffet-comes-to-abrupt-end — 2026-09-01
• Signal 2 (feasibility): Intuit App Partner Program meters QuickBooks reads from 1 November 2025 — free tier hard-blocks at 500K read ops/mo, paid tiers $300–$4,500/mo — confirming a two-platform, same-shape metering standard a single tool can serve — https://truto.one/blog/how-much-does-the-quickbooks-api-cost-2026-pricing-rate-limits/ — 2026-09-01
• Signal 3 (economic): Cost-attribution tooling is a funded, active category (CloudZero, Vantage, Finout, Helicone, Langfuse, OpenMeter) but aimed exclusively at cloud and LLM spend — per-tenant attribution is the acknowledged hard problem, and partner-platform API egress is outside all of their coverage — https://www.finout.io/blog/best-ai-cost-observability-tools-in-2026 and https://www.cloudzero.com/blog/api-metrics/ — 2026-09-01 Category: Platform shift

3. The opportunity

Three camps are circling this and all three miss the same thing.

The unified-API middleware camp — Codat, Apideck, Truto, Merge. They resell accounting connectivity, and the pricing change is an existential problem for them, not a product opportunity. Their sync-based architecture is precisely what got expensive. Codat’s public guidance to its own customers was to reduce sync frequency. They will optimise their own egress because their margin depends on it, but they have a structural conflict: their whole pitch is “we handle the integration, don’t think about it.” Selling a customer a microscope that shows exactly how much data their middleware is dragging out per tenant is not a product they want to ship.

The FinOps / cost-observability camp — CloudZero, Vantage, Finout, and on the LLM side Helicone, Langfuse, OpenMeter, Portkey. These are real, funded, competent companies. They attribute cloud infrastructure and model inference spend per tenant. Partner-platform API egress is not in their data model — it isn’t in a cloud bill, it isn’t an LLM token count, it’s bytes returned by a third-party SaaS API that only the builder’s own outbound HTTP client can observe. Adding it means instrumenting someone else’s integration layer, which is not what these tools do.

The platforms themselves — Xero and Intuit. Both give you a usage number against your allowance. Neither gives you per-tenant attribution, and it is not in their interest to. A vendor that hands you a precise map of which reads are wasteful is helping you buy a smaller tier. The platform is the counterparty here: it invoices you for the metric and controls the only official reporting of it. This is the buy-side/sell-side gap in its purest form.

The wedge is small, sharp, and unglamorous: sit in the builder’s outbound path to Xero and QuickBooks, measure response bytes per tenant per endpoint, and answer four questions the builder currently cannot answer at all. Which client is costing me the most? Which endpoint is wasteful? Am I going to blow my tier this month? What happens to my bill if I change this client’s sync interval?

Beat the incumbents not on cost dashboards — a commodity — but on the one number nobody else can compute: cost per connected customer. Because once a builder knows that, the follow-on decision is a business decision, not an engineering one. Some of those tenants are unprofitable at the builder’s own price point.

4. Target market

• Primary customer: Founder-engineers and CTOs at small B2B SaaS companies whose product reads accounting data — 2 to 25 people, roughly $150K–$3M ARR, with 50 to 2,000 connected Xero/QBO organisations. Concretely: reconciliation tools, cash-flow forecasting apps, spend-management tools, inventory and job-costing apps, reporting and benchmarking tools, lending and underwriting products that pull ledgers, and practice-management add-ons sold to accounting firms. Anglosphere-weighted — Australia, New Zealand, UK, US, Canada — because that is where the Xero and QBO app ecosystems are dense.
• Why they buy: “My Xero bill went from zero to five figures and I have no idea which customers are causing it.” The pain is a specific monthly moment: the invoice arrives, it’s bigger than last month, and the only diagnostic available is a single aggregate gigabyte number. Their current workaround is to globally slow syncs and hope — which degrades the product for every customer to fix a problem caused by a few. The second workaround is a weekend of hand-rolled logging that nobody maintains.
• Rough TAM reasoning: Xero’s app marketplace lists well over a thousand connected apps; Intuit’s is larger. Not all are viable customers — the big ones will build this internally and the tiny ones sit in free tiers. The serviceable slice is the band that is past the free tier but below the price point where a dedicated platform team exists: realistically a few thousand companies across both ecosystems, growing as more apps cross the free-tier threshold. A few hundred of them at $79–$249/mo is a real bootstrapped business. This is a micro-SaaS niche, correctly sized — too small for VC, fine for one or two people.
• Why now for them: The Xero mandatory migration deadline was 1 July 2026. Every app is now on a paid tier or capped at 5 connections. The first genuinely painful invoices — the ones covering a full month of unoptimised production traffic plus overage — are landing right now. Intuit’s builders have had this since November 2025 and have had longer to feel it. The urgency is real and it is dated.

5. Product sketch (MVP)

• A drop-in wrapper/proxy for the builder’s existing Xero and QuickBooks HTTP client that records response bytes, endpoint, and tenant ID on every call — no rewrite of their integration.
• Cost per connected organisation, ranked. The headline screen: your 400 tenants sorted by what they cost you this month, in dollars, not gigabytes.
• Endpoint burn breakdown — which API calls generate the most bytes, and which of those are re-fetching data that hasn’t changed.
• Tier forecast with a projected overage figure — “at current run rate you finish the month 14 GB over Plus, which is A$34 in overage; you cross into Advanced territory in about six weeks.”
• Waste detector — flags full-collection GETs that should be delta syncs, polling that a webhook could replace, backfills that re-ran, and pagination pulling pages nobody read.
• What-if simulator — model the egress and staleness impact of changing sync frequency for one tenant, one cohort, or globally, before shipping the change.
• Margin view — pair each tenant’s API cost against what that customer pays the builder, surfacing connected orgs that are gross-margin negative.
• Alerts on tenant-level anomalies: a client that 10בd its egress overnight, usually a reconnect triggering an unthrottled backfill.

6. AI angle — what’s load-bearing

Honest answer: the measurement layer is deterministic plumbing, and I would be lying if I called byte-counting an AI product. Remove the AI and a useful tool still exists. That costs this idea points on defensibility and I’ve scored it accordingly.

Where AI does real work is the remediation half, which is the half builders actually want. Given a captured trace of a builder’s live API traffic — endpoints, parameters, response shapes, frequencies, per-tenant patterns — a model reads that traffic and writes the specific fix: this endpoint should use If-Modified-Since, this poll should be a webhook subscription on Contacts and Invoices, this backfill re-runs on every reconnect because of a missing cursor, this pagination fetches 40 pages when the caller reads 2. That is a code-shaped recommendation derived from unstructured, per-customer traffic, and it is genuinely hard to write as static rules across two platforms with different endpoint semantics.

Without it, the product hands a builder a number and a shrug. With it, the product hands them a diff. That’s the difference between a dashboard people cancel in month three and a tool that pays for itself the week they install it. But I’m scoring this as a well-executed measurement product with AI assistance, not an AI-native play.

7. Localization angle (if any)

N/A — this is a global play, sold in English to a developer audience. The one geographic nuance worth naming is that Xero’s billing is denominated in AUD and its ecosystem is heaviest in Australia, New Zealand and the UK, while Intuit’s is US and Canada. Any pricing page needs to show both currencies and both platforms’ tier structures side by side, because a builder integrated with both is running two different metering regimes at once. That’s a UX detail, not a localization wedge.

8. Business model — path to $1M–$5M ARR

• Pricing: $79/mo (up to 100 connected orgs), $149/mo (up to 500), $249/mo (up to 2,000), custom above. Deliberately priced under the delta it saves — a builder on Xero Plus at A$245/mo who avoids a tier jump to Advanced at A$1,445/mo has saved roughly A$1,200/mo. Charging $149 for that is easy arithmetic, and easy arithmetic is what closes self-serve developer deals.
• ACV: ~$1,800/yr blended.
• Rough math to $1M ARR: 550 customers × ~$150/mo × 12 ≈ $1M. Across two ecosystems with thousands of paying-tier apps, that’s low-single-digit percentage penetration.
• Rough math to $5M ARR: Needs the category to widen beyond accounting. The same architecture — metered reads, per-tenant attribution, aggregate billing — is spreading: Strava moved to paid API tiers from 30 June 2026, X moved to per-request credits, HubSpot went to credits in July 2026. If EgressMap becomes the generic “what does each of my customers cost me in partner API spend” tool covering 8–10 metered platforms, 2,500 customers at a higher blended ACV gets there. That is the real expansion thesis and it is a 24-month question, not a launch question.
• Expansion path: Priced on connected-org count, so it grows automatically as the customer grows. Upsell to a multi-platform tier as builders add integrations. A plausible later tier is auto-remediation — the tool ships the sync-config changes rather than recommending them.

9. Go-to-market wedge — first 100 customers

• The marketplace lists are public and finite. Xero’s app marketplace and Intuit’s app store both publish their connected apps with categories and company websites. Scrape both, filter to companies that read accounting data (reconciliation, forecasting, reporting, inventory, lending) and that look small enough to lack a platform team. That is a target list in the low thousands, assembled in a day. Personalised email leading with a single number: an estimate of their monthly egress based on their app category and visible customer count, and an offer to measure it exactly in an afternoon.
• Go where the anger already is, by name. The 4 December 2025 announcement produced a documented public trail — the Xero developer community forum, LinkedIn threads under Stephen Edginton’s post, comments on the Accountants Daily and AccountingWEB and Register pieces, r/Xero and r/QuickBooks, and the Xero Developer Slack. Every person who publicly complained about this pricing change is a named, qualified lead who has already articulated the pain in their own words. Alex Lacota published his A$17,340 figure. That is not a cold list.
• Publish the benchmark nobody has. The one artefact this market lacks is data on what typical egress looks like per connected org by app type. Run the tool across the first 30 design partners, anonymise, and publish “what 30 Xero apps actually spend on API egress.” That is a link accountancy-tech press and the middleware vendors’ own blogs will pick up, and it doubles as the qualification question in every sales conversation: are you above or below the median?
• Partner with the people whose customers are complaining. Middleware vendors (Truto, Apideck) and integration consultancies are fielding “why did my bill jump” questions they can’t fully answer. A referral arrangement gives them an answer to hand over. They compete with EgressMap on nothing.
• Ship a free egress calculator. Input connected org count, sync frequency, and app type; output an estimated monthly bill and tier. Pure lead magnet, ranks for the exact queries — “Xero API pricing,” “QuickBooks API cost,” “reduce Xero egress” — that panicked builders are typing right now. Guard against the failure mode where the free tool answers the question completely: the calculator estimates, the product measures.

10. Build complexity — justification

Low. The core is an instrumented HTTP client plus a time-series store plus a dashboard — a solo builder ships a credible v1 in 6–8 weeks. There is no novel infrastructure, no ML training, no compliance regime. The genuine work is in breadth rather than depth: mapping Xero and QuickBooks endpoint semantics accurately enough that the waste detector doesn’t produce false positives, and making installation genuinely a few lines so a skeptical engineer tries it in one sitting. The AI remediation layer sits on off-the-shelf model APIs reading captured traffic traces. The riskiest build decision is proxy-versus-SDK-wrapper; wrapper first, because asking a builder to route production traffic through your proxy on day one is a hard sell.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Measuring your own outbound API traffic. Note Xero’s updated terms restrict using Xero-obtained data to train AI/ML models — the product must analyse traffic metadata and the builder’s own config, not ingest customer ledger content into a model. Designed that way from day one.
Ethical — no harm / dark patterns	✅	Helps a small vendor understand a bill they’re already paying. No dark patterns available.
Market exists (evidence above)	✅	Two platforms with dated, enacted metering; a named developer with a published A$17,340 figure; public ecosystem backlash.
1–5 person team can build this	✅	Solo-buildable v1.
Launchable with <$50K / ₹40L	✅	Well under $10K. Hosting, model API credits, a domain.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Real, recurring, monetary, and felt monthly when the invoice lands. Docked because it’s a cost-control pain, not a revenue-loss or compliance-penalty pain — builders can survive by bluntly slowing syncs, which is bad but not fatal. Not quite hair-on-fire.
Demand evidence	15	12/15	Strong: two enacted platform changes with hard dates, a named developer with a published bill, quoted executives, trade-press coverage, middleware vendors publicly telling customers to reduce sync frequency. Short of full marks because nobody is yet demonstrably paying for attribution tooling specifically.
Build feasibility	15	13/15	Off-the-shelf stack, solo v1 in 6–8 weeks. Docked slightly for the endpoint-semantics mapping work across two platforms.
Distribution clarity	15	12/15	Named, scrapeable marketplace lists; a public complaint trail with real names; a credible content wedge. Docked because developer tools convert slowly and self-serve trials churn.
Revenue mechanics	15	11/15	Pricing is anchored to a tier-jump the customer can compute themselves, which is the strongest possible pricing position. Docked because ACV is modest and the whole thing depends on customer count per builder, which varies wildly.
Time to first revenue	10	8/10	Six to eight weeks to v1, and the buyer is an engineer who can approve $149/mo without a procurement cycle. Design partners plausibly pay inside 8 weeks.
Defensibility	10	2/10	The weakest axis by a distance and the reason this isn’t a higher score. A competent competitor rebuilds the measurement layer in a month. Xero or Intuit could ship per-tenant attribution natively and vaporise the core value — as HubSpot did when it shipped native credit alerts and dashboards. The only real moat is accumulated cross-app benchmark data and speed.
Total	100	74/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · content-heavy

This needs someone who can talk to engineers as a peer and who will write the benchmark reports that do the distribution work. A sales-led founder would struggle; developers don’t take demo calls about $149/mo tools.

Key assumptions to validate (3–5)

1. Assumption: Egress is genuinely concentrated — a small minority of tenants drives the majority of a typical app’s bill. How to test: Instrument 5 design-partner apps for two weeks and compute the distribution. If the top 10% of tenants aren’t driving 50%+ of egress, per-tenant attribution is a curiosity rather than a lever and the product loses its point.
2. Assumption: Builders will pay for visibility rather than just globally throttling and moving on. How to test: 30 outreach conversations to marketplace-listed apps; count how many have already cut sync frequency globally and consider the matter closed. If most have, the pain is resolved-if-ugly and willingness-to-pay collapses.
3. Assumption: Xero and Intuit will not ship per-tenant attribution natively within 12 months. How to test: Read both developer changelogs and roadmap communications weekly; ask Xero developer relations directly. HubSpot closed exactly this kind of gap on its own credits product within months.
4. Assumption: Installation is genuinely low-friction enough that a skeptical engineer tries it same-day. How to test: Time five real installs end-to-end. If median install exceeds 30 minutes, the self-serve funnel won’t work at this price point.
5. Assumption: The AI remediation output is accurate enough to trust. How to test: Have three experienced integration engineers grade 50 generated recommendations. Below ~80% acceptance, ship measurement-only and drop the AI claim.

Risk flags

1. Platform dependency — severe. The entire product exists because of two vendors’ pricing decisions, and those vendors control both the metric and the reporting of it. Either could ship native per-tenant attribution and remove the reason to buy. Either could reverse the pricing entirely — Amazon announced SP-API fees on 31 January 2026 and cancelled them outright on 12 May 2026 after developer pushback, collecting nothing. A Xero climbdown under ecosystem pressure would take most of this market with it.
2. Defensibility — near zero at month three. No data moat at launch, no network effect, no regulatory knowledge barrier. The only defence is being first, being obviously best, and accumulating benchmark data faster than anyone else.
3. Market timing — possibly narrow. Builders adapt. Twelve months from now, sync architectures will have been rewritten to be event-driven, egress will be lower across the board, and the acute panic will have passed. The window where this is urgent may be 12–18 months unless the product expands to other metered platforms in time.
4. Small absolute market. A few thousand serviceable companies. Fine for a bootstrapped operator, structurally capped well below $5M ARR on accounting platforms alone. The multi-platform expansion isn’t optional if this is meant to reach the top of the range — it’s load-bearing.

14. Structured verdict

Score:                  74/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical solo founder or pair who has personally shipped a
                        Xero or QuickBooks integration and felt this bill
Time to revenue:        6-10 weeks
Capital to launch:      <$10K (₹8L)
Top 3 assumptions to validate first:
  1. Egress concentration — instrument 5 design partners for 2 weeks, confirm the
     top decile of tenants drives 50%+ of bytes
  2. Willingness to pay vs. blunt throttling — 30 conversations with marketplace-listed
     apps; if most have already globally slowed syncs and consider it solved, stop
  3. Platform roadmap risk — direct question to Xero and Intuit developer relations on
     whether per-tenant attribution is planned; weekly changelog monitoring
Kill criteria:
  - Abandon if Xero or Intuit ships per-tenant egress attribution natively
  - Abandon if either platform reverses its API pricing (as Amazon did with SP-API
    on 12 May 2026)
  - Abandon if fewer than 8 of 30 qualified builders will commit to a paid pilot
  - Abandon if median install time exceeds 30 minutes across 5 real installs

15. Next step — 1-week validation sprint

• Day 1–2: Scrape the Xero app marketplace and Intuit app store. Filter to read-heavy apps in the 50–2,000 connection band. Build a list of ~300 named companies with founder contacts. Separately, harvest every public complaint about the December 2025 Xero announcement — forum posts, LinkedIn comments, Reddit threads, article comments — into a named list of people who have already described this pain unprompted.
• Day 3–4: Build the free egress calculator and ship it. Simultaneously run 30 direct conversations, split between the cold marketplace list and the warm complainers. One question decides everything: “When your bill went up, could you tell which customers caused it — and what did you do about it?” Record verbatim whether they throttled globally, built internal logging, or absorbed it.
• Day 5: Decide. Go if: ≥10 of 30 report they cannot attribute egress per tenant AND have not resolved it satisfactorily, AND ≥8 will commit to a paid pilot at $149/mo, AND no evidence surfaces of native attribution on either platform’s roadmap. No-go if most have already throttled globally and consider the problem closed — that is a resolved pain, and a resolved pain does not sustain a subscription.