The 60-second version of the gap below, straight from ServiceTitan's own KPI-module docs.
ServiceTitan's custom dashboards can show up to six KPIs pulled from ServiceTitan data, in real time, if the shop is on the Works package. An EOS Scorecard needs five to fifteen weekly measurables, and on almost every contractor's scorecard, roughly half of them are financial numbers, cash, gross margin, A/R aging, that live in QuickBooks Online, not ServiceTitan. Neither system knows about the other's numbers or the specific measurables a leadership team picked. So contractors running EOS on ServiceTitan and QuickBooks end up doing the same thing every Monday: opening both systems, copying the right numbers by hand into a spreadsheet or an EOS tool, and rebuilding the whole thing again next week. That manual step, not the EOS framework and not either piece of software, is the actual gap.
If you run your leadership team's Level 10 Meeting off a scorecard someone rebuilds from scratch every Monday morning, you already know the pattern. The numbers are usually right. Getting them onto one page, from two different systems that were never built to talk to each other, is the part that eats the hour before the meeting even starts.
This is not a knock on ServiceTitan's dashboards or on QuickBooks Online, both do exactly what they were built to do. It is a specific, checkable gap in what happens between them.
Can ServiceTitan build my EOS Scorecard for me?
Partially, and it is worth knowing exactly where the line sits. According to ServiceTitan's own documentation on KPI modules, custom dashboards support modules that display up to six key performance indicators from a report template, updating in real time, and the feature is available on the ServiceTitan Works package. That is genuinely useful for tracking revenue, bookings, and conversion inside ServiceTitan.
What it does not do, by ServiceTitan's own description of the feature, is reach into QuickBooks Online. Cash position, gross margin after cost of goods sold, and accounts receivable aging, the numbers that live in your general ledger rather than your dispatch board, are simply not part of what a ServiceTitan KPI module can show. On a typical EOS Scorecard, those financial measurables are usually close to half the list.
What exactly is an EOS Scorecard?
In the Entrepreneurial Operating System, a Scorecard is a one-page tool that tracks five to fifteen weekly, activity-based measurables so a leadership team can see a problem coming before it shows up in the month-end financials. Each measurable needs three things: a clear definition, a named owner, and a weekly goal. The team reviews the same Scorecard, in the same order, every week at its Level 10 Meeting, marks each number on track or off track, and sends anything off track to the Issues List to work through using Identify, Discuss, Solve.
The whole design leans on the numbers being leading indicators, not a lagging report. A Scorecard that only shows what happened last month has already missed its window to matter.
Why do most EOS Scorecards need data from both ServiceTitan and QuickBooks?
Because a good Scorecard is built to mix two kinds of numbers on purpose. Leading, operational measurables, jobs completed, calls booked, technician utilization, live inside ServiceTitan. Lagging, financial measurables, cash on hand, gross margin percent, accounts receivable over 60 days, live inside QuickBooks Online. A Scorecard built from only one system tells the leadership team half the story: strong booking numbers can sit right next to a cash position that is quietly getting worse, and a ServiceTitan-only dashboard has no way to show that in the same view.
That split is exactly why the six-KPI ceiling on ServiceTitan's own dashboard was never going to be the whole answer. It is not that ServiceTitan's dashboard is missing a feature. It is that the EOS Scorecard was designed to pull from more places than any one operations platform tracks.
Why do ServiceTitan and QuickBooks contractors still build their scorecard by hand every Monday?
The mechanism is the same in almost every shop. Sunday night or Monday morning, someone, usually the office manager, opens ServiceTitan and pulls the operational numbers. Then they open QuickBooks Online and pull the financial ones. Then they type all of it into a spreadsheet, or into an EOS tool like Ninety or Bloom Growth, in the specific order and format the leadership team is used to reviewing. Then the Level 10 Meeting starts, and next Monday the whole thing happens again.
Neither ServiceTitan nor QuickBooks Online has any concept of "our leadership team's five to fifteen measurables." Both systems report on their own data, well, and neither one was built to know what the other one is tracking. The EOS format itself, the specific weekly measurables a team picked in a planning session, exists only in the team's head and in whatever spreadsheet or tool they type it into by hand.
What does a typical contractor's weekly scorecard actually contain?
All figures below are illustrative, built to show a realistic split, not a specific client's numbers.
| Jobs completed this week | 142 |
| Revenue booked this week | $187,400 |
| Average ticket | $1,319 |
| Technician utilization | 71% |
| Membership renewals sold | 18 |
| Cash on hand | $94,200 |
| A/R over 60 days | $41,600 |
| Gross margin % | 38.5% |
| Overhead run rate (MTD) | $61,300 |
| Payroll as % of revenue | 29% |
How would an automated ServiceTitan and QuickBooks scorecard actually work?
The starting point is always the leadership team's own measurables, the ones already agreed on in a planning session, never a generic template swapped in for them.
Does this replace the Level 10 Meeting or the leadership team's judgment?
No. The Scorecard is an input to the meeting, never a replacement for the people in the room. The leadership team still marks each measurable on track or off track, still decides what counts as off track for their business, and still runs Identify, Discuss, Solve on anything that needs it. Automating the pull removes the hour of spreadsheet assembly that happens before the meeting. It does not touch a single decision made inside it.
Comparison: manual scorecard vs. ServiceTitan dashboard vs. an automated ServiceTitan + QuickBooks pull
| Capability | Manual (spreadsheet / Ninety / Bloom Growth) | ServiceTitan KPI modules | Automated ServiceTitan + QuickBooks pull |
|---|---|---|---|
| Tracks the team's own 5-15 measurables | Yes, entered by hand | Limited to 6 ServiceTitan-only metrics | Yes, mapped to the team's actual list |
| Includes QuickBooks financial numbers | Yes, if someone keys them in | No — ServiceTitan data only | Yes, read directly from QBO |
| Weekly rebuild required | Every week, by hand | — | No — same pull runs every week |
| Ready before the Level 10 Meeting | Only if someone finds the time | Real-time, ServiceTitan data only | Delivered on schedule every week |
| Replaces the leadership team's judgment | No | No | No — proposes numbers only, team decides |
The short version: ServiceTitan's dashboard is a real, useful tool for ServiceTitan data, and EOS tools like Ninety and Bloom Growth are genuinely good at tracking Rocks and Issues once the numbers are in them. Neither one bridges the two systems. That is the specific gap a weekly automated pull closes, without asking the leadership team to change how they run the meeting.
What if my shop does not formally run EOS?
The same gap shows up under a different name. Any leadership team that reviews the same weekly numbers, whether they call it a scorecard, a KPI dashboard, or just "the Monday numbers," runs into the identical problem: the operational half lives in ServiceTitan, the financial half lives in QuickBooks, and nothing pulls both into one view without someone doing it by hand every week.
What will this never do without your approval?
- No changes to your general ledger. Building a scorecard is read-only. It never posts a journal entry, edits an invoice, or changes a QuickBooks balance.
- No invented numbers. Every figure traces to a specific ServiceTitan report or QuickBooks Online query. Nothing is AI-estimated.
- No replacing the leadership team. The team still marks on track or off track, still runs Identify, Discuss, Solve, and still makes every call.
- No generic template. The measurables mapped are the ones your leadership team already picked, not a one-size-fits-all dashboard.
How does this fit into a Top Builder AI install?
Mapping and building the weekly ServiceTitan and QuickBooks scorecard pull is part of the reporting work done during a Top Builder AI Teardown and 90-Day Install, alongside reconciling the two systems and setting up the collections and job-costing views covered in the ServiceTitan-QuickBooks job costing piece. It is scoped around the specific measurables your leadership team already picked in your last planning session, not sold as a generic dashboard nobody asked for.
Stop rebuilding the scorecard every Monday
If your office manager is still copying numbers from ServiceTitan and QuickBooks into a spreadsheet every week, that is exactly the gap a mapped, automated pull closes. Book a 30-minute fit call and bring your actual measurables list.
Book a fit call →