Mar 7, 2024 · 26m · top-founders
51 year old dad raises $31.5m to help companies do meter based billing
0:00 / 0:00
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview with Nathan Latka, Meter co-founder Griff Parry discusses transitioning from his previous AWS acquisition to building a $31.5 million venture-backed platform that powers hybrid usage-based billing for scale-ups generating over $50 million ARR.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Nathan holds 33.8% of the talking time here. How this is scored →
Nathan as informed peer 5.1 Guest teaching 4.3 Guest disagreement 2.9 Nathan pushing back 4.2
speaking balance: gold is Nathan, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 19:40 Debate over who counts as a founder
Griff resists Nathan's narrow definition of co-founders by defending their broader core team from GameSparks before conceding technical founding details.
Hardest push from Nathan ▶ 14:53 Nathan citing the real-time transcript to pin down minimum commitmentsWhen Griff denies stating customers need minimum API calls, Nathan quotes Griff's exact words from minute 8:57 back to him to force clarification.
Biggest teaching moment ▶ 12:25 Griff educating Nathan on true cloud API scaleGriff dispels Nathan's assumption that a high API volume is a few million per year by pointing out enterprise infrastructure runs billions per year and 40B per month.
Nathan holds their own ▶ 22:12 Nathan deducing valuation and ARR multiples from headcount benchmarksNathan demonstrates financial mastery by applying VC revenue-per-employee rules of thumb and market multiples to pressure Griff on valuation management.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Nathan as informed peer | Guest teaching | Guest disagreement | Nathan pushing back | Why |
|---|---|---|---|---|---|---|
| The Rise of Hybrid Usage-Based Pricing | 6 | 5 | 3 | 2 | Nathan frames the market with specific examples like Chargify's failed pivot to SaaSOptics and Stripe's dominance. Griff counters the premise of 'pure' usage-based pricing, explaining the shift toward hybrid subscription models. | |
| Customer Use Case: Sift and Meter's Core Architecture | 5 | 5 | 1 | 2 | Nathan references multi-billion dollar single-function companies like Pendo to probe Meter's dual scope. Griff articulates the full data pipeline and business applications using Sift as a case study. | |
| Target Market: Serving $50M+ ARR Scale-Ups | 5 | 4 | 3 | 6 | When Griff initially dodges customer numbers by calling Meter a 'solid Series A business', Nathan firmly pushes back twice to force quantifiable bounds ($50M+ ARR, tens of customers). | |
| Founding Journey: From GameSparks to AWS | 4 | 4 | 1 | 1 | Nathan asks about GameSparks' architecture and sale to AWS. Griff explains how video game backend demands shifted to active-player models and cloud infrastructure. | |
| Handling Billions of API Calls and Pricing Complexity | 4 | 7 | 4 | 5 | Nathan estimates API volumes in the millions, but Griff schools him by explaining enterprise scale reaches billions of calls, citing GameSparks handling 40 billion per month and reframing the core challenge as pricing complexity rather than raw ingestion. | |
| Contract Mechanics: Platform Fees and Commitments | 6 | 5 | 4 | 7 | Nathan quotes Griff's earlier statement verbatim to press on minimum commitments and whether fees are refunded, prompting Griff to reframe Meter's pricing as an infrastructure platform fee with variable overages. | |
| Team Structure and Founder Responsibilities | 5 | 3 | 5 | 7 | Nathan presses aggressively on the ratio of engineers versus sales staff and questions whether the founders code or if there are uncredited co-founders, leading Griff to admit he is dissembling on exact numbers before clarifying roles. | |
| Sales-Led Enterprise Motion and Economics | 7 | 4 | 4 | 7 | Nathan calculates benchmark metrics ($110k ARR/employee, $100M+ valuation multiples) to challenge Griff on dilution and options risk, then directly interrupts Griff's 'tinkering phase' comment to demand financial rigor. | |
| The Famous Five Rapid-Fire Questions | 4 | 2 | 1 | 1 | A collaborative and standard Famous Five wrap-up covering books, tools, sleep habits, family, and age. |
Statements from this episode (11)
Parry: SaaS will not transition entirely to pure usage-based pricing
“I definitely don't think it's the case that everything is going to be usage based and everything is going to be sort of an extreme variation of usage based.”
Parry: Most B2B software companies now use or plan usage-based pricing
“It was probably a minority concern as recently ago as, you know, three or four years. But now like the majority of B to B software companies are using some planning usage based pricing.”
Parry: Sift uses API pricing with minimum commitments and overages
“Sift is a good example. So if you know Sift, they used to be called Sift Sciences. They're a great business, and they're doing fraud detection for online retail effectively, and the core of the core metric that they charge against is, is based around APIs. So …”
m3ter targets companies with $50M+ ARR for usage-based billing
“Simplistically, I would say revenue, so it's fifty million dollar ARR and above.”
Parry: m3ter has tens of enterprise customers above $50M ARR
“The stage of our business is that we had tens of customers like that and growing fast.”
Parry: Do not build services for industries you do not know intimately
“If I did it all over again, I wouldn't have Built a service for an industry that I didn't know intimately myself”
Parry: m3ter structures deals as minimum commitments with generous usage allowances
“Our deals typically are under underneath the hood. They're usage based. But the way they work is that our customers make a minimum commitment to us. And that involves generous allowances of those usage vectors. And if they exceed them, they pay overages. But s…”
Parry: GameSparks processed 40 billion API calls per month
“I'll use games box as an example. So we were doing about forty billion API calls a month.”
Parry: SKU complexity and custom pricing cause billing headaches, not volume
“They could be trying to cope with a high degree of price complexity that might not have a huge amount to do with the volume of usage ingest. So, you know, it might be whatever, like a 1,000,010 million, a hundred million. It doesn't matter. But what the reason…”
Parry: Billing infrastructure requires heavy capital due to high MVP bar
“We're building critical infrastructure for significant companies, and that requires quite a lot In comparison, quite a lot of capital. So, you know, the minimum MVP to do this kind of stuff, which, you know, touches dollars, you know, it drives billing is quit…”