I was a guest at Quinta da Bella Vista, a historic estate in Sintra, Portugal. The former home of Arthur Conan Doyle, the man who wrote Sherlock Holmes. The property is stunning. The website was not. Slow, template-built, generic. It did not match the place at all.
Most consultants would book a discovery call, then write a proposal, then a timeline. Weeks of back and forth before a single line of code. I saw the problem in the evening and had a rebuilt site by morning.
What got built
A complete site, not a landing page. Seven pages: home, weddings, events, stay, history, gallery, contact. Next.js with a custom palette built for the property rather than pulled from a template. Cream, gold, a serif for the headers, classic without being dated. A content layer so the venue can change its own text without calling a developer. Deployed to a live staging URL.
The whole thing came out of a conversation. I described what I wanted, reviewed each change, corrected the things that were off. The hero needed more weight. The gold was too bright. Add a section on the estate's history. Each note turned into a change I could see within minutes.
The honest part
This was a guest rebuilding a site for the pleasure of it, on staging, not a signed contract with a launch behind it. So treat it as a demonstration, not a delivered project. What it demonstrates is real: the distance between seeing a problem and shipping a fix has collapsed to the length of a conversation.
Why it matters
I did not rebuild that site because I am fast at coding. I rebuilt it because I no longer need to schedule the gap between noticing something is wrong and making it right. I noticed, I described, I reviewed, it shipped. The next morning I walked the gardens where Conan Doyle once wrote, and the website finally matched the place.