Billing vendors build what they sell — but only a third can prove they bill themselves on it
Companies whose product is a usage-billing platform tend to bill themselves on their own product — dogfooding the meter they sell. Of 13 billing/metering vendors in the corpus, 11 disclose a billing system of record and 10 of those run their own product as it (Lago, Metronome, Stripe Billing, Sequence, Flexprice, Maxio, m3ter, Togai, OpenMeter, Schematic). Orb is the lone exception: its only named monetization tool is Salesforce.
What's happening — and why
What's happening: the billing-infrastructure vendors in the corpus overwhelmingly run their own product to bill their own customers. Lago bills on Lago, Metronome on Metronome, Stripe on Stripe Billing, Sequence on Sequence — and as more metering platforms entered the corpus the pattern held: Flexprice built its own Go metering engine rather than wiring up Stripe Billing, Maxio runs its native Chargify-lineage billing, m3ter and Togai price their own products on the rating engines they sell, OpenMeter says plainly "we use OpenMeter to bill for OpenMeter," and Schematic is its own entitlements-and-metering system of record. It doubles as a credibility signal and a built-in product test.
Why: a vendor whose pitch is meter and bill accurately gains the most credible reference customer by being one. Dogfooding also surfaces product gaps faster than any test suite. Of the 13 billing/metering vendors carrying a monetization-stack profile, 11 disclose a billing system of record and 10 of those dogfood. The exception is telling: Orb, named as the bought biller in eight other corpus stacks (Baseten, Chroma, fal.ai, Fireworks, Pinecone, Relevance AI, Replit, Vercel), discloses only Salesforce for its own monetization — it powers others' billing without publicly running its own product as system of record. Two more (Alguna, Zenskar) disclose no biller in their block at all, so they are left as honest unknowns rather than counted either way.
How it works
Evidence over time
11 supporting · 4 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Lago | Jun 2026 | Explicit dogfood: "we... logically decided to use Lago to craft and power our own custom billing. With Lago metering, we can track down to each API call." Runs an undisclosed PSP (Stripe/Adyen/GoCardless) for collection; 8 billing-eng reqs on the open-source billing engine. Source: getlago.com/blog/how-lago-uses-lago-tackling-our-own-billing-nightmares. |
| Sequence | Jun 2026 | Two explicit disclosures — a job names its own finance stack "Sequence (Accounts Receivable & Quote to Cash)" and a blog details "how we use Sequence to level up pricing flexibility... without breaking our revenue collection workflow." Pairs with QuickBooks Online and Xero for rev-rec — dogfoods the meter, buys the accounting. |
| Metronome | Jun 2026 | Block names the Metronome usage-based billing platform (own product) as its in-house metering stack (basis in-house, confidence stated); the sourced quote is the product positioning ("the leading usage-based billing platform built for modern software companies") rather than a first-person "we bill ourselves on it" line. |
| Metronome | Jul 2026 | Evidence upgrade — the weak 2026-06-16 positioning quote is now backed by a rate card. Metronome published Starter usage rates for the first time in company history: $100,000 in billing volume and 10M events included per month, then 0.8% of billing volume and $0.04 per 1,000 events. Those are the exact two dimensions Metronome meters for its customers, so it now demonstrably prices itself on its own meter. Reverses a years-long no-published-rates posture and lands after Stripe completed the acquisition in January 2026; Custom remains sales-quoted. Source: changes/metronome-2026-07-14-price-change.md. |
| OpenMeter | Jun 2026 | The flattest dogfood disclosure in the corpus: "and yes, we use OpenMeter to bill for OpenMeter." Runs its own Kafka + ClickHouse real-time metering engine ("OpenMeter manages scale by ingesting events into Kafka topics first … we rely on Kafka Connect") with Stripe appearing only as a downstream payments integration. Two stack entries, both basis in-house / confidence stated. Source: monetization_signals in-house + data-platform stack entries. |
| m3ter | Jul 2026 | Dogfoods in the pricing-design sense rather than the plumbing sense: m3ter built the high-scale metering and rating engine it sells (in-house / stated) and prices its own gated quote on the two dimensions that engine meters — a core platform fee bundling allowances for "usage data ingested and bill calculations performed," plus incremental add-on allowances. Verified unchanged word-for-word at the 2026-07-21 capture that relabelled the site "m3ter from Salesforce." Source: monetization_signals in-house stack entry + changes/m3ter-2026-07-21-funding.md. |
| Flexprice | Jun 2026 | Claim A only (builds, self-billing undisclosed): "Flexprice IS the meter it sells — an open-source, real-time usage-metering and billing engine it built in Go rather than wiring up Stripe Billing, with ClickHouse as the event store under the hood." The sourced quote is a customer testimonial ("after moving to Flexprice, they got … real-time metering for any usage type, credit wallets for prepaid plans"), not a first-person self-billing statement, and no public ATS is reachable to corroborate. Counts for the build law, not the dogfood law. Source: monetization_signals metering stack entry. |
| Maxio | May 2026 | Claim A only: three separate in-house stack entries — the native billing platform of Chargify lineage ("we have built a world-class billing platform that integrates with a variety of leading payment gateways"), a native surcharging engine ("built natively into the billing platform … a single, consistent experience across every flow"), and Maxio Metering with Advanced Formulas (2026-06-17). It never names the PSP it processes its own revenue on — only "a variety of leading payment gateways" — so the self-billing half is undisclosed. Source: monetization_signals in-house + metering stack entries. |
| Schematic | Jun 2026 | Claim A only, and the sharpest illustration of why the two claims differ: Schematic's own entitlements-and-usage-metering engine is the in-house build ("Schematic is the system of record for plans, software entitlements, limits, credits, trials, add-ons, overrides, and exceptions") while the product itself is "built on Stripe." Every Stripe reference in its docs describes the product reading a CUSTOMER's Stripe, not Schematic's own checkout — how it collects its own Free/Growth revenue is not disclosed. Source: monetization_signals in-house + payments stack entries. |
| Togai | Apr 2024 | Claim A only, with the strongest possible external validation of the build: "Zuora announced a definitive agreement to acquire Togai to extend its monetization suite with Togai's sophisticated metering and rating." Its Kotlin services run a NATS event queue feeding metering consumers with Postgres, Timescale and Redis underneath. No disclosure of what Togai billed itself on. Source: monetization_signals in-house stack entry. |
| Stripe Billing | Jun 2026 | Block names Stripe Billing (own product) as its in-house billing system of record (basis in-house, confidence stated) and is the corpus's heaviest billing-engineering hirer (22 reqs); the sourced quote describes the product's reach rather than explicitly stating self-collection. |
Counterexamples
- Orb · Jun 2026 — Exception: a usage-billing vendor whose only named monetization tool is Salesforce — and which is itself named as the bought biller in 8 other corpus stacks (baseten, chroma, fal-ai, fireworks-ai, pinecone, relevance-ai, replit-ai, vercel) yet does not disclose dogfooding its own product as system of record.
- Alguna · Jun 2026 — Honest unknown, not a dogfood claim: Alguna's product is quote-to-cash / usage-billing, but its monetization_signals block carries no stack entry naming any biller — it discloses neither running Alguna on itself nor buying an alternative, so it is left uncounted rather than asserted either way. Its direction note does say "AR and dunning stay built in-house," which is dogfood-shaped, but no sourced stack entry backs it.
- Orb · Jun 2026 — The counterexample survived an acquisition without resolving. Adyen announced a definitive agreement on 2026-06-11 to acquire Orb for $335M all-cash (reverse triangular merger, closed early July 2026, Orb powering billing for Vercel, Perplexity, Pinecone, Replit and Supabase). Under Adyen's stated "incubator" model Orb's operations, brand, multi-PSP support and its three gated Core/Advanced/Enterprise tiers are unchanged — and its monetization_signals block still names Salesforce as its only monetization tool, with open roles clustered in customer-success/solutions and enterprise sales rather than a billing-platform team. A vendor that meters eight other corpus companies, now owned by a payments processor, still does not disclose running its own product as system of record. Source: changes/2026-06-11-orb-adyen-acquisition.md.
- Zenskar · Jun 2026 — New counterexample, and a harder one than Orb: Zenskar is a 2022-vintage usage-billing vendor whose own monetization block discloses no stack at all and whose direction reads "Zenskar runs its own monetization the legacy way it sells against: no self-serve, every deal quoted." The tell is a founding enterprise-AE req staffing a North-America field-sales motion post-Series-A rather than a self-serve funnel. A company selling automated usage billing that quotes every one of its own deals is not dogfooding the model, whatever engine sits underneath.
Trivia
-
Of the 13 corpus billing vendors carrying a monetization stack, 10 disclose building the engine they sell but only 4 document actually billing themselves on it (2 more assert it without a first-person quote) — a direct credibility play for a category whose whole pitch is to meter and bill accurately, and one that most of the category does not publicly make.
-
The loudest exception sells the meter but runs Salesforce: Orb is named as the bought biller in 8 other corpus companies' stacks (baseten, chroma, fal-ai, fireworks-ai, pinecone, relevance-ai, replit-ai, vercel) yet discloses only Salesforce for its own monetization — it powers others' billing without publicly dogfooding, a position unchanged by Adyen's $335M acquisition (announced 2026-06-11, closed early July 2026).
-
Even the dogfooders still buy the rails around the core: Lago runs an undisclosed payment service provider (Stripe / Adyen / GoCardless) for its own collection, and Sequence pairs its own product with QuickBooks Online and Xero for rev-rec — dogfooding the meter, not the accounting.
-
Zero of the 13 billing-platform vendors in the corpus names a competing billing vendor as its own system of record — the only category in the whole monetization dataset with a 0% buy rate for its own core function. What varies is not build-vs-buy but whether the vendor will say out loud that its own money runs through the thing: only 4 of 13 do.
-
OpenMeter wrote the flattest dogfood sentence in the corpus — "and yes, we use OpenMeter to bill for OpenMeter" (2026-06-23) — while Metronome needed a repricing to prove the same point: on 2026-07-14 it published Starter rates for the first time in company history and priced itself on the exact two dimensions it meters for customers, 0.8% of billing volume plus $0.04 per 1,000 events after $100K and 10M included.
-
The dogfood cohort is consolidating faster than it is growing: 4 of the 13 vendors are now owned by a larger platform — Togai by Zuora (2024-04-30), Metronome by Stripe (January 2026), Orb by Adyen for $335M all-cash (announced 2026-06-11), and m3ter by Salesforce (site relabelled "m3ter from Salesforce" by the 2026-07-21 capture). In all three 2026 deals the acquired vendor's own pricing page survived the acquisition word-for-word.
For buyers
If you are evaluating a billing vendor, ask whether it runs its own product — the answer is a fast credibility check. Ten of the eleven corpus billing vendors that disclose a system of record do, which means their own invoices are a live test of the product you are buying. But read it with nuance: even the dogfooders buy the rails around the core (Lago runs an undisclosed payment processor for collection; Sequence runs QuickBooks/Xero for rev-rec; OpenMeter and Schematic leave payments to Stripe), so dogfooding the meter does not mean the whole finance stack is self-served.
For vendors
For a billing-platform vendor, dogfooding is close to table stakes — it is both the most credible reference and the fastest bug-finder, and the norm has only sharpened as the corpus grew: 10 of the 11 vendors that disclose a billing system of record run their own product as it. The Orb counterexample shows it is not strictly required (Orb wins plenty of deals as others' biller without publicly running its own product as system of record), but it is the norm the segment converges on. The practical limit: dogfood the metering and invoicing, but expect to still buy a payment processor and an accounting/rev-rec tool around it.
Outlook — what to watch
Logged as sharpening through June 2026 as the cohort grew from 5 to 13 billing/metering vendors and the dogfood norm held (10 of the 11 that disclose a system of record). The Orb exception is worth tracking — if Orb discloses running its own product as system of record, the pattern becomes near-universal. The two honest unknowns (Alguna, Zenskar) would tilt the ratio further toward dogfood if they later disclose running their own engine. The bound on the other side is that dogfooding stops at the meter; the accounting and payment rails are still bought even by the dogfooders.
Bottom line
Ten of the eleven corpus billing vendors that disclose a system of record bill themselves on their own product — among the highest self-consumption rates of any segment, and a direct credibility play. Orb is the lone exception, named as eight other companies' biller while running only Salesforce itself; Alguna and Zenskar disclose no biller and stay uncounted.
FAQ
Do billing software vendors use their own product?
Mostly yes. Of the 13 billing/metering vendors in the corpus, 11 disclose a billing system of record and 10 of those dogfood: Lago, Metronome, Stripe Billing, Sequence, Flexprice, Maxio, m3ter, Togai, OpenMeter, and Schematic all run their own product as it. It serves as both a credibility signal and a built-in product test.
Which billing vendor doesn't use its own product?
Orb is the corpus exception — its only named monetization tool is Salesforce. It appears as the bought biller in 8 other corpus company stacks (Baseten, Chroma, fal.ai, Fireworks, Pinecone, Relevance AI, Replit, Vercel) but does not publicly disclose running its own product as system of record. Alguna and Zenskar disclose no biller at all, so they are left uncounted rather than treated as exceptions.
Do dogfooding billing vendors build their entire finance stack?
No — they dogfood the meter and invoicing but still buy the rails around it. Lago runs an undisclosed payment processor (Stripe, Adyen, or GoCardless) for collection, Sequence pairs its own product with QuickBooks Online and Xero for revenue recognition, and OpenMeter and Schematic leave downstream payments to Stripe.
Why does dogfooding matter for a billing vendor?
A vendor whose value proposition is meter and bill accurately becomes its own most credible reference customer by running on its own product, and dogfooding surfaces product gaps faster than testing. Stripe — the heaviest billing-engineering hirer in the corpus at 22 reqs — runs its own Stripe Billing, and OpenMeter says plainly "we use OpenMeter to bill for OpenMeter."