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.
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.
basically my whole back office runs on grok bots now 😅
→ Operations: runs studio ops, keeps my notion specs and business brief up to date
→ Finance: invoicing and CFO for the studio
→ Lead Gen: finds and qualifies potential clients
→ Inbox: triages new emails and drafts replies
→ Content: brainstorms posts from my week and drafts them, scouts X and reddit threads worth replying to
→ SEO/AEO: writes the blog articles and checks if we show up in google and AI answers
→ Backlinks Builder: gets the site listed on design galleries
in 2024 i said yes to everything.
every project, every call, every "can we squeeze this in?"
work was coming in faster than i'd ever seen. i was working weekends and telling myself it was the good kind of busy.
then i burned out and took a month off.
the honest reason i got there: i had a hard time saying no. turning down work felt like turning down growth, so i took all of it.
the work paid for it. i can't ship something i don't think is right, so every extra project meant more late nights fixing details instead of thinking better.
now i tell clients upfront when i'm at capacity. it costs me a project sometimes. a rushed project costs me the relationship.
more clients was never the goal. better work for the ones i have is.
One video & the modal has to show its views, earnings, engagement, creator, and both social accounts.
that's a lot for one screen, so the layout reads in order: performance on top, the raw numbers in the middle, the creator at the bottom.
designed for methods, the ugc marketplace made by instinct.
What would you change first?
i don't make clients file tickets.
there's no board to fill in, no priority dropdown, and nobody waiting for a status to flip from "to do" to "in progress."
i join their slack. their calls. their linear if that's where they live. a founder sends a loom, a rough note, or a screenshot covered in arrows, and that's the brief.
here's why:
a ticket tells me what a founder asked for. a call tells me why.
say a founder asks for "a cleaner pricing page." that's the ticket. on a call it turns out nobody can tell the difference between the two plans. a cleaner page doesn't fix that. a different structure does.
across 80+ projects, the request is rarely the real problem. it's the symptom, and the real problem lives in the conversation around it.
ticket-based design gets you exactly what you asked for.
sitting next to the founder gets you what the product actually needs.
YC-backed. strong product. a landing page that wasn't getting demo signups.
that was Sero when they came to me.
the messaging wasn't clear, the flow didn't guide anyone toward the demo, and the look didn't read as serious b2b.
so i redesigned the page around one job: get the right visitor to book.
delivered in 2-3 weeks.
which section do you think does the most work here?
A rough, developer-built app. one month of retainer later, a full redesign of methods.
chat, knowledge base, workflows, onboarding, creator library. every screen in dark and light.
plus a component system, so their team keeps shipping without waiting on us.
if your product still feels developer-built, my dms are open.
we got @figma mcp which is great when do we have branches/redesign of version history?
a client asked for consistent email signatures.
old me would have designed a few versions, exported the files, and moved on.
this time i prompted a small tool instead. their team picks a name and it generates the signature.
stop asking "is this worth building?" and start asking "can i just prompt this?"
look at your week. something you do by hand, or a request your clients keep making. prompt it. you'll be surprised how much works.
and ai isn't for being lazy. it's for making what you deliver better.
try building something with it every week.

















