Please describe your company, your role, and the industry you operate in.
As Chief Product Officer at Lumen Media Collective I oversee technology spend and delivery across our Manufacturing operations out of San Diego, USA. We're a commercially minded business, so every technology decision gets judged on what it actually contributes to the bottom line, not on how elegant it looks on paper.
What specific problem or business challenge led you to hire this company?
A competitor move forced our hand and compressed a roadmap item we'd planned for the following year. The Cloud Services investment we'd scheduled twelve months out suddenly needed to happen in six, and building it internally in that window wasn't realistic.
What services did the company provide for your project?
The core of it was Cloud Services, though their involvement grew to include technical consulting during discovery that meaningfully sharpened our own requirements. They also took full ownership of the third-party integration work, which had been a coordination headache on past projects, and just handled it themselves.
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?
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?
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 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 Manufacturing network, both times to people facing Cloud Services 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.