From scattered travel applications to a reusable business workflow

A founder in the travel-services sector needed a better way to manage the booking and application journey for older travellers applying to visit an Asian market.

The process worked, but it depended on a great deal of manual coordination. Customer information was scattered across WhatsApp, email and WeChat. Questions were repeated, updates were difficult to track, and spreadsheet handoffs made it hard to see where each application stood.

As demand grew, the founder needed a way to keep information in one place, create a more consistent customer experience, and reduce dependence on individual memory and follow-up.

The problem was not simply “we need an app”. The founder had already created an initial mock-up with Claude, but there was no practical system yet for capturing, storing, organising or managing the information behind it.

Before choosing tools or building the working application, we needed to clarify:

• What customers were actually trying to complete;
• Where the existing journey created confusion or delay;
• Which information needed to be collected, checked, stored and handed over, which part of it is personal data, and how that data must be handled;
• Which updates and notifications customers and the founder needed at each stage;
• What could be standardised without making the experience rigid; and
• What the founder needed to be able to own, operate and adapt after launch.

I mapped the end-to-end customer workflow: the booking journey, application information, decision points, handoffs, status updates and follow-up steps. We then translated that map into a practical working application. My role was to help the founder clarify what the application needed to do, choose and set up appropriate tools, and turn a promising mock-up into a workflow the business could actually run.

The focus was not a polished prototype that introduced new work behind the scenes. It was a usable operating system for the process:

• Structured information instead of disconnected messages;
• A clearer view of each customer’s application status;
• Defined handoffs and follow-up points;
• Appropriate notifications; and
• A workflow the founder could understand, manage and improve over time.

After launch, we reviewed how the workflow performed in practice, refined what was needed, and built the founder’s confidence in adapting it.

The client launched a working application for the travel-application process, bringing a previously fragmented workflow into one more manageable system. Manual work fell by 60%, and the business gained a single database for trip-related information. The updated workflow was ready to launch within weeks, not the months they had expected.

More importantly, the client did not treat it as a one-off build. Having seen the approach work in a customer-facing setting, the founder applied the same thinking to an internal payroll application. The outcome was not only a new tool. It was a repeatable way to identify a process, map the work, build a practical solution, and extend what worked into another part of the business.

Good AI, automation and workflow work does not begin with “which tool should we buy?” It begins with:

Where is the work breaking down? What must change? What information and decisions matter? And what can the team confidently operate after implementation?

That is how a first workflow becomes a reusable capability, not another isolated experiment.