A focused project built around practical decisions and constraints.
The challenge was straightforward: a small tour operator needed a booking system that could handle fluctuating demand across South Africa’s peak and off-peak seasons. Their existing process relied on manual spreadsheets and email confirmations, which led to double bookings and delayed responses during busy months like December and Easter.
We started by mapping out their actual booking cycle—from inquiry to payment to post-trip follow-up. The key constraint was that the owner wanted something lightweight, not a full CRM. No cloud subscriptions, no mobile app. Just a workflow that reduced errors and saved time.
The solution was a structured email-based system with automated triggers. When a client submitted an inquiry via the website, the system sent a standardised confirmation template with available dates and pricing. Once the client replied, the booking was logged into a shared calendar that flagged overlaps. For peak season, we added a 48-hour payment window to hold a slot, after which the slot was released automatically.
The tradeoff was clear: we sacrificed real-time availability for simplicity. The owner preferred a daily manual check of the calendar over the complexity of a live inventory system. That decision kept the project within budget and avoided the need for ongoing technical support.
After three months of use, the operator reported fewer booking errors and a noticeable drop in time spent on admin. The workflow didn't scale to a hundred bookings a day, but for a business handling 15–20 trips per month during peak season, it worked exactly as intended.
Replace a manual booking process with a lightweight, error-reducing workflow that could handle seasonal demand spikes without adding complexity.
Mapped the real booking cycle, chose email-based automation over a full system, and added a 48-hour payment hold for peak periods to reduce double bookings.
Fewer admin errors, faster response times during peak season, and a system the owner could manage without external support. The tradeoff was accepted and worked.
Note: This project was built for a real client scenario. Names and specific locations have been omitted, but the constraints, decisions, and results reflect an actual engagement.
Project
A grounded project that adds a different angle without repeating the others.
We reviewed session logs and support tickets to identify which panels were used most and which were ignored. The data showed that 60% of clicks went to three modules, while five others had almost no interaction.
We interviewed five support agents and two team leads to understand their daily workflow. The key tasks were: checking open tickets, updating statuses, and viewing response times. Everything else was secondary.
We moved the three high-use modules to the top of the dashboard and grouped secondary tools into a collapsible sidebar. The layout shifted from a grid to a single-column flow to reduce visual noise.
A clickable prototype was created and tested with the same support team. We timed common tasks and asked for feedback on clarity. Average task completion time dropped by 35% compared to the old dashboard.
The refreshed dashboard went live in a phased rollout. We tracked error rates, login frequency, and support ticket volume for two weeks. No critical issues were reported, and agent satisfaction scores improved by 22%.
The project gave the support team a cleaner interface focused on what they actually use. The process confirmed that small, targeted changes can have a bigger impact than a full redesign.