Built it with AI?
Now make it work.
Your Lovable, Bolt or Cursor app works, but users get lost and it looks like every other AI app. I’ll fix the parts that matter, in a form your AI tools can build from.



Brands I’ve worked with

I’ve been on both sides
I’ve designed software for 30 years, and I’ve also built my own app, Paak, with Claude Code and no prior coding experience. So I know what AI tools are great at, and where they leave you.
They’re brilliant at getting something working. They’re weaker at the decisions that make it work for people: what goes on the first screen, how a new user finds their way, what happens when something goes wrong, and how it all stays consistent as you add features.
That’s the gap I fill. Not a rebuild, and not a branding exercise: a senior design pass on the parts of your app that decide whether people stick around.
I wrote about shipping an app with Claude Code and why AI has no taste.


A senior review of your app
A clear look at your app as it stands: where users get stuck, what looks generic, and what will break as you grow. You get a prioritised list of fixes, not a 60-page report.
Designs your tools can build from
Fixes delivered as Figma screens, plus the prompts, specs and a lightweight design system your AI tools can follow, with components documented in Storybook if your app is built in React. You keep building yourself without the app drifting back to generic.
Ready for real customers
Onboarding people finish, navigation that makes sense, and the empty, error and loading states AI tools tend to skip. The difference between a demo that impresses and a product people pay for.
Services
I work on the part of SaaS products users actually live in: dashboards, workflows, complex interactions and design systems. Project engagements for founders shipping new products, and one-day-a-week retainers for product teams that need senior design without the full-time hire.
Read about my UX design process or hiring an independent designer vs an agency.

Work
Recent projects across SaaS, enterprise and AI products.
Some of it under NDA, so what's here skews toward the work I can show. It's the kind of work I wrote about in why I design business apps.
Things I've built
Small tools I've designed and built for problems I had myself.
Tiidy · macOS app
A tidier menu bar.
My menu bar kept filling up with icons I rarely used. Tiidy hides them until they're needed, and lets the apps I seldom open go quiet.
Frequently asked questions
Usually not. Most AI-built apps have sound foundations and weak spots in the experience. I focus on the screens and flows that matter most, and deliver fixes you can apply with the tools you already use.
Whatever you've built with: Lovable, Bolt, Replit, v0, Cursor or Claude Code. I build with Claude Code myself, so I hand work back in a form these tools can use: prompts, specs and components, not just pictures. For React apps, I can document the design system in Storybook, so your AI tools and any developers you bring in build from the same components.
AI tools default to the same component libraries, layouts and colours, so the apps they produce share a look. A designer gives yours a clear hierarchy and visual language that fits your product and the people using it.
Yes. I explain design decisions in plain language and hand over changes in a form you can paste into your tools, so you can keep building yourself.
It depends on the size of the app and what needs fixing. I scope the work before we start so there are no surprises, and I'm upfront about pricing once I've seen what you've built.
Before you put the app in front of paying customers, or as soon as early users start getting stuck. Fixing the experience is much cheaper before the app has hundreds of screens and a user base used to its quirks.
Get in touch
👋 Hello, I live in sunny Perth, Western Australia.
If you've got a project in mind, send me a message and I'll reply within a day. If it makes sense to talk after that, we can book a short chat or grab a coffee in Perth.








































