Skip to main content
Full Stack Radio

123: Ian Landsman - Marketing and Positioning a New Tailwind CSS Product

66 min episode · 2 min read
·
Ian Landsman,Adam Wannon

Episode

66 min

Read time

2 min

Topics

Productivity, Design & UX, Marketing

AI-Generated Summary

Key Takeaways

  • Product positioning clarity: Focus on developers forced to do design work rather than mixing audiences. The core market mirrors refactoring UI buyers—developers needing implementation help with Tailwind, not designers or WordPress theme buyers seeking variety.
  • Pricing model trade-offs: Consider Sketch's approach where users pay for one year of updates then retain perpetual access to their version. This avoids perpetual obligations while incentivizing continued development without requiring subscription treadmill commitment from customers.
  • Support scope definition: Establish clear parameters around what support means when delivering code. Consider two-tier pricing where basic access excludes support while premium tier includes time-limited help, preventing unlimited support obligations for edge cases and configuration issues.
  • Feature-driven marketing: Lead with concrete features over benefit storytelling when selling to developers with existing audiences. List component counts, categories, and capabilities directly—developers want facts for comparison shopping, not lengthy pain-point narratives building trust from scratch.
  • Expansion packaging strategy: Start with core component library then add specialized packs for specific markets like ecommerce. Price specialized packs independently rather than bundling everything, allowing targeted value capture from users with higher willingness to pay for niche needs.

What It Covers

Adam Wathan consults Ian Landsman on positioning and pricing a new Tailwind CSS component product with Steve Schoger, exploring subscription models, support structures, and whether to market as templates versus educational content.

Key Questions Answered

  • Product positioning clarity: Focus on developers forced to do design work rather than mixing audiences. The core market mirrors refactoring UI buyers—developers needing implementation help with Tailwind, not designers or WordPress theme buyers seeking variety.
  • Pricing model trade-offs: Consider Sketch's approach where users pay for one year of updates then retain perpetual access to their version. This avoids perpetual obligations while incentivizing continued development without requiring subscription treadmill commitment from customers.
  • Support scope definition: Establish clear parameters around what support means when delivering code. Consider two-tier pricing where basic access excludes support while premium tier includes time-limited help, preventing unlimited support obligations for edge cases and configuration issues.
  • Feature-driven marketing: Lead with concrete features over benefit storytelling when selling to developers with existing audiences. List component counts, categories, and capabilities directly—developers want facts for comparison shopping, not lengthy pain-point narratives building trust from scratch.
  • Expansion packaging strategy: Start with core component library then add specialized packs for specific markets like ecommerce. Price specialized packs independently rather than bundling everything, allowing targeted value capture from users with higher willingness to pay for niche needs.

Notable Moment

Landsman challenges the assumption that subscription models always align interests better, noting that for component libraries—unlike daily-use software like Sketch—the friction of recurring payments may outweigh benefits since developers primarily need one-time access rather than continuous engagement.

Know someone who'd find this useful?

Episode Transcript

In this episode of Fullstack Radio, I get some help from my friend Ian Landsman on figuring out some marketing and product design challenges with a new tailwind component directory product I've been working on with Steve Schoer. This is Fullstack Radio episode one twenty three. Hey, everyone. Welcome to another episode of the Full Stack Radio podcast. I'm your host, Adam Wannon. And today, I am joined by my friend, Ian Landsman. How's it going, Ian? Hey. How you doing? Good. So the reason I wanna have you on the show today, you know, you've been on the show before. I kinda I like to bring you on the show anytime I wanna get, like, I think of you as kind of, like, my software business uncle that, like, I get to talk to once in a while that has all this, like, wisdom. Awesome. I love that. It's cool to be able to chat with you sometimes when I'm trying to figure something out and just get some, get some perspective from someone who's been in the game for a while. Your crazy software uncle. So, yeah. So kinda what I wanted to chat with you about today is, me and Steve Schoger, who I worked on, refactoring UI with, are working on this new product that we're still trying to figure out exactly what it's gonna be, but, like, there's some things that we're just struggling to to feel like we've made a confident decision on. And I thought it'd be, cool to get some of your input on that. So what we're trying to make is obviously, like, me and Steve work on Tailwind CSS for a bunch of reasons and people use it and and it's cool or whatever. But because it's like a utility framework, there's sort of a hole where a lot of people who try to use it, kinda get stuck because they just don't even though they like the workflow, they just don't know, like, what to do with it. You know what I mean? It's like Right. Yeah. P strap. Okay. I I wanna make a list group or I wanna make a nav bar. It's, like, all right there. But Yeah. With Tailwind, you're sort of, like, left to your own devices. So what we thought would be kind of an interesting way to try and, like, make the whole thing sustainable so that we can actually build a business around this tool while keeping it open source and continuing to build free stuff and everything is to kinda enter the sort of like UI kit or themes sort of space. Kinda like Bootstrap has, like, their official theme store. We're trying to figure out, like, what does it look like to make a product like that for, tailwind users or for aspiring tailwind users even. And even that positioning is kinda hard to to figure out. So I'll kind of explain where we're where we're thinking about going, …

Get the full transcript (13,910 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Full Stack Radio transcripts →

You just read a 3-minute summary of a 63-minute episode.

Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links. As an Amazon Associate, SignalCast earns from qualifying purchases.

Tools

  • Consider Sketch's approach where users pay for one year of updates then retain perpetual access to their version.

Products

  • The core market mirrors refactoring UI buyers—developers needing implementation help with Tailwind, not designers or WordPress theme buyers seeking variety.
  • positioning and pricing a new Tailwind CSS component product with Steve Schoger, exploring subscription models, support structures, and whether to market as templates versus educational content.

More from Full Stack Radio

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

You're clearly into Full Stack Radio.

Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime