Oceanbeat Ibiza:
one designer, full ship.
How I designed and built a website on my own for an Ibiza boat-party company serving 320,000+ guests, using AI tools like Claude, Cursor, VS Code and GitHub. No external developer in the loop.
A premium production site, no dev team.
Oceanbeat runs four flagship boat experiences in Ibiza, Day Party, Sunset, Formentera 12H, and a private charter route. They needed a brand site that could carry their cinematic energy, surface live pricing, and convert into a step-by-step booking, all without leaning on a developer.
The site had to feel like the actual product: warm, sunlit, premium. Not a typical "boat tour" template. And it had to actually book, take payment, and not break on a phone in Spanish 3G.
A premium product trapped in a cheap-looking funnel.
The existing site was a third-party booking widget bolted onto a generic theme. Three problems compounded:
1. Conversion leaked early. Pricing lived behind a calendar widget. Users who landed via Google bounced before seeing a price.
2. Trust was buried. 320,000+ guests, TripAdvisor Travellers' Choice awards from 2023, 2024 and 2025, none of it surfaced above the fold.
3. Mobile was unusable. The booking widget broke on Spanish carriers and Apple Pay didn't work at all.
Six weeks. Solo loop.
Stakeholder workshop, three competitor audits, journey maps for four routes. Locked the structure on day three.
Sketched the booking flow before any pixel. Five steps: route, date, group size, extras, then payment. No back-and-forth.
Built the design system in Figma, type scale, color, components. Designed every screen, mobile-first, then desktop.
Prompted Claude with the design system + clear requirements. Reviewed in Cursor, committed to GitHub, deployed. Iterated against real bookings.
Five decisions that made the difference.
Each route surfaces its starting price within two scrolls of landing. Day from €55, Sunset from €65, Formentera 12H from €129. No "request a quote" friction.
An animated counter shows guest count climbing past 320,000 on first scroll. A small TripAdvisor strip, 2023, 2024, 2025 Travellers' Choice, sits below. Trust is doing work before the price does.
Route, date, group, extras, then payment. Each step shows total + free-cancellation reminder. Payment supports Visa, Mastercard, AMEX, PayPal and Apple Pay. Group discounts apply automatically at six+ guests.
Designed mobile-first because 70%+ traffic is Spanish carriers on phones. The whole page is under 180 KB transferred, no slow scripts, Apple Pay button native.
A persistent WhatsApp button stays bottom-right on mobile. Pre-filled message includes the route they were looking at. Real humans, real-time, in Spanish or English.
How building with AI actually works.
I treat the AI like a very fast junior developer. The thinking, what to build, how it should work, and the tricky cases, stays with me. The AI turns my plan into code, and I check every change.
For Oceanbeat, that meant a Figma file with every screen, a short style guide for fonts, colors and spacing, a clear list of what each page should do, and step-by-step instructions to Claude. I made edits in Cursor and saved everything in GitHub.
The result is clean, hand-checked code, with no heavy frameworks. Just simple files on a server, fast to load and easy to update.
Event listings with live prices, a video header, a guest counter, a photo gallery, an FAQ section, a step-by-step booking flow with Visa, Mastercard, PayPal, AMEX and Apple Pay, free-cancellation rules, group discounts, pick-up location details, a WhatsApp button, a TripAdvisor 2023-2025 award section, guest reviews, and a layout that works on every screen size from small phones up.
What it moved.
Three takeaways for any solo product loop.
The AI is only as good as the artefact you point it at. With every Figma screen and a written spec, the code came out coherent. Without them, it drifted within an afternoon.
Most "AI bugs" are prompt bugs, wrong assumptions or missing constraints. Read the diff, find the gap, re-prompt with the missing piece. Twice as fast as debugging after the fact.
Day-party + booking went live in week four. Sunset and Formentera went live in week six. Iterating against real bookings beat any synthetic test plan.