How many locations does datacube support?

Datacube is built to support multi-location rollups with standardized KPI definitions across locations. The number of branches and the depth of the rollup are configured during your custom build. Operators can switch between locations in the profile menu, and access is controlled by user type so branch managers see their own data while executives see the full rollup.

What data sources need to be connected for multi-location reporting to work?

At a minimum: your CRM or field-service platform (ServiceTitan, Housecall Pro, Workiz, or similar) for each location, plus your accounting system (typically QuickBooks) and call-tracking or phone data if you want booking-rate visibility. Marketing platforms like Google Ads can be added per branch for spend and attribution. Each source is mapped to the correct branch during onboarding so the rollup does not mix locations.

Can each branch have its own goals and thresholds?

Yes. Multi-location builds include per-branch goal targets. AI-assisted flags are calibrated to each branch's own normal performance range, so a newer or smaller market is not constantly flagged as an anomaly simply because it runs lower volume than the flagship location. Goals can be set at the company level for rollups and at the branch level for individual accountability.

What stops a branch manager from seeing other branches' data?

User type controls access. A branch manager is configured to see only their location's boards. A GM or multi-location executive can see all branches. A CSR or technician sees only what is relevant to their role. The access structure is set up during your datacube build and can be adjusted as roles change.

How is this different from running separate dashboards for each branch?

Separate dashboards require someone to visit each one individually and mentally stitch the results together. AI multi location reporting shows the consolidated view by default, so an owner or GM sees the full picture at once rather than making five logins before the morning is over. The cross-branch comparison is built in: when one branch's cost per booked job spikes, the flag appears alongside the company rollup, not buried in a tab no one opened.

Does the AI make decisions about which branch to prioritize?

No. The AI surfaces the signals, such as which branch is pacing below goal, where a booking rate is sliding, or which market's lead costs have risen. The operator decides what to do about it: whether to reallocate resources, adjust marketing spend, or coach a branch team. The software finds the signal; the human supplies the context and owns the call.

How long does it take to set up AI multi location reporting?

Datacube uses a custom build and onboarding process that typically runs about 4 to 6 weeks. For multi-location builds, extra time goes into mapping each branch's data sources, standardizing KPI definitions across locations, and setting per-branch goals and display configurations. The outcome is a dashboard built for your specific branch structure, not a generic template.

AI multi location reporting for home-service contractors

Q: What is AI multi location reporting for home-service contractors?

It is a reporting system that consolidates each branch's CRM job data, call performance, marketing spend, and financial results into a single real-time dashboard, then uses AI-assisted analysis to flag which locations are pacing behind goal, where anomalies are appearing, and what trends are forming across the business. For home-service and skilled-trades companies, it replaces the manual process of logging into separate systems for each location and synthesizing the numbers yourself.

When you run two, five, or ten locations, the numbers you need to act on rarely show up in one place. AI multi location reporting consolidates every branch's CRM jobs, phone performance, marketing spend, and financials into a single view, surfaces the gaps that would otherwise stay buried in separate logins, and lets the operator act while the month is still recoverable.

By Datacube content engineAutogeneratedJune 24, 2026

Multi-location visibility

The branch problem you find on the 31st

Picture a residential HVAC operator with four locations. Three are tracking fine. The fourth is quietly having its worst month in a year: booking rate down, average ticket sliding, and a paid lead source that stopped converting two weeks ago. Nobody flagged it because each location runs its own ServiceTitan login, and the weekly call is long on updates and short on numbers. By the time the owner sees it on the month-end report, the revenue is already gone. AI multi location reporting exists to close that gap. When every branch's job data, call outcomes, marketing spend, and QuickBooks financials flow into a single custom dashboard, a location pacing 22 percent below its goal is visible on day 12, not day 31. Datacube is designed to consolidate that cross-branch view and make it available on web, mobile, and office TV without building it yourself in a spreadsheet.

What AI can help surface across multiple locations

Branch-level rollups with standardized KPIs

Every location is measured the same way: same KPI definitions, same goal structure, same thresholds. Rollups show the company total and let you drill into any branch, so a slip at one location does not hide behind a strong week somewhere else.

Outlier flags across branches

When a branch moves outside its own normal range or diverges from group performance, the dashboard can surface it. An HVAC branch with a callback rate twice the company average is visible immediately, not in the next ops meeting.

Real-time pacing against per-branch goals

Each location gets its own goal targets, and pacing is shown month-to-date and year-to-date. A GM running five locations can see in one view which branches are on track and which need attention, without switching between logins.

Trending and revenue projection

When configured with enough clean history, the dashboard can project each branch's pacing for the rest of the month or year based on current trends. The output is decision context: the owner still decides whether to shift capacity, adjust spend, or realign goals.

Cross-location leaderboards

Techs, CSRs, and sales reps from all branches can compete on the same contest board, or each branch can run its own. Standardized KPI definitions mean a win in Phoenix and a win in Tucson are measured identically.

Per-branch marketing attribution

When marketing platforms are connected, spend and cost per booked job can be broken out by branch or market, so the owner sees which locations are getting efficient leads and which are burning budget on unconverted traffic.

How multi-location reporting works in a datacube build

