In short
- Two calls with the founder before any design, then a sitemap with one page for each of the three audiences.
- No wireframes: one concept from the founder’s own words, and the hero in a few directions with the real text, photos and fonts.
- AI proposes three options for every section and I decide, sometimes against its advice, because I know this community from the inside.
Coração de Cacau runs gatherings with ceremonial cacao, ecstatic dance and live music at Vale do Rossim, a lake in the Serra da Estrela, since 2018. The founder, Momo, came with a clear wish: “the adult version of our website.” Same family, same lake, same cacao. Something more chic and more professional, without losing the warmth that makes people come back every year.

Two calls before any design
The first call was about the brand. I took Momo through a set of questions about copy and brand strategy: where the business is today, what’s new, the direction he wants to take, and the energy Coração de Cacau should keep. The second call was about the website itself: which pages, which features, the look and feel, and the experience. What should someone understand in the first 5 seconds, and what should happen if they stay for 5 minutes?
Almost every important decision on the site traces back to something Momo said in those two calls.
A sitemap first
Before any visual, I defined the sitemap. Three audiences, one page each: the people who come to the gatherings, the festivals and retreats that book Momo, and the companies that want a team building day. Fixing the structure early means nobody argues about it later.
Why I stopped making wireframes
I used to make wireframes for every project, so the client could read the content before the design. In practice, most clients went straight to “but what will it look like?”. Some simply needed to see something real. The wireframes took me a lot of time, and the energy I put into them didn’t come back.
So now I skip them. From the two calls I define one concept, and I show the hero of the homepage in a few directions, with the real text, real photos and real fonts.

One concept, in the client’s own words
The concept came from a line Momo said in the first call:
It’s a journey to arrive. But people tell me after a while: what a gift it was to be here.
Vale do Rossim is far from Lisbon and from Porto. Instead of hiding that, the site tells it: the shared rides, the road into the mountains, the lake at the end. On the homepage, a line draws itself as you scroll, from the city to the lake. It’s the one bold move on the site, and everything else stays calm around it. The concept sets the fonts, the colors and the motion for every page.
Section by section, three options each
After the hero, I build the homepage one section at a time. For each one I ask for three variations and a recommendation. Sometimes I take it. Sometimes I like another one better, and ask for three more variations from that one. Then I look at the new section next to the one before it, on desktop and on the phone, so the page flows and the contrast between sections works.
The text comes from my copywriting agent, written from the answers in the first call. The motion comes from my animation agent, which picks from a library I trust. The photos come from the client’s archive: hundreds of photos per event, well organised, so I could download them and let the AI find the right ones for each section and the concept.
When I say no to the AI
Being part of this community changes the decisions. At one point the recommendation was to avoid two full-width photos in a row: the musicians with no stage between them and the guests, and then the lake. On most sites that’s good advice. Here, those two images are the reason people want to go, and most visitors arrive on a phone, where the two of them tell the story in two scrolls. They stayed.

A final pass with fresh eyes
When the homepage was complete, a design critic agent went through the whole page with no context from the build. It found the small things I had stopped seeing:
- The welcome title in three lines on desktop, when two lines read much lighter.
- Spacing between titles and text that changed from section to section.
- Labels that said the same thing twice, and details people skim past that belong on another page.
- Play buttons in the same color as the main button, competing with it.

None of them is big. Together, they’re the difference between a page that looks generated and one that feels made.
The stack
Ship Studio with Claude Code, GitHub and Vercel for the build and the live previews, and Sanity for the photo galleries of each gathering, so new photos can go up without touching code.
What I take from it
AI made this faster. The two calls, the time spent in that community and the taste to say no stayed human, and they’re what make the site feel like Coração de Cacau.
If your website looks fine but doesn’t feel like being there, let’s talk.
Tell me what you do and where you are stuck. I will answer myself, and you will have nothing to decide yet.
