Product Design for AI & B2B SaaS
One high-friction workflow. Handed back dev-ready.
We find where people hesitate on AI and B2B SaaS products, redesign the path to the action, and ship a clickable, dev-ready flow in five days.
- One workflow
- Five days
- Dev-ready
Pay now if you already know the surface. Or 15 minutes to confirm it.
- Delivery
- Five working days
- Price
- $3,000 flat
- Who works on it
- Senior designers only
Selected work
How a week works
Five days, and none of them are a discovery phase.
Fixed scope, fixed price, fixed clock. You know on Monday what lands on Friday, and you see the work as it is made rather than at the end.
What exists at the end of it
The friction point, named and agreed in writing.01Monday
Diagnosis
We walk the workflow with you and name the point where people stop. Analytics if you have them, the product either way.
What exists at the end of itThe friction point, named and agreed in writing.
02Tuesday
Structure
The flow is rebuilt around the action it exists for: what is shown, what is decided, and what comes out.
What exists at the end of itThe new flow, mapped end to end.
03Wednesday
Design
Screens resolved at production fidelity, including the empty, loading, error and edge states nobody scopes.
What exists at the end of itEvery screen and state, resolved.
04Thursday
Prototype
The flow becomes something you can run, so the redesign is judged by using it rather than by looking at it.
What exists at the end of itA prototype your team can click through.
05Friday
Handoff
Everything is handed over on the day, with a prioritized list of what we found and deliberately did not touch.
What exists at the end of itFigma, specs and the rationale, in your hands.
Working with us
Two ways in, priced before you ask.
The Sprint takes the one workflow costing you the most and rebuilds it. The Partner engagement holds the bar across everything you ship. Neither is a trial of the other.
5-day product sprint
Fixed scopeOne high-friction workflow, diagnosed and handed back dev-ready.
- Diagnosis. Where people hesitate in the workflow, and why.
- Redesign. Resolved down to states and edge cases.
- Prototype. Clickable, not a static comp.
- Handoff. Dev-ready Figma, specs and the rationale behind each call.
One product workflow. Not a landing page, and not an unlimited request queue.
- One workflow
- Five days
- Dev-ready
We scope the workflow before the week starts. If it isn’t one flow, we say so.
Ongoing
Product Partner
- One primary workstream, held from one release to the next
- A weekly working session with the designer doing the work
- The design system held while the product keeps moving
- Month to month. Pause it when the roadmap goes quiet
Who you work with
Jacob Piorecki
Founder. The designer on the Sprint.
You book the call with the person who does the week. No project manager in between, no junior learning on your product.
Questions
Before you start.
What teams usually want to know before sending us a workflow.
Who does the work?
Senior product designers. No account-manager layer, no juniors learning on your product, no handoff between the person you met and the person who designs it.
What counts as one workflow?
One path someone takes to an outcome: onboarding, the demo path, a trial, an upgrade, checkout, an AI output that has to be judged before it can be acted on, or the core action the product is bought for. If you can name where people stall, that is the Sprint.
Do you need analytics access?
It helps and it is not required. Funnel data, session recordings or support tickets tell us where people stop, which saves us finding it ourselves. Without them we work from the product, a walkthrough, and your team’s own account of where deals stall.
What if the problem is bigger than one Sprint?
We say so before you pay. If the workflow is too broad we narrow it to the part carrying most of the friction. Anything larger we find during the week goes on a prioritized list you keep, not on your invoice.
Can you guarantee conversion will improve?
No. Design can remove friction and shorten the path to the action. Conversion also depends on traffic quality, pricing, positioning and fit, so we do not invent numbers we cannot stand behind.
Is this CRO?
No. CRO tests a landing page. The Sprint rebuilds a workflow inside the product, where the hesitation actually happens.
Do you use AI?
Yes, where it makes the work faster: exploring variations, building prototypes, drafting states. It does not make the judgment calls. Everything you receive is decided by the senior designer running the Sprint.
How quickly can we start?
Send the workflow. We confirm it is Sprint-sized, agree the scope in writing, and schedule from there. There is no onboarding process to survive.