Three Peaks Digital Solutions · What We Do
The reports you need
are hiding in the data
you already have.
Your operational systems capture everything — jobs, customers, costs, crews. The problem is that each system records it differently. We build the translation layer that makes your data usable, period by period, for good.
Your tools are doing their job. The data they produce isn't doing yours.
Small and mid-sized businesses generate rich operational data every day. The challenge is that it lives across multiple systems — scheduling, accounting, payroll, CRM — each with its own naming conventions and its own version of your customers, employees, and services.
- The same customer appears under different names across systems — so lifetime value and retention analysis are guesswork
- Service or job types are entered freeform by multiple people — so revenue by category never quite adds up
- Employee names in scheduling don't match payroll — so labor cost by job type requires manual reconciliation
- Geographic or territory data is inconsistent — so location-based performance starts with cleanup, not answers
- Lead source fields are free-text and never normalized — so marketing ROI is essentially unknowable
A governed normalization pipeline that gets smarter every period.
Export and inventory
Pull raw data exports and identify every field with normalization risk — names, categories, locations, identifiers.
Build the canonical map
Every value with an unambiguous correct form is mapped once and applied automatically every period. Settled decisions don't resurface.
Govern the exceptions
Anything requiring judgment goes through a structured review interface. Decisions are recorded and reused — the exception surface shrinks each period.
Deliver clean output
Normalized data in whatever format your team can use, alongside the reports that answer the questions you've been asking.
Working infrastructure and the reports that prove it.
An engagement ends with a governed pipeline running on your actual data and reports built from clean output — not recommendations about what to do someday.
- Canonical mapping tablesEvery customer, employee, category, and location mapped to a governed canonical form — documented, versioned, and yours.
- Revenue by categoryReliable period-over-period breakdown by whatever grouping matters — service line, job type, property, territory.
- Labor cost attributionWho worked on what, at what cost — the cross-system join, normalized and working.
- Customer retention analysisWhich customers came back, by category and period — requires normalized records across your full history, which we build.
- Geographic analysisPerformance by location based on normalized address or territory mapping — not manual sorting.
- Repeatable pipelineRuns each new period. Exception surface shrinks as the canonical map matures. Review burden decreases — it doesn't reset.
Who this is for
Small and mid-sized businesses running two or more operational systems with multiple categories, employees, locations, or customer segments. If "what did we make from X last quarter?" requires a manual pull from multiple places, you have the problem we solve.
John GardinerFounder
I've been solving the same data problem since 1996, in different forms and for different organizations. Oracle ERP implementation and data migration for the OSCE, across offices in Sarajevo, Vienna, and Pristina. The systems differed. The problems did not. Inconsistent data makes every report downstream unreliable.
From 2011 to 2024 I worked at Wells Fargo, as VP and Senior Digital Product Manager for Digital Payments. Thirteen years of shipping operational systems that had to be up every day, coordinating between business teams and technology teams that didn't always share priorities. Performance and reliability were standing requirements. That discipline travels.
In 2024 I left to build something of my own. The problem I chose was one I'd watched go unsolved for a long time in smaller operations. Every field service business runs at least three systems — something for scheduling and jobs, something for accounting, something for payroll. Each one does its job. None of them agree on what to call a service, a customer, or an employee, and none of them produce a report that pulls from all three. So every useful report gets built by hand, period by period, in a spreadsheet.
Most operators have accepted this as the cost of doing business. It doesn't have to be.
Three Peaks runs on the same discipline it sells: documented processes, auditable decisions, AI-assisted work held to a consistent standard.
We're based in Sisters, Oregon. Current focus is field service operations: contractors, cleaning companies, property managers, and similar businesses where the reporting that matters most has to be built from scratch every period. If that describes your business, reach out.