Client & Project Snapshot
| Industry | Commercial painting contractor, with a related construction business sharing the same IT footprint |
|---|---|
| Size | Roughly 35 staff across four locations in Ontario and Alberta |
| Engagement type | Managed IT, at $95 per user per month |
| Core constraint | A failing server needed replacing now, but a planned ERP change would move the core accounting system off-premise within a couple of years |
| ACT360’s role | Right-size the infrastructure decision, standardize IT across all locations, and add security monitoring that hadn’t existed before |
| Author | Adam Bowles, Partner & CEO, ACT360 |
The Situation
A failing server had become a daily productivity tax, and the quote to replace it was sized for the wrong decade.
The company runs commercial painting across Ontario and Alberta: a head office, a second office in Alberta, a remote crew, and a related construction business sharing the same IT footprint. Roughly 35 staff. Like most construction-sector businesses, it runs on Sage for accounting, job costing, and reporting. When Sage is slow, the office stops.
Sage could take up to 30 minutes to open. Not occasionally, as a routine cost of starting work. Reporting deadlines were run against a system nobody could rely on to respond.
Browsing the file share was punishing. Ordinary document work carried a delay on every action.
The drives were failing. This is the part that turns an annoyance into a risk. A failing array on the server holding accounting and job data is pending data loss, not slow performance.
Their existing IT provider had reached the right conclusion, the hardware needed replacing, and then sent a $60,000 quote by email. No conversation about what the business was planning, no discussion of alternatives, no question about where the workload would live in three years.
That quote is what sent the Controller looking for other options.
What We Did
We asked what was coming.
The answer reframed the whole decision. The company intends to replace its ERP, and that replacement will move Sage off-premise. The timing isn’t fixed, it depends on selecting the new system, but the direction is settled. Buying a full-specification on-premise server in that context means paying for five to seven years of capacity to use perhaps two.
So the requirement wasn’t “replace the server.” It was: restore performance, remove the risk of drive failure, and bridge to the ERP migration without over-committing capital.
What ACT360 delivered
Why it fit the actual requirement
A server sized and sourced to the bridging period, not a seven-year lifecycle, at $25,000 including hardware, installation, setup and migration
Restores performance and removes the drive-failure risk without paying for capacity the business won’t use once Sage moves off-premise
Managed IT across all four locations at a single standard
Replaces a fragmented arrangement across Ontario, Alberta, and the related construction entity with one point of accountability
A security stack that didn’t previously exist: endpoint detection and response, identity threat detection, managed firewall, and staff phishing reporting into a monitored queue
Closes an exposure the business didn’t know it had, found because monitoring went in as standard, not because anyone asked for it
Standardization work the previous arrangement had left undone: file storage consolidation, identity migration to Microsoft 365, network hardware replacement across sites, and monitored patching
Brings four sites and a related business onto one supportable environment
The security layer produced results almost immediately, and not the kind anyone hopes for. Within weeks of going live, identity monitoring flagged account access from Latvia, the Philippines, and the United States, along with one incident serious enough to isolate the affected account automatically. None of this had been visible before. The company hadn’t engaged ACT360 about security. They’d come about a server.
Results
Four months into the engagement. Where a figure isn’t available, we’ve said so rather than estimated.
Metric
Result
Capital avoided on the server decision
$60,000 quoted, $25,000 delivered, including installation and migration
Sage open time
Up to 30 minutes, now opens normally
File share performance
Restored to normal working speed
Failing drives
Replaced before data loss occurred
Credential-misuse detections
3 countries flagged, plus 1 automatically isolated critical incident, none previously visible
Sites on a single standard
4, across 2 provinces, including a related business
Managed IT cost
$95 per user per month
The ERP replacement, and the Sage cloud migration that follows it, hasn’t happened yet. It remains the plan, and the server was bought on that basis.
What This Engagement Shows
A correct diagnosis can still produce the wrong recommendation. The previous provider was right that the hardware was finished. They were wrong about what to replace it with, because they never asked what the business was going to be running on. Being technically right isn’t the same as being useful.
The size of a purchase is a business question, not a technical one. Nothing about the specification of a $60,000 server is wrong in the abstract. It was wrong for this company, at this moment, given this plan. That’s only knowable by asking.
Businesses rarely come to you about the thing that’s most dangerous. This engagement started as a hardware conversation. The exposure that mattered most, live credential misuse from three countries, was found because a monitoring layer went in as standard, not because anyone asked for it.
Fragmented IT across locations hides problems. Four sites, two provinces, and a related company under one standard isn’t an efficiency argument. It’s the difference between seeing what’s happening and not.
Adam’s Take
Right-sizing an infrastructure decision means matching the lifespan of what you buy to the lifespan of how you plan to work. A server is typically a five-to-seven-year commitment. If a business intends to move a core application to the cloud inside two years, a full-specification on-premise server isn’t a solution, it’s a stranded asset.
The question that determines the right answer isn’t “what does this server need to run today.” It’s “what is this business going to be running on in three years.” Tools don’t fail to answer that question. Providers do, when they’d rather send a quote than have a conversation.
Common Questions
Would this work for a smaller business?
Yes. The decision pattern applies at any size: match what you buy to how long you plan to work that way. It matters most for businesses between roughly 20 and 100 staff, where a single infrastructure purchase is large enough to hurt and there’s usually nobody internally whose job is to ask the lifecycle question.