01
Map every data source by branch
During onboarding, each location's CRM instance (ServiceTitan, Housecall Pro, Workiz), phone or call-tracking account, and marketing campaigns are mapped so job data, call outcomes, and spend flow to the right branch in the rollup.
02
Standardize the KPI definitions
Before connecting anything, the datacube team aligns with the operator on what each metric means across all locations: how booking rate is counted, how revenue is categorized, how callbacks are defined. Standardization is what makes a cross-branch comparison meaningful.
03
Set branch goals and alert thresholds
Each branch gets its own goal targets. AI-assisted flags are calibrated to each branch's normal range, so a smaller market is not constantly flagged because it runs lower volume than the flagship location.
04
Build the rollup and the branch views
The company-level rollup gives executives a single number for every KPI across all locations. Clicking into a branch opens that location's detailed view. Managers at each branch see their own board; executives see all of them.
05
Deliver on TV, mobile, and web
Headquarters displays the rollup on office TV, auto-rotating through boards. Branch managers get mobile and web access to their view. Access is controlled by user type, so a CSR sees call boards without seeing another branch's financials.

Who sees what: AI multi location reporting by role

Role	Primary view	AI-assisted signals most useful to this role	Typical action taken
Owner / CEO	Company rollup: revenue pace, gross profit, goal attainment by branch	Branch pacing below group average; anomaly in cost per booked job at one location	Call branch GM; reallocate marketing spend; adjust monthly goal
GM / operations leader	Multi-branch ops board: capacity, dispatch, job completion rate	One branch running over capacity while another is under; callback spike at a location	Re-route technicians; escalate callback pattern to branch manager
Branch manager	Own-branch board: sales, calls, tech performance, reviews	CSR booking rate sliding vs. prior week; one tech's average ticket falling	Listen to recorded calls; one-on-one coaching with the tech
Marketing leader	Per-branch spend vs. revenue attribution; ROAS by market	Cost per booked job rising in one market; a campaign converting in one city but not another	Pause the underperforming campaign; shift budget to the converting market
Controller / finance	QuickBooks financial board: revenue, COGS, gross profit, labor % by branch	Labor percentage climbing at one branch; COGS trending above target	Flag to owner; review payroll timing and job-cost categorization

Warning

Data visibility gap: the silent branch problem

Most multi-location operators have more data than visibility. Every branch generates CRM records, call logs, marketing clicks, and accounting entries, but they live in separate logins across disconnected platforms. The result is that a branch can underperform for two or three weeks before anyone with oversight even sees it. By then, the lost revenue is already in the rearview mirror. AI multi location reporting is only useful when the data flows in. If a branch's job statuses are not kept current in the CRM, or if call outcomes are not logged, the rollup will show a clean-looking board that does not reflect reality. Getting data hygiene right at each location is the prerequisite, not the afterthought.

Illustrative multi-location rollup board

A sample view showing how a datacube rollup board could surface company-wide KPIs alongside per-branch breakdowns on a headquarters TV display. Data and KPI selection vary by build.

Dashboard preview

Figures are illustrative. Your datacube board is built from your own connected data, branch structure, KPIs, and goals.

Info

Owner takeaway: standardize before you scale

The most common reason multi-location reporting fails is inconsistent definitions, not bad software. If Branch 1 tags a declined estimate as a 'lost opportunity' and Branch 2 leaves it as 'pending', the conversion rate comparison is meaningless. Before building the rollup, take the time to align on how every KPI is defined, counted, and categorized in your CRM and accounting system. That work pays off every time someone looks at the board.

AI multi location reporting FAQs

See all your locations in one board

Bring your current multi-location reporting setup and we will show you, on a live demo, how datacube would consolidate every branch's CRM, call, marketing, and QuickBooks data into a single real-time rollup, and flag the gaps that are currently invisible until month-end.

Schedule a live demo Take the self-guided demo

Keep exploring

AI reporting softwareMost home-service companies run on yesterday's numbers. AI reporting software for home services changes the timing: instead of pulling reports at month-end or waiting for a weekly ops call, a GM or owner sees booking rates, revenue pacing, and tech performance shift through the day, in one place, without touching a spreadsheet. Datacube builds that reporting layer custom for HVAC, plumbing, electrical, roofing, and other skilled-trades operations.

AI revenue forecastingMost contractors find out revenue is short when the month is already over. AI revenue forecasting changes that timing: it reads the jobs completed, the calls in the queue, the seasonal curve, and the current pace, then shows owners and GMs where the month is heading while there is still time to change it.

AI technician performance analyticsTwo HVAC technicians, same territory, same price book. One averages $4,200 per job. The other averages $2,100. Without AI technician performance analytics, the owner often has no idea the gap exists, let alone what is driving it. Datacube can surface those numbers in real time, by tech, by job type, and by day, so service managers coach on facts instead of gut.

Anomaly detection dashboardAn anomaly detection dashboard watches the numbers your operation produces every day, then flags the ones that moved outside their normal range before they become a month-end problem. For HVAC, plumbing, electrical, and other skilled-trades businesses, that usually means catching a callback spike, a booking-rate slide, or a margin dip while there is still time to act.

Go deeper