Home
Work
Method
Services
Experience
Book a call

Five stages.
Weeks not months.

Every engagement runs a version of this sequence. Short ones compress it, long ones repeat stages three and four.

01
Co-creation discovery
Who the users are, what the constraints are, what success looks like. Ends in a blueprint embodied by an agent you can argue with.
1–5 DAYS
02
Brand & language
Type, colour, tone and the visual language, settled before screens exist. Building on your existing brand or from scratch, we ideate with AI in the room and human craft brings it home.
3-21 DAYS
03
Design & build
The core flows, built as working software on real data. Deployed where your team can open it. Full interaction, database, logins. A functional app or website.
2–6 WEEKS
04
Research rounds
Each round ends with a list of what broke and an evolved build, not a report. Low doc, instant impact.
1 DAY EACH
05
Handoff
Front end code, design system, specs, assets and the reasoning, structured for a team and their agents to continue the build.
DELIVERABLE

The code is the source of truth.

BRAND
FIGMA
GOALS
SPECS
RESEARCH
AI ENABLED
DESIGN PROCESS
PROTOTYPE
USER TESTING
HANDOFF
AGENT
GITHUB
ITERATION
SCREEN FLOWS
Scroll the diagram →
FIGMA
BRAND
GOALS
SPECS
RESEARCH
AI ENABLED
DESIGN PROCESS
PROTOTYPE
USER
TESTING
HANDOFF
AGENT
GITHUB
ITERATION
SCREEN FLOWS
Questions
Is the prototype throwaway code?
+

No. It's a working spec: every screen, interaction and piece of copy is already resolved and clickable. A code agent takes that spec, the styles, the patterns, the interactions, the responsive layouts, and rebuilds it in whatever framework your codebase already runs on. What survives is everything you validated to get here, as front end code; what changes is the plumbing underneath.

We already have Figma files. Are they wasted?
+

No. These assets feed our workflow but aren’t the source of truth post-prototype; the codebase is authoritative. Managed on GitHub, designs can be visualised in Figma or another canvas for collaboration and feedback.

How is this different from a prompt-to-app tool?
+

Platforms like Bolt or Lovable will generate an app that runs. They will not decide what goes into the product, what to cut, and how to best execute. I work mainly in Claude Code/Design and pull into the stack what is needed for the job. Full agility in a fast moving landscape is key. You leave with a design system and a repo and a front-end you can keep and build on.

Can you work inside our existing codebase?
+

Yes. With access to your repository, the prototype is built on your stack, your components and your conventions from the first day.

What if research shows the idea does not work?
+

Then you found out in weeks, for the cost of a prototype rather than a build. Most rounds change the product rather than end it, and the research record shows what users responded to and what is worth trying next.

Who owns what at the end?
+

You own all design, code, assets, research and specifications produced for your project. I share but keep IP of my starting templates, AI skills, harnesses and methods that are project agnostic.

Bring the idea at whatever
stage it is in.

Book a call
Experience →
SYDNEY · ABN 46 110 078 950 · © 2026