KIST / PRICING
How this is priced.
There is no price list here, on purpose. Kist is sold as an engagement, not a seat, and what a given business pays depends on the shape of what it is connecting. What follows is that shape: what moves the number, what is included regardless, and how the conversation actually starts.
WHAT VARIES
What varies
A quote is built from the same handful of things every time, and we would rather you see them than guess at them.
| What we look at | Why it moves the number |
|---|---|
| Number of clients or properties in scope | Each one gets its own governed warehouse and its own tenant boundary, not a shared table with a filter on it. More properties is more infrastructure to run correctly, not more rows in one database. |
| Number and kind of connectors | Paid media, analytics, search, bookings, CRM, accounting. See what we connect. Each connector we operate on your behalf is ongoing work: scheduled ingest, a schema that survives the vendor changing theirs, and a place the raw response is kept so we never have to ask the vendor twice. |
| Whether it is white-labelled to your own clients | An agency reselling the dashboard under its own name is a different engagement from a single business using it internally, because the tenant isolation, the branding and the support line all have to hold up in front of someone who is not us. |
| How much of the work is bespoke | A standard connector runs the same for everyone. A one-off report shape, a non-standard source, or a recommendation engine tuned to a specific business is work we scope and quote separately, because it is not the same cost to run twice. |
- Tenant boundary
- The wall around one client's data. Every query runs inside one client's walls and cannot read another client's rows.
- Connector
- The scheduled pull from one platform into the warehouse, with the platform's raw response kept on disk.
- White-labelled
- The dashboard shown to your clients under your agency's name rather than ours.
WHAT IS INCLUDED
What is included, regardless of scope
Underneath any of the above, every engagement gets the same floor.
A warehouse per client
A governed, per-client warehouse with runtime tenant isolation, not a shared one with a permission flag.
Every connector to one standard
Raw responses kept, written as they arrive, rebuildable from disk without going back to the vendor.
A record of every answer
What was asked and what was returned, so an answer can be checked rather than taken on trust.
Read more at what is actually live today and how the plug-in works.
HOW IT IS BOUGHT
How it is bought
There is no signup form and no automated checkout. Onboarding is a runbook we run with you, not something you configure alone, and the first conversation is where we work out which of the variables above apply to your business. Where an agency is connecting a client’s data, that conversation also covers the data processing agreement that has to be signed before the first connection, the same gate described on the terms of service.
Charges, billing period and notice are set out in your order form or engagement letter once scope is agreed, not published here as a general figure, because a number that has to fit every business ends up meaning nothing to any one of them.