Please describe your company, your role, and the industry you operate in.
Summit Line Logistics is a Insurance business headquartered in Salt Lake City, USA. As VP of Operations Technology I'm responsible for the whole technology agenda — infrastructure, product, and how we pick vendors. Every decision we make on the technology side has to tie back to a clear business case before it gets approved.
What specific problem or business challenge led you to hire this company?
Our DevOps Services 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 DevOps Services 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?
Really well, partly because they already had Insurance experience that cut down on the amount of context we had to provide. They knew the terminology, asked the right questions, and translated our business requirements into technical specs accurately enough that development barely needed any clarification cycles.
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?
The ROI model we took to the board was deliberately conservative. Current performance against that model puts us on track to hit payback well ahead of the eighteen-month target we set. The operational efficiency gains in particular have outpaced the model, partly because the new platform's data quality supports decisions the old system simply couldn't.
What did you like most about working with this company?
Their willingness to just be direct. If our requirements were unclear, they said so. If our priorities contradicted each other, they explained why. If an approach we'd assumed was right actually had real downsides, they told us before we'd committed to it. That kind of honesty is exactly what I look for in a long-term partner.
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.