Hello, I’m Iona
a product designer
I design and build product interfaces for B2B software teams. 31 shipped products in four years, 9 of them now past Series A.
24
Clients since 2022
4.9/5
Average rating
Recent clients
I have been a product designer for eleven years, the last four of them independent, working from Austin. Before that I sat inside product teams at Quorum and Marlow, which is where I learned what a design costs to build.
I work in Figma and in code. Most engagements run six to twelve weeks and end with a component library your engineers can install the same day, alongside the source file and a written handover.
Experience
Product designer, independent
2022 to now
24 clients, seed to Series B software. I run the whole surface: research, flows, UI, and the component library the team builds from.
Senior product designer, Quorum
2019 to 2022
Owned the payments dashboard. Rebuilt the dispute-response flow and cut support tickets about it by 41 percent in one quarter.
Product designer, Marlow
2015 to 2019
Redesigned onboarding across 11 markets. Time to a first completed task fell from 9 minutes to 4.
Four ways to work together
01.
Product UI design
Screens, states and flows for the part of your product people touch every day. The Figma file ships with every empty, loading and error state drawn, so nothing gets invented during the build. One surface, four to six weeks.
02.
Design systems
Tokens, components and the rules for using them, built to match how your engineers already write code. Handover includes a Storybook-ready component list and a written spec for spacing, type and colour. Teams typically halve the time it takes to build a new screen.
03.
Research and testing
Five to eight moderated sessions with people who actually use your product, recorded and transcribed. You get the raw clips, the full transcript and a ranked fix list with an effort estimate written against every item. Two weeks from kickoff to report.
04.
Design engineering
I build the front end for what I design, in React or in Framer, so the page that ships matches the file that was signed off. Best used for marketing sites and for the first version of a product surface. Priced per page.
What lands in your drive
Built in the tools your team already runs
Figma
The working file, in your workspace, with edit rights for your whole team.
React
Components typed in TypeScript, no styling library you have to adopt.
Storybook
Every component with its states and props documented and running.
Framer
Marketing pages you can edit without opening a pull request.
GitHub
Code lands in your repository, under your licence, from the first week.
Linear
Design tickets written in your board, in your format, sized by me.
Four recent projects
Ledger, billing dashboard
Rebuilt invoicing for a 40 person fintech. Time to send a first invoice fell from 6 minutes to 90 seconds.
Cadence, clinic scheduling
A booking surface for outpatient clinics. 11,000 appointments booked in the first quarter at a 3 percent no-show rate.
Halo, design system
62 components and 340 tokens for a Series B team. New screens now ship in two days where they used to take nine.
Foundry, marketing site
Site and design system for a developer tools launch. Visitor to signup went from 2.4 percent to 8.1 percent.
Reviews from 24 clients
“Iona redrew our onboarding in five weeks and stayed through the build, reviewing every pull request. Activation went from 31 to 52 percent in the month after launch and has held there since. She left us a component library we still work from.”
Marcus Bell
Head of Product, Ledger Financial
“Four agencies pitched us a design system. Iona’s is the one our engineers actually adopted. New screens went from nine days to two, and every one of them now uses the library.”
Priya Raman
VP Engineering, Cadence Health
“We booked Iona for a two week research sprint and kept her for six months. She ran 34 user sessions, wrote up every one, and turned the findings into a roadmap our board approved without changes. Trial to paid moved from 6.2 to 9.4 percent over that period.”
Daniel Okafor
Founder, Foundry Dev Tools
Fixed prices, quoted before we start
Product UI
One surface in four to six weeks. Flows, every state drawn, a clickable prototype and two rounds of revision. Built for a team that already knows the problem and needs the screens.
Design system
Tokens, components and documentation, built against your codebase over six to ten weeks. Includes the Storybook-ready component list and two hours a week of engineering support for a month after handover.
Research sprint
Two weeks. Five to eight moderated sessions with your users, recorded and transcribed, plus a ranked fix list with an effort estimate written against every item.
Questions people ask before they book
What does a project cost?
Product UI design starts at $12,000 for one surface over four to six weeks. A design system runs $28,000 to $45,000 depending on component count. Research sprints are $6,500. Every quote is fixed before the work starts, so the number you approve is the number you pay.
How soon can you start?
I take two projects at a time. The next opening is usually about three weeks out. I reply to a first message within one business day, hold the call within two, and send a scoped proposal within four days of that call.
We already have a design system. Does that get thrown away?
About half my work starts from an existing system. I audit what you have, keep the components that already carry their weight, and rebuild only the ones your team keeps working around. On the Quorum engagement, 60 percent of the old library survived and the migration ran alongside normal feature work.
Who owns the files and the code?
You do, from the first day. The Figma file lives in your workspace, the code lands in your repository under your licence, and I hand over the source for every asset including any font I licensed for the project. Nothing is hosted on my account and nothing needs my permission later.
How do you handle our users’ data during research?
Recordings live in your storage, never mine. I sign your DPA before the first session, use your consent script, and delete my local copies within 30 days of delivering the report. I have run research under both HIPAA and GDPR and will share the process document before you commit.
What if the direction is wrong?
The first two weeks of any engagement are a paid trial. If you do not like where it is going at the end of them, you pay for those two weeks, keep everything produced, and we stop. Three clients have used that exit in four years.