Please describe your company, your role, and the industry you operate in.
Meridian Cloud Partners has been operating in Agriculture for a while now, headquartered in Boston, USA. As VP of Engineering I sit across both strategic planning and day-to-day technology delivery. We hold our vendors to a high bar because our own clients hold us to one — it's only fair to expect the same discipline from partners.
What specific problem or business challenge led you to hire this company?
Our CMS 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 CMS 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?
We were coming off a failed engagement and went into vendor selection this time with a lot more scrutiny. We asked pointed questions about how they handle scope changes, how they estimate, how they communicate bad news. The answers were specific and consistent across everyone we spoke to on their team, which gave us confidence it wasn't a rehearsed pitch.
How clearly did the company understand your requirements and business goals?
Better than we understood them ourselves, honestly. The workshops they ran surfaced assumptions we'd never questioned and exposed a few requirements that flatly contradicted each other. Sorting that out before development started saved us from what would have been serious rework later.
How was your overall experience with their communication and project management?
Professional throughout. The project manager always had a clear view of the critical path and flagged changes to it honestly, without spin. The one significant scope change we made mid-project went through a clean process — fairly priced, clearly documented, and absorbed without knocking the rest of the timeline off course.
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?
Their instinct for never losing the business goal in the middle of technical decisions. I've worked with technically strong teams before who lose that thread once things get complicated. This team kept every architectural call tied back to the outcome we'd actually agreed to, which made the harder trade-off conversations a lot easier.
Would you recommend this company to others, and would you work with them again?
Yes, no hesitation. I've already referred them twice within my own Agriculture network, both times to people facing CMS Development problems similar to ours. I made those referrals confidently because I know the experience I had was repeatable, not a one-off stroke of luck on our project.