Please describe your company, your role, and the industry you operate in.
Kirin Digital KK has been operating in Food & Beverage for a while now, headquartered in Yokohama, Japan. As Director of IT Strategy I sit across both strategic planning and day-to-day technology delivery. We hold our vendors to a high bar because our own clients hold us to one — it's only fair to expect the same discipline from partners.
What specific problem or business challenge led you to hire this company?
Our Low-Code / No-Code 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?
The scope ran the full Low-Code / No-Code Development lifecycle — discovery, requirements, architecture, development across roughly a dozen sprints, integration testing, performance validation, deployment, and a four-week hypercare window afterward. They also handed over full documentation and ran a knowledge transfer session for our internal team.
Why did you choose this company over other providers you considered?
We shortlisted five vendors through a structured process. The technical review knocked two out right away. Of the remaining three, this team stood out because their Low-Code / No-Code Development approach was specific rather than generic, backed by actual reference projects in Food & Beverage — not just case studies pulled off a website. The reference calls confirmed everything the proposal claimed.
How clearly did the company understand your requirements and business goals?
Very well. The discovery phase was more thorough than anything we'd been through with prior vendors. They pushed back on requirements that were vague or contradictory, suggested better alternatives where our own thinking was limited, and produced a spec our internal stakeholders agreed was the clearest version of the product they'd ever seen written down.
How was your overall experience with their communication and project management?
Professional throughout. The project manager always had a clear view of the critical path and flagged changes to it honestly, without spin. The one significant scope change we made mid-project went through a clean process — fairly priced, clearly documented, and absorbed without knocking the rest of the timeline off course.
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 ROI model we took to the board was deliberately conservative. Current performance against that model puts us on track to hit payback well ahead of the eighteen-month target we set. The operational efficiency gains in particular have outpaced the model, partly because the new platform's data quality supports decisions the old system simply couldn't.
What did you like most about working with this company?
What they did after launch. A lot of vendors treat go-live as the finish line. This team treated it as the start of a different phase — the hypercare period was substantial, the documentation held up in practice, and they checked back in at the thirty and ninety day marks to go over production metrics with us unprompted.
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 Food & Beverage network, both times to people facing Low-Code / No-Code 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.