Founder + Lead Designer @tryartone Design and build agency for tech companies. 80+ projects, $1B+ in client valuation.
Work with us →
Joined January 2016
- Tweets7.1K
- Following575
- Followers1.8K
- Likes18.2K
Pinned Tweet
My designs helped:
• Raise $10M+ in total funding
• Secure funding from top VCs like Y Combinator, Pioneer Fund, Global Brain, Imec.istart and more.
• Exceed $1B in combined valuation for partner companies
• Be recognized by Awwwards, Framer with a Site of the Year nomination, Landbook & more.
So far, 80+ projects shipped across AI, B2B SaaS, and consumer apps.
My DMs are open.
a lot of our clients found us by just asking their AI who to hire
here's the exact prompt to make your site show up there. drop it into claude code, cursor, grok bot, whatever agent has your site's codebase and let it get to work 👇
what we actually run on artone.studio:
- schema on every page (org, services, pricing, articles w real publish + update dates, faq)
- llms.txt rebuilt on every deploy + a markdown version of every article
- 2 AI writers daily, keyword articles + honest "us vs them" comparisons
- i approve every single one before it goes live
- static html so AI crawlers see everything without js
stuff that'll backfire:
- schema that doesn't match what's on the page
- fake faqs nobody actually asked
- bumping "last updated" when nothing changed
- pumping out thin AI articles nobody reviews
- comparisons that trash competitors. be honest, say when they're the better fit
- llms.txt isn't magic, treat it as cheap docs not a ranking hack
founders fire designers for being slow on screen 1.
then hire someone new who's also slow on screen 1.
what's actually happening: the first stretch isn't screens. it's components. every button state, disabled, hover, every size, the icon system. all of it has to exist before real screens can.
once it's there, new screens assemble themselves.
it's why per-screen pricing feels wrong. screen 3 and screen 30 aren't the same work.
and why a good design system ends up being the cheapest part of the project, even if month one looks expensive.
if your designer's first delivery has fewer screens than expected, ask to see the components. that's where the time went, and it's what makes everything after faster.
stop opening figma first.
a static screen hides what matters: the flow, the loading state, whether step 3 makes sense once you tap through it.
now i code a clickable prototype before any design.
founders stop saying "looks good" and start asking "why does this take three clicks?"
that question saves a week of polishing the wrong thing.
Figma still matters, it just comes second.
Razvan Badea retweeted
tip for designers: add a logo explanation slide.
it sells the idea behind your work and looks cool 😅
want a particular idea picked? sell it better.
its because you can hold a coffee. see it, smell it, taste it. the value is right there in your hand
and theres like 3 coffee shops around the block. you know which one is best or closest, you need energy, done
an app has 100 others doing the same thing at different prices, all one search away. so you stop and think am i even getting the best one?
kinda dumb but its all perceived value
a legit good product that solves an actual problem makes $4.99 a no brainer 😅
tip for designers: add a logo explanation slide.
it sells the idea behind your work and looks cool 😅
want a particular idea picked? sell it better.
