I Rebuilt a Luxury Website From My Bed at 11 PM

I'm lying in bed at Quinta da Bella Vista. A historic estate in Sintra, Portugal. The former home of Sir Arthur Conan Doyle—yes, the Sherlock Holmes author. The property is stunning. The website is not. Wix-based. Slow. Generic templates. It doesn't match the luxury of what I'm experiencing. I open Telegram. "Let's rebuild this website tonight."

The Scene

It's 11 PM. I'm a guest at this wedding venue. Tomorrow I'll walk the gardens where Conan Doyle once wrote. Right now, I'm talking to my AI colleague about typography choices. The original site: quintadabellavista.com — built on Wix, loads slowly, looks like every other template site. What I want: A luxury experience that matches the property. Fast. Elegant. Something worthy of a historic estate.

What Happened Next

I described what I wanted. My colleague started building. "I'll use Next.js 15 with Tailwind. Going for a luxury palette—cream backgrounds, gold accents, Playfair Display for headers. Classic but not dated." I gave feedback from my phone. "The hero needs more impact." Changes appeared. "The gold is too bright." Adjusted. "Add a section about Conan Doyle's history here." Done. By midnight, we had: • Complete homepage with hero, services grid, testimonials • 7 pages: Home, Weddings, Events, Stay, History, Gallery, Contact • Custom color system matching the estate's aesthetic • Mobile responsive throughout • Deployed to staging

The Stack That Got Built

From that conversation in bed:

• Next.js 15 with App Router — Fast, SEO-optimized, modern architecture
• Tailwind CSS with custom luxury palette — Cream, beige, brown, gold. Typography with Playfair Display and Lato
• Sanity CMS integration — So the venue can update content themselves. No developer needed for text changes
• Vercel deployment — Auto-deploy on push, instant previews, global CDN
• Complete content architecture — Wedding packages, room descriptions, history timeline, gallery categories

The Reality

I never opened my laptop. Never touched a keyboard. Never wrote a line of code manually. I lay in bed, looked at my phone, and described what I wanted. My AI colleague built it. The staging site went live that night. The next morning, I walked those historic gardens knowing the website now matched the experience. This isn't about speed. It's about removing the barrier between "this should exist" and "this exists."

Why This Matters

Most consultants would schedule a discovery call. Then a proposal. Then a timeline. Weeks of back-and-forth before a single line of code. I was a guest at the venue. I saw the problem. I fixed it. That night. Not because I'm faster at coding. Because I don't need to code anymore. I describe. My colleague builds. The system handles everything in between. From bed. At 11 PM. On a phone. That's what AI infrastructure actually looks like.