Ben
🚨 Troubleshooting Tools
Troubleshoot event integrations, API interactions, and flag evaluations. In this video, Ben covers:
- API logs, track interactions with the REST API, including request details and response bodies
- Flag checks feature, where you can view evaluations of individual flags.
Gio
📏 Rule-based Audiences
In Schematic V0, you'll be able define the audience that gets a certain plan, add-on, or product.
You could do this very simply and merely add the companies that are part of the plan.
Or you can use rules to create an audience with traits coming from your CRM and billing system.
⚖️ Reconciliation layer
Schematic integrates with your CRM so your sales and success users can continue managing customer packaging from their own familiar tool
Schematic coordinates packaging across CRM and billing to ensure what the customer is getting billed and what they have access to is in sync
Schematic bridges the divide between GTM and product
Gio
📦 Entitlements
Entitlements are the core of Schematic. Take a look at how we're building them.
- Entitle features to plans according specific limits
- Feature types: boolean, event-based, trait-based
- Feature-level entitlement UX -> Flag-level targeting rules
✅ Permissive policy
Companies in Schematic can be part of multiple plans at a once (Plan + Add On, etc). What happens when a company is part of two plans that disagree on whether the company should have access?
Answer: Favor the most permissive policy
Ben
👥 Company / User model
We now support users that belong to multiple companies is a key need for our design partners
💾 Caching architecture
Learn how we've built our caching layer to ensure targeting doesn't go down and changes instantly.
Gio
⛳️ Flags vs. features
In the next version of Schematic, we are separating flags and features.
- Flags are code-level checks and you using targeting rules to roll them out
- Features are go-to-market concepts that can be have be associated to plans and company.
- Features are Boolean, usage-based, or value-based
🔢 Flag Evaluation Order
Once associated with a features, a flag gets rules applied according to a new set of rules applied at the feature level. In this order:
1. Company Override
2. Plan Entitlement
3. Flag Rules
What's next?
We're building V0 right now and it's slated for release some time in January for our design partners. Here's a preview on what else is on the roadmap.
📺 Tech Demos from Ben, our CTO
⛳️ Flags -> Features
📦 Plan Entitlements
🏢 Company Overrides
📏 Rules-based Plan Audience
👥 Many-to-many companies and users
📝 Change and error log