Why Your Field Software Isn't Fixing Your Cash Flow

The Pitch That's Half True

Every field service software sales pitch promises the same outcome: "You'll collect faster. You'll know your margins. You'll have financial visibility."

Most of it is true. The parts that aren't true are where contractors lose money.

I spent four years as Director of Growth Product at BuildOps. Before that I was a PE analyst doing diligence on contractor acquisitions. Now at Level I review contractor P&Ls for a living. I've seen the full arc — what field software sells, what it actually delivers, and what falls through the cracks.

This isn't a post about BuildOps or ServiceTitan being bad. They're both excellent products. They're the best thing that's happened to contractor operations in 20 years. But they were built to run the field, not the financial layer on top of the field. And that distinction is where every contractor running a six- or seven-figure FSM subscription still has cash stuck.

Here's what I mean — with real numbers from contractors running on the leading platforms.

---

What Field Software Actually Does

Before we get into the gap, let's be precise about what FSMs are built to do. When they work well, they:

• Route technicians efficiently and cut drive time
• Replace paper tickets with digital work orders
• Capture time, parts, and photos at the job
• Trigger an invoice the moment a job closes
• Store customer history in one place
• Enable techs to quote and collect in the field

That's the operational job. And to be clear: that alone is usually worth the $150K–$500K/year in FSM subscription a $20M–$50M contractor pays. The payback is real.

The pitch starts to break down when the operational data has to become financial intelligence.

---

The $110M Contractor Who Was Flying Blind on BuildOps

I'll make this concrete with one real engagement — anonymized, but the numbers are exact.

A commercial mechanical contractor running roughly $110M in annual job revenue. Fully deployed on a leading field service platform for three years. Clean dispatch, strong utilization, solid reviews from the ops team. By every FSM-health metric, a reference customer.

Here's what we found in the first 30 days of the engagement:

This is a contractor who — on paper — has a best-in-class tech stack. In reality, the field platform is doing its job. The financial layer on top of it doesn't exist.

And they're not alone. Across the 2,242-contractor Level benchmarking dataset, the pattern repeats: FSM adoption is up. Financial intelligence gaps are unchanged.

---

The Eight Specific Gaps Between Your FSM and Your P&L

Here's where the breakdown consistently happens. Every gap below is a real pattern across contractors on BuildOps, ServiceTitan, Housecall Pro, FieldEdge, and the rest.

Gap 1: "Invoice Ready" ≠ "Invoice Sent"

FSMs flag a job as "complete" when the tech hits done. They flag it as "ready to invoice" once the quote/PO/materials reconcile. That's not the same thing as the invoice actually being in the customer's inbox.

Across the Level dataset, the median contractor invoices in 1 day (including the ~25% that progress-bill on install work). But among post-completion invoicers only, the adjusted median is 7 days, and the bottom 10% sit for 30+ days. The FSM will happily hold a $12K work order in "ready to invoice" for three weeks if nobody's watching.

Dollar impact on a $10M service contractor: at 7-day average billing lag vs. 1-day, that's roughly $190K of cash permanently in float. (Billing speed benchmarks →)

Gap 2: Job Costing Exists, But Isn't Attached

Every FSM has job costing as a feature. Almost nobody uses it correctly. Across the dataset, roughly half of contractors have labor hours linked to jobs. Far fewer have materials, subcontractor costs, and overhead allocations all flowing into a per-job margin.

The result: a dashboard that shows "average gross margin 48%" when the reality — if you actually assign costs — is 28%. This is the phantom margin problem. It's not the FSM's fault. The FSM can't force you to tag materials to the right job. But it also isn't raising its hand telling you 87% of your jobs have no cost data.

Gap 3: Collection Rate Is Tracked After the Fact, Not Driven

FSMs show you AR aging. They don't drive collections. There's no workflow that says "this invoice is 14 days old, the customer pays on average in 22 days, escalate now." The median collection rate across the dataset is 80.8%. The achievable number is 96%. The gap for a $10M contractor: $1.6M in permanently lost or delayed cash per year.

Closing that gap isn't an FSM feature. It's a financial operations workflow that sits on top of the FSM.

Gap 4: Margins Are Visible Per Job, Not Per Segment

You can pull up one job and see its margin. But can you answer: "What's my gross margin on residential refrigeration service jobs under $2K, this quarter, vs. last quarter?" Almost no FSM can do that natively without custom reporting — and custom reporting is a $100K+ engagement with the implementation team.

That segment-level visibility is where pricing decisions live. Without it, you raise prices across the board or you don't raise them at all. Both are wrong.

Gap 5: Service Agreements Track Visits, Not Economics

Your FSM knows how many SA visits happened this month. It doesn't know whether those SAs are profitable. Median SA gross margin across Level's dataset is 37.9%. One contractor I reviewed was running at -23.2% SA margin — losing $3.8M per year on the book — and their FSM dashboard showed "SA visits completed on time: 94%." Operationally excellent. Financially devastating.

That's not a product bug. It's a category bug. FSMs were built to run operations. SA profitability is a financial question.

Gap 6: Quotes Sit With No Follow-Up Triggers

The data here is brutal: median quote conversion across 794 contractors in the dataset is 73.9% — but only for quotes that get decided. The ones that never get decided — that go quiet for 14+ days and never get followed up — are the entire problem. At one $30M contractor, $2.3M in expired quotes went un-followed-up in a single year. FSM captures the quote. Nothing inside the FSM says "this $47K quote is 9 days old, call them today."

