How Relay Found $100K a Month in Missed Billing

Relay's FP&A lead stitched Sage and ServiceTrade exports by hand. An AI analyst now drills across both, finding $100K a month in missed billing and turning 3-hour reports into minutes.
$100K
Monthly billing leak, stopped
< 4 weeks
Implementation Time
Not disclosed
Project Cost

the challenge

Relay Fire & Life Safety, a fire protection and life safety services company, ran finance on Sage and field operations on ServiceTrade, and the two had never been joined. Large queries meant repeated exports and manual stitching, reconciliation was monthly, and reports took three hours or more to compile. One market was posting falling revenue while job volume climbed, and nobody could explain the contradiction from existing reports. The team was quoting Snowflake and Databricks to fix the reporting gap, and every acquisition added source systems that had to be migrated on deadline.

what they built

Synopsis connected Sage and ServiceTrade into a single, continuously updated view covering branch-level gross margin, revenue tracking, technician utilization, scheduling and deficiency tracking. An AI interface on top answers questions, drills to root causes across both systems, drafts reports and operating review decks, and runs proactive workflows that notify the relevant team members when multi-step conditions signal a risk or opportunity. The same foundation ingested and cleaned data from acquired companies' source systems for Relay's M&A platform migration.
Relay was weighing a Snowflake or Databricks build when it chose Synopsis instead, starting with the join nobody had made: Sage financials and ServiceTrade job data in one view. CEO Kevin Gray came in skeptical, having watched similar projects stall, so the first test was a live question. One market showed revenue falling while job volume rose. The team pointed the platform at it and kept drilling until it found the cause: an employee responsible for final invoicing had been rounding labor hours down before billing customers, a leak of roughly $100K a month. From there adoption spread. The Head of FP&A moved reporting onto the platform, where first drafts land about 80% complete and monthly operating review decks take minutes. CRO Kyle Bailey moved the revenue function over, replacing Salesforce dashboards, Power BI and manual Excel, and set up alerts that trigger on multi-step business conditions. During an acquisition-driven platform migration, the team used Synopsis to ingest, unify and export clean datasets from legacy source systems in about a week.

best fit for

PE-backed, multi-branch field-service businesses running separate accounting and operations systems, especially those making frequent add-on acquisitions or weighing a data warehouse build.
Ai ROLE

impact

8 days to the first useful answer

Versus a quoted 16–20 weeks and $300K–$500K for a data warehouse build

$100K a month in missed billing found and stopped

Labor hours rounded down before invoicing, found within weeks of go-live

3+ hour reports cut to minutes

Operating review decks compiled in minutes; FP&A estimates 10 hours back per 3 invested

implementation complexity

Medium, editorial call: two core systems (Sage, ServiceTrade) joined on a vendor platform rather than a custom warehouse build, but the rollout spanned finance, revenue, ops and an M&A data migration, so more than a light configuration.

Kris Krisco

Co-Founder
Synopsis
Co-Founder & CEO of Synopsis, building AI-ready data infrastructure for PE-backed mid-market companies to unify systems, enable trusted insights, and power autonomous execution.
Get an intro
Talk to this team
industry
Construction & Engineering
business organization
Finance & Accounting
Sales & Revenue
Operations
AI TYpe
Data Synthesis & Reporting
Decision Support & Scoring
Process Automation (RPA + AI)
value type
Revenue Growth
Time Savings
Cost Reduction

frequently asked questions

How did a fire and life safety company find $100K a month in missed billing with AI?

Relay Fire & Life Safety joined its Sage accounting data and ServiceTrade field-service data in one AI-queryable view, then drilled into a market where revenue was falling while job volume rose. The root cause was labor hours being rounded down before customers were billed, a leak of roughly $100K a month, found within weeks of going live.

What AI tools and approach did Relay use?

A unified data layer over Sage and ServiceTrade with an AI interface for questions, cross-system root-cause analysis, report and deck drafting, and proactive alerts on multi-step business conditions. Relay chose this over building a Snowflake or Databricks data lake.

What results did Relay achieve?

About $100K a month in missed billing found and stopped, reports that took three hours or more now produced in minutes, and source systems for an M&A migration ingested and unified in about a week. The Head of FP&A estimates ten hours back for every three hours put in, and Relay spent nothing on data lake infrastructure or data engineering hires.

How long did it take Relay to see results?

The first useful answer came eight days after kickoff, the billing finding came within weeks of going live, and the M&A data ingest took about a week. The data warehouse alternative had been quoted at 16 to 20 weeks.

Who is this AI data platform approach best for?

PE-backed, multi-branch field-service businesses running separate accounting and operations systems, especially those making frequent add-on acquisitions or weighing a data warehouse build.

Have a similar challenge?

Ask whether this would work for you, or describe what you're trying to solve.
TELL US WHAT YOU'RE EXPLORING