Product UI Build: a design system and your key flows, in code by Pedro GuarizeProduct UI Build: a design system and your key flows, in code by Pedro Guarize
Product UI Build: a design system and your key flows, in codePedro Guarize
Your product’s core UI, designed and built once: the design system as production components, and the key flows on top of it, with every state designed. Four to eight weeks.
Best fit if
You’re building your core UI, or rebuilding it, and want it right the first time.
Your product uses AI and needs streaming, review and undo designed properly.
Not a fit if
You need backend or infrastructure work.
Your product exists and needs finishing, not building. That’s a Polish Sprint.
What you get
Tokens and components, with every state designed.
The key product flows, keyboard first.
AI interfaces where the product needs them: streaming, review, undo.
At handover
Tokens and components in your repo, every state designed: hover, focus, disabled, loading, empty, error.
A Storybook with every component and state, documented.
The key flows built in your app, tested and keyboard first.
Docs and a handover call, so your team can extend the system.
Done before
Two years as the only frontend engineer at an AI security startup, from first commit to a $15M Series A: the design system, every page and the core product flows.
How it runs
A 30-minute call: the goal, the deadline, who decides, the budget range.
A proposal within 48 hours, with three options: small, recommended, full.
Half to start, on a signed scope. Half on delivery.
A weekly update with a short video and a staging link.
Three rounds of revisions.
See it done
A checkout is reviewed in five changes as you scroll, each one yours to keep or drop. It’s in my Work: “Your call”.
Your product’s core UI, designed and built once: the design system as production components, and the key flows on top of it, with every state designed. Four to eight weeks.
Best fit if
You’re building your core UI, or rebuilding it, and want it right the first time.
Your product uses AI and needs streaming, review and undo designed properly.
Not a fit if
You need backend or infrastructure work.
Your product exists and needs finishing, not building. That’s a Polish Sprint.
What you get
Tokens and components, with every state designed.
The key product flows, keyboard first.
AI interfaces where the product needs them: streaming, review, undo.
At handover
Tokens and components in your repo, every state designed: hover, focus, disabled, loading, empty, error.
A Storybook with every component and state, documented.
The key flows built in your app, tested and keyboard first.
Docs and a handover call, so your team can extend the system.
Done before
Two years as the only frontend engineer at an AI security startup, from first commit to a $15M Series A: the design system, every page and the core product flows.
How it runs
A 30-minute call: the goal, the deadline, who decides, the budget range.
A proposal within 48 hours, with three options: small, recommended, full.
Half to start, on a signed scope. Half on delivery.
A weekly update with a short video and a staging link.
Three rounds of revisions.
See it done
A checkout is reviewed in five changes as you scroll, each one yours to keep or drop. It’s in my Work: “Your call”.