Family Office & Affiliated Organization · MSP Assessment & Vendor Transition
A family office and its affiliated organization had signed a 36-month agreement with a Managed Service Provider — without ever asking what the organization actually needed. The MSP deployed the systems they knew how to support, not the systems that fit how this organization worked. The result was a technology environment that the vast majority of staff found incompatible with their daily operations.
By the time we were brought in, fewer than 10% of staff were using the platforms the MSP had put in place. Most had found workarounds. The organization had adapted to dysfunction so gradually that they had stopped expecting the relationship to improve. The monthly invoices — nearly $10,000 — arrived and were paid. Several core implementation items remained incomplete.
The MSP had implemented their standard stack. It was not compatible with the organization's actual workflows. Staff who tried to use it restructured their processes to accommodate the tools — most declined to and found other ways to work.
U.S.-based support had been a stated requirement during the sales process. The MSP's support function operated primarily offshore. This was never clearly communicated before contract execution.
Several components of the agreed scope had never been deployed. The organization was paying for a full managed services engagement and receiving a partial one.
This is not a change management problem. When fewer than 1 in 10 staff use a platform, the platform does not fit the organization. No amount of training resolves a product-market fit failure.
Before beginning the needs assessment, we conducted a line-by-line review of the MSP contract against the services actually being delivered and the organization's actual usage. Services fell into three categories: never fully implemented, implemented but unused due to the adoption failure, and low-value relative to the cost.
We negotiated each category directly with the MSP. By the time the review was complete, the monthly recurring bill had been reduced from nearly $10,000 to under $5,000 — without any change to the organization's technology posture, because the removed items were either not working or not being used.
We conducted a full needs assessment across both the family office and its affiliated organization — mapping actual workflows, data environments, security requirements, and support patterns. The assessment produced a clear picture of what any MSP relationship would need to deliver to actually serve this organization.
Key requirements: U.S.-based support as a non-negotiable. Technology aligned to actual workflows, not the reverse. Security governance appropriate to a family office environment. Transparent, structured pricing. A vendor capable of completing what they commit to.
Once the needs assessment was complete, we presented the findings to the existing MSP in a formal meeting — not to terminate unilaterally, but to examine whether the vendor was genuinely able to meet the organization's needs. The answer, to their credit, was no. When presented with the full picture, it became clear to everyone in the room that the organization had outgrown what this vendor could provide. Rather than contesting the findings, the MSP agreed to release the organization from the remaining 18 months of the contract — a savings of over $94,000 that had been considered a sunk cost.
We developed a formal RFP based on the needs assessment and distributed it to a carefully selected group of MSP candidates — firms whose size, capabilities, and client profiles indicated genuine fit. The RFP required explicit disclosure of support staffing location, references from comparable organizations, and detailed implementation methodology.
Proposals were evaluated against the needs assessment criteria. The lowest-cost proposal was not selected. The selected vendor demonstrated the strongest alignment between what the organization required and what they were genuinely capable of delivering — at a transparent price the organization could verify and understand.
18 months of the original agreement released by the MSP after the needs assessment presentation. A liability the organization had accepted as unavoidable — resolved through preparation and honest conversation.
Reduced from nearly $10,000 to under $4,000 with the new partner — a reduction of over 60% — while delivering materially better support quality, a completed implementation, and security governance the organization had never had.
Combining the contract exit savings, monthly reductions during the transition period, and the ongoing cost differential with the new partner.
The new MSP delivered a complete implementation against a documented scope — something the previous relationship had never achieved. U.S.-based support. Technology aligned to how people actually work. Adoption was no longer a metric anyone needed to manage.
A private consultation to assess your current vendor environment and identify what should change.