Idea to working prototype in a week: what we actually do each day

A working prototype in a week sounds ambitious. With a clear daily rhythm, AI-accelerated build tools and the right people in the room, it is a dependable way to test an idea with real users before anyone commits a serious budget. Here is what each day looks like.

Why a week?

A week is long enough to build something people can genuinely use, and short enough that nobody becomes attached to the wrong idea. It forces decisions. It also fits the principle at the heart of The Lean Pivot: test the riskiest assumption first, cheaply, and let evidence decide what happens next.

Monday: clarify

We start with the problem, the user and what success would look like. By the end of the day we have a short brief: who the prototype is for, the one job it must do well, the assumption we most need to test and how we will know whether it worked. Everything else waits.

Tuesday: map

We sketch the user journey from first contact to the moment of value, then choose the smallest set of screens and features that let a user complete it. Anything that does not serve that journey goes on a later list. We also book the users who will test on Thursday.

Wednesday: build

This is where modern AI-assisted design and build tools change the economics. A working, clickable prototype with realistic content and data takes shape in a day. It is real enough to use, and it is built to be thrown away or rebuilt properly if the idea earns it.

Thursday: build and test

In the morning we finish and polish the flows that matter most. In the afternoon, real users try it while we watch. We ask them to complete the journey, listen to what they say and note where they hesitate. Small fixes go in between sessions.

Friday: decide

We bring the findings together for the sponsor: what users did, what surprised us and what the evidence says about the core assumption. The output is a clear recommendation to build, change or stop, with a scoped next step if the answer is build.

What makes it work

• A decision maker on hand: someone who can make calls on scope the same day.
• Real users booked early: testing with the people the product is for.
• A narrow brief: one job done well beats five done partly.

Prototypes are as useful for internal tools and client portals as they are for new products. If you have an idea that keeps coming up in meetings, a one-week sprint is a low-risk way to find out whether it deserves a budget. Our rapid prototyping service explains how we run them.