From Brief to Live Site: The Norden Build
Norden is the restaurant demo on our homepage: a high-end Nordic dining concept with a full website including menu, story, and a reservation form. It was built in under 6 hours. Here is the detailed breakdown.
Restaurant websites are a good stress test for the AI-native workflow because they require something Pulse did not: strong visual identity. A SaaS dashboard needs to look functional and trustworthy. A restaurant site needs to make you want to go there. That is a harder aesthetic problem.
The brief
The brief was deliberately vague on content but specific on feel: a Nordic fine dining restaurant, minimal, dark, photography-led. The name Norden was chosen to anchor the concept. The brief specified five pages: landing with a hero, menu, our story, events (quarterly), and a reservation page.
One key decision was made in the brief: no online booking engine. The reservation page would be a form that sent an email. This eliminated 4 to 8 hours of availability management complexity for a demo that did not need it.
Design decisions
The spec included explicit design direction: near-black background (#0d0d0d), off-white text, a warm accent for interactive elements, and a single serif typeface for headings. The instruction to the agent was: everything should feel like the restaurant is in no hurry.
That last instruction is an example of aesthetic direction that an agent can implement in specific ways once it is given a frame. It translated to: generous white space, slow-loading transitions, large photography, and minimal navigation. The agent implemented all of this correctly from a brief description.
Photography was the one area where the demo diverges from a real build. We used placeholder images from Unsplash with careful attribution. In a real project, the client would supply photography or we would arrange it as part of the engagement.
The menu layout challenge
The menu page was the most design-intensive part of the build. Restaurant menus have a specific visual convention: course headers, dish names, descriptions in a smaller weight, and prices aligned right. Getting this to feel luxurious rather than generic required three iterations.
The agent's first version was functionally correct but felt too dense. The second version added more vertical space between courses but the price alignment was off on mobile. The third version, after a specific instruction about the typographic hierarchy, produced the result we kept.
This pattern is representative. The agent handles structure correctly on the first pass. Getting the feel right, the subtle typographic choices and the whitespace relationships, takes 2 to 3 iterations with specific feedback.
The reservation form
The reservation form was deliberately simple: name, email, phone, date, party size, and a notes field. The form validates client-side and submits to a Cloudflare Worker that formats the data and sends an email via Resend.
The agent implemented the form correctly on the first pass. The Cloudflare Worker required one correction: the agent used a fetch-based email API call that did not work in the Workers runtime. We provided the correct Resend SDK import and it worked on the next run.
Total time on the reservation system, including the integration correction: about 45 minutes.
Timeline
Start of spec writing to deployment: 5 hours 40 minutes. Of that, about 1.5 hours was spec writing and design direction. About 3.5 hours was agent execution. About 40 minutes was human review, iteration, and deployment.
The final site: 8 pages including the legal pages, approximately 1,900 lines of JSX and TypeScript, integrated form handling, and a production deployment on Cloudflare Pages with a custom domain.
What made it work
Two things made the Norden build faster than average for its type: clear visual references in the spec, and a deliberate scope cut on the reservation system.
Every time a spec includes a reference point (a website, a restaurant, an aesthetic that the client already loves), the agent has something concrete to calibrate against. Abstract direction like “premium” or “modern” produces generic results. Concrete references like “imagine the website of a two-star restaurant in Stockholm” produce something specific.
The scope cut on reservations is an example of the principle covered in the scope article: the form delivers the same user outcome as a full booking engine for a demo, at a fraction of the complexity. The full booking engine can be added later if the restaurant actually needs it.