You know how everyone knows when something was written with AI because of the em dash? Same goes for AI design. Drop shadows everywhere. Gradients on every button. Border radius so aggressive it looks like a Fisher-Price toy. If you know, you know.
The good news: most of these are one-prompt fixes. And once the visual defaults are gone, your app stops reading as a prototype and starts reading as something someone actually thought about.
Why this matters before you launch
Branding isn't just what your product looks like. It's whether your product feels like someone made deliberate decisions about it. Users can't always articulate why something feels unfinished — but they feel it immediately, and it affects conversion, activation, and retention before most of them can name what's wrong.
The gap between a product and a prototype isn't features. It's intentionality.
Signals of a real product:
- UI that looks considered — at least a few deliberate decisions that differ from the AI defaults
- Consistent fonts, colours, and border radius everywhere
- A real logo, not the app name in the default typeface
- No gradients on buttons or backgrounds
- Sentence case throughout
Signals of an AI experiment:
- Default UI with no visual decisions changed
- Drop shadows on every card
- Large rounded corners on everything
- Title Case On Every Heading
- One font used for everything
- A placeholder logo
The difference between these two lists is not design skill. It's whether someone ran through a 45-minute fix list.
Step 1: Remove drop shadows on cards
Drop shadows on cards are dated — a 2017 trend that hasn't aged well. Modern web design uses borders and background colour to create separation instead.
Prompt your builder:
Remove drop shadows from all cards and replace them with a 1px border using a subtle grey (#E5E7EB or similar). Keep the background white.
Step 2: Reduce the border radius
AI builders default to a very large border radius — usually 20px or higher. It makes everything look rounded and soft in a way that reads as unpolished.
12px or 16px is the sweet spot for most SaaS products. Tight enough to look intentional, not so tight it looks corporate.
Prompt your builder:
Change the border radius on all cards, buttons, and input fields to 12px.
Step 3: Switch everything to sentence case
Title Case On Every Heading Looks Like A Presentation From 2015. Sentence case is more modern, easier to read, and how most design-forward products write today.
If font styles were generational: Gen Z does lowercase. Millennials do sentence case. Gen X does Title Case. Pick your side.
This one is easy to miss because it's subtle — but once you see it you can't unsee it.
Prompt your builder:
Change all headings, button labels, navigation items, and UI copy to sentence case. Only proper nouns should be capitalised.
Step 4: Remove all gradients
Gradients on buttons and backgrounds are the single clearest "this was built by an AI" signal right now. They were having a moment. The moment is over.
Flat, solid colours look more confident and more modern. If you want depth, use subtle background tints between sections — not gradients.
Prompt your builder:
Remove all gradients from buttons, backgrounds, and cards. Replace with solid colours from the existing colour palette.
Step 5: Add a second typeface
One font used for everything — headings, body, labels, buttons — is one of the clearest signs a product came from an AI builder unchanged. A two-font system makes a noticeable difference with almost no effort.
The combination that works for almost everything right now: a mono font for labels, eyebrows, tags, and small UI elements, paired with a clean sans-serif for headings and body copy.
Good pairings:
- Geist Mono + Geist
- JetBrains Mono + Manrope
- JetBrains Mono + Inter
Prompt your builder:
Set up a two-font system: use [MONO FONT] for labels, eyebrows, tags, and small UI text. Use [SANS-SERIF FONT] for headings and body copy. Both are available on Google Fonts.
Step 6: Make a real logo
The app name in the default font is not a logo. It's a placeholder. You don't need something elaborate — a simple wordmark in a custom typeface or a minimal icon is enough.
Options that don't require a designer:
- A custom wordmark — take your app name, pick a distinctive typeface (not the one your app defaults to), set it manually
- A simple icon in Figma — a geometric shape or symbol you spend an afternoon on
- Looka — AI logo tool, produces something usable fast
A real logo signals deliberate decisions were made. That matters more than it sounds.
Step 7: Set your colour palette
Two or three colours. That's it.
One primary colour that carries most of the work — buttons, links, key UI elements. One neutral for backgrounds and borders. One accent if you need it.
Most AI builders default to the same blues and purples. Pick something that isn't that. Check it works on both light and dark backgrounds before you commit.
What to avoid:
- More than three colours in active use
- Gradients (see step 4)
- Using your primary colour for everything — it loses meaning
Step 8: Check the positioning layer
Once the visual defaults are fixed, the next thing that makes an app look unfinished is vague positioning. Generic hero copy, no clear audience, no outcomes on the landing page.
Ask yourself:
- Who is this specifically for?
- What does it do for them that nothing else does as well?
- Is that obvious within 5 seconds of landing on the page?
If the answer to any of those is no, the design won't save it. But fix the visuals first — it's faster and makes the positioning problems easier to see.
Checklist
- Drop shadows removed from all cards
- Border radius is 12–16px everywhere, not 20px+
- No gradients on buttons or backgrounds
- All headings and UI copy in sentence case
- Two typefaces set up and applied consistently
- Real logo exists — not just the app name in the default font
- 2–3 brand colours in use
- Hero copy names a specific audience and outcome
- Landing page and app UI feel consistent with each other
Prompt: Un-AI my design
Take a screenshot of your app and upload it with this prompt:
Here's a screenshot of my app. I want it to look less like a default AI build and more like a considered product design.
Specifically: 1. Identify every default AI design pattern you can see (drop shadows, gradients, large border radius, title case, single font, placeholder logo) 2. Tell me what to change and what to prompt my builder to fix each one 3. Prioritise the list by what will have the biggest visual impact
FAQ
Do I need a designer?
No. Not at this stage. The fixes above require no design skill — just a willingness to prompt your builder and spend an afternoon. Hire a designer when you have revenue and a clear product direction, not before.
How long does this actually take?
45 minutes for the core fixes if you're moving. Two hours if you're doing the full setup including logo and copy. That's it.
What if my app has a lot of screens?
Fix the most visible ones first: landing page, login, dashboard, and your core feature screen. Then work outward. You don't need to fix everything at once — you need to fix what users see first.
Does visual design actually affect conversion?
Yes. Not because users are judging your pixel work — because inconsistent design signals that something wasn't thought through. And if this wasn't thought through, maybe the product wasn't either. Users can't always name it. They act on it.
What's the single highest-impact change?
Removing gradients and drop shadows in the same prompt. It's the biggest visual shift for the least effort and the clearest signal that you've moved past the defaults.
What fonts should I use?
Manrope or Inter for headings and body. Geist Mono or JetBrains Mono for labels and UI elements. All are free on Google Fonts, all are used by real products, none of them will date quickly.
What if I don't have a logo yet?
Set your app name in a typeface you chose deliberately — not the one your builder defaulted to. That's enough to ship. Upgrade later.