Please describe your company, your role, and the industry you operate in.
Summit Line Logistics has been operating in Construction for a while now, headquartered in Salt Lake City, USA. As VP of Operations Technology 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?
Regulation in our Construction segment shifted and the compliance deadline came from the regulator, not from us. The scale of the DevOps Services changes required justified bringing in a specialist rather than pulling our internal team off the product roadmap to handle it.
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?
The questions they asked during the briefing stage told us most of what we needed to know. Vendors who ask sharp questions during sales tend to bring that same rigor into delivery, and that held up. The technical proposal had real substance, the team was senior from the start, and the pricing was straightforward.
How clearly did the company understand your requirements and business goals?
Really well, partly because they already had Construction 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?
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?
Yes to both. I'd quietly built in some contingency given the complexity and the number of integrations involved, and none of it ended up being needed. Delivery landed on the agreed date and the final invoice was within a rounding error of the approved budget — rarer than most people in this industry would admit.
What tangible results or business impact have you seen since the project was completed?
The clearest measure is how the system's actually performing in production. In the four months since go-live we've had zero major incidents, our page performance scores improved across every Core Web Vitals metric, and two enterprise clients who'd previously flagged our old platform's limits during renewal talks signed again without raising it.
What did you like most about working with this company?
What they did after launch. A lot of vendors treat go-live as the finish line. This team treated it as the start of a different phase — the hypercare period was substantial, the documentation held up in practice, and they checked back in at the thirty and ninety day marks to go over production metrics with us unprompted.
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.