We start with an audit
I go through your product the way your users do and record what I find on Loom. Within 48 hours you have a ranked list of fixes.
I find where you lose users. Then I fix it.
UX audits, redesigns and the front-end code that ships them. A senior designer who writes the code too, and a price you know before anything starts.
How it works
We fix it in a sprint
We pick the fixes that will move the numbers most. Two weeks later they are designed, coded and live.
We check the result
After launch I look at what changed. If it didn't improve enough, we plan the next sprint. If it worked, that's where it ends.
One checkout page, start to finish
Scroll down to watch one job go from start to finish on a single checkout page.
I mark the problems
Guest checkout sits under the sign-up form, a card error wipes everything, shipping appears on the last step.
I fix them one by one
Guest checkout comes first, the form keeps what people typed, shipping shows in the cart.
We check the result live
The changes are live. We watch completed orders day by day.
A sample checkout page. Guest checkout moves to the top, the card form keeps what was typed, and shipping shows in the cart.
1High
Guest checkout is buried under the sign-up form
Most first-time buyers don't want an account. Put guest checkout first and offer sign-up after payment.
2High
One typo wipes the whole card form
People have to type everything again and many give up. Keep what they entered and show the error next to the field.
3Medium
Shipping cost appears on the last step
Surprise costs are a well-known reason people abandon a cart. Show an estimate in the cart.
Completed orders, today
312
First I find it, then I fix it, then I ship it.
Teams I've worked with. Same prices for everyone.
Pricing
Three ways to start
Not sure what to fix? Start with an audit. If you already know, go straight to a sprint or a project.
Not sure? Let's talkAlways included
- One request at a time
- I aim to deliver each sprint request within 24 hours
- Unlimited brands
- Design, web and mobile development
- Licensed images that fit the project
- Up to 2 users
- Pause or stop whenever you like
Prices are in USD and exclude VAT.
Why teams work with me
You talk to the person doing the work
There's no account manager in between. When you message, I answer, and I'm the one who opens the pull request.
Research and code in one head
Most studios split this between people. I don't, so nothing gets lost between the audit and the code.
The price is clear up front
You see the number before we start. It only changes if the scope does, and we agree on that in writing.
Small on purpose
AI tools do the repetitive work. My time goes into the decisions.
Stop whenever you like
No monthly retainer. You can take one audit and leave.
Code that holds up as you grow
I write to SOLID principles, set up a design system and build with components. When the product grows or your team takes over, nobody has to start again.
How this compares
| Feature | UX agency | Design subscription | ux.center |
|---|---|---|---|
| Finds the problem (research, audit) | Yes | No | Yes |
| Designs the fix | Yes | Yes | Yes |
| Writes the production code | Sometimes | No | Yes |
| Price known before you start | No | Monthly fee | Yes |
| You talk to whoever does the work | Rarely | Usually | Yes |
What do you need?
Pick an option and write a few lines. I reply within one business day: a payment link for audits, a fixed quote for everything else.
Teams I've worked with
Who does the work?
I do. I'm Sezer: I do the research, the design and the front-end or mobile code. I use AI tools to move faster, but nobody else touches your project.
How is this different from a design subscription?
A subscription hands you design files on request. I first find out what's hurting your numbers, then design the fix and ship it as code.
Can I buy just the audit?
Yes. Plenty of teams take the audit and build the fixes themselves. If you book a sprint within 30 days, I credit the audit fee.
Can our own team take over the code later?
Yes, I write it that way from day one. The code follows SOLID principles, the UI is built from reusable components in a design system, and everything lives in your repo. Adding a screen means putting existing pieces together, so nobody has to start over as the product grows.
What do you build with?
Usually whatever you already use. Most often React or Next.js, Vue, Webflow, Framer, and React Native or Flutter on mobile. I work in your repo.
How do I pay?
Up front, by card. Audits and sprints are paid through Whop. For a fixed-price project I send a payment link once you approve the quote.
Will you sign an NDA?
Of course. Send yours before you share anything sensitive.
Not sure where to start?
Give me 15 minutes. We'll look at your product together and I'll tell you honestly whether an audit, a sprint or neither makes sense.