LeadSimple Data Platform

Grow every market like you grew the first.

Every market measured the same way, so you can see who is pulling ahead and what they are doing differently. Answered in a dashboard, in your warehouse, or in a chat window.

Talk to sales
Rollup reporting REST API Event webhooks MCP server
LeadSimple LeadSimple
WORKSPACE
Inbox24
Leads7
Pipelines
Processes3
Reports
DATA
API keys
Webhooks
MCP server
DW
Dana W.
VP Operations · HQ
Search metrics…⌘K
Reports / Market scoreboard
Export ▾ Share
DW
Market scoreboard All markets ▾ 8 markets · 5,855 doors Month to date ▾ vs. corporate goal
ANSWER RATE
94.2%▲ 2.1 pts
Goal 94.0% · +0.2 over
LEAD → SIGNED
28.6%▲ 1.4 pts
Goal 30.0% · 1.4 under
SPEED TO LEAD
3m 40s▼ 22s
Goal 5m 00s · met
CALLS HANDLED
2,861▲ 312
Pace 3,240 · on track
Answer rate by marketVariance to goal ▾
MARKETDOORSANSWER RATEVS GOALSPEED
PX
Phoenix Metro
1,412
97.1%
+3.12m 10s
DF
Dallas–Fort Worth
1,186
95.4%
+1.42m 58s
AT
Atlanta
964
94.8%
+0.83m 12s
TB
Tampa Bay
892
93.2%
−0.83m 44s
DE
Denver
761
91.7%
−2.34m 05s
CH
Charlotte
640
88.9%
−5.15m 21s
All markets5,855
94.2%
+0.23m 40s
Dallas–Fort Worth6 months
90.8% Feb95.4% today╌ goal 94.0%
Below goal3 of 8 markets
Charlotte — 5.1 pts under
Two queues unstaffed after 4pm local
Denver — 2.3 pts under
Speed to lead slowed 40s; 2 reps out
Tampa Bay — 0.8 pts under
12 leads unworked in the last 24h
Streaming to 4 webhook subscribers
Who it’s for

When one P&L is really eight, reporting is an infrastructure problem

Every office already runs sales and operations on LeadSimple. The Data Platform turns that into one set of numbers every market counts the same way.

Franchise networks

Corporate sees every franchisee on the same scorecard, with data boundaries that keep each owner in their own market.

Multi-market operators

Compare Dallas to Denver on identical definitions, then drill to the rep who moved the number — without exporting anything.

Acquisitions

New acquisitions inherit the same metric definitions on day one, and board reporting stops being a monthly spreadsheet project.

Reporting layer

From every door down to one rep

One metric, one definition, at every altitude. Change the altitude, not the math — so a market conversation and a coaching conversation use the same number.

Company rollup. Every market aggregated into one live view — no spreadsheet stitching, no month-end lag.
Drill down. Company → market → team → rep, with the same definitions the whole way down.
Saved views per role. The regional director, the BDM lead, and the board each open their own scoreboard.
Scheduled digests. Monday’s numbers land in every leader’s inbox before the week starts.
Drill down
Answer rate
Company Novo Property Group 94.2%
Market Dallas–Fort Worth 95.4%
Team Leasing — North 96.0%
Rep J. Alvarez 97.4%
The same drill-down path is available over the API — pass a dimension and get the level you asked for.
Goals & variance
Corporate goal
Answer rate ≥ 94.0%
Phoenix Metro97.1%+3.1
Dallas–Fort Worth95.4%+1.4
Tampa Bay93.2%−0.8
Charlotte88.9%−5.1
Goal line · a goal.breached event fires the moment a market crosses it

Set the KPI at corporate. Watch it land.

Goals are first-class objects, not a column someone maintains in a spreadsheet. Define them once per metric — company-wide or per market — and every view reports variance against them automatically.

Variance everywhere. Dashboards, digests, and API responses all carry the same to-goal delta.
Alert on the breach, not the report. Subscribe to goal events and let the exception find the operator.
Ramp targets. A market acquired last quarter can carry its own curve without breaking the company number.
Build on it

Three ways in. Same numbers behind all of them.

