Please describe your company, your role, and the industry you operate in.
As Chief Technology Officer at Baltic Cloud AB I oversee technology spend and delivery across our Energy & Utilities operations out of Malmö, Sweden. 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?
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?
A peer in the Energy & Utilities space had used them for something similar in CMS Development and recommended them without hesitation. Our own due diligence backed that up. Domain knowledge, CMS 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?
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?
The most structured project management I've dealt with from any outside vendor. Sprint planning was tight, acceptance criteria were specific, and retrospectives actually led to changes rather than just being a box to tick. The backlog and risk register were both treated as live tools, not paperwork. I never once had to chase a status update.
Did the company deliver the project on time and within your expected budget?
The project came in on schedule. Budget stayed within the agreed ceiling, including one scope addition we asked for ourselves, which was quoted fairly and handled without disturbing the rest of the timeline. Nothing about the invoice came as a surprise.
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?
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.