Yellowtail Software

Please describe your company, your role, and the industry you operate in.

As Head of Product Engineering at Scandia Digital AB, a Agriculture organisation in Gothenburg, Sweden, I manage technology investment and delivery outcomes. We make commercial decisions about technology — every project needs a credible case before it gets approved.

What specific problem or business challenge led you to hire this company?

A competitor move accelerated our timeline by six months. A E-commerce Development investment that had been planned for next year suddenly needed to happen now. Internal build was not viable — we needed to find the right external team quickly.

What services did the company provide for your project?

E-commerce Development design and build, plus the performance testing that revealed an architecture concern we needed to address before launch. The testing investment paid for itself. They also handled the deployment pipeline and monitoring configuration, which our internal team had not budgeted time for.

Why did you choose this company over other providers you considered?

We had a fixed budget and a non-negotiable timeline. Several vendors told us it could not be done. These were the ones who said it could and explained clearly why. They turned out to be right.

How clearly did the company understand your requirements and business goals?

Very well. The discovery process was more thorough than anything we had experienced before. They challenged requirements that were vague, proposed better alternatives where our thinking was limiting, and produced a spec that our stakeholders agreed was the clearest articulation of the product they had ever seen written down.

How was your overall experience with their communication and project management?

Communication was proactive and well-calibrated. Technical detail for the engineering audience, executive summaries for the steering group, and risks raised with proposed mitigations rather than just problem statements. The fortnightly sprint reviews kept our stakeholders informed without pulling them into every working session.

Did the company deliver the project on time and within your expected budget?

On time. Budget was within the approved ceiling, including one scope addition we introduced mid-project that was quoted fairly and handled in parallel without affecting the main delivery stream. No surprises at invoice stage.

What tangible results or business impact have you seen since the project was completed?

Four months live. User adoption exceeded our first-month target by around 20%. Support volume is down. Features we had deferred for years because the old architecture made them too expensive to build are now in active development. The platform opened our roadmap.

What did you like most about working with this company?

Team continuity. The engineers who ran the discovery sessions built the system. That consistency over a five-month engagement is valuable in ways that are hard to articulate until you have worked on projects where it was absent. Every conversation built on the previous ones.

Would you recommend this company to others, and would you work with them again?

Yes. The value starts in the discovery phase — clients who invest time in that process will get the most out of the engagement. We did and it is evident in what was delivered.

Please describe your company, your role, and the industry you operate in.

Highland Analytics Ltd is a Agriculture business based in Glasgow, UK. As Operations Director, I own the technology strategy and vendor relationships. Every spending decision gets evaluated against a concrete business case — we do not invest in technology for its own sake.

What specific problem or business challenge led you to hire this company?

Our Cloud Services capability had become the bottleneck for everything. Feature requests, client requirements, internal initiatives — all of them were queuing behind a platform we had patched past its design limits. We needed a proper rebuild.

What services did the company provide for your project?

The core engagement was Cloud Services delivery. During discovery they also provided technical consultancy that materially improved our requirements — things we would not have caught until development if they had not raised them. They also took ownership of the third-party integrations that had caused problems in previous projects.

Why did you choose this company over other providers you considered?

We had been through a failed engagement the year before and took vendor selection seriously this time. We asked specific questions about how they handle scope change, estimate work, and communicate problems. The answers were consistent across everyone we spoke to, which suggested the process was real rather than sales-trained.

How clearly did the company understand your requirements and business goals?

Very well. The discovery process was more thorough than anything we had experienced before. They challenged requirements that were vague, proposed better alternatives where our thinking was limiting, and produced a spec that our stakeholders agreed was the clearest articulation of the product they had ever seen written down.

How was your overall experience with their communication and project management?

Very strong on the async side, which mattered given the time difference between Glasgow, UK and the delivery team. Written updates were specific and consistent, decisions got responses the same day, and nothing was dropped across a five-month engagement. That discipline is harder than it looks.

Did the company deliver the project on time and within your expected budget?

Yes. I had privately planned for a contingency given the integration complexity involved. None of it was needed. Final invoice came in within rounding of the approved budget and we launched on the agreed date. That outcome is less common than vendors would have you believe.

What tangible results or business impact have you seen since the project was completed?

Biggest impact: our internal team is no longer spending three days a week maintaining a platform they hated working with. That productivity is now going into building. The platform change was as much about our engineering team's quality of life as it was about the end user.

What did you like most about working with this company?

Team continuity. The engineers who ran the discovery sessions built the system. That consistency over a five-month engagement is valuable in ways that are hard to articulate until you have worked on projects where it was absent. Every conversation built on the previous ones.

Would you recommend this company to others, and would you work with them again?

Yes. The value starts in the discovery phase — clients who invest time in that process will get the most out of the engagement. We did and it is evident in what was delivered.

Please describe your company, your role, and the industry you operate in.

