how we run a six-week prototype
six weeks is not very long. that is the point. here is how we shape an engagement so the calendar does most of the work.
most of our prototype work runs six weeks. that is short by industry standards and intentionally so — the deadline forces every meeting, every screen, every line of code to be necessary.
week one
we read whatever you have, talk to two or three users, draw the smallest end-to-end loop on a wall. by friday we have a written brief, signed off in email. nothing fancier.
weeks two through five
we ship one demo every friday. each demo is a real, deployed url, not a slide deck. you click through it on your phone over the weekend.
week six
we lock the scope on monday. tuesday and wednesday are bug bash. thursday is a clean handover — repository, runbook, and a 30-minute walkthrough on video.
by friday afternoon you own a thing that works, the documentation it needs, and a clear list of what we did not build and why.