A spreadsheet nobody could audit, an old editor people kept going back to, a sales centre that closed at six. Each one was somebody solving a problem the product wouldn't. All three start with what the research turned up and end with the interface that shipped.
The old Pricing Library couldn't bundle, tier, or route an approval, so every quote got rebuilt by hand. I interviewed four mid-market accounts, then replaced it with the Pricing Catalog: folders, search, inline editing, and a detail view that stays one screen for most people.
| Item Name | Price | Billing |
|---|---|---|
| Enterprise LicenseEPL-001 | $24,999 | One-time |
| Managed SupportMS-220 | $1,200 | Monthly |
| Pro ServicesPS-100 | $5,000 | One-time |
V3 was thin enough that people tried it and went back to V2. Weekly interviews with super-users drove two years of work: a real block system, reusable content and custom fields, and a pricing table rebuilt until you could actually quote from it.
| Item | Qty | Total |
|---|---|---|
| Implementation | 1 | $18,000 |
| Support (optional) | 1 | $2,400 |
Three products covering discovering, configuring, verifying and reserving a home without a sales centre. The lesson came from verification: three quarters of buyers who started a reservation never found it at all. Making it follow the reservation took that drop-off from 75% to 45%.
Product design, design systems, and brand work. Fixed scope and fixed price, and I'll tell you on the first call if I don't think it's a design problem.
Research, flows, and high-fidelity UI for one workflow, plus enough time during build to keep it from drifting.
Components and tokens sized to what your team can maintain once I'm gone.
Identity, type, and colour. I design the product the brand ends up wrapping, so I know what it needs to do once it's on a screen.
A read on where people stall, which of those stalls turns into a support ticket, and a fix list ordered by effort against impact.