GSL Solutions Inc

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

Cascadia Digital Ventures operates in the Agriculture sector out of Vancouver, Canada. In my role as Director of Platform Engineering I am responsible for both the technology strategy and day-to-day delivery. We hold our vendors to the same standards our clients hold us to.

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

Our Digital Marketing 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 Digital Marketing 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?

A peer in the Agriculture sector had used them for a similar Digital Marketing engagement and recommended them without qualification. Our own due diligence confirmed the picture they described. The combination of domain knowledge and delivery track record made the decision straightforward.

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?

Very strong on the async side, which mattered given the time difference between Vancouver, Canada 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?

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?

We went live six weeks ago so it is early. The launch was clean, adoption is tracking ahead of plan, and the first client demo of the new platform generated a positive reaction we had not seen for the previous version. Ask me again in six months and I will have better numbers.

What did you like most about working with this company?

The fact that problems surfaced upward before they became crises. I have worked on enough vendor engagements to know that the ability to manage upward — to raise bad news early rather than bury it — is genuinely rare. This team did it consistently.

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.

Zenith FinServ Ltd operates in the Nonprofit & NGO sector out of Bangalore, India. In my role as Chief Data Officer I am responsible for both the technology strategy and day-to-day delivery. We hold our vendors to the same standards our clients hold us to.

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

Our previous vendor had left us with three years of accumulated technical debt. Delivery velocity had dropped to maybe a third of what it should have been. We needed new engineering eyes and a structured plan to dig out.

What services did the company provide for your project?

Full Embedded Systems Development lifecycle — discovery, architecture, development across ten sprints, integration testing, performance validation, production deployment, and a four-week hypercare period. They also produced system documentation and ran structured knowledge transfer sessions for our team.

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?

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?

Very strong on the async side, which mattered given the time difference between Bangalore, India 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?

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?

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?

Honestly, the quality of the questions they asked. It sounds simple but good questions at the start of a project make everything easier. Their discovery process was better than any briefing our internal team would have run independently.

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.

I am the Head of Innovation at Desert Tech Ventures, a Fashion & Apparel company headquartered in Riyadh, Saudi Arabia. My role covers product, platform, and the vendor partnerships that support them. We had reached a point where our internal team could not execute our roadmap fast enough without outside help.

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

Our Blockchain 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?

Full Blockchain Development lifecycle — discovery, architecture, development across ten sprints, integration testing, performance validation, production deployment, and a four-week hypercare period. They also produced system documentation and ran structured knowledge transfer sessions for our team.

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?

Honestly, better than we understood them ourselves going in. The workshops they ran surfaced assumptions we had not examined and caught three requirements that were in direct conflict with each other. Resolving those before development started saved us a significant amount of rework.

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?

Yes on both. There was one sprint where a third-party API dependency introduced a one-week slip. They flagged it three weeks before it became critical, presented two options, and we agreed on one that recovered the timeline within the same sprint. That kind of foresight is the difference between good and average project management.

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?

Honestly, the quality of the questions they asked. It sounds simple but good questions at the start of a project make everything easier. Their discovery process was better than any briefing our internal team would have run independently.

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.

As CTO at Kiwi Cloud Solutions Ltd, a Aerospace & Defense organisation in Auckland, New Zealand, 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?

Our Software 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?

Software 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 shortlisted five vendors. Two were eliminated immediately based on the technical proposals. Of the remaining three, this team's Software Development approach was the most specific and evidenced — actual Aerospace & Defense reference cases, not generic slides. The reference calls confirmed what the proposal described.

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?

Professional and efficient. The PM had a clear view of the critical path at all times and was transparent when anything threatened it. We made one significant scope change mid-project. It was handled through a proper change request, fairly priced, and absorbed without disrupting the delivery timeline.

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?

Hard to isolate perfectly given other business variables, but the metrics attributable to the Software Development work are meaningful — session time up, conversion up, error rate down, NPS for the digital channel improved by double digits. Account managers say it is coming up positively in client conversations for the first time.

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, without reservation. I have already referred two peers in the Aerospace & Defense sector who were facing similar Software 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.

Cerrado Tech SA is a mid-size Automotive business in Brasília, Brazil. 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 previous vendor had left us with three years of accumulated technical debt. Delivery velocity had dropped to maybe a third of what it should have been. We needed new engineering eyes and a structured plan to dig out.

What services did the company provide for your project?

Primarily Cloud Services, with QA and solution architecture included in scope. They owned the build end-to-end from requirements through to go-live, including three existing system integrations. Not needing to coordinate separate QA or architecture vendors was genuinely valuable.

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?

Good. The sprint cadence worked well for our team. Fortnightly reviews gave us the checkpoints we needed. The one friction point — time zone overlap — was resolved after the first sprint and did not reoccur.

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

Yes. The estimates they provided during scoping proved accurate throughout delivery, which is rare. Most vendor estimates start optimistic and drift. These did not.

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?

The fact that problems surfaced upward before they became crises. I have worked on enough vendor engagements to know that the ability to manage upward — to raise bad news early rather than bury it — is genuinely rare. This team did it consistently.

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 Cloud Services partner in the Automotive space who will actually deliver against a serious brief, this is the team.