Today we’re launching a new kind of usage-based billing system. Every other product meters usage after the fact, then invoices. Schematic is the first billing platform with runtime enforcement, usage governance, and enterprise transparency built in.

RT @stripe: Available now: additional providers on Stripe Projects. @chatbase @composio @BuildOnNodeOps @CustomerIO @datadoghq @depotdev @…

high praise from a @GetSchematic customer interview today: “your SDK worked” we like things that work

Pricing therapy session coupon. Hats off to @fynnglover19 and his team at @GetSchematic 🫡 Spotted at @stripe Tour NY

I'm excited for @GetSchematic to join the Cloudflare Workers Launchpad program as part of its sixth cohort, announced today!

Ever hear of a company quietly crushing it behind the scenes? Meet @GetSchematic. 😉 Schematic is a usage-based billing platform that helps SaaS and AI companies drive revenue across product-led, sales-led, and hybrid pricing models. Learn more: schematichq.com/

Isn’t this where something like @GetSchematic comes in?

These 9 @ProductHunt launches might just blow your tech-loving mind (launched on May 21, 2025) 1. @AlgebrasAI 2. @superdotwork 3. @GetSchematic 4. @Google Flow 5. @EchoAINotes 6. Snapdeck for Figma 7. Imagen 4 8. Brief 9. Crosspost Explore. Upvote. Support builders. #AI #Tech

I recently did a podcast about billing engineering at @supabase, where @fynnglover19 from @GetSchematic and I were discussing a variety of billing topics and how I ended up at Supabase ⬇️ schematichq.com/podcast/buil…

Check out @fynnglover19 at @GetSchematic

SaaS and AI founders say they want pricing flexibility. What they really want is: → To launch new plans *w/o* asking developers to stop shipping → To support exceptions for enterprise deals → To automatically drive expansion when a customer reaches a limit That’s why @GetSchematic exists.

Let's build a Receipt Tracker SaaS with NEXT.JS 15 (AI Agents, @inngest , @GetSchematic , @stripe , @clerk ) piped.video/live/iBFHWS8rbW4… via @YouTube

every day seeing more and more search traffic to @GetSchematic coming from @ChatGPTapp kudos @supabase for having such a fun & instructive pricing page and overall billing experience to explore

It feels like B2B SaaS monetization is starting to shift in some really exciting ways. For example, one of our most popular features right now is "timed override"—temporary access to a premium feature that isn’t part of a customer’s plan. A product manager using @GetSchematic can grant time-limited access, letting customers try a feature before they buy. If they see the value, they can upgrade plans or buy it as an add-on—self-serve, no friction. This feature started as a way to give product managers a bunch of flexibility with how they monetize new features they're launching. And now what's interesting is that our customers who are using this feature are requesting a new feature: paywalls. And it’s not just product-led SaaS companies asking for this. Sales-led companies want paywalls too—especially founder-led sales teams. Here's why I think this is happening: At startups, products evolve fast – Founders close a deal, ship a ton of new value within a quarter, and want their product handling upsells while they hunt for new customers. Less buying friction – Customers want to expand their usage without needing a sales call. Better monetization – Customers and product developers want more granular control over how features are packaged, trialed, bundled, and monetized. Back to the shift -- it feels like B2B SaaS is starting to monetize more like e-commerce and B2C SaaS: - Paywalls & gated access - Targeted promos & incentives - Self-serve upgrades/downgrades - Pausing & flexible billing - Personalized pricing & exceptions And from there, you can start to imagine further use cases where product folks can easily embed even more consumer-grade monetization experiences in their apps: - Cart abandonment recovery - Bundling & cross-selling - Loyalty & rewards programs - Referral incentives

Today on #StartupSuccess, Fynn Glover @fynnglover19, co-founder & CEO of @GetSchematic, shares his expert insights on monetization, customers' willingness to pay, and overcoming common pricing & packaging challenges! 🎙️Available now on Apple Podcasts or wherever you listen!

Dogfooding is king. If you're not using your own product, then you are building blind. It's really that simple. We use @GetSchematic daily to launch, track and monetize our features as well as manage our customers access and subscription. Take a look: piped.video/vMWDiyi_0jE

Got off the phone yesterday with a product developer at a fast-growing AI startup that’s been trialing @GetSchematic. I asked him why he intends to use our product. Loved his framing: "All of the features we prioritize should impact growth. And we need the tooling to deliver on this. We’re launching a ton of features, and with you guys, I can run time-bound trials, bundle and unbundle, manage overrides, get feedback and engagement, test paywalls, and build tight feedback loops on business impact." I think this is where SaaS is headed. For years, PLG has been about making product the engine of growth. But most teams still monetize features slowly, painfully, and with way too many stakeholders: - Developers need to deploy the feature. - Product needs to figure out rollout. - Success needs to update access and communicate to the customer. - PMM needs to update assets. - Finance needs to make sure it ties in the billing system. It kills speed. Most teams hacking this together today run into two major blockers: 1/ Feature management tools were built for devops. Great for toggling features on/off, hard to use for monetization. 2/ Billing systems don’t talk to the product. So to run trials, limit and enforce usage-based entitlements, or execute pricing experiments always requires engineering sprints. What gets me hyped about what we're building is that you can start to realize a world in which one enterprising product developer can do all of the above on the fly. - Launch, test, and iterate on features without code changes. - Bundle, unbundle, and monetize inside the product. - Connect feature access directly to billing.

We're releasing part 2 of our teardown of @posthog's pricing page and overall billing experience later this week. They do a great job, and there's a lot to learn from them. Here's a quick teaser on what I found really compelling overall. 1. Frictionless developer-led motion – Developers can get started instantly, no credit card required. 2. Add-ons as a revenue driver – They pull users in with a cheap bundle, and then drive expansion with add-ons. 3. They're counter-positioning on price – In other words they're bundling tools across multiple categories and trying to be a lower cost alternative to incumbents in each of the categories they're serving. 4. Pricing as a brand asset – Their pricing page isn’t just functional—it’s a marketing tool. It makes fun of status quo software sales, seeks to commoditize competitors, and delivers a ton of transparency into their pricing philosophy.

🎙️ @fynnglover19 and Ben Papillon, cofounders of @GetSchematic, join the pod to discuss managing feature flags in software development, including exploring practical applications of feature flags and how orgs could manage pricing models more effectively. stackoverflow.blog/2025/01/3…

If you're a founder or product person working on your startup's pricing, this is so good from Michael Dearing & @heavybit heavybit.com/library/video/h… A few things it reminds us to consider: 1️⃣ Pricing is about perceived value, not cost. Customers buy when they feel they’re getting more value than they’re paying for. 2️⃣ Behavioral economics beats spreadsheets. Understanding why people buy is just as important as setting the price itself. 3️⃣ Intuition matters. Great pricing decisions blend data with gut instinct, just like great product decisions. If you're working on pricing & packaging in a startup and haven’t seen this talk yet, it’s worth your time.