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.

SLA

Service level agreement: uptime and support commitments

What it is

An SLA is a contractual promise about your service: usually an uptime percentage, support response times by severity, and credits if you miss them. 99.9% uptime allows about 43 minutes of downtime a month, and 99.99% allows about four. Behind the number you need monitoring that measures uptime the way customers experience it, and a support team staffed to meet the response times.

Enterprises depend on your product for their own work. An SLA shows you'll stand behind it, and procurement often won't sign without one.

What it takes

About 3–6 engineer-weeks to build in-house, or 1–3 using Better Stack, Datadog Synthetics, Statuspage or incident.io.

Answer these first

Engineering: What has our availability actually been, measured from the customer's side?
Finance: What would the proposed credits have cost us over the last year?
Support: Who responds to a severity-one issue at 3am?
Product: What counts as downtime: a full outage, degraded service, or one feature failing?
Legal: Are credits the only remedy, and are they capped?
Sales: What number are buyers asking for, and would 99.9% do?

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.