Sprint
Focused diagnosis and design direction
Senior product and design leadership that grows with your team—from one critical sprint to an embedded design function.
01 The engagement model
The Product & Design Sprint is a focused starting engagement.
After the Sprint, choose how much ongoing design ownership and delivery capacity the team needs:
Focused diagnosis and design direction
Experienced critique without delivery ownership
Judgment plus hands-on design and ownership
Everything in Fractional, plus additional designers brought in to increase velocity and output across more of the product
Each level builds on the one before it. Start with a Sprint. Continue at the right level.
02 Focused starting engagement
For teams that know the product needs work but want to start with focus, improve something meaningful, and make progress through a fixed-scope engagement.
The team has a clear design direction, tested work it can build, and a shared understanding of what good looks like.
The Sprint outputs, including the design direction, principles, system foundation, and priority list, feed directly into any ongoing engagement.
If ongoing design leadership is not needed, the engagement can end here.
03 Ongoing engagements
Progress from advice to direct ownership to a scaled design function. Open any model to see exactly how it works.
For teams that can execute independently but want experienced design judgment.
Your team owns the design and delivery. I help improve the decisions.
Hands-on design, design-system production, workstream ownership, and day-to-day engineering support are not included.
For teams that need ongoing design ownership without hiring a full-time design leader yet.
A workstream is one focused product area or connected feature set. New priorities replace existing priorities rather than being added on top.
I take primary ownership of the design direction, experience quality, and active design workstreams from problem to release.
The founder remains the final owner of business priorities. I will surface prioritisation recommendations and challenge the scope, but full PM ownership and backlog management are a different engagement.
For teams moving several important product areas at once and needing a senior design function inside the company, supported by additional designers brought in to increase delivery velocity and output.
Custom pricing, starting at approximately $15,000 USD/month.
Pricing depends on the number of concurrent workstreams, the number and seniority of additional designers required, and the depth of the design-system, engineering, and automation work.
Starting pricing includes my design leadership and the design capacity agreed in the engagement scope. Additional specialists or capacity beyond that scope are quoted separately.
The number of concurrent workstreams is agreed before the engagement begins and reflected in the final pricing.
I own the design direction, active experience work, system quality, and the working relationship between design and engineering.
I also lead and coordinate any additional designers brought into the engagement, including their priorities, standards, collaboration, and output.
The founder or designated PM retains final prioritisation and roadmap ownership.
04 How the levels build
Every model keeps the senior design direction. The difference is how much hands-on delivery, ownership, and parallel capacity the team needs.
| Capability | Sprint | Advisor | Fractional | Embedded |
|---|---|---|---|---|
| Senior design direction | Yes | Yes | Yes | Yes |
| Product and UX critique | Yes | Yes | Yes | Yes |
| Hands-on product design | One fixed-scope workstream | None | Two concurrent workstreams | As agreed in scope |
| Additional designers | No | No | No | Agreed in scope |
| Design-team coordination | No | No | No | Yes |
| Interactive prototypes | Yes | Review only | Yes | Yes |
| Build-ready interface code | Where agreed | No | Yes | Yes |
| Engineering collaboration | During Sprint | Limited | Ongoing | Embedded |
| Design-system work | Initial setup | Advice | Evolving system | Wider system |
| Custom AI design skills | Initial setup | Advice | Ongoing | Wider automation |
| Design QA | Agreed workflow | Review sessions | Agreed releases | Across workstreams |
| Workstream ownership | Fixed scope | None | Two parallel | Agreed in scope |
| Design capacity | Fixed scope | Advisory | Individual lead | Lead plus agreed designers |
Scroll sideways to compare all models →
05 Tangible design outcomes
The exact output depends on the selected engagement and active product priorities.
The goal is not to produce more design artefacts. It is to help the team make better product decisions, move faster, and create a product that earns or saves more money.
Important existing workflows redesigned to be clearer, easier to use, and ready for engineering.
Flows, screens, interactions, states, and prototypes for upcoming product capabilities.
Production-quality interface code in the same language and framework as the engineering team, including responsive behaviour, edge cases, permissions, empty states, loading states, and error states.
Build-ready interface code covers agreed front-end surfaces. The engineering team owns integration, architecture, testing, deployment, and ongoing maintenance.
Reusable foundations, tokens, components, patterns, and rules that designers, engineers, and AI agents can follow.
A clear standard for layout, hierarchy, typography, spacing, interaction, motion, and product personality.
Reusable instructions that teach the team’s AI tools how to create, review, and improve interfaces using the product’s standards.
Implementation reviews with clear, prioritised fixes before agreed releases.
Important design decisions, the reasoning behind them, and the standards the team should continue using.
These outcomes are created when they support active product work. They are not documentation produced for its own sake.
Success is measured by better product decisions, faster team velocity, less rework, and progress toward relevant commercial outcomes such as revenue, conversion, retention, support cost, or time to ship.
06 Commercial terms
The boundaries protect focus, delivery quality, and the working relationship on both sides.
07 Next step
We’ll establish the right design direction, improve one meaningful part of the product, and leave the team with work it can build.