We are a Insurance company based in Denver, CO, USA. My role as Head of Digital Operations at Northstar Logistics Corp means I sit at the intersection of business goals and technical delivery — which means I care a lot about vendors who can translate between both.

What specific problem or business challenge led you to hire this company?

Compliance requirements in our Insurance space changed and the deadline was set by our regulator, not by us. The Embedded Systems Development work required was specialist enough that pulling our internal team off the product roadmap to do it was not an option.

What services did the company provide for your project?

The stated scope was Embedded Systems Development delivery. In practice they also contributed to product strategy conversations, flagged gaps in our requirements, and produced integration documentation that our partner vendors later told us was unusually thorough.

Why did you choose this company over other providers you considered?

The questions they asked during the briefing were the first signal. Vendors who ask precise questions in the sales process tend to apply the same discipline during delivery. The technical proposal was detailed, the team was senior, and the pricing was transparent. All three were factors.

How clearly did the company understand your requirements and business goals?

Very well. The discovery process was more thorough than anything we had experienced before. They challenged requirements that were vague, proposed better alternatives where our thinking was limiting, and produced a spec that our stakeholders agreed was the clearest articulation of the product they had ever seen written down.

How was your overall experience with their communication and project management?

The most structured project management I have experienced with an external vendor. Sprint planning was tight, acceptance criteria were specific, retrospectives were honest and acted on. The PM treated the risk register as an operational tool, not a compliance document. I never had to ask for a status update.

Did the company deliver the project on time and within your expected budget?

Yes. I had privately planned for a contingency given the integration complexity involved. None of it was needed. Final invoice came in within rounding of the approved budget and we launched on the agreed date. That outcome is less common than vendors would have you believe.

What tangible results or business impact have you seen since the project was completed?

The ROI case we presented to the board was intentionally conservative. We are tracking to hit the payback point in under twelve months against an eighteen-month model. The efficiency gains have exceeded the forecast, partly because the data quality the new system produces enables decisions the previous one could not support.

What did you like most about working with this company?

The post-launch engagement. Some vendors treat go-live as the end of their obligation. This team treated it as a transition to a different kind of engagement. Hypercare was substantive, documentation was genuinely useful, and they checked in proactively at thirty and ninety days.

Would you recommend this company to others, and would you work with them again?

Yes, without reservation. I have already referred two peers in the Insurance sector who were facing similar Embedded Systems Development challenges. I gave those referrals confidently because I know the experience I described was not a one-off — it reflects how they work.

Please describe your company, your role, and the industry you operate in.

BlueSky Retail Holdings is a mid-size Retail & E-commerce business in Chicago, IL, USA. I joined as Chief Digital Officer two years ago specifically to modernise how we build and buy technology. This engagement was part of that programme.

What specific problem or business challenge led you to hire this company?

Our CMS Development capability had become the bottleneck for everything. Feature requests, client requirements, internal initiatives — all of them were queuing behind a platform we had patched past its design limits. We needed a proper rebuild.

What services did the company provide for your project?

The stated scope was CMS Development delivery. In practice they also contributed to product strategy conversations, flagged gaps in our requirements, and produced integration documentation that our partner vendors later told us was unusually thorough.

Why did you choose this company over other providers you considered?

Referral from someone whose technical judgment I trust. The due diligence we ran confirmed what we had been told. The proposal stage was also notably more thorough than the alternatives — they clearly understood the CMS Development requirements better than the other vendors we evaluated.

How clearly did the company understand your requirements and business goals?

Well. They pushed back on areas where our requirements were vague or poorly thought through and helped us arrive at something more considered. That consultative approach during discovery is not universal and it made a real difference to the quality of what was built.

How was your overall experience with their communication and project management?

The most structured project management I have experienced with an external vendor. Sprint planning was tight, acceptance criteria were specific, retrospectives were honest and acted on. The PM treated the risk register as an operational tool, not a compliance document. I never had to ask for a status update.

Did the company deliver the project on time and within your expected budget?

On time and on budget. The estimation accuracy was the part I found most impressive — they had broken the work down thoroughly enough during discovery that the forecast held throughout rather than drifting with every scope conversation. We had one change request, and it was for scope we had added ourselves.

What tangible results or business impact have you seen since the project was completed?

Four months live. User adoption exceeded our first-month target by around 20%. Support volume is down. Features we had deferred for years because the old architecture made them too expensive to build are now in active development. The platform opened our roadmap.

What did you like most about working with this company?

Team continuity. The engineers who ran the discovery sessions built the system. That consistency over a five-month engagement is valuable in ways that are hard to articulate until you have worked on projects where it was absent. Every conversation built on the previous ones.

Would you recommend this company to others, and would you work with them again?

Yes, with the caveat that they are not the cheapest option and they are selective about what they take on. If price is the primary criterion there are alternatives. If you want a CMS Development partner in the Retail & E-commerce space who will actually deliver against a serious brief, this is the team.