Case Study: From Excel Sheets and WhatsApp Chats to a Global SaaS Product

How we helped a hospitality business owner go from doing everything by hand to running on a system built for growth.

At a Glance

• Industry: Hospitality

• What we did: Process digitisation, legacy code rescue, backend re-platforming, web and mobile development, QA, SaaS productisation

• Tech stack: Java (moved from .NET), React, iOS/Android, AWS, Firebase, Stripe, Sentry, AI-assisted development

• Engagement: Long-term dedicated partnership (still going)

• The big win: Around 60% of manual time and effort saved
  
  

How It Started

When the owner first reached out to us, the business was running on Excel sheets, WhatsApp groups and a lot of back-and-forth messages. Attendance lived in one spreadsheet, payroll in another, and team updates were buried somewhere in a chat thread. The owner was handling almost all of it personally, and as the business kept growing, that simply wasn't sustainable anymore.

There was also some code already on the table. An earlier attempt at building a system had left behind a .NET backend and a React frontend, but honestly, it was messy. There was no clear structure, the business logic was scattered all over the place, and every new change felt like it might break something else. It never really became something the business could rely on.

So we had two jobs from day one: really understand how the business worked, and build something that would take the weight off the owner's shoulders.

Getting on the Same Page

The owner isn't from a tech background, and they never needed to be. Our job was to make every decision easy to follow. Before we touched anything, we walked them through what we found, what we planned to change, and how the development cycle would run, all in plain business language rather than jargon.

That habit stayed with us for the whole project. Every feature, every change and every timeline was shared openly. No black boxes, no surprises.

We also spent a good amount of time with those Excel sheets and WhatsApp workflows. It sounds basic, but that's exactly where the real requirements were hiding. We built the system around how the business actually runs, not the other way round.

The Big Call: Moving the Backend to Java

After digging into the existing code, we recommended moving the backend from .NET to Java, while keeping the React frontend and cleaning it up properly. This wasn't about liking one language more than another. It was about where the product was headed. Here's why it made sense:

It's built to scale. The long-term plan pointed towards a platform that could serve many businesses at once. Java, with frameworks like Spring Boot, has a proven track record for large, multi-tenant systems with lots of users working at the same time.

Security comes first. We're dealing with payroll, attendance and HR data here. Java's mature security frameworks and its long history in enterprise and finance systems gave us a solid base to protect that data.

It's ready for the cloud. Java fits nicely with containers and modular services on AWS, so different parts of the system can scale on their own as demand grows.

A fresh start beats endless patching. Fixing the old code bit by bit would only have carried its problems forward. Rebuilding gave us the chance to put the business logic on a clean, well-documented foundation.

It's easier to maintain for years. A huge talent pool, long-term support releases and a stable ecosystem mean the product stays affordable and low-risk to maintain and grow.

Looking back, this was one of the best decisions we made on the project. Everything that came after, including the SaaS product, sits on that foundation.

How We Worked Together

Anyone on the team, any time

The owner could message anyone on our team directly: a developer, our QA engineer or the product manager. No waiting for an account manager to pass things along. For someone without a tech background, knowing that help was always just one message away made a real difference.

A secure environment for everyone

Since the system handles sensitive employee and financial data, security wasn't just a feature of the product. It was part of how we work every day. We kept strict security practices across development, testing and support, which gave the owner peace of mind and gave our own team confidence in the environment they were working in.

Clear ownership, module by module

We split the work into clear modules such as attendance, payroll, finance, learning and HR documentation. Each one had people who owned the backend, frontend, mobile app and QA. Everyone knew exactly what they were responsible for, which let us move fast on several fronts without things slipping through the cracks.

Bumps along the way

Were there challenges? Of course. Technical blockers, changing requirements, the odd difference of opinion. Every one of them got sorted out calmly and quickly, because we all agreed on one thing: a disagreement is never a good enough reason to ship something below our best.

A team that treats it like their own

This is probably the part we're proudest of. Our developers didn't just close tickets. They cared about the product as if it were their own. Our product manager made a point of recognising everyone's effort, and the team genuinely enjoyed the work.

Yes, there were some late nights. But when the owner came back and told us how much the system was helping the business, every one of those nights felt worth it.

What We Built

We replaced the spreadsheets and chat threads with one secure, central platform on Java and React, plus a mobile app for staff. Here's what it covers:

• Attendance tracking with fingerprint clock-in and GPS location checks, instead of manual Excel logs

• Payroll processing connected with specialised payroll services

• Staff training through an integrated learning platform

• HR documents and compliance, including employee eligibility checks

• A finance module for a clear view of the numbers

• A mobile app so staff can clock in and stay updated without relying on WhatsApp groups

• Secure payments, reliable cloud hosting and real-time error monitoring
  
  

The Difference It Made

60% of manual time and effort saved

The biggest win is simple: the system now saves the owner around 60% of the time and effort they used to spend on manual work. Everything lives in one place instead of across files and chats. Mistakes in attendance, payroll and compliance are far easier to avoid. And the business no longer depends on one person holding it all together.

What Came Next: Going SaaS

Once the first product was live and doing its job, the owner saw something bigger. If this system could make such a difference for their business, it could do the same for other hospitality businesses stuck with the same manual headaches.

So we scaled up the existing system and started building a new SaaS product on top of it. It's more advanced, with more features and global functionality, designed for hospitality businesses anywhere in the world.

Using AI, but staying in control

For the SaaS build, we've brought AI-assisted development into our workflow to speed things up. What we haven't done is hand over the thinking.

Our team keeps a clear, well-documented knowledge base of both the code and the business logic, so everything AI helps produce is guided by people who know exactly how the product works and why. The full scope is covered and tracked, and every change still goes through our developers and QA before it goes live. The result is faster delivery with the same quality the owner has trusted from the start.

Where We Are Today

The SaaS journey is still going, and we're genuinely excited about where it's heading.

One big reason this partnership has lasted is how we approach the commercial side. At times, we've adjusted development costs to fit the owner's investment plans and the stage the business was at, because we care more about the product succeeding in the long run than about any single invoice. That flexibility has built a lot of trust, and honestly, it's made the product better too.

What We Took Away From This

• Great software starts with understanding how the business really works, even when that means reading through WhatsApp chats and Excel sheets.

• Being open and easy to reach matters most when the client isn't technical.

• Sometimes the right move is a bold one, like rebuilding the backend on a better foundation.

• AI can speed things up, as long as people who know the product stay firmly in charge.

• Long-term trust is worth more than short-term margins.

Still running your business on spreadsheets and chat groups?

We'd love to hear about it. Let's talk.