Nodes

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

I am the CTO at Kiwi Cloud Solutions Ltd, a Insurance company headquartered in Auckland, New Zealand. 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?

A competitor move accelerated our timeline by six months. A IoT 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?

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

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

The requirements process took longer than we expected but the thoroughness showed in the development phase — we had noticeably fewer mid-sprint clarifications and no major requirement changes that required 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?

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?

Five months post-launch: zero P1 incidents, Core Web Vitals in the green, and two enterprise clients who had been citing platform limitations in renewal conversations have since renewed without raising the issue. The system is doing what we needed it to do.

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. I would specifically recommend them for IoT Development projects where getting the requirements right at the start is critical. That is where they earn their fees — and the downstream delivery reflects it.

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

Karachi Tech Solutions operates in the Healthcare sector out of Karachi, Pakistan. In my role as Senior Engineering Manager 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?

Compliance requirements in our Healthcare space changed and the deadline was set by our regulator, not by us. The Game 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 core engagement was Game Development 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?

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?

Thoroughly. The requirements document they produced was detailed enough that our QA team used it directly to write acceptance criteria. Every story had a defined business outcome attached. Nothing was left to interpretation, which paid dividends all the way through to testing.

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

I used to chase status updates weekly on vendor engagements. This was the first time I did not have to. Updates came consistently, problems surfaced early, and the shared project board always reflected reality rather than optimism.

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

Delivered on time. We had one week of unplanned delay due to an external API issue that neither party controlled. They communicated it early, proposed a workaround, and the launch date stayed the same. That is how delays should be managed.

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?

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?

Absolutely. We are scoping a second engagement and I expect this to become a multi-year partnership. For anyone in the Healthcare space looking for serious Game Development delivery, I would put them at the top of the evaluation list.

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

I am the Founder at Meridian SaaS Ltd, a Events & Event Management company headquartered in Bristol, UK. 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 internal team was good but maxed out. The IT Managed Services work needed for this phase of the product required a depth of experience we did not have internally, and could not build in time.

What services did the company provide for your project?

The core engagement was IT Managed 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?

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?

Extremely well — partly because they had enough Events & Event Management context to ask the right questions without us having to explain the basics. The functional spec translated our business requirements into technical language with a precision that meant the development phase had almost no clarification cycles.

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

I used to chase status updates weekly on vendor engagements. This was the first time I did not have to. Updates came consistently, problems surfaced early, and the shared project board always reflected reality rather than optimism.

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?

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 directness. When our requirements were unclear, they said so. When our priorities were contradictory, they explained why. When a technical approach we assumed was right had significant downsides, they told us before we committed. That kind of honesty is what I actually want from a technology partner.

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 Food & Beverage company based in Singapore. My role as CTO at Marina Bay Ventures Pte Ltd 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?

Honestly, we had been deferring this Low-Code / No-Code Development investment for eighteen months. User feedback had been consistent and our conversion data confirmed the impact. We eventually ran out of reasons to delay.

What services did the company provide for your project?

The stated scope was Low-Code / No-Code 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?

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?

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 Singapore 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 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?

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?

I already have. Three people in my network have used them based on my recommendation and all three have reported positively. That is the only endorsement that matters.