ExpertsFMHow To Stand Out In A World Of AI Designs
Y Combinator Startup Podcast · October 22, 2026
5 Selected Lessons:
heuristic · 2 framework · 2 priority · 1
Trust/privacy transparency is a rising requirement for AI products with deep data access
Source
Y Combinator Startup Podcast — How To Stand Out In A World Of AI Designs (October 22, 2026) · at 28:15 ▸ · at 31:54 ▸ · at 40:06 ▸
When this applies
when building any product that requires access to sensitive personal or organizational data to function well
The takeaway
When a product's value depends on access to sensitive data, lead with transparent, proactive communication about data handling as a core part of the value proposition, not an afterthought FAQ.
Why it works
As AI products need broader data access to be valuable, user hesitation about privacy becomes the binding constraint on adoption; proactively explaining data use, retention, and security removes that friction and builds the confidence needed to install/share.
One level up
The bottleneck for adoption shifts to trust once capability is no longer the limiting factor.
Where it stops holding
This stops working when the product doesn't need sensitive data access, or in B2B contexts where procurement/security review happens through other channels regardless of landing page content.
Detail
hierarchy:
- 1. Communicate what data is accessed and why.
- 2. Explain how it's used and retention policy.
- 3. State security/on-device/open-source guarantees prominently (e.g., in the hero section).
- 4. Only then pursue deeper feature marketing.
rationale: Alex's own product's 'hero on the landing page was open source, completely on device' messaging was what users 'really, really cared about'; he predicts products that go 'above and beyond' on this will have more success getting downloads and word-of-mouth.
In their words
My take is that I actually think the products that really lean into that and go above and beyond to make users feel super comfortable around what is the data we're going to have access to? How are we going to use it? What are our retention policies? Is this secure or not? All these things and being very proactive about that are the ones that I think are going to have more success of getting users to download and try it and spread the word and tell their friends.
Model-agnostic, export-agnostic platform strategy
Source
Y Combinator Startup Podcast — How To Stand Out In A World Of AI Designs (October 22, 2026) · at 4:31 ▸ · at 13:36 ▸
When this applies
when building a tool in a fast-evolving technical ecosystem with multiple competing underlying providers (models, clouds, frameworks)
The takeaway
Build your product as connective infrastructure across providers rather than as an exclusive extension of one, to maximize reach and reduce platform risk.
Why it works
Locking into one model/provider ties the product's fate to that provider's trajectory and alienates users already embedded in other ecosystems (Figma, Cursor, Codex, etc.); staying agnostic maximizes addressable workflows.
One level up
In infrastructure plays, optionality across suppliers/ecosystems is a competitive moat against both lock-in risk and competitor exclusivity.
Where it stops holding
This stops working when deep, exclusive integration with a single provider yields quality or speed advantages that generic integrations can't match.
Detail
procedure:
- Support export to multiple destinations (Figma for high-fidelity, multiple coding agents for production code).
- Avoid being locked to a single model provider.
- Let users bring their existing tool context (Cursor, Claude Code, PRDs) into the product via MCP rather than forcing a single workflow.
benchmarks: {}
rationale: Being 'model agnostic and feature agnostic' broadens the addressable user base versus single-ecosystem competitors.
In their words
One thing that's very different about our tool is that we're model agnostic and, in a way, feature agnostic, right? Where we encourage folks to export to Figma if they want to and get high fidelity precision or export to the coding agent of their choice, right?
Mandatory company-wide customer support to keep UX issues visible and fixed fast
Source
Y Combinator Startup Podcast — How To Stand Out In A World Of AI Designs (October 22, 2026) · at 43:20 ▸
When this applies
when trying to keep a growing team's product decisions grounded in real user pain rather than abstraction
The takeaway
Put the people who can fix a product directly in the path of the users who are frustrated by it, rather than routing complaints through intermediaries.
Why it works
Direct firsthand exposure to user frustration (e.g., confusing duplicate-colored CTAs) creates immediate motivation and context for the person who can actually fix it, collapsing the feedback loop between discovering and resolving a UX problem.
One level up
Shorten the distance between problem discovery and the person empowered to solve it to accelerate quality improvement.
Where it stops holding
This stops working when support volume at scale becomes too large to route through every engineer without harming throughput on other work.
Detail
procedure:
- Every employee (not just support staff) spends time in the support inbox.
- They directly witness specific user frustrations (e.g., can't find the share button due to duplicate CTA colors).
- The same person who saw the issue often fixes it immediately since they experienced it firsthand.
benchmarks: {}
rationale: Builds a company-wide 'high bar' culture where people naturally 'tackle the extra 20%' because they've felt the user's pain directly.
In their words
You know, like a couple of things that we do is everyone in our company does customer support. So every single person is in the support inbox talking to users every single day, seeing their frustrations when they can't find the share button because we have two CTAs that are the exact same color, two primary buttons, right? And the next thing you know, because the engineer is there, they're going ahead and fixing it because they experienced the user problem firsthand.
Build on your unfair skill, not your current idea
Source
Y Combinator Startup Podcast — How To Stand Out In A World Of AI Designs (October 22, 2026) · at 0:00 ▸ · at 2:08 ▸
When this applies
when choosing what to build and you have an idea that's just okay, versus a deep skill or unfair advantage you haven't leveraged yet
The takeaway
When picking a direction, prioritize what you structurally know better than almost anyone else over an idea that merely has traction.
Why it works
Founders have higher conviction, speed, and quality output when building on domain expertise they already possess, versus chasing a generic idea with revenue but no moat.
One level up
Durable advantage comes from exploiting asymmetric knowledge or skill, not just early market validation.
Where it stops holding
This stops working when the founders' 'known skill' doesn't correspond to an underserved or growing market need.
Detail
rule: Build the product from the skill you are already uniquely good at, not merely the idea that got traction.
threshold: They had revenue on the prior idea but were told to pivot anyway because the new direction matched their core competency (front-end engineering / Figma-to-code).
rationale: Deep skill translated into a 9-month search that only succeeded once they built on their own strength.
In their words
We get in and our YC partner tells us: hey, this is your company. It's an okay idea, but I highly recommend you do something that you know really, really well.
'Vibe-coded smells' checklist for AI-generated websites
Source
Y Combinator Startup Podcast — How To Stand Out In A World Of AI Designs (October 22, 2026) · at 21:15 ▸ · at 23:51 ▸ · at 28:15 ▸
When this applies
when auditing any AI-assisted creative output (copy, design, code) for signs it wasn't sufficiently reviewed or polished by a human
The takeaway
Learn the default 'tells' of your generative tool and actively deviate from them, especially where they conflict with usability.
Why it works
Generative models have systematic stylistic defaults (certain fonts, bold patterns, animation tendencies, instructional UI text) that, left unedited, create recognizable, often counterproductive patterns because they weren't validated against real user behavior.
One level up
Any generative system's unedited defaults tend toward homogeneity and will eventually look dated or conspicuous; deliberate human curation is what creates distinctiveness and timelessness.
Where it stops holding
This stops working when the trendy AI-default style is actually what the target audience currently associates with credibility/cutting-edge (the effect may invert over time).
Detail
rule: Watch for: fake-looking but non-interactive UI elements, scroll-jacking/scroll-dragging, literal 'scroll' prompts, unnecessary bolded words, default trendy fonts (Space Grotesque, Instrument Serif), over-the-top gradients/drop-shadows, and em-dash-heavy AI writing.
threshold: n/a (pattern list)
rationale: These are consistent, repeated patterns Alex has seen 'thousands' of times across vibe-coded designs, and some actively hurt usability (e.g., scroll-jacking doesn't convert; Fortune 500/decacorn sites never scroll-jack).
In their words
I mean, just notice like, okay, if I missed it, right? Again, go to like the top Fortune 500 company sites that have millions and millions of page views, they are not scrolljacking.