Portal · Studio · Deliverables
I'm a designer who builds. These three tools run a partner engagement end to end: the portal partners sign into, the studio I run the work from, and the deliverables in between. A quick tour.


Three tools
01·The plan
Every engagement begins as a plan the partner and I both see. Everything downstream hangs off it.
Pye · Phases & scope
02·Deliverables
Everything I ship lands in one place, each as its own page.
Pye · Deliverables
5 of 1203·Comments
Feedback sits on the work itself. They comment, I reply, in one place.
Deliverable · Comments
3 messagesThe phase-2 surface reads cleanly. One nit: the heuristics column on the bug-blitz is heavy for a first-time reviewer.
Good call. Moved it into a hover-revealed reference. Same column, less weight.
Shipped. Reviewing today.
04·Approvals
Approving feels like signing, and behaves like it.
Deliverable · Approval
Three-week audit of the trading product. Signed by both sides; appended to engagement archive.
05·Bug-blitz
A small app for testing software quickly. A few people run through it, and I turn what they find into a clean list of fixes.
Bug-blitz · Cluster
3 reportersHeuristic · Visibility of system status
06·Artefacts
Most of what I hand over is one of these four. Keeping to a few kinds means everything reads the same way, engagement to engagement.
External · linked surface
react
Working sites and software, built fast in React. An idea gets tried, not described.
Figma · prototype
figma
Clickable flows, embedded at the right size and kept to the partner.
Brand audit · Pye
html
Strategy and narrative written as web pages. Read in the browser, forwarded, printed.
Wireframe · live copy
live-copy
A copy editor over the wireframe, for writing and aligning words together in a session.
Closeout
The portal is where partners sign in. The studio is where I run the work. The deliverables are what travels between us.
Portal · Deliverables
Studio · Phases
Marketing · 2026-05-27
Testing the draft tool