Approach
How an engagement actually runs.
Statin is a small studio on purpose. The method is there so a founder can see the work, change it in time, and leave with something the company can operate.
01 · Week 0
Brief
A working session and a written scope. You see the plan, the boundary, and the team before anyone designs a screen.
02 · Weeks 1–2
Shape
Information architecture, the key flows, and a visual direction you can react to with specifics.
03 · Weekly
Build
One environment, one lead, a demo every week. Scope changes are written down before they enter the work.
04 · Handoff
Launch
Access, measurement, documentation, and the first month of stewardship so launch is not the last conversation.
Working rules
The cadence is part of the product.
A weekly review, forty-five minutes
Working software or a decision that unblocks it. We do not spend the meeting rereading last week’s notes.
One decision log
Scope, open questions, and changes live in a record. If it is not written, it is not in the build.
You approve the words
The offer is yours. We draft structure and interface copy. You approve anything a customer will read.
No six-week reveal
You see the work while it can still change. A surprise at the end is a missed week, not a presentation.
- 01A founder, or one person who can decide, in the weekly review.
- 02Access to the current site, product, or store, and to the people who fulfill orders or support users.
- 03The commercial facts: who pays, what the first release must do, and what can wait.
- 04A willingness to cut. The date depends on the boundary.
