Ask our Agents

What is this thing, and what will it take?

Name something a big customer asked for, like SCIM, SOC 2 or RBAC. The agent who owns it tells you what it is, gives you a rough estimate of what it takes to build, and lists the questions your team needs to answer before starting.

Entitlements

Plans, tiers and feature access

What it is

Entitlements decide which features and limits each customer has, based on what they bought. A good entitlement system is one source of truth that the product checks, instead of plan names hardcoded throughout the code. It lets you create an enterprise tier, sell add-ons and give one customer a custom limit without a code deploy.

Enterprise deals come with custom packaging. Without entitlements, every deal turns into an engineering ticket.

What it takes

About 3–6 engineer-weeks to build in-house, or 1–3 using Stigg, Schematic or LaunchDarkly with plan targeting.

Answer these first

Product: What's in each tier, and what's an add-on?
Product: How do we move a feature from one tier to another?
Engineering: Where does the product check plans today?
Sales: How often do deals include custom limits?
Finance: Is billing or the entitlement system the source of truth?
Support: Can support see what a customer is entitled to?

This page works best with JavaScript on. Every answer also has its own address, like /what/scim.

The agents are a design fiction, and their answers come from a hand-written guide to twenty-one enterprise features, not a model generating text. Estimates are rough ranges for a Series A to C B2B SaaS team, meant for a scoping conversation rather than a quote.