One Week App

What it can produce

• —Product definition and scope
• —UX flows and screens
• —Positioning and product narrative
• —Basic identity — wordmark, type, colour
• —Landing page
• —Clickable prototype
• —Functional build of the core flow
• —A live domain, configured and pointed

The artifacts serve the decision, not the other way around — which of these a climb produces depends on the Question it resolves.

Details

One week. You arrive with an idea and leave with something people can use, click through, and react to. Most early products die in the gap between the idea and the first thing anyone outside the room can see. Closing that gap normally means a designer, a brand person, a developer and the coordination between all three — and the coordination is usually the expensive part. This compresses it into one week with one person. Day 1 — Intake and definition. What this is, who it is for, and what has to be true for it to work. The week is scoped here and not renegotiated later. Day 2 — UX and product exploration. Wide before narrow: the flows, the screens, and the shapes this could take, explored far enough to rule things out. Day 3 — Brand and positioning. What it is called, how it sounds, and how it looks. This is the last day the week changes shape. Day 4 — Build. Heads-down execution against a settled definition. Day 5 — Launch and handoff. It goes live, and you get everything: the files, the repository, the domain, and the narrative to go with it. You are not buying five days of labour. You are buying the removal of the uncertainty and the coordination that normally sit between an idea and its first real version — and direct access, for the whole week, to one person who does the product thinking, the design, the brand and the build. There is no account layer, no handover between disciplines, and nobody to brief twice.