A family-owned commercial contractor had invested in sophisticated job costing, but leads, estimates and follow-ups still lived in a patchwork of tools, and an off-the-shelf CRM rollout by another vendor had failed. We mapped the full customer and job lifecycle, then designed and built a custom CRM around it, connected to the company’s job-costing system.
The company ran its customers and projects across an off-the-shelf CRM, a note-taking app, shared drives, email, spreadsheets and plenty of individual workarounds. Leads, field notes, estimates, proposals, follow-ups, scheduling and financial information all lived in different places.
Then the company adopted a sophisticated job-costing platform. It could now price and evaluate jobs in far more detail, but it had no reliable, connected way to move opportunities through the pipeline or act on what the numbers showed. An earlier CRM rollout by an outside vendor hadn’t helped; it left the team with more friction and less visibility.
Owners and managers spent their time chasing updates across people and platforms. Employees re-entered the same data, kept parallel notes and relied on personal knowledge to keep jobs moving. After one failed implementation, the team was understandably skeptical of another.
It looked like a CRM replacement problem, made urgent by the failed rollout. It wasn’t simply a weak CRM.
The business had outgrown a set of tools that had grown up around individual roles rather than one shared customer and job lifecycle. No single workflow or shared data model connected them. The new job-costing system brought real discipline to estimating, but the work feeding it (lead management) and the work flowing out of it (handoffs to production, finance and reporting) weren’t organized to support it. The earlier implementation had focused on software without matching how the company actually operates or what its people needed to adopt it.
From the inside, each tool solved a local problem, and experienced team members quietly bridged the gaps, so the cost of disconnected information was easy to miss. Rigorous job costing, and the failed rollout, finally made those hidden dependencies visible.
With the owners, executive leadership, estimators, sales, field and operations leaders and finance, we agreed on the company’s Optimal Horizon: one usable customer and job lifecycle connecting
Owners should be able to see pipeline value, conversion, margin, outstanding actions and exceptions without assembling reports by hand. And the software had to fit the way the company works, with adoption and accountability designed in from the start.
The team now works from one connected process for leads and follow-up instead of piecing updates together from several tools and informal notes. Administrative friction has dropped, and owners have a clearer basis for judging the sales pipeline, handoffs and job profitability.
The work is ongoing. The next horizon goes beyond the CRM to AI-assisted management reporting that will surface stalled opportunities, unanswered inquiries, outstanding tasks, financial exceptions and the decisions that need an owner’s attention, so leadership knows not only what happened but what to do next.
Better job costing didn’t create clarity on its own; it exposed the systems around it. The answer was software built around the real work, not the other way around.
Next story
All client storiesNonprofit
A small nonprofit needed to leave a badly outdated donor database, but its tiny development team had no time or technical capacity to run a migration. Change Up served as the implementation team: cleaning the data, setting up the new system around how the team really works, writing new protocols and guiding staff through the switch.
Tell us what you’re seeing. We’ll help you find where it starts and what your next horizon could be.