Let’s talk
Menu

Engagement & pricing

One senior partner.
A queue of real problems.

I bring hands-on product strategy and UX, prototypes and design-system work to your team. Choose an ongoing subscription or a fixed-scope project. Subscriptions keep one main priority active at a time.

Before we start

Start, pause, resume, or cancel anytime. No contracts. We confirm scope, responsibilities and availability before starting.

Design

$5,000/ month

For teams that need help deciding what to do, and someone senior to design how it should work.

  • Strategy & product decisions
  • Flows, prototypes & interface design
  • Design systems & implementation guidance
  • Unlimited queued requests, one active priority

Design + Build

$9,000/ month

Everything in Design, plus agreed frontend implementation in your codebase, with testing and release support through your team’s process.

  • Everything in Design
  • Frontend implementation & testing
  • Agreed launch or release support

Fixed-scope project

Starting at $20,000

A focused project with an agreed scope. The final quote is based on scope.

The partnership, in practice

So what do I get?

Think of me as your principal design partner: fractional, and focused on the hard parts.

You have a backlog, a few ambiguous problems and work that’s hard to move forward. When we start, I help you sort what matters, and we take the backlog on one priority at a time.

You get judgment about what to do next, and the hands-on work to do it. Someone to challenge assumptions, make trade-offs explicit and keep the product coherent while it changes.

Choose a plan to see work examples

Design plan examples

  1. You bring

    An unclear product problem

    What I do

    Work through the options with you, make the trade-offs clear and recommend the next useful move.

    What you’re left with

    A decision your team understands, and a plan for the first step.

  2. You bring

    An awkward user flow

    What I do

    Map and prototype the flow, design the screens and refine them with your feedback.

    What you’re left with

    A reviewed prototype and screens your engineers can build from.

  3. You bring

    A design system with gaps

    What I do

    Untangle the patterns and define how components should behave.

    What you’re left with

    Usable guidance and component specs your team can apply.

Pace depends on complexity, inputs and feedback. For each priority we agree the scope and next review point. Larger projects arrive in useful stages.

Showing examples for Design.

How a priority moves

From the queue to done,
in the open.

The same rhythm on both plans. Design + Build adds implementation inside step three.

01

Queue

You add requests, questions and ideas as they come up. No limit, no formal brief.

02

Choose

We pick the active priority together and agree its scope and next review point.

03

Work

I do the thinking and hands-on work, sharing progress as we go.

04

Review, then next

While you review, I start the next ready request. Your feedback goes back into the queue.

Transparent scope

A focused way to work together.

The subscription model

  • Unlimited queued requests
  • One active priority at a time
  • Strategy and hands-on work from the same person
  • Scope and next review point agreed for each priority

Not promised on this page

  • Start dates and availability
  • Guaranteed hours or fixed turnaround times

Scope, start dates and availability are confirmed before work begins.

Questions

About the model.

Is there really no limit on requests?

There’s no cap on what you add to the queue. That is different from unlimited work at once: I work on one active priority at a time, and we choose the next ready request together.

How fast will each request be done?

Pace depends on complexity, inputs and feedback. We agree the scope and next review point for each priority. This page does not promise fixed hours or turnaround times.

What counts as frontend build?

Frontend work in your existing codebase, through your access, code review and release process. Release depends on your approvals, environments and integrations being ready. Backend services, infrastructure and data work stay with your engineers unless we scope them separately.

Which plan should we start with?

Start with Design if your team needs senior strategy and design alongside your engineers. Consider Design + Build if you also need agreed frontend work in your codebase. We discuss fit, access and responsibilities before choosing.

How does this relate to the design system audit?

The audit is a focused way to inspect your current system and decide what needs attention. The monthly partnership is an ongoing model for prioritized strategy and hands-on work. We can discuss which starting point fits your team.

See the work behind the approach

Next step

Talk through your backlog.

Bring the list, or the one problem at the top of it. We’ll look at fit, which plan makes sense and what the first priority would be.

Book a 30-minute intro

No obligation to proceed.