I talk to many business owners about their current systems. The impression I get from most of them is that they work, but they don't particularly add any competitive advantage. They do what they're supposed to, but nothing more. At some point, the systems almost get in the way more than they help. At that point, you need to seriously consider an upgrade.
Case Study
Selecting a New Workflow and Project Tracking System for a Small Risk Management Company
Case Study: From Patchwork Processes to a Unified Operations Platform
The Situation
A growing risk management firm found itself in a position that’s surprisingly common among successful small businesses. They had built a set of systems that worked until growth exposed their limits.
At the center of their operations was a field inspector system. It was originally designed for a very specific purpose: storing inspection data in the field. But over time, the company had stretched it into something much more. By layering in custom fields and adapting workflows, they turned it into their primary operational system. It became the place where work was tracked, decisions were made, and data was stored, even though it was never designed to serve that role.
Around this core system, other tools began to accumulate. They interacted regularly with bank lender platforms to receive and fulfill project requests. Internally, they relied on Monday.com to organize work, Microsoft Teams to communicate, and SMS messages to fill in the gaps when processes broke down. None of these tools was inherently wrong, but together, they created a fragmented environment where no single system governed their operations.
As the business grew, the issues became harder to ignore. Data was duplicated across systems, and sometimes lost altogether. Teams developed manual workarounds to keep projects moving. Important steps in the workflow lived in text messages or in someone’s memory rather than in a system. Even onboarding new employees became a challenge, because there was no clear or intuitive way to understand how work actually flowed through the organization.
What the company was experiencing wasn’t a tooling problem, it was an architecture problem. Their systems had evolved organically, but their operations had never been intentionally designed.
Discovery and Engagement
When I engaged with the team, we didn’t begin by looking at new platforms or vendors. Instead, we started with discovery. I spoke with stakeholders across the business to understand what systems they actually used day to day, where they experienced friction, and what capabilities they wished they had. These conversations revealed that the real workflow of the business didn’t exist inside any single system. It existed in the spaces between them.
From there, I moved into a structured analysis. We built a complete inventory of systems and data, identifying not just what tools were in place, but what information lived in each one. Then we developed a high-level business process diagram that mapped how work actually flowed—from incoming lender requests, through internal coordination, to final delivery. This diagram made something visible that had previously known but not well documented: the exact points where manual processes were compensating for gaps in the system.
With that foundation in place, I facilitated a requirements session with the leadership team. I brought forward the needs identified during discovery and asked the group to refine, expand, and prioritize them. This step was critical. It transformed a collection of individual observations into a shared, ranked set of business requirements.
At that point, we had a blueprint of both the current and desired future states.
Request for Proposal
Using that blueprint, I developed a detailed RFP that described the company, its workflows, and the capabilities it needed in a new system. We sent this to a mix of vendors the company had previously encountered and new options we identified together. Once responses came in, we evaluated them systematically, comparing each against the defined requirements rather than relying on demos or surface impressions. Finalists were invited to present, and the selection process became a disciplined evaluation.
After choosing the right partner, I supported contract negotiations to ensure pricing, scope, and support were aligned with the company’s long-term needs. From there, I worked alongside the vendor’s project manager to build a practical implementation plan, one that accounted not just for the technical rollout, but for change management and post-launch support. The goal was not simply to deploy a new system, but to ensure the organization could successfully adopt it.
The Results
The result was a fundamental shift in how the company operated. Instead of relying on a repurposed field tool and a collection of side systems, they now had a purpose-built platform that integrated well with external systems and intelligently adjusted workflows based on the type of project request. Data that had once been scattered now lived in a single, reliable system of record. Leadership gained visibility through a centralized dashboard that tracked revenue, expenses, and the full project lifecycle, from initial request through completion.
Equally important, the team's day-to-day experience improved. Manual workarounds were reduced. Communication became more structured. New employees could be onboarded more quickly because the system reflected how the business actually worked, rather than requiring them to piece it together themselves.
In the end, the company didn’t just implement a new system. They moved from a reactive, patchwork approach to a deliberate, scalable model. That shift allowed their technology to stop being a constraint and to start accelerating growth.