Sprint
A focused product scope. A clear direction.
Everything design for early-stage teams looking for a reliable partner. The first direction takes shape in days. I stay with the work through release.
Start with the product decisions that matter most. Create the clarity, momentum, and product quality that catalyse what comes next.
A focused product scope. A clear direction.
Senior judgment. Your team delivers.
Direction, hands-on design, and ownership.
A complete design function for work moving in parallel.
Start with a Sprint, then continue at the level the work requires.
Tokens, components, patterns, and custom instructions give people and AI tools the same product standards. Your team keeps the system and extends it as the product changes.
Reusable foundations for layout, interaction, components, and product quality.
Reusable instructions teach the team’s AI tools how to create, review, and improve the interface.
The system expands with the product, so new work starts from decisions the team has already made.
Founder-led software teams with engineers ready to build and important workflows that need senior product and design direction.
Teams looking for branding, marketing production, staff augmentation, or someone to run the entire product backlog.
Focus on the product decisions that matter most. In 3–4 weeks, the team has a tested direction, build-ready work, and a foundation for what comes next.
The team has a clear direction, tested work it can build, and a shared standard for quality.
The Sprint outputs feed directly into ongoing work.
If that’s enough, the engagement ends here.
Every level includes senior design direction. The difference is capacity, hands-on work, and who carries the work to release.
For teams that can execute independently but want experienced design judgment.
For teams that need an ongoing design owner before making a full-time leadership hire.
For teams moving several product areas at once and needing a senior design function inside the company.
Every level includes senior design direction. The change is capacity and ownership.
| Area | Sprint | Advisor | Fractional | Design department |
|---|---|---|---|---|
| Hands-on product design | Fixed product scope | — | Two active workstreams | As scoped |
| Additional designers | — | — | — | Led as needed |
| Design-team coordination | — | — | — | Included |
| Interactive prototypes | Included | Review only | Included | Included |
| Build-ready interface code | Where agreed | — | Included | Included |
| Engineering collaboration | During Sprint | Limited | Ongoing | In the team |
| Design-system work | Initial setup | Guidance | Active development | Wider coverage |
| Custom AI design skills | Initial setup | Guidance | Built for active work | Broader implementation |
| Design QA | Agreed scope | Review sessions | Agreed releases | Across workstreams |
| Workstream ownership | Fixed scope | — | Two parallel | As scoped |
| Design capacity | Fixed scope | Advisory | Individual lead | Lead plus agreed designers |
Swipe to compare all four levels →
Early-stage companies, including teams founded by Fortune 500 technology leaders from Silicon Valley. Agentic AI, finance operations, professional services, EV infrastructure, and logistics.
Shaped the product experience and positioning for synthetic AI engineers working in complex industrial operations.
Designed software for EV fleet charging and energy management before the company became part of Ford Pro.
Led product and design across a unified operating system for professional-service firms, from proposals and contracts to billing and client work.
Defined agentic finance workflows for complex multi-location operations. One deployed cash-forecasting process reduced work from 20+ hours to minutes.
Designed for the operational work behind last-mile delivery, including driver and vehicle allocation, on-road rescues, and payroll compliance.
Better decisions become reusable patterns. Reusable patterns become speed, consistency, and product quality the team keeps.
Make important work easier to understand and easier to use.
Less friction. Better activation.Test the path before engineering commits.
Clearer priorities. Less wasted build.Give engineering the detail it needs to build with confidence.
Fewer questions. Less rework.Give the team a shared way to make and review interfaces.
More consistency. Faster delivery.Make the product feel like one product.
Clearer hierarchy. More trust.Teach the team’s AI tools how this product should look and behave.
Faster exploration. Standards remain intact.Review important releases before users see them.
Fewer quality problems. More confidence at launch.Keep the decisions and standards that matter.
Faster onboarding. Fewer repeated debates.Build-ready means agreed front-end surfaces. The engineering team owns integration, architecture, testing, deployment, and ongoing maintenance.
All prices are in USD. Payment, capacity, ownership, and boundaries are agreed before work begins.
Tell me what the team is building and where design leadership would change the outcome.