
Episode 775 | A.I. Coding Tools, User Experience, Racking Your Own Servers, and More Listener Questions (with Derrick Reimer)
May 20, 2025
Key Takeaways
- AI coding tools significantly shorten MVP development time, but maintainability and catching AI-generated mistakes remain critical concerns for long-term viability.
- The importance of user experience (UX) in SaaS is context-dependent, often correlating with whether UX is a primary differentiator or if the buyer is removed from the end-user.
- For most SaaS startups, leveraging cloud platforms for hosting and infrastructure is a more cost-effective and reliable choice than managing on-premise servers due to the expertise and operational overhead involved.
Segments
UX Importance in SaaS (00:16:11)
- Key Takeaway: The necessity of a formal UX process depends on whether superior user experience is a core value proposition and if the target customer values it.
- Summary: Arthur asks about the essentiality of UX in the early stages of app development. The hosts debate whether to prioritize a formal UX process or rapid MVP development, concluding it depends on the product’s market and competitive landscape.
Cloud vs. On-Prem Hosting (00:23:47)
- Key Takeaway: For the vast majority of SaaS startups, cloud hosting offers superior cost-effectiveness and reliability compared to on-premise servers due to outsourced operational expertise.
- Summary: Lewis questions the trend of moving back to on-premise servers. The hosts strongly advocate for cloud hosting, citing the significant overhead and expertise required for self-hosting and highlighting the value of platform-as-a-service providers.
Email Deliverability Strategies (00:32:29)
- Key Takeaway: None
- Summary: Kyle asks for advice on preventing emails from going to spam. The hosts recommend using services like SendGrid or Postmark, emphasizing the importance of email authentication protocols and maintaining a good sender reputation.
Sales vs. Marketing for SaaS (00:40:26)
- Key Takeaway: Enterprise SaaS requires a sales-driven approach with longer cycles and higher customer acquisition costs offset by higher price points, while SMB SaaS often relies on marketing for demand generation with lower price points and higher churn.
- Summary: Mike inquires about the difference between sales and marketing roles for enterprise vs. SMB targets. The hosts define sales and marketing, discuss the spectrum of business sizes, and highlight the distinct challenges and advantages of each go-to-market strategy.
Debug Information
Processing Details
- VTT File: c1e-w409f3zq47u8po91-25n37914bddx-8b4ehy.vtt
- Model Used: models/gemini-2.5-flash-lite
- Processing Time: September 12, 2025 at 10:03 AM
- Total Chunks: 1
- Transcript Length: 79,067 characters
- Caption Count: 701 captions
- Temperature: 0.1
- Max Tokens: 1024
- Top-K: Not used
- Top-P: 0.95
- Candidate Count: 1
- Affiliate Tag: spokengoods-20
Prompts Used
Prompt 1: Context Setup
You are an expert data extractor tasked with analyzing a podcast transcript.
I will provide you with part 1 of 1 from a podcast transcript.
I will then ask you to extract different types of information from this content in subsequent messages. Please confirm you have received and understood the transcript content.
Transcript section:
[00:00:00.240 --> 00:00:02.560] This podcast is brought to you by Mercury.
[00:00:02.560 --> 00:00:09.840] I've been banking with Mercury for years, and whenever I set up a new account, I'm reminded why traditional banking feels stuck in the past.
[00:00:09.840 --> 00:00:17.760] When our previous bank faced solvency issues, we needed to spin up new accounts quickly that could handle millions in funds across multiple businesses.
[00:00:17.760 --> 00:00:20.480] Mercury had us up and running almost immediately.
[00:00:20.480 --> 00:00:33.200] I manage half a dozen different Mercury accounts across a wide range of companies, from my personal single-member LLC, to MicroConf, our seven-figure global events and education platform, to TinySeed, our venture fund and accelerator.
[00:00:33.200 --> 00:00:35.360] Mercury easily handles them all.
[00:00:35.360 --> 00:00:50.080] The interface is elegantly simple for daily banking, paying invoices, and sending and receiving international wires, yet powerful enough to handle the multi-step approval processes we needed to put in place when funding founders with large transfers.
[00:00:50.080 --> 00:00:55.120] Anytime founders ask me who they should set up their accounts with, I send them to mercury.com.
[00:00:55.120 --> 00:01:01.040] Check the show notes for more details and note that Mercury is a financial technology company, not a bank.
[00:01:01.040 --> 00:01:03.520] It's another episode of Startups for the Rest of Us.
[00:01:03.520 --> 00:01:05.280] I'm your host, Rob Walling.
[00:01:05.280 --> 00:01:10.720] And in this episode, Derek Reimer and I sit down and we answer listener questions.
[00:01:10.720 --> 00:01:21.360] We answer a question about the impact of new AI coding tools, talk about user experience and how much time you should or shouldn't invest in the early days.
[00:01:21.360 --> 00:01:31.040] Talk about racking your own servers versus cloud hosting, the trade-offs between those two things, email deliverability and reliability, risks around that.
[00:01:31.040 --> 00:01:33.520] And we handle another topic or two.
[00:01:33.520 --> 00:01:37.440] If you could possibly believe it, we packed it in to this amazing episode.
[00:01:37.440 --> 00:01:44.320] And if you stick around till the hidden track at the end, you'll get to hear Derek Reimer get ambushed by my trivia questions.
[00:01:44.320 --> 00:01:49.680] Before we dive into the episode, I want to let you know about some exciting updates to the SAS Launchpad course.
[00:01:49.680 --> 00:01:56.720] It's my nine-and-a-half-hour video course that walks you through the process of going from no idea to your first paying customer.
[00:01:56.720 --> 00:02:03.080] We've just added a new module that dives deep into what founders should think about before adding AI to their SAS.
[00:02:03.320 --> 00:02:06.200] It's actually a private conversation I had with Arvid Kahl.
[00:02:06.200 --> 00:02:10.760] He's been integrating AI into his own SAS, podscan.fm.
[00:02:10.760 --> 00:02:16.280] We talk through the landmines and tricky spots that founders are hitting right now so you can avoid some costly mistakes.
[00:02:16.280 --> 00:02:25.800] And here's the thing I'm really excited about: if you buy and you complete the course material in the next 30 days, you'll be entered for a chance to win a 30-minute one-on-one chat with me.
[00:02:25.800 --> 00:02:31.400] We can talk through your SAS idea, any roadblocks you're running into, or just brainstorm next steps together.
[00:02:31.400 --> 00:02:36.840] If you want to test drive the content first, grab the free sample module at sasslaunchpad.co.
[00:02:36.840 --> 00:02:40.840] It's a 28-minute video all about the DNA of a great SAS idea.
[00:02:40.840 --> 00:02:48.600] As a bonus, our team is giving away a free copy of the full course to one person who watches that video by June 1st.
[00:02:48.600 --> 00:02:55.960] And for loyal podcast listeners, use promo code launch at checkout to get $150 off this course.
[00:02:55.960 --> 00:03:00.760] Get all the details and access the free sample at sasslaunchpad.co.
[00:03:00.760 --> 00:03:03.880] And with that, let's dive into listener questions.
[00:03:14.280 --> 00:03:17.080] Derek Reimer, welcome back to Startups for the Rest of Us.
[00:03:17.400 --> 00:03:18.600] Always a pleasure.
[00:03:18.600 --> 00:03:20.040] It's great to have you back, ma'am.
[00:03:20.040 --> 00:03:22.360] So we are going to dive into listener questions today.
[00:03:22.360 --> 00:03:27.880] I have hand-picked several that I think are well designed for you to answer.
[00:03:27.880 --> 00:03:32.120] Before we do that, though, you've been working on some pretty awesome stuff with SavvyCal.
[00:03:32.120 --> 00:03:38.040] You want to tell folks, give them a hint, give them a teaser, and maybe a little call to action if they want to reach out to you.
[00:03:38.040 --> 00:03:41.720] Yeah, I think this actually might be the first time I'm publicly talking about this.
[00:03:41.720 --> 00:03:48.960] But yeah, we've been working on some interesting new product lines around appointment scheduling.
[00:03:49.360 --> 00:03:54.800] So SavvyCal has historically been sort of a Calendly competitor that's mostly for meeting scheduling.
[00:03:54.800 --> 00:03:59.200] Like, you know, you need to take a sales call or just book something with a colleague or something like that.
[00:03:59.200 --> 00:04:01.600] So meeting scheduling has its own dynamics.
[00:04:01.600 --> 00:04:12.560] And appointment scheduling, it's something that has come up basically the entire time we've been in business, people inquiring about using SavvyCal for scheduling appointments for more service-based businesses.
[00:04:12.560 --> 00:04:24.720] And we're just now starting to work on kind of a second product line that repurposes a lot of the goodness that we've developed over time with SavviCal meetings, but for the appointment scheduling use case.
[00:04:24.720 --> 00:04:30.560] So right now we're kind of partnering with one agency who's using this for a cool new project.
[00:04:30.560 --> 00:04:44.800] But I'd love to have more conversations with folks who are sort of in this space of building sort of custom flows for service-based businesses, whether it's telemedicine or whatever, and need kind of lower-level scheduling infrastructure.
[00:04:44.800 --> 00:04:47.520] Very interested in having those types of conversations.
[00:04:47.520 --> 00:04:48.000] Awesome.
[00:04:48.000 --> 00:04:49.600] So how can folks reach you?
[00:04:49.600 --> 00:04:55.440] Yeah, you can hit me up at derek at savvycal.com over email and I'd love to hear from you.
[00:04:55.440 --> 00:05:00.240] And that's D-E-R-R-I-C-K at savvycal.com.
[00:05:00.240 --> 00:05:03.040] All right, let's dive into listener questions.
[00:05:03.040 --> 00:05:09.920] Our first one is from Zach, and his question is about the impact of new coding tools.
[00:05:09.920 --> 00:05:17.760] He says, Hey, Rob, I just finished your book, and I'm feeling inspired to get started on my next startup, Rocket Ship Emoji, which I love.
[00:05:17.760 --> 00:05:28.560] One thing I was curious on is your take on the new wave of AI coding platforms, cursor, lovable, et cetera, and the impact of these specifically on the micro startup.
[00:05:28.560 --> 00:05:35.240] Does your 300-hour rule still hold up if you can build an MVP in just a few hours?
[00:05:35.240 --> 00:05:38.920] And so, I believe he's referring to in start small, stay small.
[00:05:38.920 --> 00:05:41.560] I used to think, I thought I said four to 600 hours, but whatever.
[00:05:41.560 --> 00:05:44.680] I wrote that book 15 years ago, so maybe I said 300.
[00:05:44.680 --> 00:05:46.360] It's approximately directionally correct, right?
[00:05:46.360 --> 00:05:50.440] Of like, hey, I have like the 220, 200 framework even these days, right?
[00:05:50.440 --> 00:05:59.320] Which is like two hours to, if you're kind of trying to validate an idea to do some research and to go to Google and to go to look at keyword volume and other hrefs and other things.
[00:05:59.320 --> 00:06:03.320] The 20 hours is, hey, maybe I'm going to put up a landing page, have customer conversations.
[00:06:03.320 --> 00:06:12.440] And then if I make it past both of those points with an idea, maybe I do spend the 200 or 300 or whatever that number is to build that MVP and get it in the hands of folks.
[00:06:12.440 --> 00:06:16.040] But AI coding tools do, in fact, change that timeline.
[00:06:16.040 --> 00:06:17.640] I think it's significantly shortened.
[00:06:17.640 --> 00:06:23.160] Now, I don't know if a few hours feels a little, I don't know, it feels a little exaggerated.
[00:06:23.480 --> 00:06:28.280] I don't know how maintainable that code will be and beyond that, but let's kick it off.
[00:06:28.280 --> 00:06:30.440] Like, are you using AI coding tools?
[00:06:30.440 --> 00:06:33.800] Have you found them to live up to the promise that people are talking about?
[00:06:33.800 --> 00:06:37.320] Of, hey, I'm a non-technical so-and-so and I can build everything in three minutes.
[00:06:37.320 --> 00:06:39.560] You know, what's your experience and thoughts here?
[00:06:39.560 --> 00:06:45.000] Yeah, so I have become a pretty deep user of AI coding assistance tools.
[00:06:45.000 --> 00:06:46.200] I kind of came late to the game.
[00:06:46.200 --> 00:06:51.320] There's been GitHub Copilot, which was launched like, I don't know, two or three years ago, I think.
[00:06:51.320 --> 00:06:54.920] And I just never really caught on to that mode back when it initially came out.
[00:06:54.920 --> 00:06:56.520] I think because the models weren't as good.
[00:06:56.520 --> 00:07:01.960] And so the kind of auto-correct as you type was just a bunch of kind of bad suggestions.
[00:07:01.960 --> 00:07:09.400] And these days, it has gotten considerably better, especially if you're in certain languages that the LLMs really know well, like JavaScript, Python.
[00:07:09.640 --> 00:07:13.320] It knows Elixir decently well, and that's what I mainly use: TypeScript.
[00:07:13.320 --> 00:07:16.800] I regularly now use Windsurf, which is similar to Cursor.
[00:07:16.800 --> 00:07:20.000] These are kind of the big two AI-assisted code editors.
[00:07:20.000 --> 00:07:22.560] And then I think you mentioned also V0 and Lovable.
[00:07:22.560 --> 00:07:30.640] And I think those are more like specific products from companies that allow you to kind of type in, like, here's the app I want you to build for me.
[00:07:30.640 --> 00:07:34.560] And it just like spikes out an MVP based on what you tell it.
[00:07:34.560 --> 00:07:43.600] And yeah, I think it's really interesting how these tools do considerably shortcut a V1.
[00:07:43.840 --> 00:07:48.160] Now, the question is: how long are you expecting to use this V1?
[00:07:48.160 --> 00:07:51.280] Like, is this purely for validating something?
[00:07:51.280 --> 00:07:59.360] Like, think of it like a working mock-up wireframe thing that actually persists things to a database and you can show flows off.
[00:07:59.360 --> 00:08:02.880] It can get you to that place really quickly.
[00:08:02.880 --> 00:08:09.840] I am skeptical about the maintainability of some of these code bases that were generated from scratch fully by AI.
[00:08:09.840 --> 00:08:20.480] I haven't found the code that it generates to be good enough for, I'm trying to imagine someone who doesn't know code at all using this to try to maintain an application for the long haul.
[00:08:20.480 --> 00:08:22.000] And I don't think we're there quite yet.
[00:08:22.000 --> 00:08:22.880] We might get there.
[00:08:22.880 --> 00:08:27.120] I mean, this might be a horribly outdated take, even in six months, not sure.
[00:08:27.120 --> 00:08:36.880] But like, at the present moment, it makes a lot of mistakes that if you're not technical, you may not catch it, and that would kind of not serve you well in the long run.
[00:08:36.880 --> 00:08:44.320] But for sure, for the purpose of proving something out and being able to demonstrate something, I think it has radically changed the game.
[00:08:44.640 --> 00:08:46.000] I would agree.
[00:08:46.320 --> 00:08:52.240] And there is an it depends to all of this, and the it depends is: are you a developer?
[00:08:52.240 --> 00:08:56.000] And are you a senior developer, mid-level, or junior, or not at all?
[00:08:56.000 --> 00:09:01.560] And I do think that AI coding tools, I think of it as almost like a mech suit, right?
[00:09:01.560 --> 00:09:04.680] Like you think of like alien, or do they have an alien suit?
[00:09:04.760 --> 00:09:12.920] Anyways, you know, a mech suit like makes you super powerful if you know how to use it, but imagine getting in it for the first time and letting it run on autopilot question mark.
[00:09:12.920 --> 00:09:14.200] You know, it's like, right?
[00:09:14.200 --> 00:09:32.920] And the analogy breaks down because you don't have to maintain a mech suit five years from now and have infrastructure and spaghetti code or like weird bugs that nobody, you know, nobody can really find because there's been machine-generated code for 40, 50 years, 60, I mean, for a very long time.
[00:09:32.920 --> 00:09:41.560] And back in the day, I actually was a contractor at LADWP, Los Angeles Department of Water and Power, and I was a developer working on .NET stuff there.
[00:09:41.560 --> 00:09:50.280] And they had a system, it was, I think it was in COBOL, and they had generated code in the 70s to do a bunch of stuff.
[00:09:50.280 --> 00:09:52.520] And it was machine-generated, and no one wanted to touch it.
[00:09:52.600 --> 00:09:56.600] I didn't know COBOL, but they had COBOL contractors who are like, everyone's scared to touch it.
[00:09:56.600 --> 00:09:58.680] It is a complete disaster.
[00:09:58.680 --> 00:10:00.040] And people are scared.
[00:10:00.040 --> 00:10:05.000] It was like a payroll system or maybe it ran the grid, you know, the electrical grid in LA for all we know.
[00:10:05.240 --> 00:10:09.000] And that's just the state of affairs sometimes with government systems.
[00:10:09.000 --> 00:10:12.760] But I remember being like, wow, they generated code and no one can touch it.
[00:10:12.760 --> 00:10:13.880] That sucks.
[00:10:13.880 --> 00:10:15.160] Like, what's the point then?
[00:10:15.160 --> 00:10:17.400] I mean, it works until dot dot dot.
[00:10:17.400 --> 00:10:27.480] Like, so I'm not saying AI code is that bad, but I think that's the big concern: you and I were just having a conversation a couple of weeks ago when you came over for DD.
[00:10:27.480 --> 00:10:36.840] And I believe you said, you know, you give it instructions and then you go through that code to really make sure that it is not screwing around and it makes mistakes, right?
[00:10:37.160 --> 00:10:37.720] Yeah.
[00:10:37.720 --> 00:10:45.600] I would say it's, I've still found this to be true, even in my few months of using it aggressively now, that it is best at writing test code.
[00:10:45.840 --> 00:10:53.040] And test code is just like, it's usually kind of an afterthought when you're trying to move quickly, you know, especially earlier stage.
[00:10:53.040 --> 00:11:00.240] You want to make sure stuff is kind of baseline sanity checked and you have some support for preventing regressions and stuff.
[00:11:00.240 --> 00:11:05.920] But like, you know, we don't love spending a ton of time writing tests if you're just trying to like deliver value quickly.
[00:11:05.920 --> 00:11:15.200] And I have found it is very good at analyzing your code, figuring out all the different permutations that should be tested, and then writing that test code for you.
[00:11:15.200 --> 00:11:21.680] And ideally, it writes it in such a way where you can pretty quickly easily read through it and see, like, all right, this is the setup.
[00:11:21.680 --> 00:11:23.280] These are the assertions.
[00:11:23.280 --> 00:11:25.040] Yep, that looks correct.
[00:11:25.040 --> 00:11:26.160] And then it'll run it.
[00:11:26.160 --> 00:11:32.240] And if it fails, then it's pretty good at at least helping you start to think about how to solve the bug, but it's not always perfect at that.
[00:11:32.240 --> 00:11:45.360] But even just having like those test cases where it's like actually rigorous and does every single kind of important permutation that has sped up my process a lot and made me feel like I have you know a stronger foundation of tests.
[00:11:45.360 --> 00:11:47.120] Yeah, faster and better.
[00:11:47.120 --> 00:11:47.520] Yeah.
[00:11:47.520 --> 00:11:50.720] And more thorough than you would care to do yourself.
[00:11:50.720 --> 00:11:51.200] Yeah.
[00:11:51.200 --> 00:11:56.960] And I think really getting back to Zach's question, because we've talked about AI and how it generates code and the dangers of that.
[00:11:56.960 --> 00:12:02.800] But really he's asking, so what if it makes me twice as fast, three, four, five times as fast?
[00:12:02.800 --> 00:12:07.840] Can I get it done in a day what used to take me a week, or two days it used to take me a week?
[00:12:07.840 --> 00:12:10.640] And in the future, will it be even faster?
[00:12:10.960 --> 00:12:12.960] How does that change all this methodology?
[00:12:12.960 --> 00:12:25.440] It's really interesting to think about because one of the reasons that I talk about, like that 220, 200 framework, the reason that framework exists is because I don't want you to spend 200 or 300 or 400 hours building something that no one wants.
[00:12:25.440 --> 00:12:27.440] So that's why there are those steps before it.
[00:12:27.440 --> 00:12:31.800] But he's asking a question, I think, what if it doesn't take me 200 hours?
[00:12:29.680 --> 00:12:35.560] What if it takes me 40 hours to do what it used to take 200 hours?
[00:12:35.560 --> 00:12:41.880] Should I just build more stuff more quickly without doing all the kind of the validation?
[00:12:41.880 --> 00:12:50.840] Here's the thing for me: as I said, the two is kind of doing research online, looking at competitors and SEO traffic and interest and demand and blah, blah, blah.
[00:12:50.840 --> 00:12:52.760] To me, I still want that.
[00:12:52.760 --> 00:12:55.720] If I'm starting it, like, I'm going to spend a few hours plugging away.
[00:12:55.720 --> 00:13:01.400] If I have a list of 10 ideas that I'm thinking about, could I feasibly go and build all 10 of those ideas in a weekend?
[00:13:01.400 --> 00:13:06.440] Probably not now, but let's say you could, and I could just, I don't want to do that without knowing there's some demand.
[00:13:06.440 --> 00:13:09.240] I don't want a product if there's like no search traffic, right?
[00:13:09.240 --> 00:13:11.800] Or if there's no, I can't find anybody who wants this.
[00:13:11.800 --> 00:13:13.000] It's not solving a problem.
[00:13:13.000 --> 00:13:14.840] So I still want to do the two part.
[00:13:14.840 --> 00:13:22.120] And then the 20 part is either it's a landing page or customer interviews conversations or both, frankly, which is usually what I recommend.
[00:13:22.120 --> 00:13:23.320] I still want to do that too.
[00:13:23.320 --> 00:13:36.120] Now, maybe could I shortcut, can I build mock-ups really fast with AI or can I build kind of a clunky click-through paper prototype thing with AI that's not maintainable and build an MVP in order to do the 20?
[00:13:36.120 --> 00:13:36.920] Maybe.
[00:13:36.920 --> 00:13:40.360] I think the danger, I mean, it could cut both ways, right?
[00:13:40.360 --> 00:13:51.880] If sometimes the danger is you're getting ahead of yourself and giving too much specificity to someone of like, here are 17 screens with text boxes and buttons to click through.
[00:13:51.880 --> 00:13:55.240] And it's like, is that what they need to know if it's worth it?
[00:13:55.240 --> 00:13:57.800] Or are you basically saying, hey, I'm going to solve this problem.
[00:13:57.800 --> 00:14:03.880] I'm going to build a system that manages your entire business and allows people to log in and log out and click and audit and this and that.
[00:14:03.880 --> 00:14:06.280] And is that what they need to hear?
[00:14:06.280 --> 00:14:07.880] Especially if they're non-technical.
[00:14:07.880 --> 00:14:13.000] And sometimes I think they maybe do need to see a few screens of like, ah, I get it.
[00:14:13.000 --> 00:14:18.800] But other times, I think presenting them with completed software could actually be a detriment.
[00:14:19.120 --> 00:14:39.200] Yeah, I think that that's a really good point that like the process of building a product for a particular market segment entails that you are actually speaking to that customer set and figuring out what needs to go into that product because it's hubris to assume that you have all those answers from the get-go.
[00:14:39.200 --> 00:14:50.720] So like building something based on a bunch of assumptions that you haven't actually confirmed by working with customers means you're probably going to miss the mark if you if you come with this fully built out product.
[00:14:50.720 --> 00:14:55.680] I mean, talk about this this kind of new appointment scheduling stuff that I'm working on right now.
[00:14:55.680 --> 00:15:08.960] And like a big part of this is getting kind of real-time feedback from the actual end user, the clinic who's going to be using this product on a day-to-day basis and incorporating that in as we build stuff.
[00:15:08.960 --> 00:15:13.200] Because I can just make a bunch of guesses and think like try to envision what they need.
[00:15:13.200 --> 00:15:20.800] And that's certainly a big part of it is like just trying to like get into their shoes and think about what they would need, but that'll only get you so far.
[00:15:20.800 --> 00:15:27.120] You need to actually talk to the real customer to figure out, you know, how do you really nail it for all of their workflows and use cases?
[00:15:27.120 --> 00:15:37.040] And like that kind of stuff, AI can certainly help you workshop some of that, but I think ultimately you're still selling to humans and you need to accommodate human needs.
[00:15:37.040 --> 00:15:41.360] So, you know, getting the actual human data is pretty key there.
[00:15:41.600 --> 00:15:44.240] Still selling to humans for now, Derek.
[00:15:44.240 --> 00:15:45.040] For now.
[00:15:45.920 --> 00:15:46.640] Until AI starts.
[00:15:46.880 --> 00:15:49.120] This also might be an outdated take.
[00:15:49.440 --> 00:15:53.760] Two years from now, people are like, guys, AI buys everything now.
[00:15:53.760 --> 00:15:56.880] So anyways, yeah, I appreciate the question, Zach.
[00:15:56.880 --> 00:16:00.440] And I hope Derek and my takes were helpful.
[00:15:59.840 --> 00:16:06.120] Next question is an audio question from Arthur Ravelski.
[00:16:11.560 --> 00:16:12.520] Hi, Rob.
[00:16:12.520 --> 00:16:16.760] Arthur here, an aspiring entrepreneur living in Denver, Colorado.
[00:16:16.760 --> 00:16:20.760] I have an idea for an app that I've recently started developing.
[00:16:20.760 --> 00:16:27.560] After validating the concept with potential customers, it seems like a strong business opportunity to move forward on.
[00:16:27.560 --> 00:16:34.760] As I work on building this, I'm realizing there are various ways to approach the app structure, pages, and user interactions.
[00:16:35.080 --> 00:16:41.320] My question for you is, how do you approach the user experience when bringing an idea to life?
[00:16:41.320 --> 00:16:52.120] A traditional UX designer might create user profiles, wireframes, prototypes, conduct user testing to uncover pain points, and follow other structured steps.
[00:16:52.120 --> 00:16:56.840] I have a college background in graphic design and now work as a software engineer.
[00:16:56.840 --> 00:17:00.280] So part of me wants to go through this formal process.
[00:17:00.280 --> 00:17:08.200] But another part of me feels I should focus on quickly building an MVP to prove the concept and refine the user experience later.
[00:17:08.200 --> 00:17:12.600] When in the process do you believe it's most essential to focus on user experience?
[00:17:12.600 --> 00:17:15.800] How do you typically approach UX for a new idea?
[00:17:15.800 --> 00:17:18.840] I think a great user experience can make or break an idea.
[00:17:18.840 --> 00:17:21.880] So I'm very curious about your perspective on this.
[00:17:21.880 --> 00:17:23.320] Appreciate what you do.
[00:17:23.320 --> 00:17:24.680] Thanks so much.
[00:17:25.320 --> 00:17:26.680] All right, Derek.
[00:17:26.680 --> 00:17:35.160] As one of the best UX folks that I know that exists on the internet today, what is your take on Arthur's question?
[00:17:35.480 --> 00:17:42.040] So, obviously, I come from a place of being biased towards wanting to solve problems from a UX-first perspective.
[00:17:42.040 --> 00:17:50.080] Like, it's something that I really value in the products that I buy and in the products that I build, you know, considering yourself a craftsperson and like, this is what I really care about.
[00:17:50.400 --> 00:17:55.520] However, my answer to this, trying to be objective, is like, I think it really depends.
[00:17:55.520 --> 00:18:04.080] Like, are you staking a big portion of your value proposition on better UX when you compare yourself to the rest of the landscape?
[00:18:04.080 --> 00:18:07.120] You know, what does your buyer actually care about the most?
[00:18:07.120 --> 00:18:10.960] I tried to think about some examples in my own stack, right?
[00:18:10.960 --> 00:18:18.000] So, like, I use Linear for project management, and they've been around for, I don't know, three, four, five years, something like that.
[00:18:18.000 --> 00:18:35.360] And I think their main differentiator, I guess, is that they're trying to be JIRA, but with better UX, like experiences that people actually like to use, but it's kind of solving the same underlying problem that JIRA is, which JIRA kind of has a bad reputation for being a little bit of a nightmare to use.
[00:18:35.360 --> 00:18:43.040] And so, for them, in order to deliver on this promise, they have to be executing top-notch user experiences.
[00:18:43.040 --> 00:18:50.080] Otherwise, people will just use JIRA because if it's no better, no different than JIRA on the UX front, then like, why bother?
[00:18:50.080 --> 00:18:56.880] SavvyCal, you know, we're promising to be a more delightful user experience for the scheduler and the person who's configuring the links.
[00:18:56.880 --> 00:19:02.880] So, you should be able to go in and fine-tune your availability faster, more efficiently than you can in the other tools.
[00:19:02.880 --> 00:19:10.080] So, I think for us, like the customers we attract are the people who are looking for those better user experiences.
[00:19:10.080 --> 00:19:13.520] So, I would say in these cases, it matters a lot.
[00:19:13.520 --> 00:19:23.920] For other products, I'm just trying to think of examples like software for construction firms, like yeah, yeah, where like you're you're logging in, you're doing stuff.
[00:19:24.040 --> 00:19:36.040] There's there's screens with forms, and you're viewing reports and charts and things, but like the level of UX attention that a lot of the products that a lot of us use, like linear, is just probably not as important.
[00:19:36.440 --> 00:19:39.160] What you're doing is you're driving a different kind of value.
[00:19:39.160 --> 00:19:43.240] I think of even more stark examples like HitTail back in the day, right?
[00:19:43.400 --> 00:19:46.680] Product that we worked on was SEO keyword tool.
[00:19:46.680 --> 00:19:52.280] So you could log in, you could get reports on like these are the keywords you should be targeting in your content.
[00:19:52.280 --> 00:20:00.200] And like the settings screen in that app was not very important, that it was like top, top notch UX.
[00:20:00.200 --> 00:20:04.280] Like it's, you know, form fields and buttons and you have the basic essentials.
[00:20:04.280 --> 00:20:09.960] It had to be obviously like navigatable, but like the core value prop there was the keywords it was giving you.
[00:20:09.960 --> 00:20:16.360] So let's say in an app like that, like the quote-unquote user experience of the product mattered a whole lot less.
[00:20:16.360 --> 00:20:20.120] The user experience was really like, is it delivering the right keywords?
[00:20:20.120 --> 00:20:20.600] Right.
[00:20:20.920 --> 00:20:31.080] And so I guess that is essentially a different kind of user experience than what we classically think of as like the way that you lay out menus and form fields and things like that.
[00:20:31.400 --> 00:20:33.160] I don't know that I have much to add to that.
[00:20:33.160 --> 00:20:41.480] That was pretty much my take was it depends and it depends specifically on is this your advantage or one of your advantages or not.
[00:20:41.480 --> 00:20:44.120] And there's certain spaces that just don't know the difference.
[00:20:44.120 --> 00:20:53.080] And again, I think of construction firms or maybe, you know, someone, an owner of a gymnasium, right, of a fitness gym, a fitness studio.
[00:20:53.080 --> 00:20:57.080] Are they going to know the difference between linear and JIRA?
[00:20:57.080 --> 00:20:57.640] Are they real?
[00:20:57.640 --> 00:21:00.360] I mean, they could tell the difference, but are they going to be like, ooh, this is good UX?
[00:21:00.360 --> 00:21:02.440] Like, like they don't really even know what that is, right?
[00:21:02.440 --> 00:21:06.360] So that's, I think, the big thing is like your end user, do they care?
[00:21:06.360 --> 00:21:13.320] And not only do they care, but do you want to invest the time to make this one of your advantages?
[00:21:13.320 --> 00:21:14.640] I personally would.
[00:21:14.200 --> 00:21:19.520] I would tend to enter spaces where, just like you, where the users do care.
[00:21:19.840 --> 00:21:23.120] But probably most software doesn't matter.
[00:21:23.120 --> 00:21:34.160] If I think of most B2B SaaS software, I shouldn't say doesn't matter at all, because you can have catastrophic US and then UX and then everyone hates it, but it doesn't matter nearly as much as I think.
[00:21:34.480 --> 00:21:40.960] I have often opined, like, why is the most successful software out there kind of the crappiest software?
[00:21:40.960 --> 00:21:42.720] Like, how does this actually happen?
[00:21:42.720 --> 00:21:49.520] But I think there are plenty of examples where, like, it's kind of that adage of like, it's always safe to buy IBM kind of thing.
[00:21:49.520 --> 00:21:55.360] Like, like, Salesforce is known for being quite painful to use, but it's Salesforce.
[00:21:55.360 --> 00:22:08.080] And they have staked this incredible position in the market of like, this is one of the two tools, maybe HubSpot and Salesforce, or like the only big two that, like, any serious business of a certain size will be on one of these platforms.
[00:22:08.080 --> 00:22:11.520] And the people buying them don't care about the user experience.
[00:22:11.520 --> 00:22:15.520] There's a whole bunch of other things that cause them to make that buying decision.
[00:22:15.520 --> 00:22:23.440] And so I think it would also, you know, this is a trap that a lot of times people fall into where you look at a successful incumbent and you say, their UX is terrible.
[00:22:23.440 --> 00:22:25.120] I can do better UX.
[00:22:25.440 --> 00:22:37.840] And you ignore the fact that the actual person buying it, maybe the actual person buying it doesn't even use the product, but they're charged with buying it because they're a VP at some level and they're the one who has to make that procurement decision.
[00:22:37.840 --> 00:22:44.800] And they buy it because their peers are buying it or because like companies of our level of importance buy this software.
[00:22:44.800 --> 00:22:46.560] And so there's just different motivations.
[00:22:46.560 --> 00:22:56.160] And but I think that often causes kind of a mismatch in the entrepreneur who thinks I can build a better version of this thing when in reality the market doesn't care.
[00:22:56.480 --> 00:23:07.000] And I think that's a good distinction you just made, which is the further your buyer is from the user of said software, I think the worse your UX can be because the buyer doesn't care.
[00:23:07.160 --> 00:23:14.120] The buyer is usually going to buy based on market and brand and reputation rather than easy to use.
[00:23:14.440 --> 00:23:16.200] So thanks for that question.
[00:23:16.200 --> 00:23:18.040] Hope it was helpful.
[00:23:19.320 --> 00:23:26.600] I wanted to jump in here for a second and invite you to Microconf Remote, which is happening live tomorrow, May 21st from 10 a.m.
[00:23:26.600 --> 00:23:27.400] to 1 p.m.
[00:23:27.400 --> 00:23:28.360] Eastern Time.
[00:23:28.360 --> 00:23:33.000] The event consists of three presentations talking about early stage SaaS sales.
[00:23:33.000 --> 00:23:39.000] In addition, we have a founder by founder, which is like an online version of the hallway track at our in-person events.
[00:23:39.000 --> 00:23:42.040] Talks will be recorded in case you're listening to this event after.
[00:23:42.040 --> 00:23:45.960] To get access, head to microconf.com/slash remote.
[00:23:47.240 --> 00:23:55.000] Next one comes from Lewis Mertens, and Lewis asks a question about on-prem versus cloud hosting.
[00:23:55.000 --> 00:24:00.440] He says, Hey, Rob, I really enjoyed the book and I've listened to it twice now on Audible.
[00:24:00.440 --> 00:24:02.680] I think SAS Playbook, if I'm guessing.
[00:24:02.680 --> 00:24:10.920] I also love Linus Tech Tips, and they recently built a server on-prem and said that these days it's cheaper to run on-prem.
[00:24:10.920 --> 00:24:14.440] And many people were moving back to on-prem rather than the cloud.
[00:24:14.600 --> 00:24:15.880] I love proclamations like that.
[00:24:15.880 --> 00:24:16.600] Many people.
[00:24:16.600 --> 00:24:19.160] It's like, all right, yeah, there's five of them.
[00:24:19.240 --> 00:24:23.240] I wonder if you could talk through the pros and cons of cloud versus on-prem.
[00:24:23.240 --> 00:24:27.000] I suppose it would avoid vendor lock-in.
[00:24:27.000 --> 00:24:28.200] What do you think about this, Derek?
[00:24:28.200 --> 00:24:33.640] I mean, this, he's basically saying like getting a physical server in a cage somewhere, right?
[00:24:33.640 --> 00:24:37.640] And like getting it in a, we used to do this 15, 20 years ago.
[00:24:37.640 --> 00:24:39.720] We also used to charge one time for our software.
[00:24:39.720 --> 00:24:40.520] Should we do that as well?
[00:24:40.520 --> 00:24:41.000] No, I'm just kidding.
[00:24:41.080 --> 00:24:43.720] You can tell my opinion on this, but what are your thoughts?
[00:24:43.720 --> 00:24:55.280] Because, you know, you as an operator could totally save monthly hosting cost if you spun up a physical database, go buy a Dell, buy a database server, and then go buy your.
[00:24:55.520 --> 00:25:03.200] I say this because I remember doing this 25 years ago with clients, with big e-commerce clients, and like going and racking the servers in a place.
[00:25:03.520 --> 00:25:08.800] I mean, I have seen a lot of talk off and on in our space about this, about exiting the cloud.
[00:25:08.800 --> 00:25:11.040] And I think a lot of it's driven by DHH.
[00:25:11.040 --> 00:25:16.320] Maybe there are others that have done this, but I think he's been the most vocal lately who's been talking about doing this.
[00:25:16.320 --> 00:25:24.800] And basically, 37 Signals looked at their cloud spend and they said, hmm, we're paying, I don't know, it's like $10 million a year for S3 or something.
[00:25:24.800 --> 00:25:29.200] And then there, you know, had EC2 instances that were probably similar orders of magnitude.
[00:25:29.520 --> 00:25:36.000] You know, I think they were probably looking at their staffing and saying, well, we have all these DevOps people on staff who are kind of bored.
[00:25:36.000 --> 00:25:37.200] And I think we could.
[00:25:37.520 --> 00:25:38.320] This is the key.
[00:25:39.440 --> 00:25:43.280] And so, you know, we have the talent on staff.
[00:25:43.280 --> 00:25:45.600] We're not necessarily shipping a bunch of new products.
[00:25:45.600 --> 00:25:47.360] So we have extra capacity.
[00:25:47.360 --> 00:25:53.440] And we could probably stand to save some money and pull this stuff in-house.
[00:25:53.440 --> 00:25:58.400] They're a very mature business and they understand their traffic patterns really well.
[00:25:58.400 --> 00:26:04.560] So they know, like, Basecamp, I'm sure, just kind of mostly chugs along at a very consistent rate.
[00:26:04.560 --> 00:26:08.000] And if they get a bunch of new customers, it still doesn't really move the needle so much.
[00:26:08.000 --> 00:26:12.880] So they just have a very strong understanding of like, this is how many servers we need.
[00:26:12.880 --> 00:26:16.400] And maybe in six months, we'll need to buy one more server.
[00:26:16.400 --> 00:26:19.200] But we can anticipate that, we can predict it.
[00:26:19.200 --> 00:26:29.800] And so, yeah, I think for them, they're at such a stage of maturity with so much in-house expertise that, sure, you know, have at it, do it.
[00:26:29.280 --> 00:26:37.720] But I think for, I guess I wouldn't say 100% of us, but for 99.9% of the rest of us, like this is not a good decision.
[00:26:37.720 --> 00:26:46.920] With platform as a service, you're effectively getting all of those site reliability engineers and DevOps people at your platform of choice.
[00:26:46.920 --> 00:26:51.400] You're getting all of them as a functional extension of your team for metered cost.
[00:26:51.400 --> 00:26:55.480] You know, usually it's like an extra $10 for the next size up server.
[00:26:55.480 --> 00:27:01.960] And so you're getting this incredible amount of expertise for very, very low marginal cost.
[00:27:01.960 --> 00:27:12.120] This is just close to a miracle for us people at a smaller stage, like being able to start out, crack open a fresh application, you have close to zero dollars a month in cost.
[00:27:12.120 --> 00:27:19.640] And then as you get more customers, you can just incrementally, you know, expand your resource usage at your platform as a service.
[00:27:19.640 --> 00:27:25.080] Like, this is just, I think, a no-brainer to stay in these systems.
[00:27:25.080 --> 00:27:25.960] And yeah.
[00:27:26.280 --> 00:27:27.640] You and I are on the same page with this.
[00:27:27.880 --> 00:27:39.160] It's the old thing where I say, don't use Steve Jobs and Apple as an example unless you are co-founding with a guy who invented the personal computer, Steve Wozniak.
[00:27:39.160 --> 00:27:41.800] And when you're 20 years old, you're worth a million.
[00:27:41.800 --> 00:27:43.000] 21, you're worth 10 million.
[00:27:43.080 --> 00:27:44.680] 22, you're worth 100 million.
[00:27:44.680 --> 00:27:45.880] It's something approximately that.
[00:27:45.880 --> 00:27:47.720] I think that was Steve Jobs' situation.
[00:27:47.720 --> 00:27:49.480] And you've started this incredible company.
[00:27:49.480 --> 00:27:49.880] Great.
[00:27:49.880 --> 00:27:52.600] Then you can take Steve Jobs' advice of not listening to your customers.
[00:27:52.600 --> 00:27:55.160] They don't know what they want until you give it to them.
[00:27:55.160 --> 00:28:07.640] Or if you started a SaaS that is, as you said, 20 years mature, has nine figures, hundreds of millions in revenue, we would guess, tens of millions a year in profit, which is confirmed, Jason Freed confirmed at MicroConf.
[00:28:07.640 --> 00:28:12.520] And you are so bored, I'll say that you've rewritten the app multiple times.
[00:28:12.520 --> 00:28:14.760] Don't they have a Basecamp V2 and a Basecamp V3?
[00:28:14.960 --> 00:28:19.440] And when I say bored, I want to, I have a ton of respect for DHH and Jason Freed.
[00:28:19.440 --> 00:28:22.480] And I think they've done a lot for SAS and a lot for entrepreneurs.
[00:28:22.480 --> 00:28:24.880] They are tiny seed investors, they are tiny seed mentors.
[00:28:24.880 --> 00:28:27.120] So, like, they're in our circles.
[00:28:27.120 --> 00:28:32.240] But I think that they've been successful in spite of a lot of the advice they give.
[00:28:32.240 --> 00:28:42.000] When they used to say, we don't do marketing, we don't track analytics, we don't track opens, we don't have any type of web analytics or conversion tracking on our website.
[00:28:42.000 --> 00:28:43.120] They used to say that.
[00:28:43.120 --> 00:28:44.400] I don't know that they do anymore.
[00:28:44.400 --> 00:28:53.760] And it's like, yeah, and if you built a SAS in 2005 and we're one of the first ever, and you're, you know, you'd also don't need that, but like, none of us are in that position.
[00:28:53.760 --> 00:28:58.000] So just really take the stuff that they do with a grain of salt, these outliers.
[00:28:58.000 --> 00:28:59.520] And that's what we're talking about here.
[00:28:59.520 --> 00:29:11.760] In fact, if a tiny seed company, if I was interviewing a tiny seed applicant and things were going well and they told me that they were racking their own servers, it would be a major red flag for me that I would dig into.
[00:29:11.760 --> 00:29:13.680] And I would say, why are you doing that?
[00:29:13.680 --> 00:29:15.360] And they would better have a damn good reason.
[00:29:15.360 --> 00:29:23.920] And I believe of all the tiny seed companies, 204 investments we've done, there was one founder who had physical servers.
[00:29:23.920 --> 00:29:34.320] And the reason was, is it was like three years ago, and he was doing AI and needed physical GPUs because it was way too, he built his own model.
[00:29:34.320 --> 00:29:37.440] It was before the chat GPT became a thing, right?
[00:29:37.440 --> 00:29:38.400] About two years ago.
[00:29:38.400 --> 00:29:45.200] And he convinced me and Ainar, because ANR has a PhD in computer science and I know my way around a keyboard.
[00:29:45.200 --> 00:29:46.800] And we dug into that with him.
[00:29:46.800 --> 00:29:48.400] I'm like, wait, why are what?
[00:29:48.400 --> 00:29:49.200] And he was like, yeah.
[00:29:49.200 --> 00:29:50.520] And he kind of showed us the cost.
[00:29:50.520 --> 00:29:53.520] And we're like, ah, you actually, that is the right choice.
[00:29:53.520 --> 00:29:54.400] But that's it.
[00:29:54.400 --> 00:30:00.280] He's the one out of 204 that we're like, okay, yeah, physical, all right, fine.
[00:30:00.280 --> 00:30:06.280] Cloud is more expensive, but it's not as expensive as hiring your own SREs and DevOps folks.
[00:29:59.840 --> 00:30:06.920] Yeah, yeah.
[00:30:07.080 --> 00:30:26.200] And I think there's, I don't know, even like over the years, clouds kind of started out as like a virtual private server or whatever, where it's just like, it's like an on-prem server that they will make sure to keep the power on to it, but everything else is managed by you, you know, so you're still doing a heavy amount of DevOps.
[00:30:26.200 --> 00:30:41.800] And like that's some people choose to go that route, but even that, like, it would be so hard for me to justify just like getting a digital ocean droplet and just like trying to, you know, rotate my own server logs and doing all this stuff where like you just don't have to deal with that anymore.
[00:30:41.800 --> 00:30:57.320] And you can get so much more reliability by going with a more modern platform as a service where like you have a Docker file that describes what your server should be and your host would ideally allow you to just say like deploy servers that follow this spec and they manage all other aspects of it.
[00:30:57.320 --> 00:31:07.000] Like this is the way to go unless you're planning on investing in having your own people on constant on-call rotation and doing a bunch of DevOps work.
[00:31:07.000 --> 00:31:08.280] Some people are passionate about that.
[00:31:08.280 --> 00:31:09.160] More power to you.
[00:31:09.160 --> 00:31:17.400] But like if you're if you're just starting out especially, like you do not want to have to be responsible for that portion of your reliability.
[00:31:17.400 --> 00:31:20.360] Yeah, your most valuable asset as a founder is your time.
[00:31:20.360 --> 00:31:28.440] And any time you spend not building value for customers, not selling, not growing the business, even if you enjoy it, it is detrimental to the business, right?
[00:31:28.440 --> 00:31:32.680] And your number two asset is money, but only because money buys you time.
[00:31:32.680 --> 00:31:34.600] C number one, you know what I mean?
[00:31:34.600 --> 00:31:37.560] And so let's say you are truly bootstrapping.
[00:31:37.560 --> 00:31:41.400] If you're around with DevOps, you're that's a catastrophic mistake.
[00:31:41.400 --> 00:31:53.520] And let's say you raise a million dollars and you hire a DevOps person to run your servers out of that million and you save the same amount of money or something.
[00:31:53.520 --> 00:32:01.760] Like it's just, you have another person on your team that really you probably don't need, you know, I just can't justify it in any, in almost, as you said, 99.9.
[00:32:01.760 --> 00:32:03.920] So maybe one out of a thousand or one out of 500.
[00:32:03.920 --> 00:32:08.880] Like there's some number where this is probably appropriate, but otherwise, don't make this mistake.
[00:32:08.880 --> 00:32:11.760] And it is a little bit of, yeah, it's cargo culting in a way.
[00:32:11.760 --> 00:32:14.720] It's kind of like it's listening to advice from the wrong folks.
[00:32:14.720 --> 00:32:19.040] It's just also like, don't follow Silicon Valley founders and see how they grow their company.
[00:32:19.040 --> 00:32:23.200] And then as a bootstrapper, think that's how you're going to do it because usually their advice doesn't apply.
[00:32:23.200 --> 00:32:25.040] So thanks for that question, Lewis.
[00:32:25.120 --> 00:32:26.320] Hope it was helpful.
[00:32:26.320 --> 00:32:29.760] Our next question gives me some PTSD, Derek.
[00:32:29.760 --> 00:32:31.600] So I'm going to let you weigh in first.
[00:32:31.600 --> 00:32:33.600] This is from Kyle.
[00:32:38.400 --> 00:32:39.840] Hey, Rob, my name is Kyle.
[00:32:39.840 --> 00:32:41.440] I've listened to the show for a long time.
[00:32:41.440 --> 00:32:46.000] I've actually had you answer one or two of my questions on the show, I think, in the past.
[00:32:46.000 --> 00:33:02.640] Just to kind of get straight to it, basically, we are a client and project tracking tool for tattoo artists that also allows them to schedule appointments and send kind of appointment reminders and whatnot.
[00:33:02.640 --> 00:33:06.160] So my question really is about that last piece of the puzzle.
[00:33:06.320 --> 00:33:09.600] Kind of think of like a Vegaro or QE or Schedule Easta.
[00:33:09.840 --> 00:33:11.200] There are lots of them out there.
[00:33:11.200 --> 00:33:24.720] One of the issues that we've heard from artists that we've talked to so far that they have on those other platforms is emails getting sent to spam or not delivered or similar issues, right?
[00:33:25.040 --> 00:33:31.800] And what I'm trying to figure out is just kind of steps or steps I could take or tools I could use to help limit that risk.
[00:33:32.040 --> 00:33:40.280] The plan is to use SendGrid for all those automated and customized messages that come out of the platform to our artists' clients.
[00:33:40.520 --> 00:33:47.240] But yeah, any insight you might have on how we can help mitigate that risk just from day one would be greatly appreciated.
[00:33:47.240 --> 00:33:48.440] Thanks in advance.
[00:33:48.440 --> 00:33:52.360] Hopefully you get time to hit this question and keep doing the good work.
[00:33:52.360 --> 00:33:59.320] You've been a great help to me so far, as well as countless other founders and hopeful founders.
[00:33:59.320 --> 00:34:00.200] Thanks, Rob.
[00:34:00.200 --> 00:34:01.240] Take care.
[00:34:01.240 --> 00:34:09.640] So, Derek, having never managed email sending infrastructure nor dealt with blacklists and deliverability, would you care to weigh in?
[00:34:09.640 --> 00:34:22.760] Should we give folks background who don't know that we started Drip, which it was sending, I don't know, by the time we left, so we sold it in 2016, left in 2018, I believe, and it was sending 150 million emails a month, maybe by the time we left.
[00:34:22.760 --> 00:34:27.480] And we started what with Mandrel and then we used Mailgun and we used SendGrid.
[00:34:27.480 --> 00:34:30.040] So we use multiple sending providers.
[00:34:30.040 --> 00:34:32.520] But to our point from the prior question, you know what we never did?
[00:34:32.520 --> 00:34:34.760] We never spun up our own email sending servers.
[00:34:34.840 --> 00:34:35.640] You know what I mean?
[00:34:35.640 --> 00:34:36.600] That's kind of equivalent.
[00:34:36.600 --> 00:34:37.560] It would have been way cheaper.
[00:34:37.560 --> 00:34:40.680] I mean, our SendGrid bill by the end, it was a lot of money.
[00:34:40.680 --> 00:34:47.160] And I don't remember exactly, but certainly tens of thousands of dollars a year, might even have been six figures.
[00:34:47.160 --> 00:34:50.200] And so, could you justify hiring someone in SpaceX servers?
[00:34:50.200 --> 00:34:51.880] Maybe I would do it.
[00:34:51.880 --> 00:34:52.280] Yeah.
[00:34:52.280 --> 00:34:54.520] All that said, you know, this is about email deliverability.
[00:34:54.520 --> 00:34:56.040] What do you, what are your thoughts here?
[00:34:56.040 --> 00:34:56.280] Yeah.
[00:34:56.280 --> 00:35:02.520] So, I mean, taking the point that, like, even running Drip, we never endeavored to do our own email sending.
[00:35:02.520 --> 00:35:08.600] I mean, I think point number one is definitely use a mature provider in the space like SendGrid.
[00:35:08.600 --> 00:35:12.120] Postmark is another good one that's been around a long time.
[00:35:12.120 --> 00:35:14.600] I use them for SavvyCal sending.
[00:35:14.600 --> 00:35:16.000] I think Amazon has a service.
[00:35:16.320 --> 00:35:28.480] So, yeah, there are a handful of these out there that, you know, their sole purpose is to manage pools of IP addresses and sending reputation with all the major email service provider or ISPs.
[00:35:28.480 --> 00:35:36.960] Postmark just recently had an incident where a bunch of their emails coming out of their system were getting flagged by Google, I think.
[00:35:36.960 --> 00:35:45.360] And at a certain point, a status page post came out and they're like, we are actively talking to Google to mitigate the issue.
[00:35:45.360 --> 00:35:48.080] And within a few hours, the issue was mitigated.
[00:35:48.080 --> 00:35:57.360] And can you imagine, like, if you were responsible for getting your stuff into people's inboxes, not using a middleman like that, like, are you going to call up Google?
[00:35:57.360 --> 00:35:58.560] Like, no.
[00:35:58.560 --> 00:36:01.600] So I don't think that's what our asker here is asking.
[00:36:01.600 --> 00:36:10.000] Like, he obviously knows, you know, use an email sending provider, but I just wanted to underscore that point that you definitely want to use a SendGrid or something like that.
[00:36:10.000 --> 00:36:16.400] Beyond that, DMARC has become a very important part of email authentication these days.
[00:36:16.400 --> 00:36:20.960] I think all the major email providers look for a strong DMARC policy.
[00:36:20.960 --> 00:36:24.560] So you can Google that or ChatGPT that to get more details about it.
[00:36:24.560 --> 00:36:30.400] Look to your provider of choice for instructions on how to make sure you have that stuff dialed in for their system.
[00:36:30.400 --> 00:36:39.440] And of course, your DKIM and all the DNS-level authentication stuff to make sure that your own domain is in a good place.
[00:36:39.440 --> 00:36:54.880] And then I think the other couple other big pieces here, when you're sending email, so it sounds like this is similar structure to what SavvyCal does, where like we send new appointment emails and reminders and things to people who schedule through our system.
[00:36:54.880 --> 00:36:59.280] So we have a lot of emails going out to people scheduling into the system.
[00:36:59.280 --> 00:37:08.520] And so you need to make sure that any place where an email address can get in, so that's through the booking pages, that you have good spam protection there.
[00:37:08.520 --> 00:37:17.160] Because if you have people, malicious actors, hitting those and putting junk email addresses through your system, that's going to reflect back on your domain's reputation.
[00:37:17.160 --> 00:37:18.840] And that's the biggest thing.
[00:37:19.000 --> 00:37:23.960] With email deliverability, point number one is always like, well, make sure you have high quality sending.
[00:37:23.960 --> 00:37:31.720] And it's like, well, easier said than done in a lot of cases, but the biggest thing you can do is make sure that you're protecting all the places where emails can get in.
[00:37:31.720 --> 00:37:34.440] I also these days like to use an email validation service.
[00:37:34.440 --> 00:37:41.800] I use emailable, and you can run email addresses through it, and it'll confirm to the best of its ability whether it's a valid email address.
[00:37:41.800 --> 00:37:50.200] And that keeps your bounce rate low and just makes sure that like the less invalid email you attempt to send on your domain, the better for your reputation.
[00:37:50.200 --> 00:37:53.480] And then also MX Toolbox, that's kind of an oldie but goody tool.
[00:37:53.480 --> 00:37:55.880] We used it back in the day with Drip and it's still around.
[00:37:55.880 --> 00:38:00.920] And you can use that to just kind of keep tabs on your email sending reputation.
[00:38:00.920 --> 00:38:04.120] And yeah, just make sure that you're not ending up on blacklists.
[00:38:04.120 --> 00:38:05.000] There it is.
[00:38:05.000 --> 00:38:05.880] That's a clinic.
[00:38:05.880 --> 00:38:07.560] We should make that into a course.
[00:38:09.800 --> 00:38:13.480] I don't have much to add, although I thought of a couple things.
[00:38:13.480 --> 00:38:18.360] We used Mandaril and their deliverability was phenomenal back in the day.
[00:38:18.360 --> 00:38:25.560] And they allowed marketing email at the time and then they kicked everyone off sending marketing email and it's only transactional now.
[00:38:25.560 --> 00:38:31.400] These days, if you were to ask me who I would use, it'd probably be Mandrel if it's purely transactional.
[00:38:31.400 --> 00:38:34.920] I would verify that and check with other people and this and that.
[00:38:34.920 --> 00:38:41.560] But I remember, I mean, MailChimp's infrastructure is so good and they've had it for so long that Mandarill is an extension of MailChimp.
[00:38:41.560 --> 00:38:45.200] So definitely add that to the list of, you know, the postmarks and the send grids.
[00:38:44.760 --> 00:38:48.160] The other thing is there is a tiny C company that kind of helps with all this.
[00:38:48.240 --> 00:38:54.640] They're called SkySnag and they help with DECIM and they monitor all this stuff and monitor phishing and this and that.
[00:38:54.640 --> 00:38:56.960] So if you're listening to this and you're like, man, I don't really know what I'm doing.
[00:38:56.960 --> 00:39:00.240] Like skysnag.com is probably a place to check out.
[00:39:00.240 --> 00:39:04.400] And the last thought is, because I agree with everything you said and I think that's that's great advice.
[00:39:04.400 --> 00:39:11.040] The other thing is this is why a lot of folks have you noticed how many are asking for phone numbers and doing SMS now for reminders?
[00:39:11.040 --> 00:39:18.880] Like my haircut place only does SMS and it's because they know inboxes are full and there's the multiple inboxes, right?
[00:39:18.880 --> 00:39:24.400] I don't use these like in Gmail, but where it's the promotions tab, reminders get in there and SMS is more direct.
[00:39:24.400 --> 00:39:28.320] Now your RSMS inboxes, so to speak, are getting crowded.
[00:39:28.320 --> 00:39:30.400] And so then we're going to have to move to WhatsApp or something.
[00:39:30.400 --> 00:39:39.920] But that's the other thing to think about is: you know, is in certain areas, like especially appointment reminders and stuff, most of the ones I receive now are via text.
[00:39:39.920 --> 00:39:44.480] And so that doesn't remove the need to comply with stuff.
[00:39:44.480 --> 00:39:46.160] There's a bunch of regulations around this.
[00:39:46.160 --> 00:39:55.200] You know, we have, I mean, gosh, there's got to be, there's at least 10 probably tiny C companies where SMS is like their main focus and their main value prop.
[00:39:55.200 --> 00:39:59.360] And then there's probably another 20, if not more, that actually send SMS.
[00:39:59.360 --> 00:40:02.400] And so there are some hurdles there.
[00:40:02.400 --> 00:40:13.600] But if you use the equivalent, if you use a Twilio and you don't need a dedicated number for each of your customers and you kind of just have a few, I think it's significantly less complicated than one might think.
[00:40:13.600 --> 00:40:15.520] So thanks for that question, Kyle.
[00:40:15.520 --> 00:40:17.040] I hope it was helpful.
[00:40:17.040 --> 00:40:21.360] Our last question for today is from Mike.
[00:40:26.160 --> 00:40:26.960] Hi, Rob.
[00:40:26.960 --> 00:40:28.320] My name is Mike.
[00:40:28.320 --> 00:40:39.160] I was listening to your EMA for the SaaS Launchpad course, and you made a statement that for enterprise or other companies selling to the enterprise, you'd want a salesperson.
[00:40:39.160 --> 00:40:44.280] And for somebody targeting like Web Editor, SMBs, you'd want a marketer on your team.
[00:40:44.280 --> 00:40:56.760] Can you expand on your thinking between the differences and how does that affect what your choices are in terms of what kind of business you might want to start or how you give advice to people deciding what kind of business they want to start?
[00:40:56.760 --> 00:41:08.120] And then how critical is it to have either skill set on the founding team or can, for example, the sales side for the enterprise, could that be learned from something like Founding Salesbook by Pete Kazanchi?
[00:41:08.120 --> 00:41:09.640] Thank you for everything you do.
[00:41:09.640 --> 00:41:13.880] I think the first question maybe is like sales versus marketing.
[00:41:13.880 --> 00:41:14.600] What's the difference?
[00:41:14.600 --> 00:41:16.440] But just very fundamentally, right?
[00:41:16.440 --> 00:41:20.600] And the way I think about it is marketing is generating demand, right?
[00:41:20.600 --> 00:41:38.120] So this is going out and getting in Google search results or running ads or doing any of the 20 B2B SaaS marketing approaches I have in the SaaS playbook, doing integrations and having someone else talk about you to their audience, any of these things that gets you and your app and your value proposition in front of them.
[00:41:38.120 --> 00:41:39.880] And that is inbound, right?
[00:41:39.880 --> 00:41:43.960] And then people come to your website and they either book a demo or they sign up for a free teller.
[00:41:43.960 --> 00:41:44.680] That's marketing, right?
[00:41:44.680 --> 00:41:45.800] It's spreading the word.
[00:41:45.800 --> 00:41:47.640] Sales is a couple things.
[00:41:47.640 --> 00:41:50.120] Like sales is often outbound, right?
[00:41:50.120 --> 00:41:51.640] It's approaching on LinkedIn.
[00:41:51.640 --> 00:41:54.120] It's all the cold emails we get on a typical day.
[00:41:54.120 --> 00:41:56.200] It's the Twitter DMs and all that stuff.
[00:41:56.200 --> 00:42:01.000] And then it's doing the demos face to face, in essence, right over Zoom.
[00:42:01.160 --> 00:42:03.400] It used to be in person, obviously, years ago.
[00:42:03.400 --> 00:42:05.320] And it is trying to close a sale.
[00:42:05.320 --> 00:42:07.800] So, just marketing versus sales, those are two things.
[00:42:07.800 --> 00:42:08.920] They are complementary.
[00:42:08.920 --> 00:42:12.440] Sometimes, if you have a low-touch, no-touch funnel, you don't have sales at all.
[00:42:12.440 --> 00:42:14.520] You don't do any outbound and you don't do demos.
[00:42:14.520 --> 00:42:17.280] And so, it's purely a marketing-driven SaaS.
[00:42:17.280 --> 00:42:20.400] And that is kind of the bootstrapper indie hacker dream.
[00:42:14.760 --> 00:42:21.120] It's pretty rare.
[00:42:21.360 --> 00:42:30.000] And in fact, those tend to need lower price points so then they have higher churn and they don't grow into multi-million dollar businesses.
[00:42:30.320 --> 00:42:44.480] It can happen, but it's often bringing sales in, doing demos, and closing the $2,000 a month deal versus the $200 a month deal or the $20 a month deal that really kicks that engine into growing into that seven or eight figure mark.
[00:42:44.480 --> 00:42:47.040] So, I want to kind of want to level set that with some definitions.
[00:42:47.040 --> 00:42:50.880] But then, beyond that, enterprise versus SMBs.
[00:42:50.880 --> 00:42:52.160] What do you think?
[00:42:52.480 --> 00:42:55.920] Yeah, there's also kind of different levels inside of here, right?
[00:42:55.920 --> 00:42:57.920] Like the definition of a small business.
[00:42:57.920 --> 00:43:01.440] Some would say a small business is up to 100 million a year in revenue or something.
[00:43:01.440 --> 00:43:03.760] And it's like, that's usually not what we mean by that.
[00:43:03.760 --> 00:43:17.520] When we say small business, we're usually talking like much, much smaller, like maybe a team of 10 people or something like that, and versus like, and we often qualify enterprise as like capable of buying at a higher price point, basically, right?
[00:43:17.840 --> 00:43:21.040] And the grass is always greener on the other side, I will say.
[00:43:21.040 --> 00:43:23.680] Like, this is kind of a choose your pain.
[00:43:23.680 --> 00:43:30.640] Like, if you go with the higher price point product and you're able to do sales for it, then you typically have longer cycles.
[00:43:30.640 --> 00:43:34.400] Like, there's more involved, more investment involved in order to make a sale.
[00:43:34.400 --> 00:43:40.400] Cost to acquire a customer is often higher, but you can offset that with a higher price point.
[00:43:40.400 --> 00:43:53.760] But I've talked to plenty of founders who get frustrated with this motion and like needing to have all these conversations and make it through procurement and all of the kind of sucky things that come along with that piece.
[00:43:53.760 --> 00:44:06.040] But on the flip side, when you're going marketing-driven, you generally have a lower price point, people are more price-sensitive, churns higher, and it can be really difficult to move the needle on these lower-price point businesses.
[00:44:06.200 --> 00:44:08.120] Don't ask me how I know that.
[00:44:08.280 --> 00:44:09.800] Asking for a friend.
[00:44:09.800 --> 00:44:25.480] Yeah, because each individual customer is only paying you a little bit of money, and you have to be really good at getting a lot of distribution and showing people who care enough about the differences between you and maybe a bunch of other options on the market, like, why should they pick you?
[00:44:25.480 --> 00:44:28.840] And some of this just comes from being around for a while.
[00:44:28.840 --> 00:44:41.240] Like, it just takes a while to build up reputation where you're showing up in conversations and making it onto the lists where people are comparing different products and making it into Chat GPT so that it starts recommending you.
[00:44:41.240 --> 00:44:45.320] Like, I don't know who the hell knows how to actually do that other than just be around, you know?
[00:44:45.320 --> 00:44:54.760] So, there's so many things involved with the marketing-driven approach where, and obviously, if you're a master marketer, you will have better success at like building up a business with this approach.
[00:44:54.760 --> 00:44:59.160] But I guess all that to say, both of these approaches take a certain amount of expertise.
[00:44:59.160 --> 00:45:12.680] And I think typically the more sales-driven approach is something where you can kind of brute force it a little easier, I guess, than the marketing-driven approach, which is like you just have to get really good at generating a ton of traffic in the right places.
[00:45:12.680 --> 00:45:15.240] And that is a bit of a dark art for many of us.
[00:45:15.560 --> 00:45:17.400] Yeah, and I like the way you put that.
[00:45:17.400 --> 00:45:19.800] And it's not just two, it's not a dichotomy, right?
[00:45:19.800 --> 00:45:25.720] There's like small and medium-sized businesses, and which I think of like, oh, is there one decision-maker usually, you know?
[00:45:25.720 --> 00:45:28.840] And oftentimes, is the decision maker also the user of the software?
[00:45:28.840 --> 00:45:37.080] So, maybe that's even like solopreneurs, you know, or prosumers, and they're extremely price-sensitive because they think of the money they're spending as their money.
[00:45:37.240 --> 00:45:39.160] So, they think of it almost like consumers.
[00:45:39.160 --> 00:45:45.000] And then SMBs, maybe a notch up, and then there's mid-market, and then there's enterprise, and there's this whole spectrum of it.
[00:45:45.120 --> 00:46:00.320] But generally, the tough part is if you get these big, big contracts, let's say you're selling $250,000 a year, which we have some tiny seed companies, that's their contract size, but they only close a deal every quarter or every six months, and it's just brutal and agonizing.
[00:46:00.320 --> 00:46:05.120] And there's no momentum, and it's super, it's not even, it's spiky in a way that's just not that fun.
[00:46:05.120 --> 00:46:10.000] And as you said, you know, months in procurement, but they close these really big deals and they have this negative churn.
[00:46:10.000 --> 00:46:11.200] You know, everybody's expanding.
[00:46:11.200 --> 00:46:21.120] That's great, except for it's kind of agonizing as, you know, as the founder, on the flip side, you're charging 15 bucks a month and your churn's really high and it's hard to hard to outrun that churn.
[00:46:21.120 --> 00:46:22.480] You need a really massive funnel.
[00:46:22.480 --> 00:46:29.760] I'll say it's impossible to outrun, you know, the churn of a $15 a month business if you want to become, let's say, a $10 million or $20 million business.
[00:46:29.760 --> 00:46:34.800] And that's why, like, when we started Drip, it was $50 a month, $100, $150,000 I think those are the price points.
[00:46:34.800 --> 00:46:42.880] But we soon realized like people were reaching out with really big email lists and they were like, oh, I would pay you $500 a month based on my list size or $1,000 a month.
[00:46:42.880 --> 00:46:46.320] Or I think when we left, there were people paying us two or three grand a month.
[00:46:46.320 --> 00:46:51.120] You know, and these were getting, these are not enterprise in the enterprise sense, but for us, they're enterprise.
[00:46:51.280 --> 00:46:56.400] It's anything over 25K, I kind of think of it as like a bootstrapper enterprise plan.
[00:46:56.400 --> 00:46:58.960] And that was pretty interesting, right?
[00:46:59.040 --> 00:47:00.720] And this is, I call this a dual funnel.
[00:47:00.720 --> 00:47:05.920] It's where you have folks paying you no churn and paying you a lot of money on the top end.
[00:47:05.920 --> 00:47:09.440] And you do have some folks doing sales demos and procurement, maybe.
[00:47:09.440 --> 00:47:15.360] But then you have this nice low-touch funnel that usually has higher churn, more price-sensitive customers on the bottom end.
[00:47:15.360 --> 00:47:17.920] And this only works in really, I think, pretty big markets.
[00:47:17.920 --> 00:47:25.280] Like it doesn't work in these tight niches, but that's a nice way to even it out to get a little bit of the best of both worlds if you can swing it.
[00:47:25.280 --> 00:47:29.360] You know, and we've seen like Ruben with Seinwell has that type of funnel, right?
[00:47:29.360 --> 00:47:33.880] And like Riverside or Squadcast has that type of funnel.
[00:47:33.880 --> 00:47:40.600] And it's not always possible, but it is a way to even out the agony of, oh, we close a deal every three months.
[00:47:40.600 --> 00:47:41.720] This is fun.
[00:47:42.120 --> 00:47:43.640] This is so great.
[00:47:43.960 --> 00:47:51.480] Yeah, and I can imagine just if it's that extreme where it's like, you know, hundreds of thousands of dollars from individual customers.
[00:47:51.480 --> 00:47:54.520] And I'm sure there's a bit of cost involved with maintaining those.
[00:47:54.520 --> 00:47:59.080] So it's like you would want to make sure you have the people on staff to maintain that.
[00:47:59.080 --> 00:48:04.280] But if one of those churns and it's like, oh my gosh, we have to replace them or else we're yeah.
[00:48:04.280 --> 00:48:17.320] So yeah, like having a bit of diversification is probably ideal where you don't have too much customer concentration to the point where you're like potentially have to lay someone off from your team if the customer cancels or whatever, but it's business.
[00:48:17.320 --> 00:48:19.880] So you got to do it.
[00:48:20.440 --> 00:48:21.640] So thanks for that question, Mike.
[00:48:21.640 --> 00:48:24.760] And Mike actually sent in another question, but we don't have time to get to it today.
[00:48:24.760 --> 00:48:27.560] So I will answer that in a future episode.
[00:48:27.560 --> 00:48:33.320] Derek Reimer, folks want to use the best scheduling link on the internet, head to savvycal.com.
[00:48:33.320 --> 00:48:43.160] And as a reminder, if you are an agency or a freelancer consultant and you are building solutions for folks who are booking appointments, right?
[00:48:43.160 --> 00:48:46.920] This is like service businesses and other types of folks.
[00:48:47.160 --> 00:48:49.240] You should reach out to Derek to find out what he's building.
[00:48:49.720 --> 00:48:50.760] I'd love to chat.
[00:48:50.760 --> 00:48:51.400] Yeah.
[00:48:51.400 --> 00:48:54.840] D-E-R-R-I-C-K at savvycal.com.
[00:48:54.840 --> 00:48:56.040] Thanks again for joining me.
[00:48:56.040 --> 00:48:57.400] Thanks for having me.
[00:48:57.400 --> 00:48:59.560] Thanks again to Derek for coming on the show.
[00:48:59.560 --> 00:49:09.640] And a reminder, SASLANCHPAD.co and use the code launch to get $150 off the course, as well as Microconf Remote is happening tomorrow.
[00:49:09.640 --> 00:49:12.280] That's microconf.com/slash remote.
[00:49:12.280 --> 00:49:14.440] Thanks for listening this week and every week.
[00:49:14.440 --> 00:49:18.320] This is Rob Walling signing off from episode 775.
[00:49:53.600 --> 00:50:00.080] Derek, I have four fifth edition Dungeons and Dragons trivia questions for you.
[00:50:00.080 --> 00:50:02.880] Order from easiest to hardest.
[00:50:03.520 --> 00:50:12.800] The first is in combat in fifth edition Dungeons and Dragons, what determines the order in which characters act?
[00:50:13.440 --> 00:50:14.880] You roll for initiative.
[00:50:14.960 --> 00:50:16.000] There it is.
[00:50:16.000 --> 00:50:16.560] All right.
[00:50:16.560 --> 00:50:18.320] That's one out of four.
[00:50:18.320 --> 00:50:19.040] All right.
[00:50:19.040 --> 00:50:26.880] Second question: if you attack a prone enemy with a melee attack, what do you gain?
[00:50:27.840 --> 00:50:28.640] Advantage.
[00:50:28.640 --> 00:50:30.480] You do indeed gain advantage?
[00:50:30.480 --> 00:50:31.440] Two out of four.
[00:50:31.440 --> 00:50:31.760] All right.
[00:50:32.160 --> 00:50:32.880] Capital A advantage.
[00:50:33.040 --> 00:50:34.080] Capital A.
[00:50:35.040 --> 00:50:36.000] All right.
[00:50:36.000 --> 00:50:37.680] This one, it's getting harder.
[00:50:38.400 --> 00:50:45.920] When attacking a creature you cannot see because they're invisible, hidden, etc., what disadvantage do you suffer?
[00:50:46.240 --> 00:50:48.000] Do they have surprise on you?
[00:50:48.000 --> 00:50:48.960] Incorrect.
[00:50:48.960 --> 00:50:53.920] What disadvantage do you suffer when you attack them if they're invisible?
[00:50:53.920 --> 00:50:54.880] When I attack.
[00:50:54.880 --> 00:50:55.600] Oh, okay.
[00:50:55.600 --> 00:50:56.000] Okay.
[00:50:56.320 --> 00:51:02.440] Well, wait, you can make an attack on someone who's invisible, like not like you, you know they're there, but you can't see them.
[00:51:02.440 --> 00:51:06.360] Or hidden, like if you know, thieves or rogues, I guess, can hide in shadows.
[00:51:06.520 --> 00:51:07.000] I see.
[00:51:07.000 --> 00:51:07.800] I see.
[00:51:08.760 --> 00:51:09.720] I don't know.
[00:51:09.720 --> 00:51:12.360] You have disadvantage on your attack roll.
[00:51:12.360 --> 00:51:12.840] No.
[00:51:12.840 --> 00:51:13.160] Oh.
[00:51:13.480 --> 00:51:14.200] Kind of makes sense, right?
[00:51:14.360 --> 00:51:15.000] Should have discussed that.
[00:51:15.560 --> 00:51:16.280] Totally.
[00:51:16.280 --> 00:51:17.000] All right.
[00:51:17.000 --> 00:51:18.120] What disadvantage do you have?
[00:51:18.440 --> 00:51:19.480] Disadvantage, yeah.
[00:51:19.480 --> 00:51:21.000] It has it as lowercase D.
[00:51:21.000 --> 00:51:22.200] It should be uppercase.
[00:51:22.200 --> 00:51:25.160] And then the fourth and final.
[00:51:25.160 --> 00:51:27.080] Ah, that one's too easy.
[00:51:27.080 --> 00:51:27.720] Oh, my God.
[00:51:27.720 --> 00:51:29.080] These are really easy.
[00:51:29.080 --> 00:51:32.200] I asked ChatGPT for 10 and I said make them easy to hard.
[00:51:32.200 --> 00:51:35.080] And I meant like eight, nine, and ten, and they're just gimme.
[00:51:35.400 --> 00:51:41.000] Like, listen, if you roll a natural 20 on an attack roll, what special effect occurs?
[00:51:41.320 --> 00:51:45.960] If you roll a nat 20 on an attack.
[00:51:47.240 --> 00:51:49.560] Wow, maybe it's not as easy as I thought.
[00:51:49.560 --> 00:51:50.600] Hmm.
[00:51:50.920 --> 00:51:51.880] See, this is rare.
[00:51:51.880 --> 00:51:55.240] It's only happened a few times.
[00:51:55.560 --> 00:51:56.760] It happens now and again.
[00:51:56.760 --> 00:51:57.160] Yeah.
[00:51:57.160 --> 00:52:05.080] So if you were to roll a nat 20 on a bow attack or a sword attack, what do we do?
[00:52:05.080 --> 00:52:06.440] Do you get an extra attack?
[00:52:06.440 --> 00:52:09.960] You get it's a critical hit is what it's called.
[00:52:09.960 --> 00:52:14.600] And you roll your damage dice twice, but you only take the bonus.
[00:52:14.760 --> 00:52:15.960] You know how there's a damage bonus?
[00:52:15.960 --> 00:52:18.360] You only take that once, but you roll the damage die twice.
[00:52:18.360 --> 00:52:18.600] Right.
[00:52:18.600 --> 00:52:20.040] There are some DMs that it's all.
[00:52:20.040 --> 00:52:24.920] A lot of this is house rule, but like, let's say you're doing a D8 plus three damage, right?
[00:52:24.920 --> 00:52:27.960] Some DMs will just say you do max damage automatically.
[00:52:27.960 --> 00:52:30.840] Some will say you do two dice max damage.
[00:52:30.840 --> 00:52:33.160] That feels like a lot to me because that would be 19 points of damage.
[00:52:33.160 --> 00:52:34.440] And others say roll it twice.
[00:52:34.440 --> 00:52:35.080] That's what I do.
[00:52:35.080 --> 00:52:37.000] Roll it twice, add, add three.
[00:52:37.320 --> 00:52:38.200] All right.
[00:52:38.200 --> 00:52:39.640] Bonus question.
[00:52:39.640 --> 00:52:47.680] What condition occurs if your hit points become negative, equal to, or greater than your maximum hit points from a single attack?
[00:52:48.000 --> 00:52:56.800] So let's say you had 20, your max hit points are 20, and you took 41 points of damage with a single attack, like a dragon breath.
[00:52:56.800 --> 00:52:58.080] What would happen to you?
[00:52:58.080 --> 00:52:59.520] Is that an instant kill?
[00:52:59.520 --> 00:53:00.080] It is.
[00:53:00.080 --> 00:53:00.480] Yeah.
[00:53:00.800 --> 00:53:05.280] You immediately die versus the fifth edition freaking death-saving throws.
[00:53:05.920 --> 00:53:08.720] I was going to say, you must be extremely dead in that case.
[00:53:09.120 --> 00:53:09.520] Yeah.
[00:53:09.520 --> 00:53:12.080] I think I actually played as 10 below.
[00:53:12.080 --> 00:53:13.280] Is that what I did?
[00:53:13.280 --> 00:53:17.520] See, I said if you went negative, I think I've been house rolling negative 10.
[00:53:17.520 --> 00:53:18.640] That's yeah, I think so.
[00:53:18.640 --> 00:53:20.480] I think that's what I did, which is interesting.
[00:53:20.480 --> 00:53:21.680] It's slightly more deadly.
[00:53:21.680 --> 00:53:27.040] But if you have 50 hit points, let's say, and you go to negative 10, that can happen, you know?
[00:53:27.040 --> 00:53:27.680] Yeah.
[00:53:27.680 --> 00:53:34.000] Meaning if your max is 50, but you're as you start to get down and get damaged, like going to negative 10 is not unheard of.
[00:53:34.000 --> 00:53:37.040] So I like there to be death possible, man.
[00:53:37.360 --> 00:53:43.120] Yeah, and in our campaign, none of us have ever died yet with that house rule.
[00:53:43.120 --> 00:53:52.720] So but in the other, the early, the Fandelver one where it was first and second level characters, I lost two, I lost two and one Dragon Breath.
[00:53:52.720 --> 00:53:54.560] And I was like, oops.
[00:53:55.200 --> 00:53:59.440] I bet you went kind of easy on us on the other campaign that we started years ago.
[00:53:59.440 --> 00:53:59.920] You probably did.
[00:54:00.160 --> 00:54:00.720] I did.
[00:54:00.720 --> 00:54:02.400] I didn't really want anybody to die.
[00:54:02.800 --> 00:54:08.480] I mean, I never, I didn't like fudge dice rolls, but I always kind of made sure it's really hard DMing.
[00:54:08.480 --> 00:54:09.120] Not really hard.
[00:54:09.120 --> 00:54:14.160] It is difficult DMing like first and second level campaigns because they're so fragile, you know?
[00:54:14.160 --> 00:54:14.640] Yeah.
[00:54:14.960 --> 00:54:15.440] So.
[00:54:15.440 --> 00:54:15.920] Yeah.
[00:54:15.920 --> 00:54:18.320] Well, Derek Reimer, thanks for playing.
[00:54:18.640 --> 00:54:20.640] Well, that was nerve-wracking.
[00:54:20.640 --> 00:54:21.040] Thanks.
[00:54:21.040 --> 00:54:21.600] Thanks for having me.
[00:54:21.760 --> 00:54:22.480] You did okay.
[00:54:22.880 --> 00:54:25.360] You got four out of five, if I'm counting correctly.
[00:54:25.360 --> 00:54:26.960] Yeah, let's call it that.
[00:54:26.960 --> 00:54:29.440] Yeah, let's call it that, he says.
Prompt 2: Key Takeaways
Now please extract the key takeaways from the transcript content I provided.
Extract the most important key takeaways from this part of the conversation. Use a single sentence statement (the key takeaway) rather than milquetoast descriptions like "the hosts discuss...".
Limit the key takeaways to a maximum of 3. The key takeaways should be insightful and knowledge-additive.
IMPORTANT: Return ONLY valid JSON, no explanations or markdown. Ensure:
- All strings are properly quoted and escaped
- No trailing commas
- All braces and brackets are balanced
Format: {"key_takeaways": ["takeaway 1", "takeaway 2"]}
Prompt 3: Segments
Now identify 2-4 distinct topical segments from this part of the conversation.
For each segment, identify:
- Descriptive title (3-6 words)
- START timestamp when this topic begins (HH:MM:SS format)
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Most important Key takeaway from that segment. Key takeaway must be specific and knowledge-additive.
- Brief summary of the discussion
IMPORTANT: The timestamp should mark when the topic/segment STARTS, not a range. Look for topic transitions and conversation shifts.
Return ONLY valid JSON. Ensure all strings are properly quoted, no trailing commas:
{
"segments": [
{
"segment_title": "Topic Discussion",
"timestamp": "01:15:30",
"key_takeaway": "main point from this segment",
"segment_summary": "brief description of what was discussed"
}
]
}
Timestamp format: HH:MM:SS (e.g., 00:05:30, 01:22:45) marking the START of each segment.
Prompt 4: Media Mentions
Now scan the transcript content I provided for ACTUAL mentions of specific media titles:
Find explicit mentions of:
- Books (with specific titles)
- Movies (with specific titles)
- TV Shows (with specific titles)
- Music/Songs (with specific titles)
DO NOT include:
- Websites, URLs, or web services
- Other podcasts or podcast names
IMPORTANT:
- Only include items explicitly mentioned by name. Do not invent titles.
- Valid categories are: "Book", "Movie", "TV Show", "Music"
- Include the exact phrase where each item was mentioned
- Find the nearest proximate timestamp where it appears in the conversation
- THE TIMESTAMP OF THE MEDIA MENTION IS IMPORTANT - DO NOT INVENT TIMESTAMPS AND DO NOT MISATTRIBUTE TIMESTAMPS
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Timestamps are given as ranges, e.g. 01:13:42.520 --> 01:13:46.720. Use the EARLIER of the 2 timestamps in the range.
Return ONLY valid JSON. Ensure all strings are properly quoted and escaped, no trailing commas:
{
"media_mentions": [
{
"title": "Exact Title as Mentioned",
"category": "Book",
"author_artist": "N/A",
"context": "Brief context of why it was mentioned",
"context_phrase": "The exact sentence or phrase where it was mentioned",
"timestamp": "estimated time like 01:15:30"
}
]
}
If no media is mentioned, return: {"media_mentions": []}
Full Transcript
[00:00:00.240 --> 00:00:02.560] This podcast is brought to you by Mercury.
[00:00:02.560 --> 00:00:09.840] I've been banking with Mercury for years, and whenever I set up a new account, I'm reminded why traditional banking feels stuck in the past.
[00:00:09.840 --> 00:00:17.760] When our previous bank faced solvency issues, we needed to spin up new accounts quickly that could handle millions in funds across multiple businesses.
[00:00:17.760 --> 00:00:20.480] Mercury had us up and running almost immediately.
[00:00:20.480 --> 00:00:33.200] I manage half a dozen different Mercury accounts across a wide range of companies, from my personal single-member LLC, to MicroConf, our seven-figure global events and education platform, to TinySeed, our venture fund and accelerator.
[00:00:33.200 --> 00:00:35.360] Mercury easily handles them all.
[00:00:35.360 --> 00:00:50.080] The interface is elegantly simple for daily banking, paying invoices, and sending and receiving international wires, yet powerful enough to handle the multi-step approval processes we needed to put in place when funding founders with large transfers.
[00:00:50.080 --> 00:00:55.120] Anytime founders ask me who they should set up their accounts with, I send them to mercury.com.
[00:00:55.120 --> 00:01:01.040] Check the show notes for more details and note that Mercury is a financial technology company, not a bank.
[00:01:01.040 --> 00:01:03.520] It's another episode of Startups for the Rest of Us.
[00:01:03.520 --> 00:01:05.280] I'm your host, Rob Walling.
[00:01:05.280 --> 00:01:10.720] And in this episode, Derek Reimer and I sit down and we answer listener questions.
[00:01:10.720 --> 00:01:21.360] We answer a question about the impact of new AI coding tools, talk about user experience and how much time you should or shouldn't invest in the early days.
[00:01:21.360 --> 00:01:31.040] Talk about racking your own servers versus cloud hosting, the trade-offs between those two things, email deliverability and reliability, risks around that.
[00:01:31.040 --> 00:01:33.520] And we handle another topic or two.
[00:01:33.520 --> 00:01:37.440] If you could possibly believe it, we packed it in to this amazing episode.
[00:01:37.440 --> 00:01:44.320] And if you stick around till the hidden track at the end, you'll get to hear Derek Reimer get ambushed by my trivia questions.
[00:01:44.320 --> 00:01:49.680] Before we dive into the episode, I want to let you know about some exciting updates to the SAS Launchpad course.
[00:01:49.680 --> 00:01:56.720] It's my nine-and-a-half-hour video course that walks you through the process of going from no idea to your first paying customer.
[00:01:56.720 --> 00:02:03.080] We've just added a new module that dives deep into what founders should think about before adding AI to their SAS.
[00:02:03.320 --> 00:02:06.200] It's actually a private conversation I had with Arvid Kahl.
[00:02:06.200 --> 00:02:10.760] He's been integrating AI into his own SAS, podscan.fm.
[00:02:10.760 --> 00:02:16.280] We talk through the landmines and tricky spots that founders are hitting right now so you can avoid some costly mistakes.
[00:02:16.280 --> 00:02:25.800] And here's the thing I'm really excited about: if you buy and you complete the course material in the next 30 days, you'll be entered for a chance to win a 30-minute one-on-one chat with me.
[00:02:25.800 --> 00:02:31.400] We can talk through your SAS idea, any roadblocks you're running into, or just brainstorm next steps together.
[00:02:31.400 --> 00:02:36.840] If you want to test drive the content first, grab the free sample module at sasslaunchpad.co.
[00:02:36.840 --> 00:02:40.840] It's a 28-minute video all about the DNA of a great SAS idea.
[00:02:40.840 --> 00:02:48.600] As a bonus, our team is giving away a free copy of the full course to one person who watches that video by June 1st.
[00:02:48.600 --> 00:02:55.960] And for loyal podcast listeners, use promo code launch at checkout to get $150 off this course.
[00:02:55.960 --> 00:03:00.760] Get all the details and access the free sample at sasslaunchpad.co.
[00:03:00.760 --> 00:03:03.880] And with that, let's dive into listener questions.
[00:03:14.280 --> 00:03:17.080] Derek Reimer, welcome back to Startups for the Rest of Us.
[00:03:17.400 --> 00:03:18.600] Always a pleasure.
[00:03:18.600 --> 00:03:20.040] It's great to have you back, ma'am.
[00:03:20.040 --> 00:03:22.360] So we are going to dive into listener questions today.
[00:03:22.360 --> 00:03:27.880] I have hand-picked several that I think are well designed for you to answer.
[00:03:27.880 --> 00:03:32.120] Before we do that, though, you've been working on some pretty awesome stuff with SavvyCal.
[00:03:32.120 --> 00:03:38.040] You want to tell folks, give them a hint, give them a teaser, and maybe a little call to action if they want to reach out to you.
[00:03:38.040 --> 00:03:41.720] Yeah, I think this actually might be the first time I'm publicly talking about this.
[00:03:41.720 --> 00:03:48.960] But yeah, we've been working on some interesting new product lines around appointment scheduling.
[00:03:49.360 --> 00:03:54.800] So SavvyCal has historically been sort of a Calendly competitor that's mostly for meeting scheduling.
[00:03:54.800 --> 00:03:59.200] Like, you know, you need to take a sales call or just book something with a colleague or something like that.
[00:03:59.200 --> 00:04:01.600] So meeting scheduling has its own dynamics.
[00:04:01.600 --> 00:04:12.560] And appointment scheduling, it's something that has come up basically the entire time we've been in business, people inquiring about using SavvyCal for scheduling appointments for more service-based businesses.
[00:04:12.560 --> 00:04:24.720] And we're just now starting to work on kind of a second product line that repurposes a lot of the goodness that we've developed over time with SavviCal meetings, but for the appointment scheduling use case.
[00:04:24.720 --> 00:04:30.560] So right now we're kind of partnering with one agency who's using this for a cool new project.
[00:04:30.560 --> 00:04:44.800] But I'd love to have more conversations with folks who are sort of in this space of building sort of custom flows for service-based businesses, whether it's telemedicine or whatever, and need kind of lower-level scheduling infrastructure.
[00:04:44.800 --> 00:04:47.520] Very interested in having those types of conversations.
[00:04:47.520 --> 00:04:48.000] Awesome.
[00:04:48.000 --> 00:04:49.600] So how can folks reach you?
[00:04:49.600 --> 00:04:55.440] Yeah, you can hit me up at derek at savvycal.com over email and I'd love to hear from you.
[00:04:55.440 --> 00:05:00.240] And that's D-E-R-R-I-C-K at savvycal.com.
[00:05:00.240 --> 00:05:03.040] All right, let's dive into listener questions.
[00:05:03.040 --> 00:05:09.920] Our first one is from Zach, and his question is about the impact of new coding tools.
[00:05:09.920 --> 00:05:17.760] He says, Hey, Rob, I just finished your book, and I'm feeling inspired to get started on my next startup, Rocket Ship Emoji, which I love.
[00:05:17.760 --> 00:05:28.560] One thing I was curious on is your take on the new wave of AI coding platforms, cursor, lovable, et cetera, and the impact of these specifically on the micro startup.
[00:05:28.560 --> 00:05:35.240] Does your 300-hour rule still hold up if you can build an MVP in just a few hours?
[00:05:35.240 --> 00:05:38.920] And so, I believe he's referring to in start small, stay small.
[00:05:38.920 --> 00:05:41.560] I used to think, I thought I said four to 600 hours, but whatever.
[00:05:41.560 --> 00:05:44.680] I wrote that book 15 years ago, so maybe I said 300.
[00:05:44.680 --> 00:05:46.360] It's approximately directionally correct, right?
[00:05:46.360 --> 00:05:50.440] Of like, hey, I have like the 220, 200 framework even these days, right?
[00:05:50.440 --> 00:05:59.320] Which is like two hours to, if you're kind of trying to validate an idea to do some research and to go to Google and to go to look at keyword volume and other hrefs and other things.
[00:05:59.320 --> 00:06:03.320] The 20 hours is, hey, maybe I'm going to put up a landing page, have customer conversations.
[00:06:03.320 --> 00:06:12.440] And then if I make it past both of those points with an idea, maybe I do spend the 200 or 300 or whatever that number is to build that MVP and get it in the hands of folks.
[00:06:12.440 --> 00:06:16.040] But AI coding tools do, in fact, change that timeline.
[00:06:16.040 --> 00:06:17.640] I think it's significantly shortened.
[00:06:17.640 --> 00:06:23.160] Now, I don't know if a few hours feels a little, I don't know, it feels a little exaggerated.
[00:06:23.480 --> 00:06:28.280] I don't know how maintainable that code will be and beyond that, but let's kick it off.
[00:06:28.280 --> 00:06:30.440] Like, are you using AI coding tools?
[00:06:30.440 --> 00:06:33.800] Have you found them to live up to the promise that people are talking about?
[00:06:33.800 --> 00:06:37.320] Of, hey, I'm a non-technical so-and-so and I can build everything in three minutes.
[00:06:37.320 --> 00:06:39.560] You know, what's your experience and thoughts here?
[00:06:39.560 --> 00:06:45.000] Yeah, so I have become a pretty deep user of AI coding assistance tools.
[00:06:45.000 --> 00:06:46.200] I kind of came late to the game.
[00:06:46.200 --> 00:06:51.320] There's been GitHub Copilot, which was launched like, I don't know, two or three years ago, I think.
[00:06:51.320 --> 00:06:54.920] And I just never really caught on to that mode back when it initially came out.
[00:06:54.920 --> 00:06:56.520] I think because the models weren't as good.
[00:06:56.520 --> 00:07:01.960] And so the kind of auto-correct as you type was just a bunch of kind of bad suggestions.
[00:07:01.960 --> 00:07:09.400] And these days, it has gotten considerably better, especially if you're in certain languages that the LLMs really know well, like JavaScript, Python.
[00:07:09.640 --> 00:07:13.320] It knows Elixir decently well, and that's what I mainly use: TypeScript.
[00:07:13.320 --> 00:07:16.800] I regularly now use Windsurf, which is similar to Cursor.
[00:07:16.800 --> 00:07:20.000] These are kind of the big two AI-assisted code editors.
[00:07:20.000 --> 00:07:22.560] And then I think you mentioned also V0 and Lovable.
[00:07:22.560 --> 00:07:30.640] And I think those are more like specific products from companies that allow you to kind of type in, like, here's the app I want you to build for me.
[00:07:30.640 --> 00:07:34.560] And it just like spikes out an MVP based on what you tell it.
[00:07:34.560 --> 00:07:43.600] And yeah, I think it's really interesting how these tools do considerably shortcut a V1.
[00:07:43.840 --> 00:07:48.160] Now, the question is: how long are you expecting to use this V1?
[00:07:48.160 --> 00:07:51.280] Like, is this purely for validating something?
[00:07:51.280 --> 00:07:59.360] Like, think of it like a working mock-up wireframe thing that actually persists things to a database and you can show flows off.
[00:07:59.360 --> 00:08:02.880] It can get you to that place really quickly.
[00:08:02.880 --> 00:08:09.840] I am skeptical about the maintainability of some of these code bases that were generated from scratch fully by AI.
[00:08:09.840 --> 00:08:20.480] I haven't found the code that it generates to be good enough for, I'm trying to imagine someone who doesn't know code at all using this to try to maintain an application for the long haul.
[00:08:20.480 --> 00:08:22.000] And I don't think we're there quite yet.
[00:08:22.000 --> 00:08:22.880] We might get there.
[00:08:22.880 --> 00:08:27.120] I mean, this might be a horribly outdated take, even in six months, not sure.
[00:08:27.120 --> 00:08:36.880] But like, at the present moment, it makes a lot of mistakes that if you're not technical, you may not catch it, and that would kind of not serve you well in the long run.
[00:08:36.880 --> 00:08:44.320] But for sure, for the purpose of proving something out and being able to demonstrate something, I think it has radically changed the game.
[00:08:44.640 --> 00:08:46.000] I would agree.
[00:08:46.320 --> 00:08:52.240] And there is an it depends to all of this, and the it depends is: are you a developer?
[00:08:52.240 --> 00:08:56.000] And are you a senior developer, mid-level, or junior, or not at all?
[00:08:56.000 --> 00:09:01.560] And I do think that AI coding tools, I think of it as almost like a mech suit, right?
[00:09:01.560 --> 00:09:04.680] Like you think of like alien, or do they have an alien suit?
[00:09:04.760 --> 00:09:12.920] Anyways, you know, a mech suit like makes you super powerful if you know how to use it, but imagine getting in it for the first time and letting it run on autopilot question mark.
[00:09:12.920 --> 00:09:14.200] You know, it's like, right?
[00:09:14.200 --> 00:09:32.920] And the analogy breaks down because you don't have to maintain a mech suit five years from now and have infrastructure and spaghetti code or like weird bugs that nobody, you know, nobody can really find because there's been machine-generated code for 40, 50 years, 60, I mean, for a very long time.
[00:09:32.920 --> 00:09:41.560] And back in the day, I actually was a contractor at LADWP, Los Angeles Department of Water and Power, and I was a developer working on .NET stuff there.
[00:09:41.560 --> 00:09:50.280] And they had a system, it was, I think it was in COBOL, and they had generated code in the 70s to do a bunch of stuff.
[00:09:50.280 --> 00:09:52.520] And it was machine-generated, and no one wanted to touch it.
[00:09:52.600 --> 00:09:56.600] I didn't know COBOL, but they had COBOL contractors who are like, everyone's scared to touch it.
[00:09:56.600 --> 00:09:58.680] It is a complete disaster.
[00:09:58.680 --> 00:10:00.040] And people are scared.
[00:10:00.040 --> 00:10:05.000] It was like a payroll system or maybe it ran the grid, you know, the electrical grid in LA for all we know.
[00:10:05.240 --> 00:10:09.000] And that's just the state of affairs sometimes with government systems.
[00:10:09.000 --> 00:10:12.760] But I remember being like, wow, they generated code and no one can touch it.
[00:10:12.760 --> 00:10:13.880] That sucks.
[00:10:13.880 --> 00:10:15.160] Like, what's the point then?
[00:10:15.160 --> 00:10:17.400] I mean, it works until dot dot dot.
[00:10:17.400 --> 00:10:27.480] Like, so I'm not saying AI code is that bad, but I think that's the big concern: you and I were just having a conversation a couple of weeks ago when you came over for DD.
[00:10:27.480 --> 00:10:36.840] And I believe you said, you know, you give it instructions and then you go through that code to really make sure that it is not screwing around and it makes mistakes, right?
[00:10:37.160 --> 00:10:37.720] Yeah.
[00:10:37.720 --> 00:10:45.600] I would say it's, I've still found this to be true, even in my few months of using it aggressively now, that it is best at writing test code.
[00:10:45.840 --> 00:10:53.040] And test code is just like, it's usually kind of an afterthought when you're trying to move quickly, you know, especially earlier stage.
[00:10:53.040 --> 00:11:00.240] You want to make sure stuff is kind of baseline sanity checked and you have some support for preventing regressions and stuff.
[00:11:00.240 --> 00:11:05.920] But like, you know, we don't love spending a ton of time writing tests if you're just trying to like deliver value quickly.
[00:11:05.920 --> 00:11:15.200] And I have found it is very good at analyzing your code, figuring out all the different permutations that should be tested, and then writing that test code for you.
[00:11:15.200 --> 00:11:21.680] And ideally, it writes it in such a way where you can pretty quickly easily read through it and see, like, all right, this is the setup.
[00:11:21.680 --> 00:11:23.280] These are the assertions.
[00:11:23.280 --> 00:11:25.040] Yep, that looks correct.
[00:11:25.040 --> 00:11:26.160] And then it'll run it.
[00:11:26.160 --> 00:11:32.240] And if it fails, then it's pretty good at at least helping you start to think about how to solve the bug, but it's not always perfect at that.
[00:11:32.240 --> 00:11:45.360] But even just having like those test cases where it's like actually rigorous and does every single kind of important permutation that has sped up my process a lot and made me feel like I have you know a stronger foundation of tests.
[00:11:45.360 --> 00:11:47.120] Yeah, faster and better.
[00:11:47.120 --> 00:11:47.520] Yeah.
[00:11:47.520 --> 00:11:50.720] And more thorough than you would care to do yourself.
[00:11:50.720 --> 00:11:51.200] Yeah.
[00:11:51.200 --> 00:11:56.960] And I think really getting back to Zach's question, because we've talked about AI and how it generates code and the dangers of that.
[00:11:56.960 --> 00:12:02.800] But really he's asking, so what if it makes me twice as fast, three, four, five times as fast?
[00:12:02.800 --> 00:12:07.840] Can I get it done in a day what used to take me a week, or two days it used to take me a week?
[00:12:07.840 --> 00:12:10.640] And in the future, will it be even faster?
[00:12:10.960 --> 00:12:12.960] How does that change all this methodology?
[00:12:12.960 --> 00:12:25.440] It's really interesting to think about because one of the reasons that I talk about, like that 220, 200 framework, the reason that framework exists is because I don't want you to spend 200 or 300 or 400 hours building something that no one wants.
[00:12:25.440 --> 00:12:27.440] So that's why there are those steps before it.
[00:12:27.440 --> 00:12:31.800] But he's asking a question, I think, what if it doesn't take me 200 hours?
[00:12:29.680 --> 00:12:35.560] What if it takes me 40 hours to do what it used to take 200 hours?
[00:12:35.560 --> 00:12:41.880] Should I just build more stuff more quickly without doing all the kind of the validation?
[00:12:41.880 --> 00:12:50.840] Here's the thing for me: as I said, the two is kind of doing research online, looking at competitors and SEO traffic and interest and demand and blah, blah, blah.
[00:12:50.840 --> 00:12:52.760] To me, I still want that.
[00:12:52.760 --> 00:12:55.720] If I'm starting it, like, I'm going to spend a few hours plugging away.
[00:12:55.720 --> 00:13:01.400] If I have a list of 10 ideas that I'm thinking about, could I feasibly go and build all 10 of those ideas in a weekend?
[00:13:01.400 --> 00:13:06.440] Probably not now, but let's say you could, and I could just, I don't want to do that without knowing there's some demand.
[00:13:06.440 --> 00:13:09.240] I don't want a product if there's like no search traffic, right?
[00:13:09.240 --> 00:13:11.800] Or if there's no, I can't find anybody who wants this.
[00:13:11.800 --> 00:13:13.000] It's not solving a problem.
[00:13:13.000 --> 00:13:14.840] So I still want to do the two part.
[00:13:14.840 --> 00:13:22.120] And then the 20 part is either it's a landing page or customer interviews conversations or both, frankly, which is usually what I recommend.
[00:13:22.120 --> 00:13:23.320] I still want to do that too.
[00:13:23.320 --> 00:13:36.120] Now, maybe could I shortcut, can I build mock-ups really fast with AI or can I build kind of a clunky click-through paper prototype thing with AI that's not maintainable and build an MVP in order to do the 20?
[00:13:36.120 --> 00:13:36.920] Maybe.
[00:13:36.920 --> 00:13:40.360] I think the danger, I mean, it could cut both ways, right?
[00:13:40.360 --> 00:13:51.880] If sometimes the danger is you're getting ahead of yourself and giving too much specificity to someone of like, here are 17 screens with text boxes and buttons to click through.
[00:13:51.880 --> 00:13:55.240] And it's like, is that what they need to know if it's worth it?
[00:13:55.240 --> 00:13:57.800] Or are you basically saying, hey, I'm going to solve this problem.
[00:13:57.800 --> 00:14:03.880] I'm going to build a system that manages your entire business and allows people to log in and log out and click and audit and this and that.
[00:14:03.880 --> 00:14:06.280] And is that what they need to hear?
[00:14:06.280 --> 00:14:07.880] Especially if they're non-technical.
[00:14:07.880 --> 00:14:13.000] And sometimes I think they maybe do need to see a few screens of like, ah, I get it.
[00:14:13.000 --> 00:14:18.800] But other times, I think presenting them with completed software could actually be a detriment.
[00:14:19.120 --> 00:14:39.200] Yeah, I think that that's a really good point that like the process of building a product for a particular market segment entails that you are actually speaking to that customer set and figuring out what needs to go into that product because it's hubris to assume that you have all those answers from the get-go.
[00:14:39.200 --> 00:14:50.720] So like building something based on a bunch of assumptions that you haven't actually confirmed by working with customers means you're probably going to miss the mark if you if you come with this fully built out product.
[00:14:50.720 --> 00:14:55.680] I mean, talk about this this kind of new appointment scheduling stuff that I'm working on right now.
[00:14:55.680 --> 00:15:08.960] And like a big part of this is getting kind of real-time feedback from the actual end user, the clinic who's going to be using this product on a day-to-day basis and incorporating that in as we build stuff.
[00:15:08.960 --> 00:15:13.200] Because I can just make a bunch of guesses and think like try to envision what they need.
[00:15:13.200 --> 00:15:20.800] And that's certainly a big part of it is like just trying to like get into their shoes and think about what they would need, but that'll only get you so far.
[00:15:20.800 --> 00:15:27.120] You need to actually talk to the real customer to figure out, you know, how do you really nail it for all of their workflows and use cases?
[00:15:27.120 --> 00:15:37.040] And like that kind of stuff, AI can certainly help you workshop some of that, but I think ultimately you're still selling to humans and you need to accommodate human needs.
[00:15:37.040 --> 00:15:41.360] So, you know, getting the actual human data is pretty key there.
[00:15:41.600 --> 00:15:44.240] Still selling to humans for now, Derek.
[00:15:44.240 --> 00:15:45.040] For now.
[00:15:45.920 --> 00:15:46.640] Until AI starts.
[00:15:46.880 --> 00:15:49.120] This also might be an outdated take.
[00:15:49.440 --> 00:15:53.760] Two years from now, people are like, guys, AI buys everything now.
[00:15:53.760 --> 00:15:56.880] So anyways, yeah, I appreciate the question, Zach.
[00:15:56.880 --> 00:16:00.440] And I hope Derek and my takes were helpful.
[00:15:59.840 --> 00:16:06.120] Next question is an audio question from Arthur Ravelski.
[00:16:11.560 --> 00:16:12.520] Hi, Rob.
[00:16:12.520 --> 00:16:16.760] Arthur here, an aspiring entrepreneur living in Denver, Colorado.
[00:16:16.760 --> 00:16:20.760] I have an idea for an app that I've recently started developing.
[00:16:20.760 --> 00:16:27.560] After validating the concept with potential customers, it seems like a strong business opportunity to move forward on.
[00:16:27.560 --> 00:16:34.760] As I work on building this, I'm realizing there are various ways to approach the app structure, pages, and user interactions.
[00:16:35.080 --> 00:16:41.320] My question for you is, how do you approach the user experience when bringing an idea to life?
[00:16:41.320 --> 00:16:52.120] A traditional UX designer might create user profiles, wireframes, prototypes, conduct user testing to uncover pain points, and follow other structured steps.
[00:16:52.120 --> 00:16:56.840] I have a college background in graphic design and now work as a software engineer.
[00:16:56.840 --> 00:17:00.280] So part of me wants to go through this formal process.
[00:17:00.280 --> 00:17:08.200] But another part of me feels I should focus on quickly building an MVP to prove the concept and refine the user experience later.
[00:17:08.200 --> 00:17:12.600] When in the process do you believe it's most essential to focus on user experience?
[00:17:12.600 --> 00:17:15.800] How do you typically approach UX for a new idea?
[00:17:15.800 --> 00:17:18.840] I think a great user experience can make or break an idea.
[00:17:18.840 --> 00:17:21.880] So I'm very curious about your perspective on this.
[00:17:21.880 --> 00:17:23.320] Appreciate what you do.
[00:17:23.320 --> 00:17:24.680] Thanks so much.
[00:17:25.320 --> 00:17:26.680] All right, Derek.
[00:17:26.680 --> 00:17:35.160] As one of the best UX folks that I know that exists on the internet today, what is your take on Arthur's question?
[00:17:35.480 --> 00:17:42.040] So, obviously, I come from a place of being biased towards wanting to solve problems from a UX-first perspective.
[00:17:42.040 --> 00:17:50.080] Like, it's something that I really value in the products that I buy and in the products that I build, you know, considering yourself a craftsperson and like, this is what I really care about.
[00:17:50.400 --> 00:17:55.520] However, my answer to this, trying to be objective, is like, I think it really depends.
[00:17:55.520 --> 00:18:04.080] Like, are you staking a big portion of your value proposition on better UX when you compare yourself to the rest of the landscape?
[00:18:04.080 --> 00:18:07.120] You know, what does your buyer actually care about the most?
[00:18:07.120 --> 00:18:10.960] I tried to think about some examples in my own stack, right?
[00:18:10.960 --> 00:18:18.000] So, like, I use Linear for project management, and they've been around for, I don't know, three, four, five years, something like that.
[00:18:18.000 --> 00:18:35.360] And I think their main differentiator, I guess, is that they're trying to be JIRA, but with better UX, like experiences that people actually like to use, but it's kind of solving the same underlying problem that JIRA is, which JIRA kind of has a bad reputation for being a little bit of a nightmare to use.
[00:18:35.360 --> 00:18:43.040] And so, for them, in order to deliver on this promise, they have to be executing top-notch user experiences.
[00:18:43.040 --> 00:18:50.080] Otherwise, people will just use JIRA because if it's no better, no different than JIRA on the UX front, then like, why bother?
[00:18:50.080 --> 00:18:56.880] SavvyCal, you know, we're promising to be a more delightful user experience for the scheduler and the person who's configuring the links.
[00:18:56.880 --> 00:19:02.880] So, you should be able to go in and fine-tune your availability faster, more efficiently than you can in the other tools.
[00:19:02.880 --> 00:19:10.080] So, I think for us, like the customers we attract are the people who are looking for those better user experiences.
[00:19:10.080 --> 00:19:13.520] So, I would say in these cases, it matters a lot.
[00:19:13.520 --> 00:19:23.920] For other products, I'm just trying to think of examples like software for construction firms, like yeah, yeah, where like you're you're logging in, you're doing stuff.
[00:19:24.040 --> 00:19:36.040] There's there's screens with forms, and you're viewing reports and charts and things, but like the level of UX attention that a lot of the products that a lot of us use, like linear, is just probably not as important.
[00:19:36.440 --> 00:19:39.160] What you're doing is you're driving a different kind of value.
[00:19:39.160 --> 00:19:43.240] I think of even more stark examples like HitTail back in the day, right?
[00:19:43.400 --> 00:19:46.680] Product that we worked on was SEO keyword tool.
[00:19:46.680 --> 00:19:52.280] So you could log in, you could get reports on like these are the keywords you should be targeting in your content.
[00:19:52.280 --> 00:20:00.200] And like the settings screen in that app was not very important, that it was like top, top notch UX.
[00:20:00.200 --> 00:20:04.280] Like it's, you know, form fields and buttons and you have the basic essentials.
[00:20:04.280 --> 00:20:09.960] It had to be obviously like navigatable, but like the core value prop there was the keywords it was giving you.
[00:20:09.960 --> 00:20:16.360] So let's say in an app like that, like the quote-unquote user experience of the product mattered a whole lot less.
[00:20:16.360 --> 00:20:20.120] The user experience was really like, is it delivering the right keywords?
[00:20:20.120 --> 00:20:20.600] Right.
[00:20:20.920 --> 00:20:31.080] And so I guess that is essentially a different kind of user experience than what we classically think of as like the way that you lay out menus and form fields and things like that.
[00:20:31.400 --> 00:20:33.160] I don't know that I have much to add to that.
[00:20:33.160 --> 00:20:41.480] That was pretty much my take was it depends and it depends specifically on is this your advantage or one of your advantages or not.
[00:20:41.480 --> 00:20:44.120] And there's certain spaces that just don't know the difference.
[00:20:44.120 --> 00:20:53.080] And again, I think of construction firms or maybe, you know, someone, an owner of a gymnasium, right, of a fitness gym, a fitness studio.
[00:20:53.080 --> 00:20:57.080] Are they going to know the difference between linear and JIRA?
[00:20:57.080 --> 00:20:57.640] Are they real?
[00:20:57.640 --> 00:21:00.360] I mean, they could tell the difference, but are they going to be like, ooh, this is good UX?
[00:21:00.360 --> 00:21:02.440] Like, like they don't really even know what that is, right?
[00:21:02.440 --> 00:21:06.360] So that's, I think, the big thing is like your end user, do they care?
[00:21:06.360 --> 00:21:13.320] And not only do they care, but do you want to invest the time to make this one of your advantages?
[00:21:13.320 --> 00:21:14.640] I personally would.
[00:21:14.200 --> 00:21:19.520] I would tend to enter spaces where, just like you, where the users do care.
[00:21:19.840 --> 00:21:23.120] But probably most software doesn't matter.
[00:21:23.120 --> 00:21:34.160] If I think of most B2B SaaS software, I shouldn't say doesn't matter at all, because you can have catastrophic US and then UX and then everyone hates it, but it doesn't matter nearly as much as I think.
[00:21:34.480 --> 00:21:40.960] I have often opined, like, why is the most successful software out there kind of the crappiest software?
[00:21:40.960 --> 00:21:42.720] Like, how does this actually happen?
[00:21:42.720 --> 00:21:49.520] But I think there are plenty of examples where, like, it's kind of that adage of like, it's always safe to buy IBM kind of thing.
[00:21:49.520 --> 00:21:55.360] Like, like, Salesforce is known for being quite painful to use, but it's Salesforce.
[00:21:55.360 --> 00:22:08.080] And they have staked this incredible position in the market of like, this is one of the two tools, maybe HubSpot and Salesforce, or like the only big two that, like, any serious business of a certain size will be on one of these platforms.
[00:22:08.080 --> 00:22:11.520] And the people buying them don't care about the user experience.
[00:22:11.520 --> 00:22:15.520] There's a whole bunch of other things that cause them to make that buying decision.
[00:22:15.520 --> 00:22:23.440] And so I think it would also, you know, this is a trap that a lot of times people fall into where you look at a successful incumbent and you say, their UX is terrible.
[00:22:23.440 --> 00:22:25.120] I can do better UX.
[00:22:25.440 --> 00:22:37.840] And you ignore the fact that the actual person buying it, maybe the actual person buying it doesn't even use the product, but they're charged with buying it because they're a VP at some level and they're the one who has to make that procurement decision.
[00:22:37.840 --> 00:22:44.800] And they buy it because their peers are buying it or because like companies of our level of importance buy this software.
[00:22:44.800 --> 00:22:46.560] And so there's just different motivations.
[00:22:46.560 --> 00:22:56.160] And but I think that often causes kind of a mismatch in the entrepreneur who thinks I can build a better version of this thing when in reality the market doesn't care.
[00:22:56.480 --> 00:23:07.000] And I think that's a good distinction you just made, which is the further your buyer is from the user of said software, I think the worse your UX can be because the buyer doesn't care.
[00:23:07.160 --> 00:23:14.120] The buyer is usually going to buy based on market and brand and reputation rather than easy to use.
[00:23:14.440 --> 00:23:16.200] So thanks for that question.
[00:23:16.200 --> 00:23:18.040] Hope it was helpful.
[00:23:19.320 --> 00:23:26.600] I wanted to jump in here for a second and invite you to Microconf Remote, which is happening live tomorrow, May 21st from 10 a.m.
[00:23:26.600 --> 00:23:27.400] to 1 p.m.
[00:23:27.400 --> 00:23:28.360] Eastern Time.
[00:23:28.360 --> 00:23:33.000] The event consists of three presentations talking about early stage SaaS sales.
[00:23:33.000 --> 00:23:39.000] In addition, we have a founder by founder, which is like an online version of the hallway track at our in-person events.
[00:23:39.000 --> 00:23:42.040] Talks will be recorded in case you're listening to this event after.
[00:23:42.040 --> 00:23:45.960] To get access, head to microconf.com/slash remote.
[00:23:47.240 --> 00:23:55.000] Next one comes from Lewis Mertens, and Lewis asks a question about on-prem versus cloud hosting.
[00:23:55.000 --> 00:24:00.440] He says, Hey, Rob, I really enjoyed the book and I've listened to it twice now on Audible.
[00:24:00.440 --> 00:24:02.680] I think SAS Playbook, if I'm guessing.
[00:24:02.680 --> 00:24:10.920] I also love Linus Tech Tips, and they recently built a server on-prem and said that these days it's cheaper to run on-prem.
[00:24:10.920 --> 00:24:14.440] And many people were moving back to on-prem rather than the cloud.
[00:24:14.600 --> 00:24:15.880] I love proclamations like that.
[00:24:15.880 --> 00:24:16.600] Many people.
[00:24:16.600 --> 00:24:19.160] It's like, all right, yeah, there's five of them.
[00:24:19.240 --> 00:24:23.240] I wonder if you could talk through the pros and cons of cloud versus on-prem.
[00:24:23.240 --> 00:24:27.000] I suppose it would avoid vendor lock-in.
[00:24:27.000 --> 00:24:28.200] What do you think about this, Derek?
[00:24:28.200 --> 00:24:33.640] I mean, this, he's basically saying like getting a physical server in a cage somewhere, right?
[00:24:33.640 --> 00:24:37.640] And like getting it in a, we used to do this 15, 20 years ago.
[00:24:37.640 --> 00:24:39.720] We also used to charge one time for our software.
[00:24:39.720 --> 00:24:40.520] Should we do that as well?
[00:24:40.520 --> 00:24:41.000] No, I'm just kidding.
[00:24:41.080 --> 00:24:43.720] You can tell my opinion on this, but what are your thoughts?
[00:24:43.720 --> 00:24:55.280] Because, you know, you as an operator could totally save monthly hosting cost if you spun up a physical database, go buy a Dell, buy a database server, and then go buy your.
[00:24:55.520 --> 00:25:03.200] I say this because I remember doing this 25 years ago with clients, with big e-commerce clients, and like going and racking the servers in a place.
[00:25:03.520 --> 00:25:08.800] I mean, I have seen a lot of talk off and on in our space about this, about exiting the cloud.
[00:25:08.800 --> 00:25:11.040] And I think a lot of it's driven by DHH.
[00:25:11.040 --> 00:25:16.320] Maybe there are others that have done this, but I think he's been the most vocal lately who's been talking about doing this.
[00:25:16.320 --> 00:25:24.800] And basically, 37 Signals looked at their cloud spend and they said, hmm, we're paying, I don't know, it's like $10 million a year for S3 or something.
[00:25:24.800 --> 00:25:29.200] And then there, you know, had EC2 instances that were probably similar orders of magnitude.
[00:25:29.520 --> 00:25:36.000] You know, I think they were probably looking at their staffing and saying, well, we have all these DevOps people on staff who are kind of bored.
[00:25:36.000 --> 00:25:37.200] And I think we could.
[00:25:37.520 --> 00:25:38.320] This is the key.
[00:25:39.440 --> 00:25:43.280] And so, you know, we have the talent on staff.
[00:25:43.280 --> 00:25:45.600] We're not necessarily shipping a bunch of new products.
[00:25:45.600 --> 00:25:47.360] So we have extra capacity.
[00:25:47.360 --> 00:25:53.440] And we could probably stand to save some money and pull this stuff in-house.
[00:25:53.440 --> 00:25:58.400] They're a very mature business and they understand their traffic patterns really well.
[00:25:58.400 --> 00:26:04.560] So they know, like, Basecamp, I'm sure, just kind of mostly chugs along at a very consistent rate.
[00:26:04.560 --> 00:26:08.000] And if they get a bunch of new customers, it still doesn't really move the needle so much.
[00:26:08.000 --> 00:26:12.880] So they just have a very strong understanding of like, this is how many servers we need.
[00:26:12.880 --> 00:26:16.400] And maybe in six months, we'll need to buy one more server.
[00:26:16.400 --> 00:26:19.200] But we can anticipate that, we can predict it.
[00:26:19.200 --> 00:26:29.800] And so, yeah, I think for them, they're at such a stage of maturity with so much in-house expertise that, sure, you know, have at it, do it.
[00:26:29.280 --> 00:26:37.720] But I think for, I guess I wouldn't say 100% of us, but for 99.9% of the rest of us, like this is not a good decision.
[00:26:37.720 --> 00:26:46.920] With platform as a service, you're effectively getting all of those site reliability engineers and DevOps people at your platform of choice.
[00:26:46.920 --> 00:26:51.400] You're getting all of them as a functional extension of your team for metered cost.
[00:26:51.400 --> 00:26:55.480] You know, usually it's like an extra $10 for the next size up server.
[00:26:55.480 --> 00:27:01.960] And so you're getting this incredible amount of expertise for very, very low marginal cost.
[00:27:01.960 --> 00:27:12.120] This is just close to a miracle for us people at a smaller stage, like being able to start out, crack open a fresh application, you have close to zero dollars a month in cost.
[00:27:12.120 --> 00:27:19.640] And then as you get more customers, you can just incrementally, you know, expand your resource usage at your platform as a service.
[00:27:19.640 --> 00:27:25.080] Like, this is just, I think, a no-brainer to stay in these systems.
[00:27:25.080 --> 00:27:25.960] And yeah.
[00:27:26.280 --> 00:27:27.640] You and I are on the same page with this.
[00:27:27.880 --> 00:27:39.160] It's the old thing where I say, don't use Steve Jobs and Apple as an example unless you are co-founding with a guy who invented the personal computer, Steve Wozniak.
[00:27:39.160 --> 00:27:41.800] And when you're 20 years old, you're worth a million.
[00:27:41.800 --> 00:27:43.000] 21, you're worth 10 million.
[00:27:43.080 --> 00:27:44.680] 22, you're worth 100 million.
[00:27:44.680 --> 00:27:45.880] It's something approximately that.
[00:27:45.880 --> 00:27:47.720] I think that was Steve Jobs' situation.
[00:27:47.720 --> 00:27:49.480] And you've started this incredible company.
[00:27:49.480 --> 00:27:49.880] Great.
[00:27:49.880 --> 00:27:52.600] Then you can take Steve Jobs' advice of not listening to your customers.
[00:27:52.600 --> 00:27:55.160] They don't know what they want until you give it to them.
[00:27:55.160 --> 00:28:07.640] Or if you started a SaaS that is, as you said, 20 years mature, has nine figures, hundreds of millions in revenue, we would guess, tens of millions a year in profit, which is confirmed, Jason Freed confirmed at MicroConf.
[00:28:07.640 --> 00:28:12.520] And you are so bored, I'll say that you've rewritten the app multiple times.
[00:28:12.520 --> 00:28:14.760] Don't they have a Basecamp V2 and a Basecamp V3?
[00:28:14.960 --> 00:28:19.440] And when I say bored, I want to, I have a ton of respect for DHH and Jason Freed.
[00:28:19.440 --> 00:28:22.480] And I think they've done a lot for SAS and a lot for entrepreneurs.
[00:28:22.480 --> 00:28:24.880] They are tiny seed investors, they are tiny seed mentors.
[00:28:24.880 --> 00:28:27.120] So, like, they're in our circles.
[00:28:27.120 --> 00:28:32.240] But I think that they've been successful in spite of a lot of the advice they give.
[00:28:32.240 --> 00:28:42.000] When they used to say, we don't do marketing, we don't track analytics, we don't track opens, we don't have any type of web analytics or conversion tracking on our website.
[00:28:42.000 --> 00:28:43.120] They used to say that.
[00:28:43.120 --> 00:28:44.400] I don't know that they do anymore.
[00:28:44.400 --> 00:28:53.760] And it's like, yeah, and if you built a SAS in 2005 and we're one of the first ever, and you're, you know, you'd also don't need that, but like, none of us are in that position.
[00:28:53.760 --> 00:28:58.000] So just really take the stuff that they do with a grain of salt, these outliers.
[00:28:58.000 --> 00:28:59.520] And that's what we're talking about here.
[00:28:59.520 --> 00:29:11.760] In fact, if a tiny seed company, if I was interviewing a tiny seed applicant and things were going well and they told me that they were racking their own servers, it would be a major red flag for me that I would dig into.
[00:29:11.760 --> 00:29:13.680] And I would say, why are you doing that?
[00:29:13.680 --> 00:29:15.360] And they would better have a damn good reason.
[00:29:15.360 --> 00:29:23.920] And I believe of all the tiny seed companies, 204 investments we've done, there was one founder who had physical servers.
[00:29:23.920 --> 00:29:34.320] And the reason was, is it was like three years ago, and he was doing AI and needed physical GPUs because it was way too, he built his own model.
[00:29:34.320 --> 00:29:37.440] It was before the chat GPT became a thing, right?
[00:29:37.440 --> 00:29:38.400] About two years ago.
[00:29:38.400 --> 00:29:45.200] And he convinced me and Ainar, because ANR has a PhD in computer science and I know my way around a keyboard.
[00:29:45.200 --> 00:29:46.800] And we dug into that with him.
[00:29:46.800 --> 00:29:48.400] I'm like, wait, why are what?
[00:29:48.400 --> 00:29:49.200] And he was like, yeah.
[00:29:49.200 --> 00:29:50.520] And he kind of showed us the cost.
[00:29:50.520 --> 00:29:53.520] And we're like, ah, you actually, that is the right choice.
[00:29:53.520 --> 00:29:54.400] But that's it.
[00:29:54.400 --> 00:30:00.280] He's the one out of 204 that we're like, okay, yeah, physical, all right, fine.
[00:30:00.280 --> 00:30:06.280] Cloud is more expensive, but it's not as expensive as hiring your own SREs and DevOps folks.
[00:29:59.840 --> 00:30:06.920] Yeah, yeah.
[00:30:07.080 --> 00:30:26.200] And I think there's, I don't know, even like over the years, clouds kind of started out as like a virtual private server or whatever, where it's just like, it's like an on-prem server that they will make sure to keep the power on to it, but everything else is managed by you, you know, so you're still doing a heavy amount of DevOps.
[00:30:26.200 --> 00:30:41.800] And like that's some people choose to go that route, but even that, like, it would be so hard for me to justify just like getting a digital ocean droplet and just like trying to, you know, rotate my own server logs and doing all this stuff where like you just don't have to deal with that anymore.
[00:30:41.800 --> 00:30:57.320] And you can get so much more reliability by going with a more modern platform as a service where like you have a Docker file that describes what your server should be and your host would ideally allow you to just say like deploy servers that follow this spec and they manage all other aspects of it.
[00:30:57.320 --> 00:31:07.000] Like this is the way to go unless you're planning on investing in having your own people on constant on-call rotation and doing a bunch of DevOps work.
[00:31:07.000 --> 00:31:08.280] Some people are passionate about that.
[00:31:08.280 --> 00:31:09.160] More power to you.
[00:31:09.160 --> 00:31:17.400] But like if you're if you're just starting out especially, like you do not want to have to be responsible for that portion of your reliability.
[00:31:17.400 --> 00:31:20.360] Yeah, your most valuable asset as a founder is your time.
[00:31:20.360 --> 00:31:28.440] And any time you spend not building value for customers, not selling, not growing the business, even if you enjoy it, it is detrimental to the business, right?
[00:31:28.440 --> 00:31:32.680] And your number two asset is money, but only because money buys you time.
[00:31:32.680 --> 00:31:34.600] C number one, you know what I mean?
[00:31:34.600 --> 00:31:37.560] And so let's say you are truly bootstrapping.
[00:31:37.560 --> 00:31:41.400] If you're around with DevOps, you're that's a catastrophic mistake.
[00:31:41.400 --> 00:31:53.520] And let's say you raise a million dollars and you hire a DevOps person to run your servers out of that million and you save the same amount of money or something.
[00:31:53.520 --> 00:32:01.760] Like it's just, you have another person on your team that really you probably don't need, you know, I just can't justify it in any, in almost, as you said, 99.9.
[00:32:01.760 --> 00:32:03.920] So maybe one out of a thousand or one out of 500.
[00:32:03.920 --> 00:32:08.880] Like there's some number where this is probably appropriate, but otherwise, don't make this mistake.
[00:32:08.880 --> 00:32:11.760] And it is a little bit of, yeah, it's cargo culting in a way.
[00:32:11.760 --> 00:32:14.720] It's kind of like it's listening to advice from the wrong folks.
[00:32:14.720 --> 00:32:19.040] It's just also like, don't follow Silicon Valley founders and see how they grow their company.
[00:32:19.040 --> 00:32:23.200] And then as a bootstrapper, think that's how you're going to do it because usually their advice doesn't apply.
[00:32:23.200 --> 00:32:25.040] So thanks for that question, Lewis.
[00:32:25.120 --> 00:32:26.320] Hope it was helpful.
[00:32:26.320 --> 00:32:29.760] Our next question gives me some PTSD, Derek.
[00:32:29.760 --> 00:32:31.600] So I'm going to let you weigh in first.
[00:32:31.600 --> 00:32:33.600] This is from Kyle.
[00:32:38.400 --> 00:32:39.840] Hey, Rob, my name is Kyle.
[00:32:39.840 --> 00:32:41.440] I've listened to the show for a long time.
[00:32:41.440 --> 00:32:46.000] I've actually had you answer one or two of my questions on the show, I think, in the past.
[00:32:46.000 --> 00:33:02.640] Just to kind of get straight to it, basically, we are a client and project tracking tool for tattoo artists that also allows them to schedule appointments and send kind of appointment reminders and whatnot.
[00:33:02.640 --> 00:33:06.160] So my question really is about that last piece of the puzzle.
[00:33:06.320 --> 00:33:09.600] Kind of think of like a Vegaro or QE or Schedule Easta.
[00:33:09.840 --> 00:33:11.200] There are lots of them out there.
[00:33:11.200 --> 00:33:24.720] One of the issues that we've heard from artists that we've talked to so far that they have on those other platforms is emails getting sent to spam or not delivered or similar issues, right?
[00:33:25.040 --> 00:33:31.800] And what I'm trying to figure out is just kind of steps or steps I could take or tools I could use to help limit that risk.
[00:33:32.040 --> 00:33:40.280] The plan is to use SendGrid for all those automated and customized messages that come out of the platform to our artists' clients.
[00:33:40.520 --> 00:33:47.240] But yeah, any insight you might have on how we can help mitigate that risk just from day one would be greatly appreciated.
[00:33:47.240 --> 00:33:48.440] Thanks in advance.
[00:33:48.440 --> 00:33:52.360] Hopefully you get time to hit this question and keep doing the good work.
[00:33:52.360 --> 00:33:59.320] You've been a great help to me so far, as well as countless other founders and hopeful founders.
[00:33:59.320 --> 00:34:00.200] Thanks, Rob.
[00:34:00.200 --> 00:34:01.240] Take care.
[00:34:01.240 --> 00:34:09.640] So, Derek, having never managed email sending infrastructure nor dealt with blacklists and deliverability, would you care to weigh in?
[00:34:09.640 --> 00:34:22.760] Should we give folks background who don't know that we started Drip, which it was sending, I don't know, by the time we left, so we sold it in 2016, left in 2018, I believe, and it was sending 150 million emails a month, maybe by the time we left.
[00:34:22.760 --> 00:34:27.480] And we started what with Mandrel and then we used Mailgun and we used SendGrid.
[00:34:27.480 --> 00:34:30.040] So we use multiple sending providers.
[00:34:30.040 --> 00:34:32.520] But to our point from the prior question, you know what we never did?
[00:34:32.520 --> 00:34:34.760] We never spun up our own email sending servers.
[00:34:34.840 --> 00:34:35.640] You know what I mean?
[00:34:35.640 --> 00:34:36.600] That's kind of equivalent.
[00:34:36.600 --> 00:34:37.560] It would have been way cheaper.
[00:34:37.560 --> 00:34:40.680] I mean, our SendGrid bill by the end, it was a lot of money.
[00:34:40.680 --> 00:34:47.160] And I don't remember exactly, but certainly tens of thousands of dollars a year, might even have been six figures.
[00:34:47.160 --> 00:34:50.200] And so, could you justify hiring someone in SpaceX servers?
[00:34:50.200 --> 00:34:51.880] Maybe I would do it.
[00:34:51.880 --> 00:34:52.280] Yeah.
[00:34:52.280 --> 00:34:54.520] All that said, you know, this is about email deliverability.
[00:34:54.520 --> 00:34:56.040] What do you, what are your thoughts here?
[00:34:56.040 --> 00:34:56.280] Yeah.
[00:34:56.280 --> 00:35:02.520] So, I mean, taking the point that, like, even running Drip, we never endeavored to do our own email sending.
[00:35:02.520 --> 00:35:08.600] I mean, I think point number one is definitely use a mature provider in the space like SendGrid.
[00:35:08.600 --> 00:35:12.120] Postmark is another good one that's been around a long time.
[00:35:12.120 --> 00:35:14.600] I use them for SavvyCal sending.
[00:35:14.600 --> 00:35:16.000] I think Amazon has a service.
[00:35:16.320 --> 00:35:28.480] So, yeah, there are a handful of these out there that, you know, their sole purpose is to manage pools of IP addresses and sending reputation with all the major email service provider or ISPs.
[00:35:28.480 --> 00:35:36.960] Postmark just recently had an incident where a bunch of their emails coming out of their system were getting flagged by Google, I think.
[00:35:36.960 --> 00:35:45.360] And at a certain point, a status page post came out and they're like, we are actively talking to Google to mitigate the issue.
[00:35:45.360 --> 00:35:48.080] And within a few hours, the issue was mitigated.
[00:35:48.080 --> 00:35:57.360] And can you imagine, like, if you were responsible for getting your stuff into people's inboxes, not using a middleman like that, like, are you going to call up Google?
[00:35:57.360 --> 00:35:58.560] Like, no.
[00:35:58.560 --> 00:36:01.600] So I don't think that's what our asker here is asking.
[00:36:01.600 --> 00:36:10.000] Like, he obviously knows, you know, use an email sending provider, but I just wanted to underscore that point that you definitely want to use a SendGrid or something like that.
[00:36:10.000 --> 00:36:16.400] Beyond that, DMARC has become a very important part of email authentication these days.
[00:36:16.400 --> 00:36:20.960] I think all the major email providers look for a strong DMARC policy.
[00:36:20.960 --> 00:36:24.560] So you can Google that or ChatGPT that to get more details about it.
[00:36:24.560 --> 00:36:30.400] Look to your provider of choice for instructions on how to make sure you have that stuff dialed in for their system.
[00:36:30.400 --> 00:36:39.440] And of course, your DKIM and all the DNS-level authentication stuff to make sure that your own domain is in a good place.
[00:36:39.440 --> 00:36:54.880] And then I think the other couple other big pieces here, when you're sending email, so it sounds like this is similar structure to what SavvyCal does, where like we send new appointment emails and reminders and things to people who schedule through our system.
[00:36:54.880 --> 00:36:59.280] So we have a lot of emails going out to people scheduling into the system.
[00:36:59.280 --> 00:37:08.520] And so you need to make sure that any place where an email address can get in, so that's through the booking pages, that you have good spam protection there.
[00:37:08.520 --> 00:37:17.160] Because if you have people, malicious actors, hitting those and putting junk email addresses through your system, that's going to reflect back on your domain's reputation.
[00:37:17.160 --> 00:37:18.840] And that's the biggest thing.
[00:37:19.000 --> 00:37:23.960] With email deliverability, point number one is always like, well, make sure you have high quality sending.
[00:37:23.960 --> 00:37:31.720] And it's like, well, easier said than done in a lot of cases, but the biggest thing you can do is make sure that you're protecting all the places where emails can get in.
[00:37:31.720 --> 00:37:34.440] I also these days like to use an email validation service.
[00:37:34.440 --> 00:37:41.800] I use emailable, and you can run email addresses through it, and it'll confirm to the best of its ability whether it's a valid email address.
[00:37:41.800 --> 00:37:50.200] And that keeps your bounce rate low and just makes sure that like the less invalid email you attempt to send on your domain, the better for your reputation.
[00:37:50.200 --> 00:37:53.480] And then also MX Toolbox, that's kind of an oldie but goody tool.
[00:37:53.480 --> 00:37:55.880] We used it back in the day with Drip and it's still around.
[00:37:55.880 --> 00:38:00.920] And you can use that to just kind of keep tabs on your email sending reputation.
[00:38:00.920 --> 00:38:04.120] And yeah, just make sure that you're not ending up on blacklists.
[00:38:04.120 --> 00:38:05.000] There it is.
[00:38:05.000 --> 00:38:05.880] That's a clinic.
[00:38:05.880 --> 00:38:07.560] We should make that into a course.
[00:38:09.800 --> 00:38:13.480] I don't have much to add, although I thought of a couple things.
[00:38:13.480 --> 00:38:18.360] We used Mandaril and their deliverability was phenomenal back in the day.
[00:38:18.360 --> 00:38:25.560] And they allowed marketing email at the time and then they kicked everyone off sending marketing email and it's only transactional now.
[00:38:25.560 --> 00:38:31.400] These days, if you were to ask me who I would use, it'd probably be Mandrel if it's purely transactional.
[00:38:31.400 --> 00:38:34.920] I would verify that and check with other people and this and that.
[00:38:34.920 --> 00:38:41.560] But I remember, I mean, MailChimp's infrastructure is so good and they've had it for so long that Mandarill is an extension of MailChimp.
[00:38:41.560 --> 00:38:45.200] So definitely add that to the list of, you know, the postmarks and the send grids.
[00:38:44.760 --> 00:38:48.160] The other thing is there is a tiny C company that kind of helps with all this.
[00:38:48.240 --> 00:38:54.640] They're called SkySnag and they help with DECIM and they monitor all this stuff and monitor phishing and this and that.
[00:38:54.640 --> 00:38:56.960] So if you're listening to this and you're like, man, I don't really know what I'm doing.
[00:38:56.960 --> 00:39:00.240] Like skysnag.com is probably a place to check out.
[00:39:00.240 --> 00:39:04.400] And the last thought is, because I agree with everything you said and I think that's that's great advice.
[00:39:04.400 --> 00:39:11.040] The other thing is this is why a lot of folks have you noticed how many are asking for phone numbers and doing SMS now for reminders?
[00:39:11.040 --> 00:39:18.880] Like my haircut place only does SMS and it's because they know inboxes are full and there's the multiple inboxes, right?
[00:39:18.880 --> 00:39:24.400] I don't use these like in Gmail, but where it's the promotions tab, reminders get in there and SMS is more direct.
[00:39:24.400 --> 00:39:28.320] Now your RSMS inboxes, so to speak, are getting crowded.
[00:39:28.320 --> 00:39:30.400] And so then we're going to have to move to WhatsApp or something.
[00:39:30.400 --> 00:39:39.920] But that's the other thing to think about is: you know, is in certain areas, like especially appointment reminders and stuff, most of the ones I receive now are via text.
[00:39:39.920 --> 00:39:44.480] And so that doesn't remove the need to comply with stuff.
[00:39:44.480 --> 00:39:46.160] There's a bunch of regulations around this.
[00:39:46.160 --> 00:39:55.200] You know, we have, I mean, gosh, there's got to be, there's at least 10 probably tiny C companies where SMS is like their main focus and their main value prop.
[00:39:55.200 --> 00:39:59.360] And then there's probably another 20, if not more, that actually send SMS.
[00:39:59.360 --> 00:40:02.400] And so there are some hurdles there.
[00:40:02.400 --> 00:40:13.600] But if you use the equivalent, if you use a Twilio and you don't need a dedicated number for each of your customers and you kind of just have a few, I think it's significantly less complicated than one might think.
[00:40:13.600 --> 00:40:15.520] So thanks for that question, Kyle.
[00:40:15.520 --> 00:40:17.040] I hope it was helpful.
[00:40:17.040 --> 00:40:21.360] Our last question for today is from Mike.
[00:40:26.160 --> 00:40:26.960] Hi, Rob.
[00:40:26.960 --> 00:40:28.320] My name is Mike.
[00:40:28.320 --> 00:40:39.160] I was listening to your EMA for the SaaS Launchpad course, and you made a statement that for enterprise or other companies selling to the enterprise, you'd want a salesperson.
[00:40:39.160 --> 00:40:44.280] And for somebody targeting like Web Editor, SMBs, you'd want a marketer on your team.
[00:40:44.280 --> 00:40:56.760] Can you expand on your thinking between the differences and how does that affect what your choices are in terms of what kind of business you might want to start or how you give advice to people deciding what kind of business they want to start?
[00:40:56.760 --> 00:41:08.120] And then how critical is it to have either skill set on the founding team or can, for example, the sales side for the enterprise, could that be learned from something like Founding Salesbook by Pete Kazanchi?
[00:41:08.120 --> 00:41:09.640] Thank you for everything you do.
[00:41:09.640 --> 00:41:13.880] I think the first question maybe is like sales versus marketing.
[00:41:13.880 --> 00:41:14.600] What's the difference?
[00:41:14.600 --> 00:41:16.440] But just very fundamentally, right?
[00:41:16.440 --> 00:41:20.600] And the way I think about it is marketing is generating demand, right?
[00:41:20.600 --> 00:41:38.120] So this is going out and getting in Google search results or running ads or doing any of the 20 B2B SaaS marketing approaches I have in the SaaS playbook, doing integrations and having someone else talk about you to their audience, any of these things that gets you and your app and your value proposition in front of them.
[00:41:38.120 --> 00:41:39.880] And that is inbound, right?
[00:41:39.880 --> 00:41:43.960] And then people come to your website and they either book a demo or they sign up for a free teller.
[00:41:43.960 --> 00:41:44.680] That's marketing, right?
[00:41:44.680 --> 00:41:45.800] It's spreading the word.
[00:41:45.800 --> 00:41:47.640] Sales is a couple things.
[00:41:47.640 --> 00:41:50.120] Like sales is often outbound, right?
[00:41:50.120 --> 00:41:51.640] It's approaching on LinkedIn.
[00:41:51.640 --> 00:41:54.120] It's all the cold emails we get on a typical day.
[00:41:54.120 --> 00:41:56.200] It's the Twitter DMs and all that stuff.
[00:41:56.200 --> 00:42:01.000] And then it's doing the demos face to face, in essence, right over Zoom.
[00:42:01.160 --> 00:42:03.400] It used to be in person, obviously, years ago.
[00:42:03.400 --> 00:42:05.320] And it is trying to close a sale.
[00:42:05.320 --> 00:42:07.800] So, just marketing versus sales, those are two things.
[00:42:07.800 --> 00:42:08.920] They are complementary.
[00:42:08.920 --> 00:42:12.440] Sometimes, if you have a low-touch, no-touch funnel, you don't have sales at all.
[00:42:12.440 --> 00:42:14.520] You don't do any outbound and you don't do demos.
[00:42:14.520 --> 00:42:17.280] And so, it's purely a marketing-driven SaaS.
[00:42:17.280 --> 00:42:20.400] And that is kind of the bootstrapper indie hacker dream.
[00:42:14.760 --> 00:42:21.120] It's pretty rare.
[00:42:21.360 --> 00:42:30.000] And in fact, those tend to need lower price points so then they have higher churn and they don't grow into multi-million dollar businesses.
[00:42:30.320 --> 00:42:44.480] It can happen, but it's often bringing sales in, doing demos, and closing the $2,000 a month deal versus the $200 a month deal or the $20 a month deal that really kicks that engine into growing into that seven or eight figure mark.
[00:42:44.480 --> 00:42:47.040] So, I want to kind of want to level set that with some definitions.
[00:42:47.040 --> 00:42:50.880] But then, beyond that, enterprise versus SMBs.
[00:42:50.880 --> 00:42:52.160] What do you think?
[00:42:52.480 --> 00:42:55.920] Yeah, there's also kind of different levels inside of here, right?
[00:42:55.920 --> 00:42:57.920] Like the definition of a small business.
[00:42:57.920 --> 00:43:01.440] Some would say a small business is up to 100 million a year in revenue or something.
[00:43:01.440 --> 00:43:03.760] And it's like, that's usually not what we mean by that.
[00:43:03.760 --> 00:43:17.520] When we say small business, we're usually talking like much, much smaller, like maybe a team of 10 people or something like that, and versus like, and we often qualify enterprise as like capable of buying at a higher price point, basically, right?
[00:43:17.840 --> 00:43:21.040] And the grass is always greener on the other side, I will say.
[00:43:21.040 --> 00:43:23.680] Like, this is kind of a choose your pain.
[00:43:23.680 --> 00:43:30.640] Like, if you go with the higher price point product and you're able to do sales for it, then you typically have longer cycles.
[00:43:30.640 --> 00:43:34.400] Like, there's more involved, more investment involved in order to make a sale.
[00:43:34.400 --> 00:43:40.400] Cost to acquire a customer is often higher, but you can offset that with a higher price point.
[00:43:40.400 --> 00:43:53.760] But I've talked to plenty of founders who get frustrated with this motion and like needing to have all these conversations and make it through procurement and all of the kind of sucky things that come along with that piece.
[00:43:53.760 --> 00:44:06.040] But on the flip side, when you're going marketing-driven, you generally have a lower price point, people are more price-sensitive, churns higher, and it can be really difficult to move the needle on these lower-price point businesses.
[00:44:06.200 --> 00:44:08.120] Don't ask me how I know that.
[00:44:08.280 --> 00:44:09.800] Asking for a friend.
[00:44:09.800 --> 00:44:25.480] Yeah, because each individual customer is only paying you a little bit of money, and you have to be really good at getting a lot of distribution and showing people who care enough about the differences between you and maybe a bunch of other options on the market, like, why should they pick you?
[00:44:25.480 --> 00:44:28.840] And some of this just comes from being around for a while.
[00:44:28.840 --> 00:44:41.240] Like, it just takes a while to build up reputation where you're showing up in conversations and making it onto the lists where people are comparing different products and making it into Chat GPT so that it starts recommending you.
[00:44:41.240 --> 00:44:45.320] Like, I don't know who the hell knows how to actually do that other than just be around, you know?
[00:44:45.320 --> 00:44:54.760] So, there's so many things involved with the marketing-driven approach where, and obviously, if you're a master marketer, you will have better success at like building up a business with this approach.
[00:44:54.760 --> 00:44:59.160] But I guess all that to say, both of these approaches take a certain amount of expertise.
[00:44:59.160 --> 00:45:12.680] And I think typically the more sales-driven approach is something where you can kind of brute force it a little easier, I guess, than the marketing-driven approach, which is like you just have to get really good at generating a ton of traffic in the right places.
[00:45:12.680 --> 00:45:15.240] And that is a bit of a dark art for many of us.
[00:45:15.560 --> 00:45:17.400] Yeah, and I like the way you put that.
[00:45:17.400 --> 00:45:19.800] And it's not just two, it's not a dichotomy, right?
[00:45:19.800 --> 00:45:25.720] There's like small and medium-sized businesses, and which I think of like, oh, is there one decision-maker usually, you know?
[00:45:25.720 --> 00:45:28.840] And oftentimes, is the decision maker also the user of the software?
[00:45:28.840 --> 00:45:37.080] So, maybe that's even like solopreneurs, you know, or prosumers, and they're extremely price-sensitive because they think of the money they're spending as their money.
[00:45:37.240 --> 00:45:39.160] So, they think of it almost like consumers.
[00:45:39.160 --> 00:45:45.000] And then SMBs, maybe a notch up, and then there's mid-market, and then there's enterprise, and there's this whole spectrum of it.
[00:45:45.120 --> 00:46:00.320] But generally, the tough part is if you get these big, big contracts, let's say you're selling $250,000 a year, which we have some tiny seed companies, that's their contract size, but they only close a deal every quarter or every six months, and it's just brutal and agonizing.
[00:46:00.320 --> 00:46:05.120] And there's no momentum, and it's super, it's not even, it's spiky in a way that's just not that fun.
[00:46:05.120 --> 00:46:10.000] And as you said, you know, months in procurement, but they close these really big deals and they have this negative churn.
[00:46:10.000 --> 00:46:11.200] You know, everybody's expanding.
[00:46:11.200 --> 00:46:21.120] That's great, except for it's kind of agonizing as, you know, as the founder, on the flip side, you're charging 15 bucks a month and your churn's really high and it's hard to hard to outrun that churn.
[00:46:21.120 --> 00:46:22.480] You need a really massive funnel.
[00:46:22.480 --> 00:46:29.760] I'll say it's impossible to outrun, you know, the churn of a $15 a month business if you want to become, let's say, a $10 million or $20 million business.
[00:46:29.760 --> 00:46:34.800] And that's why, like, when we started Drip, it was $50 a month, $100, $150,000 I think those are the price points.
[00:46:34.800 --> 00:46:42.880] But we soon realized like people were reaching out with really big email lists and they were like, oh, I would pay you $500 a month based on my list size or $1,000 a month.
[00:46:42.880 --> 00:46:46.320] Or I think when we left, there were people paying us two or three grand a month.
[00:46:46.320 --> 00:46:51.120] You know, and these were getting, these are not enterprise in the enterprise sense, but for us, they're enterprise.
[00:46:51.280 --> 00:46:56.400] It's anything over 25K, I kind of think of it as like a bootstrapper enterprise plan.
[00:46:56.400 --> 00:46:58.960] And that was pretty interesting, right?
[00:46:59.040 --> 00:47:00.720] And this is, I call this a dual funnel.
[00:47:00.720 --> 00:47:05.920] It's where you have folks paying you no churn and paying you a lot of money on the top end.
[00:47:05.920 --> 00:47:09.440] And you do have some folks doing sales demos and procurement, maybe.
[00:47:09.440 --> 00:47:15.360] But then you have this nice low-touch funnel that usually has higher churn, more price-sensitive customers on the bottom end.
[00:47:15.360 --> 00:47:17.920] And this only works in really, I think, pretty big markets.
[00:47:17.920 --> 00:47:25.280] Like it doesn't work in these tight niches, but that's a nice way to even it out to get a little bit of the best of both worlds if you can swing it.
[00:47:25.280 --> 00:47:29.360] You know, and we've seen like Ruben with Seinwell has that type of funnel, right?
[00:47:29.360 --> 00:47:33.880] And like Riverside or Squadcast has that type of funnel.
[00:47:33.880 --> 00:47:40.600] And it's not always possible, but it is a way to even out the agony of, oh, we close a deal every three months.
[00:47:40.600 --> 00:47:41.720] This is fun.
[00:47:42.120 --> 00:47:43.640] This is so great.
[00:47:43.960 --> 00:47:51.480] Yeah, and I can imagine just if it's that extreme where it's like, you know, hundreds of thousands of dollars from individual customers.
[00:47:51.480 --> 00:47:54.520] And I'm sure there's a bit of cost involved with maintaining those.
[00:47:54.520 --> 00:47:59.080] So it's like you would want to make sure you have the people on staff to maintain that.
[00:47:59.080 --> 00:48:04.280] But if one of those churns and it's like, oh my gosh, we have to replace them or else we're yeah.
[00:48:04.280 --> 00:48:17.320] So yeah, like having a bit of diversification is probably ideal where you don't have too much customer concentration to the point where you're like potentially have to lay someone off from your team if the customer cancels or whatever, but it's business.
[00:48:17.320 --> 00:48:19.880] So you got to do it.
[00:48:20.440 --> 00:48:21.640] So thanks for that question, Mike.
[00:48:21.640 --> 00:48:24.760] And Mike actually sent in another question, but we don't have time to get to it today.
[00:48:24.760 --> 00:48:27.560] So I will answer that in a future episode.
[00:48:27.560 --> 00:48:33.320] Derek Reimer, folks want to use the best scheduling link on the internet, head to savvycal.com.
[00:48:33.320 --> 00:48:43.160] And as a reminder, if you are an agency or a freelancer consultant and you are building solutions for folks who are booking appointments, right?
[00:48:43.160 --> 00:48:46.920] This is like service businesses and other types of folks.
[00:48:47.160 --> 00:48:49.240] You should reach out to Derek to find out what he's building.
[00:48:49.720 --> 00:48:50.760] I'd love to chat.
[00:48:50.760 --> 00:48:51.400] Yeah.
[00:48:51.400 --> 00:48:54.840] D-E-R-R-I-C-K at savvycal.com.
[00:48:54.840 --> 00:48:56.040] Thanks again for joining me.
[00:48:56.040 --> 00:48:57.400] Thanks for having me.
[00:48:57.400 --> 00:48:59.560] Thanks again to Derek for coming on the show.
[00:48:59.560 --> 00:49:09.640] And a reminder, SASLANCHPAD.co and use the code launch to get $150 off the course, as well as Microconf Remote is happening tomorrow.
[00:49:09.640 --> 00:49:12.280] That's microconf.com/slash remote.
[00:49:12.280 --> 00:49:14.440] Thanks for listening this week and every week.
[00:49:14.440 --> 00:49:18.320] This is Rob Walling signing off from episode 775.
[00:49:53.600 --> 00:50:00.080] Derek, I have four fifth edition Dungeons and Dragons trivia questions for you.
[00:50:00.080 --> 00:50:02.880] Order from easiest to hardest.
[00:50:03.520 --> 00:50:12.800] The first is in combat in fifth edition Dungeons and Dragons, what determines the order in which characters act?
[00:50:13.440 --> 00:50:14.880] You roll for initiative.
[00:50:14.960 --> 00:50:16.000] There it is.
[00:50:16.000 --> 00:50:16.560] All right.
[00:50:16.560 --> 00:50:18.320] That's one out of four.
[00:50:18.320 --> 00:50:19.040] All right.
[00:50:19.040 --> 00:50:26.880] Second question: if you attack a prone enemy with a melee attack, what do you gain?
[00:50:27.840 --> 00:50:28.640] Advantage.
[00:50:28.640 --> 00:50:30.480] You do indeed gain advantage?
[00:50:30.480 --> 00:50:31.440] Two out of four.
[00:50:31.440 --> 00:50:31.760] All right.
[00:50:32.160 --> 00:50:32.880] Capital A advantage.
[00:50:33.040 --> 00:50:34.080] Capital A.
[00:50:35.040 --> 00:50:36.000] All right.
[00:50:36.000 --> 00:50:37.680] This one, it's getting harder.
[00:50:38.400 --> 00:50:45.920] When attacking a creature you cannot see because they're invisible, hidden, etc., what disadvantage do you suffer?
[00:50:46.240 --> 00:50:48.000] Do they have surprise on you?
[00:50:48.000 --> 00:50:48.960] Incorrect.
[00:50:48.960 --> 00:50:53.920] What disadvantage do you suffer when you attack them if they're invisible?
[00:50:53.920 --> 00:50:54.880] When I attack.
[00:50:54.880 --> 00:50:55.600] Oh, okay.
[00:50:55.600 --> 00:50:56.000] Okay.
[00:50:56.320 --> 00:51:02.440] Well, wait, you can make an attack on someone who's invisible, like not like you, you know they're there, but you can't see them.
[00:51:02.440 --> 00:51:06.360] Or hidden, like if you know, thieves or rogues, I guess, can hide in shadows.
[00:51:06.520 --> 00:51:07.000] I see.
[00:51:07.000 --> 00:51:07.800] I see.
[00:51:08.760 --> 00:51:09.720] I don't know.
[00:51:09.720 --> 00:51:12.360] You have disadvantage on your attack roll.
[00:51:12.360 --> 00:51:12.840] No.
[00:51:12.840 --> 00:51:13.160] Oh.
[00:51:13.480 --> 00:51:14.200] Kind of makes sense, right?
[00:51:14.360 --> 00:51:15.000] Should have discussed that.
[00:51:15.560 --> 00:51:16.280] Totally.
[00:51:16.280 --> 00:51:17.000] All right.
[00:51:17.000 --> 00:51:18.120] What disadvantage do you have?
[00:51:18.440 --> 00:51:19.480] Disadvantage, yeah.
[00:51:19.480 --> 00:51:21.000] It has it as lowercase D.
[00:51:21.000 --> 00:51:22.200] It should be uppercase.
[00:51:22.200 --> 00:51:25.160] And then the fourth and final.
[00:51:25.160 --> 00:51:27.080] Ah, that one's too easy.
[00:51:27.080 --> 00:51:27.720] Oh, my God.
[00:51:27.720 --> 00:51:29.080] These are really easy.
[00:51:29.080 --> 00:51:32.200] I asked ChatGPT for 10 and I said make them easy to hard.
[00:51:32.200 --> 00:51:35.080] And I meant like eight, nine, and ten, and they're just gimme.
[00:51:35.400 --> 00:51:41.000] Like, listen, if you roll a natural 20 on an attack roll, what special effect occurs?
[00:51:41.320 --> 00:51:45.960] If you roll a nat 20 on an attack.
[00:51:47.240 --> 00:51:49.560] Wow, maybe it's not as easy as I thought.
[00:51:49.560 --> 00:51:50.600] Hmm.
[00:51:50.920 --> 00:51:51.880] See, this is rare.
[00:51:51.880 --> 00:51:55.240] It's only happened a few times.
[00:51:55.560 --> 00:51:56.760] It happens now and again.
[00:51:56.760 --> 00:51:57.160] Yeah.
[00:51:57.160 --> 00:52:05.080] So if you were to roll a nat 20 on a bow attack or a sword attack, what do we do?
[00:52:05.080 --> 00:52:06.440] Do you get an extra attack?
[00:52:06.440 --> 00:52:09.960] You get it's a critical hit is what it's called.
[00:52:09.960 --> 00:52:14.600] And you roll your damage dice twice, but you only take the bonus.
[00:52:14.760 --> 00:52:15.960] You know how there's a damage bonus?
[00:52:15.960 --> 00:52:18.360] You only take that once, but you roll the damage die twice.
[00:52:18.360 --> 00:52:18.600] Right.
[00:52:18.600 --> 00:52:20.040] There are some DMs that it's all.
[00:52:20.040 --> 00:52:24.920] A lot of this is house rule, but like, let's say you're doing a D8 plus three damage, right?
[00:52:24.920 --> 00:52:27.960] Some DMs will just say you do max damage automatically.
[00:52:27.960 --> 00:52:30.840] Some will say you do two dice max damage.
[00:52:30.840 --> 00:52:33.160] That feels like a lot to me because that would be 19 points of damage.
[00:52:33.160 --> 00:52:34.440] And others say roll it twice.
[00:52:34.440 --> 00:52:35.080] That's what I do.
[00:52:35.080 --> 00:52:37.000] Roll it twice, add, add three.
[00:52:37.320 --> 00:52:38.200] All right.
[00:52:38.200 --> 00:52:39.640] Bonus question.
[00:52:39.640 --> 00:52:47.680] What condition occurs if your hit points become negative, equal to, or greater than your maximum hit points from a single attack?
[00:52:48.000 --> 00:52:56.800] So let's say you had 20, your max hit points are 20, and you took 41 points of damage with a single attack, like a dragon breath.
[00:52:56.800 --> 00:52:58.080] What would happen to you?
[00:52:58.080 --> 00:52:59.520] Is that an instant kill?
[00:52:59.520 --> 00:53:00.080] It is.
[00:53:00.080 --> 00:53:00.480] Yeah.
[00:53:00.800 --> 00:53:05.280] You immediately die versus the fifth edition freaking death-saving throws.
[00:53:05.920 --> 00:53:08.720] I was going to say, you must be extremely dead in that case.
[00:53:09.120 --> 00:53:09.520] Yeah.
[00:53:09.520 --> 00:53:12.080] I think I actually played as 10 below.
[00:53:12.080 --> 00:53:13.280] Is that what I did?
[00:53:13.280 --> 00:53:17.520] See, I said if you went negative, I think I've been house rolling negative 10.
[00:53:17.520 --> 00:53:18.640] That's yeah, I think so.
[00:53:18.640 --> 00:53:20.480] I think that's what I did, which is interesting.
[00:53:20.480 --> 00:53:21.680] It's slightly more deadly.
[00:53:21.680 --> 00:53:27.040] But if you have 50 hit points, let's say, and you go to negative 10, that can happen, you know?
[00:53:27.040 --> 00:53:27.680] Yeah.
[00:53:27.680 --> 00:53:34.000] Meaning if your max is 50, but you're as you start to get down and get damaged, like going to negative 10 is not unheard of.
[00:53:34.000 --> 00:53:37.040] So I like there to be death possible, man.
[00:53:37.360 --> 00:53:43.120] Yeah, and in our campaign, none of us have ever died yet with that house rule.
[00:53:43.120 --> 00:53:52.720] So but in the other, the early, the Fandelver one where it was first and second level characters, I lost two, I lost two and one Dragon Breath.
[00:53:52.720 --> 00:53:54.560] And I was like, oops.
[00:53:55.200 --> 00:53:59.440] I bet you went kind of easy on us on the other campaign that we started years ago.
[00:53:59.440 --> 00:53:59.920] You probably did.
[00:54:00.160 --> 00:54:00.720] I did.
[00:54:00.720 --> 00:54:02.400] I didn't really want anybody to die.
[00:54:02.800 --> 00:54:08.480] I mean, I never, I didn't like fudge dice rolls, but I always kind of made sure it's really hard DMing.
[00:54:08.480 --> 00:54:09.120] Not really hard.
[00:54:09.120 --> 00:54:14.160] It is difficult DMing like first and second level campaigns because they're so fragile, you know?
[00:54:14.160 --> 00:54:14.640] Yeah.
[00:54:14.960 --> 00:54:15.440] So.
[00:54:15.440 --> 00:54:15.920] Yeah.
[00:54:15.920 --> 00:54:18.320] Well, Derek Reimer, thanks for playing.
[00:54:18.640 --> 00:54:20.640] Well, that was nerve-wracking.
[00:54:20.640 --> 00:54:21.040] Thanks.
[00:54:21.040 --> 00:54:21.600] Thanks for having me.
[00:54:21.760 --> 00:54:22.480] You did okay.
[00:54:22.880 --> 00:54:25.360] You got four out of five, if I'm counting correctly.
[00:54:25.360 --> 00:54:26.960] Yeah, let's call it that.
[00:54:26.960 --> 00:54:29.440] Yeah, let's call it that, he says.