Ryan from Schematic shows how to override plan limits for individual customers without changing their billing. Sales teams can grant extra features or usage as temporary incentives, set expiration dates for trials, and let prospects test premium features before upgrading.
Chapters
Hi, I'm Ryan, a developer with Schematic, and I want to talk about one of the coolest parts about Schematic, and that's the way that it can handle all the real-life complexity that goes into different billing situations. In a perfect world, everyone is going to be— they're going to go to your website, they're going to sign up to one of your plans, and they're going to use the plans as written. But in the real world, life is just never that simple. There's any number of reasons for this. Maybe there are customers on legacy plans who, when they signed up, the plans were different,, and you want to honor the grants and the ability, you want to honor the grants and the level that they used to have, even though that doesn't currently match with your pricing quite right. Another example is sales-led motions, right? And a lot of important sales-led deals, you know, you need to throw in sweeteners to get people to sign up. So maybe they're supposed to be on one plan, but you give them a little bit of extra usage to get a deal done, or they need access to a feature that's not normally at their level, you know, but it's really important to this deal. Um, and that's the way it was sold. So that's the way your product has to support it. Import it. What's cool about Schematic is that we make all of these cases really easy by allowing you to essentially produce an override at a company level for a given plan. I want to talk about how that works. Um, what you're looking at now is the pricing that we use for our modeling post-hocs pricing. If you haven't seen it, check out that video. It's pretty cool. Um, but for now, let's imagine that we've got a customer that was one of our earliest customers and their actual plan doesn't quite match these 3 plans. They have access to a feature that we used to give away at the ridiculously cheap plan for free, and now we don't. But we still want to give this customer access to that. So how would we do this? Let's take Ryan's Kalachi Factory. They're one of our earliest customers, and we want to grant them access to the Teams feature, something they should have access to but doesn't align with our current plans. So we're going to add a company override. We're going to select Teams. And all we have to do is click Save, and now whenever we're evaluating what access Ryan's Kolache Factory should have, they will also have access to the Teams product. Now additionally, we could set an expiration date on that override, and this is most commonly used in, in situations where a company is thinking about upgrading and maybe they want to upgrade and there's a key feature that's the driving reason for why they want to upgrade. But before they actually conduct an entire upgrade and start paying more, they want to try it out. In that case, you could give them a timed override, and maybe we'll let this override last for a month or 2 months, 3 months, and give them some time to try out the new feature, decide it's right for them, you know, begin integrated into their workflows, um, at which point they're ready to convert. These are just 2, but some of the really cool ways in which Schematic makes managing the real-life complexity of plans and entitlements easy so that you, the business, can go back to focusing on what matters and not dealing with these complex billing situations. Thanks.
