Please describe your company, your role, and the industry you operate in.
I run technology for Meridian Cloud Partners, a growth-stage Insurance company based in Boston, USA. My role as VP of Engineering covers product engineering, platform operations, and our vendor relationships. We'd hit a point where our internal capacity just couldn't keep pace with what the roadmap demanded.
What specific problem or business challenge led you to hire this company?
Our Software Development capability had become the thing slowing everything else down. New feature requests, client asks, internal initiatives — all of it kept queuing up behind a platform that had been stretched way past what it was originally built for. We needed a proper rebuild, not another patch.
What services did the company provide for your project?
The scope ran the full Software Development lifecycle — discovery, requirements, architecture, development across roughly a dozen sprints, integration testing, performance validation, deployment, and a four-week hypercare window afterward. They also handed over full documentation and ran a knowledge transfer session for our internal team.
Why did you choose this company over other providers you considered?
A peer in the Insurance space had used them for something similar in Software Development and recommended them without hesitation. Our own due diligence backed that up. Domain knowledge, Software Development depth, and a track record of actually delivering — that combination made the decision easy.
How clearly did the company understand your requirements and business goals?
Very well. The discovery phase was more thorough than anything we'd been through with prior vendors. They pushed back on requirements that were vague or contradictory, suggested better alternatives where our own thinking was limited, and produced a spec our internal stakeholders agreed was the clearest version of the product they'd ever seen written down.
How was your overall experience with their communication and project management?
Proactive and well-calibrated. Technical detail for the engineering side, plain summaries for the steering group, and risk flags that came with a proposed fix attached rather than just a problem statement. The biweekly sprint reviews kept our stakeholders in the loop without requiring them to sit in on every working session.
Did the company deliver the project on time and within your expected budget?
Both, yes. One sprint hit a one-week delay from a third-party API dependency outside anyone's control. The team flagged it three weeks ahead of time, laid out two options, and we picked an approach that clawed the schedule back within the same sprint. That's the kind of foresight that separates real project management from just reacting to problems.
What tangible results or business impact have you seen since the project was completed?
We went live about three months ago. User adoption beat the target we'd set by roughly 20 percent in the first month, and support ticket volume has dropped noticeably since. Features we'd shelved because the old architecture made them too expensive to build are now back on the roadmap.
What did you like most about working with this company?
The team stayed the same the whole way through. The engineers in the discovery sessions were the same ones who built the system. That continuity matters more than people expect, and you really only notice it when it's missing. Every conversation picked up where the last one left off.
Would you recommend this company to others, and would you work with them again?
Absolutely, with one caveat worth mentioning: the value really starts in discovery, so clients who take that phase seriously will get the most out of it. We put real effort in upfront and it clearly paid off in what got delivered.