The numbers that tell you
the business is performing.
Uptime, ARR, NPS, latency, churn, win rate. The live indicators of how the company is actually running right now. Most organizations bury them in spreadsheets riddled with errors and BI tools their leaders quietly stopped trusting. Mistvine puts them on every member's home and keeps them current automatically — connector-fed from the systems that already produce the data.
KPIs (Key Performance Indicators) are the live signals that tell you whether the business is currently performing — uptime, ARR, NPS, latency, win rate, churn — distinct from OKRs, which are the goals you are trying to achieve over a cycle. The distinction matters because conflating them produces "key results" that measure activity (publish 12 blog posts) instead of outcome (organic traffic up 25%), and indicators that go stale because no one updates the spreadsheet. The state of practice is poor: 75% of executives do not have high trust in their own data (HFS Research / Syniti). Good KPI practice keeps numbers live (connector-fed from systems of record like Stripe, GitHub, or Datadog rather than typed in monthly), picks the right indicator shape (climb to a target, hold above a threshold, stay inside a healthy range), and surfaces the indicator everywhere it is supposed to inform decisions — including next to the OKRs that depend on it.
When the indicators are wrong, every decision is a guess
A KPI is only useful if leaders trust it enough to act on it. Today most KPIs live in spreadsheets riddled with errors, in BI tools nobody outside analytics opens, or in status decks that are already a week out of date by the time the meeting starts. The result: leaders fall back on intuition because the numbers in front of them aren't worth believing.
What changes when KPIs update themselves
The Right Indicator Shape for the Metric
Real KPIs don't all behave the same way. Uptime needs to stay above a floor (99.9%). Latency needs to stay below a ceiling (500ms). Engagement metrics need to stay inside a healthy range — too low signals churn, too high signals burnout. ARR just needs to keep growing — no fixed ceiling, just direction. Mistvine supports all four indicator shapes natively, so you stop force-fitting guardrail and growth metrics into progress bars that were never designed for them.
Connector-Fed, Not Copy-Pasted
Bind a KPI to a Google Sheet cell, an HMAC-signed webhook, or an HTTPS endpoint with a JSON path, and the value refreshes itself on a schedule. The person closest to the system that produces the number — finance, ops, support, eng — wires it once and walks away. Nobody is updating a deck the night before the review.
Visible to Everyone, Not Buried in BI
KPIs render on every member's Home — not behind a paywalled BI seat, not in a dashboard half the company has never logged into. When the indicators that matter are visible to everyone responsible for moving them, the conversation shifts from "what's the number?" to "what are we doing about it?"
One Wiring Job, Used Everywhere It Matters
The same connectors that feed KPIs also feed key results on individual, team, and wave OKRs. Wire the data once at the source of truth — Sheets cell, webhook, HTTPS endpoint — and every surface that should reflect the indicator does, automatically. No duplicate ingestion paths, no drift between what the dashboard shows and what the cycle review reports.
The dashboard era is collapsing under its own weight
The proliferation of BI tools, custom dashboards, and ad-hoc spreadsheets created a paradox: more numbers than ever, less clarity than ever. Leaders react by tuning out — or by falling back on gut. The fix isn't more dashboards; it's pinning the small set of indicators the whole company should be watching, in one place, kept live automatically.
TheyDo 2025 leadership surveyDashboard fatigue compounds the data-trust problem: when there are too many metrics from too many sources, scrutiny drops. KPIs that update themselves from the source-of-record system are easier to trust than KPIs that were assembled by hand last Thursday.
TheyDo 2025 leadership surveySpreadsheet KPIs vs. live, connector-fed KPIs
| Aspect | Spreadsheet / BI KPIs | Mistvine KPIs |
|---|---|---|
| What the number is | "Whatever was in the deck last quarter" | A live indicator of current performance |
| Where it lives | In a tab nobody opens, behind a BI seat half the company doesn't have | Pinned to every member's Home screen, no extra license required |
| How it updates | Someone copy-pastes the latest figure (when they remember) | Google Sheets cell, webhook push, or HTTPS endpoint refreshes on a schedule |
| Indicator shape | "Hit a number" is the only mental model — guardrail metrics get awkward | progress, stay-above, stay-below, or stay-between — pick what fits the metric |
| Trust | Spreadsheets contain errors 94% of the time; leaders fall back on intuition | Read straight from the system of record; "last pulled" timestamp shows freshness |
| Drift detection | Nobody notices the indicator is in the red until the board meeting | Status flag changes color the moment a KPI crosses its threshold |
| Audit trail | No version history beyond a Sheet's revision view | Every value write logged with the rest of the platform's audit infrastructure |
KPIs built like indicators, not like quarterly status fields
Most performance platforms treat metrics as a number you type in once a quarter. Mistvine treats KPIs as what they actually are: the live signals of how the business is performing — connector-fed, indicator-shape-aware, and visible to everyone they're supposed to inform.
Four Indicator Shapes, Not Just "Reach a Number"
stay-above holds a floor (NPS, uptime, CSAT). stay-below holds a ceiling (latency, error rate, churn rate). stay-between holds a healthy range (engagement, conversion, sessions per user). trend tracks direction-only against a baseline (ARR, MAU, time-to-value). Every KPI gets the shape that matches how the indicator actually behaves.
Learn moreBring-Your-Own Data Source
Google Sheets, webhook, or HTTPS GET — three primitives that cover almost any system you already run. No proprietary ingestion API to learn, no closed platform to migrate off. If you can write to a Sheet or hit an endpoint, your KPI updates itself.
Learn morePer-User Google Connection
Each user authorizes their own Drive — admins can't see other users' sheets, and the connection is scoped to the cells you bind. No service account for the whole org, no "grant access to this shared inbox" friction, no IT ticket.
Learn moreOne Connector Layer, Many Surfaces
The same Sheets / webhook / HTTPS-GET wiring that feeds KPIs also feeds key results on individual, team, and wave OKRs. Configure ingestion once at the source; every surface that depends on the number stays in sync.
Learn moreCommon questions about kpis
Why aren't my BI dashboards enough?
BI tools are great for exploration — slice, dice, drill. But the people responsible for moving the number rarely have a BI seat or open the BI tool daily. KPIs in Mistvine sit on every member's Home alongside goals, 1:1 topics, and team health, so the indicators are in the room when the decisions are made — not three clicks away in a separate product.
Which data sources are supported today?
Three connector types ship today: Google Sheets (per-user OAuth, bind to a specific cell), webhook (HMAC-signed POST endpoint we mint a secret for), and HTTPS GET (we poll a URL on a schedule and extract a value via JSON path). For anything else — Stripe, GitHub, Datadog, Linear — webhook or HTTPS GET is the bridge today; first-party connectors are on the roadmap.
Is the Google Sheets connection per-user or per-org?
Per-user, via Profile → Connections. Each person authorizes their own Google account, and Mistvine only reads the specific cell you bind to a KPI or key result. Other users in your org — including admins — can't see your Drive or your other sheets. If you disconnect, the binding stops auto-refreshing until someone else owns it.
How fresh are connected KPIs?
Sheet-bound and HTTPS-GET-bound KPIs refresh on a scheduled cron (a Supabase edge function runs throughout the day). Webhook-bound KPIs update the moment your system POSTs to the endpoint — useful for real-time signals like incident counts or signups. Every KPI shows a "last pulled" timestamp so you can see exactly how fresh the indicator is.
What happens when a KPI drifts outside its target?
Its status indicator changes color on Home — a visual signal everyone sees. We don't email-blast the org or page anyone; that pattern produces alert fatigue and trains people to ignore the dashboard. The point is to make drift visible inside the surfaces people already use, not to manufacture urgency.
What if a connector breaks?
The KPI keeps showing its last-known value plus the timestamp of the last successful pull, and the failed-pull error is recorded so you can debug. You can switch the source back to manual at any time and edit the value inline — no support ticket, no admin-only escape hatch needed.
Stop guessing at the numbers.
Pin the indicators that actually tell you how the business is performing — and keep them live. Start your 14-day free trial.
Start Your 14-Day Free Trial No credit card required