Please describe your company, your role, and the industry you operate in.
Baltic Cloud AB is a Construction business headquartered in Malmö, Sweden. As Chief Technology Officer 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 Embedded Systems 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?
Mainly Embedded Systems Development, with some adjacent architecture and QA work folded in. They owned the whole thing from requirements to go-live, including hooking it into four of our existing systems. Not needing a second vendor to cover that ground was genuinely useful, both cost-wise and logistically.
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?
Genuinely excellent, especially given the time difference between Malmö, Sweden and the delivery team. Written updates were consistent and specific, anything needing a decision got same-day turnaround, and nothing slipped through the cracks across the whole engagement.
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 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?
The team stayed the same the whole way through. The engineers in the discovery sessions were the same ones who built the system. That continuity matters more than people expect, and you really only notice it when it's missing. Every conversation picked up where the last one left off.
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 Construction network, both times to people facing Embedded Systems 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.