A construction manager at a commercial pool builder got on a call with us last week, and the story he told will sound familiar to anyone running a project-based business. He'd been in the role about two months, and the thing that kept tripping him up wasn't the work itself. It was that no two pieces of information about a job lived in the same place.
Dash Pivot for quoting and field reports. A separate tool for tracking. Excel for a few things. A shared calendar for scheduling. Expensify for expenses. And somewhere in the mix, an accounting system that might have been QuickBooks (nobody was totally sure). Every step meant someone re-keying the same data into the next tool by hand.
The real cost is what falls through the cracks
When your team manually moves information from one system to the next, things get lost. That's what happens when there's no single source of truth and the process depends on people remembering to copy things over.
Here's how he described it. If he wanted a quote, he'd call the person who handles quoting, and she'd be lost, because the request had to pass through three steps before she could even start. That's two or three days before a quote goes out the door. Meanwhile, the knowledge of where any given job stands lives entirely in people's heads.
Everything's tribal knowledge. Project management knows where everything project management has done is. Then you go to accounting, and it's a different world.
The most expensive version of this problem showed up in billing. Their jobs bill in milestones: a percentage when the customer accepts, more when the crew mobilizes, and additional amounts along the way. When those milestones are scattered across a spreadsheet and a calendar, they get missed until the job is finished. And once the pool is built, the customer has no urgency to pay. As he put it, accounting will tell you flat out that money is getting lost because milestones slip by unnoticed.
Why milestone billing punishes fragmented systems
Project-based companies live and die by cash flow between milestones. If your system doesn't automatically flag when a milestone is due to bill, you're relying on someone to catch it manually while juggling everything else. Miss the mobilization invoice, and you've financed part of the job for the customer for free.
Unbilled or late-billed milestones are one of the quietest ways a project business leaks margin. The money isn't stolen or discounted, it just never gets invoiced on time, and by the end of the job the leverage to collect is gone.
Pick one hub and branch out from there
His instinct on the call was smart. His day-to-day priority was field service, but he recognized that project management touches almost everything: design, the build, accounting, and after-sales support. So rather than fixing field service in isolation, he leaned toward making project management the central hub and connecting the other pieces to it over time.
That's usually the right way to sequence a consolidation. You don't try to replace six tools in one weekend. You identify the workflow that everything else depends on, get that onto a connected platform, and expand out module by module.
- Start with the workflow that the most departments depend on, not the one that annoys you most day to day.
- Get quoting, project status, and billing milestones into one place so a quote doesn't take three hand-offs and two days.
- Treat field service, expenses, and after-sales as connected extensions of the same system rather than separate islands.
- Plan the expansion in phases so each one delivers value before the next begins.
A word on the design tools
This company also runs a real design stack (AutoCAD, SOLIDWORKS, and the rest), and works with outside general contractors who need current drawings. When change happens on site, you don't want techs and contractors digging through archives to find the latest revision. Getting design changes visible and accessible in the same place people track the job is a big part of what makes the consolidation worth it, and it's the kind of detail worth mapping carefully before anyone commits to a platform.
If this sounds like your shop
If you're running a project-based business and your jobs live in five or six disconnected tools, you already know where the money and the deadlines slip. We're happy to talk through how a project-oriented Microsoft setup might fit your workflows, and just as happy to tell you where it wouldn't. Reach out whenever you want to think it through together.