Services
Your product, easier to use. Your business, easier to buy from.
Nine years designing for companies like Softplan, Grupo Boticário and Franklin Templeton. Besides my full-time job, I take on a few projects at a time, with scope and timeline agreed before I start.
What are you working on?
A product feature, from diagnostic to launch
About 9 weeks- Week 1
Diagnostic
Immersion, usage data, audit of the current product.
- Weeks 2–3
Strategy
Journey, success metrics, flows and wireframes.
- Week 4
Research
Interviews and tests with real users.
- Weeks 5–8
Design
High-fidelity UI, prototype tested with five users, handoff.
- Week 9+
Launch
Design QA, telemetry check, first read of the metrics.
Not sure where to start? The one-week diagnostic is a good first step.
-
- 1 week
- Good first step
Users get stuck and you don’t know where?
Product UX diagnostic
In one week, a clear list of what gets in your users’ way, ranked by what it costs you.
Ask about this → (opens in new tab)What’s included
Heuristic evaluation of key flows, usage data read, findings ranked by severity and impact on the metrics you track.
-
- 1–2 weeks
Building on guesses about your users?
User research
Five conversations with real users, and a readout your team can act on the next day.
Ask about this → (opens in new tab)What’s included
Plan and script, recruitment, five moderated sessions, recurrence analysis across sessions, readout.
-
- 1–2 weeks
Too many ideas, and no clarity on which one matters?
Product strategy
A shared view of the problem, the opportunities in priority order and how you’ll know it worked.
Ask about this → (opens in new tab)What’s included
Problem framing, user journey, prioritized opportunities and success metrics agreed with stakeholders.
-
- 2–4 weeks
A new feature that has to work the first time?
Feature design
Screens tested with five users before development, and support while your developers build them.
Ask about this → (opens in new tab)What’s included
Flows, high-fidelity UI, prototype tested with five users, handoff and design QA with your developers.
-
- 2–3 weeks
Lots of data, few decisions?
Decision dashboard
A dashboard built around the decisions your team makes, tested so everyone reads the numbers the same way.
Ask about this → (opens in new tab)What’s included
Decision and indicator mapping, five user interviews, accessible visualization components, comprehension test.
-
- 1 week
No idea how people actually use your product?
Telemetry plan
A plan for what to measure and where, so your team can see usage from day one.
Ask about this → (opens in new tab)What’s included
Events and properties, funnels and usage indicators, documentation validated with your developer.
-
- 1–2 weeks
Every screen looks a little different?
Design system audit
An inventory of what you have, what’s inconsistent or inaccessible, and a cleanup plan in priority order.
Ask about this → (opens in new tab)What’s included
Component and token inventory, inconsistencies and accessibility gaps, a prioritized cleanup plan.
-
- 3-month minimum
Want steady improvement without a new hire?
Monthly evolution
Every month, a look at your data, one round of improvements and a written report.
Ask about this → (opens in new tab)What’s included
Monthly data read, one improvement round, written report.
Companies I’ve designed for
What you can count on
Revisions
Two rounds per deliverable.
Support
30 days after any site or automation launch.
Ownership
Files and code are yours.
Out of scope
Branding and social media. I refer trusted partners.