15 Minutes, Free

Every week I open one slot. Fifteen minutes. Free. No pitch, no proposal, no follow-up deck. Just a conversation about whatever design or product problem is keeping you stuck. I do this because the patterns I see in these conversations make me sharper. The questions founders ask in fifteen minutes are worth more than any market research.


Come with one specific question. That's all I ask.


How It Works


This is a focused fifteen-minute conversation. Not a consultation. Not a discovery call. You bring the problem. I bring a perspective. Sometimes that's enough to unblock you. Sometimes it leads to more. Either way, you leave with something useful.


What Works Well in Fifteen Minutes


  • "Our landing page isn't converting and I can't figure out why."

  • "We're about to hire our first designer. What should I look for?"

  • "Our onboarding feels broken but I don't know where to start fixing it."

  • "We're deciding between building a design system or just shipping faster."

  • "We have an AI feature that works technically but the UX feels wrong."

  • "Our brand feels scattered and I'm not sure if we need a rebrand or just better consistency."

  • "We're a Web3 product losing users at the wallet connect step."

  • "I want to understand if my design is a growth lever or a growth bottleneck."


What Doesn't Work in Fifteen Minutes


  • Full design audits. Those require time, access, and context that can't fit in a short call.

  • Portfolio or career reviews. I'm happy to help with product and business problems, but career coaching needs a different format.

  • Anything that starts with "Can you just quickly..." because the answer is almost never quick.

  • "Tell me everything about design strategy." That's a course, not a conversation.

Ground Rules


One question. Make it specific. The sharper the question, the more useful the answer. "Our signup flow feels slow" is better than "How do we improve our product?"

I'll be honest. If I think you're solving the wrong problem, I'll tell you. If I think you don't need a consultant, I'll tell you that too.

No follow-up pitch. If we decide to explore working together after, that's a completely separate conversation initiated by you.

Patterns from Recent Conversations

These are the themes that keep surfacing. If you see your problem here, you're not alone. And it probably means the answer is more straightforward than you think.


The redesign that isn't a redesign. Founders who think they need a visual overhaul when the real problem is messaging and flow. The product looks fine. The communication doesn't work.


The AI interface trust gap. Products where the AI is impressive but the interface doesn't earn enough trust for users to rely on it. The technology works. The design doesn't close the confidence gap.


The design hire timing question. When to hire your first designer. Whether to hire a generalist or a specialist. Whether a consultant makes more sense at your stage. This comes up almost every week.


The Web3 onboarding wall. Products losing meaningful portions of users at wallet connect, KYC, or other high-friction steps because they haven't earned trust before asking for commitment.


The design system decision. Whether to invest in a system now or keep shipping fast. The answer depends on stage, team size, and how much inconsistency is actually costing you.


The brand identity crisis. Products that have repositioned multiple times and now have a visual identity that doesn't match any coherent story. The fix is usually simpler than they expect.

Book a Slot


One slot per week. First come, first served.

If the current week is booked, check back next week.

15 Minutes, Free

Every week I open one slot. Fifteen minutes. Free. No pitch, no proposal, no follow-up deck. Just a conversation about whatever design or product problem is keeping you stuck. I do this because the patterns I see in these conversations make me sharper. The questions founders ask in fifteen minutes are worth more than any market research.


Come with one specific question. That's all I ask.


How It Works


This is a focused fifteen-minute conversation. Not a consultation. Not a discovery call. You bring the problem. I bring a perspective. Sometimes that's enough to unblock you. Sometimes it leads to more. Either way, you leave with something useful.


What Works Well in Fifteen Minutes


  • "Our landing page isn't converting and I can't figure out why."

  • "We're about to hire our first designer. What should I look for?"

  • "Our onboarding feels broken but I don't know where to start fixing it."

  • "We're deciding between building a design system or just shipping faster."

  • "We have an AI feature that works technically but the UX feels wrong."

  • "Our brand feels scattered and I'm not sure if we need a rebrand or just better consistency."

  • "We're a Web3 product losing users at the wallet connect step."

  • "I want to understand if my design is a growth lever or a growth bottleneck."


What Doesn't Work in Fifteen Minutes


  • Full design audits. Those require time, access, and context that can't fit in a short call.

  • Portfolio or career reviews. I'm happy to help with product and business problems, but career coaching needs a different format.

  • Anything that starts with "Can you just quickly..." because the answer is almost never quick.

  • "Tell me everything about design strategy." That's a course, not a conversation.

Ground Rules


One question. Make it specific. The sharper the question, the more useful the answer. "Our signup flow feels slow" is better than "How do we improve our product?"

I'll be honest. If I think you're solving the wrong problem, I'll tell you. If I think you don't need a consultant, I'll tell you that too.

No follow-up pitch. If we decide to explore working together after, that's a completely separate conversation initiated by you.

Patterns from Recent Conversations

These are the themes that keep surfacing. If you see your problem here, you're not alone. And it probably means the answer is more straightforward than you think.


The redesign that isn't a redesign. Founders who think they need a visual overhaul when the real problem is messaging and flow. The product looks fine. The communication doesn't work.


The AI interface trust gap. Products where the AI is impressive but the interface doesn't earn enough trust for users to rely on it. The technology works. The design doesn't close the confidence gap.


The design hire timing question. When to hire your first designer. Whether to hire a generalist or a specialist. Whether a consultant makes more sense at your stage. This comes up almost every week.


The Web3 onboarding wall. Products losing meaningful portions of users at wallet connect, KYC, or other high-friction steps because they haven't earned trust before asking for commitment.


The design system decision. Whether to invest in a system now or keep shipping fast. The answer depends on stage, team size, and how much inconsistency is actually costing you.


The brand identity crisis. Products that have repositioned multiple times and now have a visual identity that doesn't match any coherent story. The fix is usually simpler than they expect.

Book a Slot


One slot per week. First come, first served.

If the current week is booked, check back next week.