Ask in plain language over MCP, pull it with the REST API, or subscribe to the event stream. Nothing is a nightly CSV, and nothing is a different definition of answer rate.

MCP server

Ask in English. It writes the query.

Connect Claude, ChatGPT, or your own agent to the LeadSimple MCP server. It exposes your metrics, markets, goals, and records as tools — scoped, read-only by default, and answering from live data rather than a stale extract.

OAuth-scoped tokens — a regional’s agent sees a regional’s data
Every answer cites the query it ran, so numbers stay auditable
Tools for metrics, drill-down, call transcripts, and process history
mcp.leadsimple.com/sse
LeadSimple MCP · connected
What’s our answer rate in Dallas–Fort Worth month to date, and how does it compare to the corporate goal?
Tool call · query_metrics
{
  "metric": "answer_rate",
  "dimension": "market",
  "filter": { "market": "Dallas–Fort Worth" },
  "window": "mtd",
  "compare_to": ["goal", "company"]
}
Dallas–Fort Worth answered 95.4% of inbound calls month to date — 1,132 of 1,186. That’s 1.4 points above the 94.0% corporate goal and 1.2 points ahead of the company average. Charlotte is the only market under goal, at 88.9%.
Which reps drove the gap? Trend it over six months Why is Charlotte behind?
REST API

One call. The whole rollup.

The Data Platform extends the LeadSimple API past records into metrics: pre-computed rollups, time series, market and team hierarchy, and goals. Ask for a number instead of paginating a quarter of calls to derive it.

GET /v1/metrics/rollup?metric=answer_rate&dimension=market&window=mtd&compare=goal
{
  "dimension": "market",
  "window": { "start": "2026-08-01", "grain": "mtd" },
  "rows": [{
    "market": "Dallas–Fort Worth",
    "answer_rate": 0.954,
    "goal": 0.94, "variance": 0.014,
    "calls": 1186, "answered": 1132
  }],
  "next_cursor": "c2_mkt_08"
}
Endpoint catalog
GET /v1/metrics/rollupAny metric, any dimension, with variance
GET /v1/metrics/timeseriesHourly to monthly grain, up to 36 months
GET /v1/marketsMarket and team hierarchy with door counts
GET /v1/goalsTargets by metric, scope, and period
GET /v1/callsOutcomes, recordings, transcripts
GET /v1/dealsPipeline, stage history, attribution
GET /v1/processesTask-level completion and cycle time
GET /v1/eventsReplayable activity stream, 30-day window
POST /v1/exportsBulk snapshot to your warehouse
Read the API docs
Event webhooks

The number moves. You know.

Subscribe to what your people and your properties do. Signed payloads, at-least-once delivery with exponential backoff, and a 30-day replay window when your consumer was down.

call.completed call.missed message.received deal.stage_changed process.task_completed process.closed goal.breached user.presence_changed report.ready
POST https://hq.novopg.com/hooks/leadsimple
{
  "event": "goal.breached",
  "occurred_at": "2026-08-04T14:02:11Z",
  "scope": { "market": "Charlotte" },
  "metric": "answer_rate",
  "value": 0.889, "goal": 0.94,
  "delivery": { "attempt": 1, "signature": "t=…,v1=…" }
}

What teams build with it

Office TV scoreboards. Comp and incentive tracking. Lead routing from a corporate site to the right market. Franchise royalty reporting that reconciles itself.

Your warehouse, your BI

Land snapshots in Snowflake or BigQuery and model them next to accounting, door counts, and royalties — then report in Power BI, Tableau, or Looker.

Access & governance

Scopes, not master keys

Grant read on metrics without read on transcripts. Every token is least-privilege and revocable on its own.

Market boundaries hold

A franchisee’s key returns a franchisee’s rows. The same scoping that governs the app governs the API and MCP.

Everything is logged

Key, scope, endpoint, and row count on every request — including the ones your agents make on your behalf.

Limits sized for a portfolio

Enterprise keys raise the rate limit well above standard access — with cursor pagination and bulk exports for backfilling a new market.

Put the numbers where the decisions are

Talk to sales about the Data Platform — reporting rollout across every office, enterprise API keys, MCP access, and event webhooks for your data team.

Talk to sales