/

/

Cost per tenant for multi-tenant SaaS

Cost per tenant for multi-tenant SaaS

Cost per tenant for multi-tenant SaaS

Allocate shared infrastructure to tenants using labels, namespaces or usage metrics, and track infrastructure cost per client.

Runs in

Claude · Slack

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Rank our top 20 tenants by allocated infrastructure cost last month and compare with their plan tier.

› get_context

› get_context

› query ↗ Explorer

› query ↗ Explorer

The top 3 tenants drive 22% of allocated infrastructure cost. Tenant acme-retail (Growth tier) costs €2,300/month, above its plan price. Most of it is search indexing triggered by their catalog syncs.

Customer success and finance decide on pricing or limits.

Playbook

What the agent does

From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.

Costory notices

A tenant's infrastructure cost grows faster than its plan.

Costory investigates

01

Tenant signal

Tenant labels, namespaces, or per-tenant usage pushed as custom metrics or read from BigQuery.

02

Allocate

Direct costs by label, shared costs by usage.

03

Unit cost

Infrastructure cost per tenant and per plan tier.

04

Watch outliers

Alert when a tenant's cost jumps.

Where you see it

Claude

You decide

Customer success and finance decide on pricing or limits.

Why it matters

In multi-tenant SaaS, a handful of customers can drive a large share of cost. Pricing and sales need to know which ones.

Who it’s for

SaaS CTOs, finance, product leaders

Where it runs

Claude · Slack

What you get

What lands in front of your team

Cost per client

Infrastructure cost per tenant, tracked monthly.

Pricing input

See which tiers are under-priced.

Outlier alerts

Know when a tenant's usage changes.

Sources and assistants

What it connects

The billing data, context and assistants this playbook uses. Each links to its setup page.

The billing data, context and assistants this playbook uses. Each links to its setup page.

Example prompts

Or drive it yourself

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

Rank

Rank our top 20 tenants by allocated infrastructure cost last month and compare with their plan tier.

Watch

Alert #customer-success when any tenant's monthly infrastructure cost grows more than 30%.

FAQ

Questions about this playbook

Do we need a tenant label on every resource?

No. Direct costs can use labels or namespaces, and shared costs can be split by per-tenant usage you push as custom metrics or read from BigQuery.

Where do business metrics come from?

From Amplitude, BigQuery, Snowflake, Google Sheets, S3, Datadog, CloudWatch or metrics you push to Costory's API.

How long does this playbook take to set up?

Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.

Does Costory change anything in our cloud accounts?

No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.

Step-by-step guide in the Costory docs

Put this playbook on call

Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Setup

About 30 minutes

Data residency

EU

Access

Read-only on your cloud