On day 6 you send your notes — all of them, in one go, from the one person who decides. We fix them the same day. On day 7 the files are yours. It sounds strict. It's the reason the week ends when it says it will, and in practice it's the kindest rule we have.
The reason
rounds multiply.
Open-ended feedback has no natural end. Every round brings a reply, every reply brings a round, and a one-week job becomes a six-week one without anyone deciding it should.
It's rarely anyone's fault. Five people look at the screens on five different days and each sees something different. The designer fixes the first note, which un-fixes the third. By round four nobody remembers what the brief said.
One round, from one voice, moves the hard conversation where it belongs: inside your team, before it reaches us. What arrives on day 6 is a decision, not a debate.
Day 1–5
you're not waiting in the dark.
One round of notes doesn't mean one look. You get updates on WhatsApp as the week goes, and you can see the system and the screens take shape. You just save your verdict for day 6, when there's a whole product to judge instead of a corner of one.
Good notes
how to write them.
- Collect everyone's notes first, then send one list.
- Point at the screen and the state: “Settings, empty state”.
- Say what's wrong, not only how you'd fix it — “this hides the price” beats “make it bigger”.
- Mark what's a must and what's a maybe.
- Check the brief before you write: if it's a new flow, it's not a note.
“one voice, one list, one day.”
The edges
notes, or new scope?
A note changes something we drew. New scope adds something we didn't: a flow that wasn't in the brief, a new role, another product. Small changes ride with the day-6 notes; anything bigger than the brief after day 1 moves to a new week.
With code or Framer there's a second round on day 13, for what the build changes, and the handoff moves to day 14.
The exit
and if you don't love it.
Tell us before the handoff on the last day. You get 50% of what you paid back and keep the work made so far. No form, no call — one email to hi@weekone.dev.
We'd rather hear it than have you sit on a file you don't like. The rule that keeps the week short also keeps the exit simple.
your week could be next.
Pick your week