# Data residency

URL: /workflows/sales/plays/data-residency · Id: `play:data-residency`

> Data residency pins a buyer’s Tenant to one region, adds the residency annex, and quotes the Price tier that includes it.

Data residency pins a buyer’s [Tenant](/business/nouns/tenant) to one region, adds the residency annex, and quotes the [Price](/business/nouns/price) tier that includes it.

## Ratings
None.

## Budget
None.

## How it runs
The [Studio](/business/nouns/studio) rolls it out to one cohort at a time: startups with [Deals](/business/nouns/deal) whose buyers require data held in one region.

## Processes
Runs as [Quoting](/workflows/processes/quoting), accountable to the [Sales Team](/agents/sales).

## Fits
| Fits | Value |
| --- | --- |
| Shelf | Compound: builds an engine that keeps growing (Grow) |
| States | [Repeatable](/business/lifecycle/states/repeatable), [Scale](/business/lifecycle/states/scale) |

## Loop
| Step | Value |
| --- | --- |
| Hypothesis | Pinning a region and quoting its tier closes more regulated buyers than declining residency requests. |
| Measure | [Outside paid Orders](/agents/sales#outside-paid-orders) over 90d, at least 10 observations |
| Learn | The learn step reads the Readout, records Evidence and a Decision, and drafts the next Variant. |

## Example
A clinic group in the EU requires patient data held there. Data residency pins its Tenant to the EU region, adds the residency annex, and quotes the $1,200 tier that includes it.