Gap 7: Budget vs. Actual Is a Feature Nobody Turned On

Bottom 10% of contractors go 22%+ over budget. Worst cases I've seen are 179–552% over. Most FSMs support budgets at the job level. Across the dataset, roughly a quarter of contractors don't track budgets at all, and among the ones who do, fewer than half actively compare budget to actual in a way that drives in-flight decisions.

The FSM allows budgets. It doesn't prosecute them. Without that prosecution loop, you find out you lost $40K on a job three weeks after it closed.

Gap 8: Nothing Pushes the Numbers to Ownership

The CEO gets a monthly P&L from the accountant. They might look at a weekly dispatch board from the FSM. Between those two views, nothing is connecting operational events to financial outcomes in anything close to real time.

The 7 numbers every $5M contractor should check weekly live in neither the P&L nor the FSM. They live in the seam. And the seam is where money hides.

---

Why the Gap Exists (And Why It Won't Close)

FSM platforms are optimizing for the next feature that wins the next deal: better dispatch, better mobile experience, better customer communication. Those are the right bets. The companies paying for an FSM subscription want their tech ops to get better; they don't want financial workflow tooling inside their dispatch platform.

The same is true of QuickBooks and Sage. They're general-ledger systems. They're built to record transactions, not to drive decisions. Ask your accountant to run "service agreement margin by customer tier, trailing 90 days" and you'll get a quote for $8K of custom work.

The financial layer sits in between. It pulls dispatch and job data from the FSM, actuals from the accounting system, and turns it into the answers that change how the business is run. That's a different product category. It's not going to be built inside BuildOps, and it's not going to be built inside QuickBooks.

---

What the ROI Actually Looks Like

When contractors tell me they're skeptical about a financial layer — "we already spend $250K/year on BuildOps, isn't that enough?" — I walk them through the same math.

For a $20M commercial contractor, the achievable impact is roughly:

Aggregate ROI is typically 10–15% on EBITDA in year one, flat on the FSM stack you already have. No rip-and-replace. No retraining. No six-month implementation.

That's not because the FSM is underperforming. It's because the FSM was never going to do this. When does a contractor need a CFO vs. a bookkeeper — and the practical answer for a $10M+ contractor is: when you realize the FSM isn't going to close these gaps on its own.

---

The Honest Framing

The FSM vendors aren't your enemy. They're doing what good software does: running operations. The financial intelligence layer — reading from the FSM, writing nothing back, pointing out the gaps before they compound — is a different product category that most contractors haven't realized they need yet.

If you're on BuildOps or ServiceTitan and you feel like the P&L still doesn't tell you what you need to know, you're not doing it wrong. You're experiencing the gap between operational software and financial software. The gap is closeable — but not from inside the FSM.

---

The Bottom Line

Field software is doing its job. The gap between what it captures and what your P&L should tell you is where cash hides. On average, a $20M contractor is leaving 10–15% of EBITDA on the table inside that seam — not because the FSM is failing, but because nobody's running the financial layer on top of it.

You don't need to rip out BuildOps or migrate off ServiceTitan. You need a layer that reads from them and surfaces the numbers that nobody's watching.

---

Q: So are you saying BuildOps/ServiceTitan are bad? A: No. They're best-in-class for what they're built for — running field operations. I worked at BuildOps for four years. What I'm saying is that financial intelligence is a different job. The FSM tells you "jobs completed today." It doesn't tell you "this segment of jobs is unprofitable, three of your SAs are losing money, and your top customer hasn't paid in 47 days." Those questions live in the financial layer on top.

Q: Can't my controller or bookkeeper do this? A: They can, partially. The constraint is time and data engineering. Pulling structured margin data out of an FSM, reconciling it with QuickBooks actuals, and surfacing the 8–10 things that matter this week is a full-time job — and it's not what a bookkeeper is trained for. Most $5–30M contractors can't justify a $150K+ FP&A hire. That's the gap an AI-native CFO layer is built to fill. See when contractors need a CFO vs. a bookkeeper.

Q: What would a financial layer actually look like on top of my FSM? A: It reads job, SA, quote, and invoice data from the FSM via API. It reads P&L and AR from QuickBooks/Sage. It runs the calculations nobody else does — margin by segment, collection probability by invoice age, expired quotes by dollar value, SA profitability by tier — and it pushes the 7–10 things ownership needs to see this week into an inbox or dashboard. No new system of record. No data migration. At Level we build this for contractors on a monthly retainer; the first audit is free and usually surfaces six-figure recovery in the first 30 days.

Q: How do you actually measure the ROI of that layer? A: Three metrics. (1) Days sales outstanding — did it come down? (2) Unbilled work at month-end — did it shrink? (3) Gross margin variance between what the FSM says and what the true P&L shows — did it tighten? A good financial layer moves all three within 60 days. If it doesn't, it's not worth the monthly fee.

Q: Where can I see the underlying benchmarks? A: The full Level Index is public at /benchmarks/contractor — collection rates, SA margins, billing speed, quote conversion, and pull-through, all with quartile breakouts. For the public-company comparison side (EBITDA multiples, DSO, FCF margins at the big listed contractors), see the Market Monitor.