Tourism

EcoBlue Tours

Sharpened the booking funnel and destination storytelling so holiday planners glide from inspiration to checkout without faff.

View build

The problem

EcoBlue Tours is a boat tourism company in the UAE, serving B2C and B2B. They had: no website, no logo, no booking funnel, no structured digital presence. A prior build lacked structure and long-term thinking. No scalable booking flow and no foundation for automation. In tourism, no digital presence means no discoverability; no funnel means manual coordination; friction kills conversions.

The objective

Success = more booked trips without operational chaos. They needed: premium brand presence, clear tourist and company funnels, automated booking logic, reduced admin time, and a system that can grow. Automation was central.

The build

Stack • Next.js • Supabase database • Supabase Auth • Custom booking dashboard • Global CDN hosting This wasn't just a site; it's a marketing layer tied to a structured booking system. Key components: multi user roles, auth-protected dashboard, custom booking calendar logic, database-driven availability, CRM + payment integrations, custom API sync. Booking calendar built with custom rules (not a plugin). Architecture separated: public marketing site; booking application layer; database logic layer. Clean handshake keeps it maintainable and scalable. Performance + SEO from day one (critical in tourism).

The experience

UX centred on clarity. From the homepage, users are funnelled to either tourist or company bookings, no wandering. Mobile-first (most traffic on mobile while travelling). Booking flow simplified to move from landing to confirmed intent with minimal steps. Trust signals via structure, clarity, and clear CTAs. Visuals: marine/premium leisure feel; clean and conversion-focused.

Integrations & automation

CRM integration; payment provider integration; calendar booking logic; auth-controlled dashboard; custom API work. Automation captures data properly, routes into the system, reflects live availability, reduces admin coordination, cutting operational strain.

Measurable impact

Formal revenue metrics weren't published, but operational impact was clear: faster performance, structured booking funnel, reduced admin time, cleaner ops, stronger digital credibility. Biggest shift: operational maturity, from basic presence to a proper booking infrastructure.

Process

~3 months total: ~1.5 months marketing site, ~1.5 months booking system. Iterative: build, test, refine. Turning point: finalising booking engine architecture; once the handshake between site and app was set, delivery accelerated.

What made this technically strong

Bespoke architecture instead of a third-party plugin. Clear separation of presentation and logic, database-driven availability, multi-role access, scalable without replatforming. The intentional handshake between site and booking system enables future growth. This is a tourism operations system, not just a website.