MEDL Mobile

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

As Chief Digital Officer at Southern Cross Technology, a Food & Beverage organisation in Sydney, Australia, 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 internal team was good but maxed out. The Game Development 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?

Game 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 Game Development approach was the most specific and evidenced — actual Food & Beverage 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?

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?

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?

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. 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.

Pacific Rim Commerce Group is a mid-size Healthcare business in Perth, Australia. I joined as GM of Technology 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?

Compliance requirements in our Healthcare space changed and the deadline was set by our regulator, not by us. The AI & Machine Learning 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?

End-to-end AI & Machine Learning delivery with particular focus on the data migration and integration workstreams, which carried the highest project risk. A dedicated QA resource was embedded throughout development and they left us with a proper operations runbook at handover.

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 Perth, Australia 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?

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?

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 AI & Machine Learning delivery, I would put them at the top of the evaluation list.

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

We are a Gaming & Gambling 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?

Our internal team was good but maxed out. The DevOps 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 stated scope was DevOps Services 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?

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?

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?

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?

Absolutely. We are scoping a second engagement and I expect this to become a multi-year partnership. For anyone in the Gaming & Gambling space looking for serious DevOps Services 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 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?

We had a clear product vision for our next growth phase in the Insurance market but the IT Consulting expertise we needed was not something we could recruit for on our timeline. An external specialist was the pragmatic answer.

What services did the company provide for your project?

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

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

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?

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, without reservation. I have already referred two peers in the Insurance sector who were facing similar IT Consulting challenges. I gave those referrals confidently because I know the experience I described was not a one-off — it reflects how they work.