Skip to main content
Startups For the Rest of Us

Episode 762 | Doing Great Work, Hierarchy of SaaS Skills, and Public Deadlines (A Rob Solo Adventure)

25 min episode · 2 min read

Episode

25 min

Read time

2 min

Topics

Career Growth, Startups, Design & UX

AI-Generated Summary

Key Takeaways

  • Four-step framework for SaaS success: Decide what to work on, learn enough to reach knowledge frontiers, notice market gaps, then execute. Building products without domain expertise is like hitting a 500-sided die—relying on luck instead of understanding creates failure rates of one in 10,000.
  • SaaS skill hierarchy ranking: Marketing and sales rank first, product sense second, engineering third, hiring and managing fourth. Founders with strong marketing but weak engineering can reach 15-20 million ARR, but engineers without marketing skills struggle to gain initial traction and customer acquisition.
  • Product understanding versus coding ability: Nontechnical founders mistakenly believe hiring an engineer solves product development. Engineers know how to write code but often lack product sense—understanding what to build, what screens need, where features belong, and critically what to exclude from the roadmap entirely.
  • Public deadline risks require rigorous planning: Drip announced their visual workflow launch two weeks early, then discovered they forgot to redesign the entire onboarding flow. Public commitments demand exhaustive checklists, sanity checks, and brainstorming sessions to identify overlooked dependencies before making announcements to customers.

What It Covers

Rob Walling examines Paul Graham's framework for doing great work, ranks essential SaaS skills with marketing over engineering, and shares lessons from Drip's only public deadline disaster in 2015.

Key Questions Answered

  • Four-step framework for SaaS success: Decide what to work on, learn enough to reach knowledge frontiers, notice market gaps, then execute. Building products without domain expertise is like hitting a 500-sided die—relying on luck instead of understanding creates failure rates of one in 10,000.
  • SaaS skill hierarchy ranking: Marketing and sales rank first, product sense second, engineering third, hiring and managing fourth. Founders with strong marketing but weak engineering can reach 15-20 million ARR, but engineers without marketing skills struggle to gain initial traction and customer acquisition.
  • Product understanding versus coding ability: Nontechnical founders mistakenly believe hiring an engineer solves product development. Engineers know how to write code but often lack product sense—understanding what to build, what screens need, where features belong, and critically what to exclude from the roadmap entirely.
  • Public deadline risks require rigorous planning: Drip announced their visual workflow launch two weeks early, then discovered they forgot to redesign the entire onboarding flow. Public commitments demand exhaustive checklists, sanity checks, and brainstorming sessions to identify overlooked dependencies before making announcements to customers.

Notable Moment

Drip took five months instead of the estimated two to three months to build visual workflows, their most complex feature. Hours after announcing the launch date publicly, the team realized their entire onboarding system needed rebuilding to accommodate the new functionality.

Know someone who'd find this useful?

Episode Transcript

It's another episode of Startups for the Rest of Us. I am your host, Rob Walling. And in this episode, I'm on a solo adventure where I'm gonna walk through Paul Graham's I was gonna say recent essay, but it's over a year old now. It's called Doing Great Work. I I think it's a fascinating look at the steps that it takes to ship amazing things and to build incredible things on this planet. And I'm gonna focus that a little bit more on being an ambitious bootstrapper rather than Paul Graham thinks of things like probably Airbnb and what DoorDash did they invest in or Instacart. You know, these these really kind of game changing apps that everyone winds up using. But for the purpose of this podcast, we wanna build real businesses for real customers that pay us real money, which look. Stripe and DoorDash and those actually actually are as well, but that's not the focus of this show. And so I'm gonna edge that or focus it more on things that relate to what you're probably building. Then I'm gonna talk about whether there's a hierarchy to skills if you're building a SaaS. This is based on an ex Twitter conversation, and I've been to a couple other solo topics. But before I do that, applications for Microsoft Connect, which is our online community and forum, are open today, and they close March 5. Since we do custom group onboarding for new connect applications, we take folks in batches once every month. And if you get in now, you will have access to our MicroConf Connect live session, which happens next month in March with Asia Aragio. She's gonna be talking about, well, all types of amazing stuff that Asia talks about. So if you're interested in potentially becoming part of MicroConf Connect, you wanna dip your toe in the water, microconfconnect.com. It's only open for a few more days and closes on March 5. Let's dive in to my first topic. I'm gonna link up this essay, How to do Great Work by Paul Graham. And when I noted down this essay, I put a a couple bullet points. I said, doing great work isn't easy and you must be ambitious and hardworking to even consider it. Paul Graham has four steps to do great work and he says this is how practically everyone who's ever done great work has done it from painters to physicists and obviously he includes startup founders in this I would assume. So step one is to decide what to work on. Step two is to learn enough about it to get you to one of the frontiers of knowledge. The third step is notice the knowledge gaps and the fourth step is boldly chase outlier ideas. The reason I wanted to talk about this in this episode is whatever you are building whether it's a lifestyle business or an ambitious SaaS startup I think the first three steps …

Get the full transcript (4,791 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 Startups For the Rest of Us transcripts →

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

Get Startups For the Rest of Us summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from Startups For the Rest of Us

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 Startup Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Startups For the Rest of Us.

Every Monday, we deliver AI summaries of the latest episodes from Startups For the Rest of Us and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime