Get template
Your design team, awake at 3am: inside an overnight agent run
What happens between the brief you write at midnight and the homepage waiting at breakfast — a full trace of one Atelier build.
Pooja Yadav
Design Lead, Agent Training
At 12:04am on a Tuesday, a founder in Lisbon typed four sentences into Atalier and closed her laptop. She wanted a homepage for a payroll tool aimed at restaurant owners. She wrote that it should feel "calm, not corporate," that her customers open it on a phone behind a bar, and that she had a logo but no brand. Then she went to bed. She woke at 7:12am to a finished homepage, eleven rejected variants, and a short note explaining why the agents had ignored one of her instructions. This is the whole run, minute by minute, with nothing tidied up.
The brief is smaller than you think
Four sentences is not much to go on, and that is the point. Most design briefs fail in the opposite direction: twelve paragraphs that specify a hero layout, a colour, a competitor to copy, and a font someone saw once. The specificity feels like clarity. It isn't. It is a series of answers to questions nobody asked yet.
What her four sentences carried was constraint, not instruction. Calm not corporate is a taste signal. Phone behind a bar is a context that rules out half of modern web design — no hover states doing real work, no dense tables, nothing that needs two hands. Logo but no brand tells the Director agent that colour, type and spacing are open territory rather than a checklist to obey.
The Director spent the first ninety seconds doing nothing visible. It was writing a spec.
Where the night went
The run took six hours and forty-one minutes, but almost none of that was continuous work. Agents wait on each other. The Critic blocks, the Designer reworks, the Director re-scopes. Here is the shape of it.
Stages | Minutes spent per stage |
|---|---|
Brief parsing | 3 |
Direction | 34 |
First layout | 71 |
Critic passes | 96 |
Rework | 148 |
Copy | 42 |
Export prep | 27 |
The largest block is rework, and that is healthy. A run where the first layout survives untouched usually means the Critic was too permissive, and you find out three days later when the page doesn't convert.
6 hr 31 min | Total run time |
38 | Layout revisions |
11 | Variants rejected |
1 | Instruction overruled |
The instruction the agents refused
Her brief said the page should feel calm, not corporate. It also said, in the last sentence, to "use the green from my logo as the main colour."
The agents didn't. The homepage that shipped uses that green exactly twice — once in the logo, once in a thin rule under the pricing table. Everything else is warm neutral.
The note explaining it was three lines long. The logo green was a saturated mid-green that, at the surface areas a homepage needs, reads as institutional: banks, insurance, hospital intranets. Used large, it fought the calm brief directly. Used small, against a warm neutral field, it became a signature instead of a wall.
She could have overridden it in one click. She didn't. That is the part of the run I keep coming back to — not that the agents worked overnight, but that they were willing to disagree with the person paying them, and to say why in plain language at 3:07am.
What you actually wake up to
Not a file. A decision log.
The homepage was there, in the browser, responsive and named properly. But underneath it sat the eleven rejected variants with the reason each one died, the four Critic rework notes, and the single overruled instruction. Twenty minutes of reading, if you want it. Skippable, if you don't.
That's the difference between a generated page and a designed one. A generated page arrives with no argument attached. You either like it or you regenerate, and neither of you learns anything. A designed page arrives with a position — and a position is something you can push back on.
She pushed back on one thing that morning: the testimonial section, which she cut entirely because she didn't have testimonials yet. That took her about nine seconds.