A portfolio that shows process
Most portfolios show final screens. Yours shows the research that justified them, the system they were built from, and the product that shipped. That is the part hiring managers say is missing.
Deliverables
Fourteen
Fourteen
finished things,
all of them
yours
No vague learning outcomes. Every week ends with a concrete artifact you produced: a document, a Figma file, a working screen, a live product. By week 12 you have a portfolio and an app in the store.
You leave with
- Strategy documents
- 3
- Figma files
- 3
- Live app
- 1
- Landing page
- 1
- Store listing
- 1
01 · The parts list
Every artifact, week by week
Weeks 11 and 12 each produce two, which is why fourteen deliverables come out of twelve weeks.
Problem Brief
Document
01
A one-page document that forces you to say exactly who your user is, what problem they have, and why the things that already exist fall short. You come back to it every week to check you are still building the right thing.
Product Brief
Document
02
The scoped plan. Competitive landscape, positioning, and a prioritised MVP: the five things your app must do, and nothing else.
User flow diagram and wireframes
Figma file
03
Every path a user can take, mapped before a single colour is chosen, with lo-fi wireframes of each primary screen.
Design system
Component library
04
Brand, tokens and a component library in Figma. This is the file you can hand to a developer or keep extending yourself.
Hi-fi screen designs
Figma file
05
Every core screen, polished to production quality.
Clickable prototype and test report
Prototype and document
06
An interactive prototype, put in front of real people, and a written record of what they did with it.
Running app shell
Live code
07
A real app running on a real device, with your first screen working.
Working backend
Live database
08
Accounts, database schema and API calls deployed on Supabase.
MVP feature complete
Working app
09
The three to five features that define the product, all functioning.
Beta build and testing report
TestFlight build
10
A build in real testers hands, and what they reported back.
App Store listing
Store ready
11
Screenshots, description, keywords and a submitted build.
Marketing landing page
Live website
11
A live site with your story and a working waitlist or download link.
Live app and public launch
Shipped
12
The product, public, with real users on it.
90-day growth plan
Strategy document
12
What you do after launch, written for your product specifically.
02 · Afterwards
What this is worth outside the program
A product with users
A live app in a store, with real people using it, is a different conversation from a concept piece. It is also yours to keep building.
A design system you can reuse
Tokens, components and documentation in Figma. The next thing you make starts from this rather than from nothing.
Evidence you can finish
Twelve weeks of dated deliverables is a record of following something through, which is the thing an unfinished side project can never demonstrate.
Bring the idea
Leave with the app
The planning session is free and one to one. If this is not the right fit for what you are trying to build, you will leave knowing that.
At a glance
- Cohort 05 starts
- Sept 7, 2026
- Last day to register
- Aug 24, 2026
- Tuition
- Was
$2,400, now $1,200