<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheet.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:podcast="https://podcastindex.org/namespace/1.0">
  <channel>
    <atom:link rel="self" type="application/rss+xml" href="https://feeds.transistor.fm/startup-to-last" title="MP3 Audio"/>
    <atom:link rel="hub" href="https://pubsubhubbub.appspot.com/"/>
    <podcast:podping usesPodping="true"/>
    <title>Startup to Last</title>
    <generator>Transistor (https://transistor.fm)</generator>
    <itunes:new-feed-url>https://feeds.transistor.fm/startup-to-last</itunes:new-feed-url>
    <description>Two founders talk about how to build software businesses that are meant to last. Each episode includes a deep dive into a different topic related to starting, growing, and sustaining a healthy business.</description>
    <copyright>© Rick Lindquist and Tyler King</copyright>
    <podcast:guid>62905165-85e3-53d0-a91e-792a1f860b09</podcast:guid>
    <podcast:locked>yes</podcast:locked>
    <language>en</language>
    <pubDate>Thu, 23 Apr 2026 13:55:22 -0500</pubDate>
    <lastBuildDate>Thu, 23 Apr 2026 13:56:01 -0500</lastBuildDate>
    <link>https://www.startuptolast.com/</link>
    <image>
      <url>https://img.transistorcdn.com/ucMcPY4g7n2k1yUyEA7LevLLFJ1YsIIAhEXQNRHA2Gk/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzI5MzgvMTU2Mzcx/ODYwMC1hcnR3b3Jr/LmpwZw.jpg</url>
      <title>Startup to Last</title>
      <link>https://www.startuptolast.com/</link>
    </image>
    <itunes:category text="Business">
      <itunes:category text="Entrepreneurship"/>
    </itunes:category>
    <itunes:category text="Business">
      <itunes:category text="Marketing"/>
    </itunes:category>
    <itunes:type>episodic</itunes:type>
    <itunes:author>Rick Lindquist and Tyler King</itunes:author>
    <itunes:image href="https://img.transistorcdn.com/ucMcPY4g7n2k1yUyEA7LevLLFJ1YsIIAhEXQNRHA2Gk/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzI5MzgvMTU2Mzcx/ODYwMC1hcnR3b3Jr/LmpwZw.jpg"/>
    <itunes:summary>Two founders talk about how to build software businesses that are meant to last. Each episode includes a deep dive into a different topic related to starting, growing, and sustaining a healthy business.</itunes:summary>
    <itunes:subtitle>Two founders talk about how to build software businesses that are meant to last.</itunes:subtitle>
    <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
    <itunes:owner>
      <itunes:name>Tyler King</itunes:name>
    </itunes:owner>
    <itunes:complete>No</itunes:complete>
    <itunes:explicit>Yes</itunes:explicit>
    <item>
      <title>Where do the humans fit in?</title>
      <itunes:episode>202</itunes:episode>
      <podcast:episode>202</podcast:episode>
      <itunes:title>Where do the humans fit in?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">6fb8ebec-836c-4dcc-9849-aed06fb49af5</guid>
      <link>https://share.transistor.fm/s/13076162</link>
      <description>
        <![CDATA[<p>In this episode, we talk about how one of the new business challenges is to figure out what skills are uniquely human, and leaning into those things as your differentiator.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about how one of the new business challenges is to figure out what skills are uniquely human, and leaning into those things as your differentiator.</p>]]>
      </content:encoded>
      <pubDate>Thu, 23 Apr 2026 13:54:47 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/13076162/fafcbbc4.mp3" length="52744310" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3296</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about how one of the new business challenges is to figure out what skills are uniquely human, and leaning into those things as your differentiator.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/13076162/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3mk6osgr6qf2e"/>
    </item>
    <item>
      <title>Where to host a marketing site in the age of AI</title>
      <itunes:episode>201</itunes:episode>
      <podcast:episode>201</podcast:episode>
      <itunes:title>Where to host a marketing site in the age of AI</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d2202eb9-5b8c-4523-a32a-bb2e84bcbe98</guid>
      <link>https://share.transistor.fm/s/f4aed52a</link>
      <description>
        <![CDATA[<p>In this episode, we talk about whether tools like Webflow still make sense to use when AI can generate professional looking marketing sites for you.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about whether tools like Webflow still make sense to use when AI can generate professional looking marketing sites for you.</p>]]>
      </content:encoded>
      <pubDate>Thu, 09 Apr 2026 10:13:54 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f4aed52a/dfe93819.mp3" length="48818857" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3050</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about whether tools like Webflow still make sense to use when AI can generate professional looking marketing sites for you.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/f4aed52a/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3mj33vz5dsb2p"/>
    </item>
    <item>
      <title>How much to invest in growth</title>
      <itunes:episode>200</itunes:episode>
      <podcast:episode>200</podcast:episode>
      <itunes:title>How much to invest in growth</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">3840f4d8-a9cb-4d06-b2de-bfbac1f42668</guid>
      <link>https://share.transistor.fm/s/9edf3cad</link>
      <description>
        <![CDATA[<p>In this episode, we talk about how Rick has changed LegUp Health’s formula that decides how much money is available to invest in growth.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about how Rick has changed LegUp Health’s formula that decides how much money is available to invest in growth.</p>]]>
      </content:encoded>
      <pubDate>Fri, 27 Mar 2026 10:18:05 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/9edf3cad/6d57dde4.mp3" length="49640128" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3102</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about how Rick has changed LegUp Health’s formula that decides how much money is available to invest in growth.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/9edf3cad/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Do custom Notion agents really work?</title>
      <itunes:episode>199</itunes:episode>
      <podcast:episode>199</podcast:episode>
      <itunes:title>Do custom Notion agents really work?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e1bbd281-89f1-41fc-9de1-c53c9ac88ad8</guid>
      <link>https://share.transistor.fm/s/3e7e04b2</link>
      <description>
        <![CDATA[<p>No, they don't!</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>No, they don't!</p>]]>
      </content:encoded>
      <pubDate>Thu, 12 Mar 2026 15:14:36 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/3e7e04b2/0f6c3fbd.mp3" length="51296090" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3205</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>No, they don't!</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/3e7e04b2/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3mgv7ofglj424"/>
    </item>
    <item>
      <title>Soft launches</title>
      <itunes:episode>198</itunes:episode>
      <podcast:episode>198</podcast:episode>
      <itunes:title>Soft launches</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e64800c7-9e92-438d-8446-3f961a394ba3</guid>
      <link>https://share.transistor.fm/s/cd823ddf</link>
      <description>
        <![CDATA[<p>Less Annoying CRM is soft launching two major features we’ve been working on for months. This episode dives into that and a bunch of other stuff.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Less Annoying CRM is soft launching two major features we’ve been working on for months. This episode dives into that and a bunch of other stuff.</p>]]>
      </content:encoded>
      <pubDate>Fri, 27 Feb 2026 16:20:06 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/cd823ddf/a0e6a8f8.mp3" length="49444080" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3089</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Less Annoying CRM is soft launching two major features we’ve been working on for months. This episode dives into that and a bunch of other stuff.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/cd823ddf/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3mfuqmjdfy72g"/>
    </item>
    <item>
      <title>New positioning</title>
      <itunes:episode>197</itunes:episode>
      <podcast:episode>197</podcast:episode>
      <itunes:title>New positioning</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e6dbe281-6341-4363-a2f5-127fe3f8669a</guid>
      <link>https://share.transistor.fm/s/45d82cff</link>
      <description>
        <![CDATA[<p>Of course we spend the first half of the episode talking about AI, but then we get into some good ol’ fashioned SaaS talk.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Of course we spend the first half of the episode talking about AI, but then we get into some good ol’ fashioned SaaS talk.</p>]]>
      </content:encoded>
      <pubDate>Thu, 12 Feb 2026 10:43:24 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/45d82cff/abc4db00.mp3" length="52012869" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3250</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Of course we spend the first half of the episode talking about AI, but then we get into some good ol’ fashioned SaaS talk.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/45d82cff/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3meogsgapxt2u"/>
    </item>
    <item>
      <title>Obligatory Claude Code episode</title>
      <itunes:episode>196</itunes:episode>
      <podcast:episode>196</podcast:episode>
      <itunes:title>Obligatory Claude Code episode</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ee8dd7bb-229d-446f-871f-5d99830d7e40</guid>
      <link>https://share.transistor.fm/s/d44bbc73</link>
      <description>
        <![CDATA[<p>In this episode, we talk about the only thing anyone is talking about right now: Claude Code.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about the only thing anyone is talking about right now: Claude Code.</p>]]>
      </content:encoded>
      <pubDate>Thu, 15 Jan 2026 10:10:52 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/d44bbc73/f4f0ee8e.mp3" length="47036244" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2939</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about the only thing anyone is talking about right now: Claude Code.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/d44bbc73/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3mchxwokie32d"/>
    </item>
    <item>
      <title>2025 Recap</title>
      <itunes:episode>195</itunes:episode>
      <podcast:episode>195</podcast:episode>
      <itunes:title>2025 Recap</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5d7dbd72-f3fb-4e32-8fb4-62e49bab073f</guid>
      <link>https://share.transistor.fm/s/2dd8417e</link>
      <description>
        <![CDATA[<p>This is our annual recap episode. We talk about how things went in 2025 and what we’re hoping to see in 2026.</p><p><strong>Personal goals for 2026</strong></p><ul><li>Rick <ul><li>Getting back to basics</li><li>Going from reactive to proactive (and surviving to thriving)</li><li>Shifting from a strategy of playing it safe and reducing risk to taking smart risk and being ok looking a little foolish</li></ul></li><li>Tyler <ul><li>Handle the transition back to full-time work (as it impacts parenting)</li><li>Find clarity on what level of wealth we’re comfortable exposing our daughter to.</li><li>Help Shelly find more ways to go out at night while I take care of Syd</li><li>Finalize will+trust</li><li>Stretch goal: Start vibe coding personal apps</li></ul></li></ul><p><strong>Professional goals for 2026</strong></p><ul><li>Rick (hopes to achieve at least two of these goals) <ul><li>Outsource, delegate, or automate recurring tasks that I no longer value doing and/or others don’t value me doing</li><li>Try to grow LegUp Health by 50%, but do it in a way that we are all excited about</li><li>Rebuild personal website + read 10 really, really good nonfiction books and publish notes on them</li><li>Experiment with AI to generate 1 additional revenue stream</li></ul></li><li>Tyler <ul><li>Spend almost all IC time on design, product management, and coding. Fewer distractions!</li><li>Management: Get the team up to speed on AI, and make it self-sustaining</li><li>Product management/design: Figure out how to keep up with the devs (especially if AI allows them to move even faster)</li><li>Product <ul><li>Ship Mobile and Kanban</li><li>Reduce support by making things more self-serve</li><li>Main theme: The first 30 minutes <ul><li>Onboarding improvements</li><li>Rebuild the importing flow</li><li>Simplification <ul><li>Separate contacts and companies</li><li>Open contacts in page dialog</li><li>Statuses on the contact record</li><li>Table view of contacts</li></ul></li></ul></li></ul></li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This is our annual recap episode. We talk about how things went in 2025 and what we’re hoping to see in 2026.</p><p><strong>Personal goals for 2026</strong></p><ul><li>Rick <ul><li>Getting back to basics</li><li>Going from reactive to proactive (and surviving to thriving)</li><li>Shifting from a strategy of playing it safe and reducing risk to taking smart risk and being ok looking a little foolish</li></ul></li><li>Tyler <ul><li>Handle the transition back to full-time work (as it impacts parenting)</li><li>Find clarity on what level of wealth we’re comfortable exposing our daughter to.</li><li>Help Shelly find more ways to go out at night while I take care of Syd</li><li>Finalize will+trust</li><li>Stretch goal: Start vibe coding personal apps</li></ul></li></ul><p><strong>Professional goals for 2026</strong></p><ul><li>Rick (hopes to achieve at least two of these goals) <ul><li>Outsource, delegate, or automate recurring tasks that I no longer value doing and/or others don’t value me doing</li><li>Try to grow LegUp Health by 50%, but do it in a way that we are all excited about</li><li>Rebuild personal website + read 10 really, really good nonfiction books and publish notes on them</li><li>Experiment with AI to generate 1 additional revenue stream</li></ul></li><li>Tyler <ul><li>Spend almost all IC time on design, product management, and coding. Fewer distractions!</li><li>Management: Get the team up to speed on AI, and make it self-sustaining</li><li>Product management/design: Figure out how to keep up with the devs (especially if AI allows them to move even faster)</li><li>Product <ul><li>Ship Mobile and Kanban</li><li>Reduce support by making things more self-serve</li><li>Main theme: The first 30 minutes <ul><li>Onboarding improvements</li><li>Rebuild the importing flow</li><li>Simplification <ul><li>Separate contacts and companies</li><li>Open contacts in page dialog</li><li>Statuses on the contact record</li><li>Table view of contacts</li></ul></li></ul></li></ul></li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Wed, 31 Dec 2025 11:21:23 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/2dd8417e/f25b6696.mp3" length="112810879" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>7050</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>This is our annual recap episode. We talk about how things went in 2025 and what we’re hoping to see in 2026.</p><p><strong>Personal goals for 2026</strong></p><ul><li>Rick <ul><li>Getting back to basics</li><li>Going from reactive to proactive (and surviving to thriving)</li><li>Shifting from a strategy of playing it safe and reducing risk to taking smart risk and being ok looking a little foolish</li></ul></li><li>Tyler <ul><li>Handle the transition back to full-time work (as it impacts parenting)</li><li>Find clarity on what level of wealth we’re comfortable exposing our daughter to.</li><li>Help Shelly find more ways to go out at night while I take care of Syd</li><li>Finalize will+trust</li><li>Stretch goal: Start vibe coding personal apps</li></ul></li></ul><p><strong>Professional goals for 2026</strong></p><ul><li>Rick (hopes to achieve at least two of these goals) <ul><li>Outsource, delegate, or automate recurring tasks that I no longer value doing and/or others don’t value me doing</li><li>Try to grow LegUp Health by 50%, but do it in a way that we are all excited about</li><li>Rebuild personal website + read 10 really, really good nonfiction books and publish notes on them</li><li>Experiment with AI to generate 1 additional revenue stream</li></ul></li><li>Tyler <ul><li>Spend almost all IC time on design, product management, and coding. Fewer distractions!</li><li>Management: Get the team up to speed on AI, and make it self-sustaining</li><li>Product management/design: Figure out how to keep up with the devs (especially if AI allows them to move even faster)</li><li>Product <ul><li>Ship Mobile and Kanban</li><li>Reduce support by making things more self-serve</li><li>Main theme: The first 30 minutes <ul><li>Onboarding improvements</li><li>Rebuild the importing flow</li><li>Simplification <ul><li>Separate contacts and companies</li><li>Open contacts in page dialog</li><li>Statuses on the contact record</li><li>Table view of contacts</li></ul></li></ul></li></ul></li></ul></li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/2dd8417e/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3mbceuniou523"/>
    </item>
    <item>
      <title>Can Rick’s optimism defeat Tyler’s pessimism?</title>
      <itunes:episode>194</itunes:episode>
      <podcast:episode>194</podcast:episode>
      <itunes:title>Can Rick’s optimism defeat Tyler’s pessimism?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">4c8576c0-371e-44f9-91f6-3ec210e080dc</guid>
      <link>https://share.transistor.fm/s/f500fa5b</link>
      <description>
        <![CDATA[<p>In this episode, we once again talk about AI, and oh boy do we get off topic.</p><p><a href="https://scribe.com/">Here's the AI tool Rick mentioned for recording your screen</a> (we'll talk about that in a future episode)</p><p><a href="https://static1.squarespace.com/static/50363cf324ac8e905e7df861/t/69267317ffc0332dfc580e20/1764127511109/2025+Autumn+AI.pdf">Here's the AI report Rick mentioned</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we once again talk about AI, and oh boy do we get off topic.</p><p><a href="https://scribe.com/">Here's the AI tool Rick mentioned for recording your screen</a> (we'll talk about that in a future episode)</p><p><a href="https://static1.squarespace.com/static/50363cf324ac8e905e7df861/t/69267317ffc0332dfc580e20/1764127511109/2025+Autumn+AI.pdf">Here's the AI report Rick mentioned</a></p>]]>
      </content:encoded>
      <pubDate>Thu, 04 Dec 2025 10:18:43 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f500fa5b/a3c0c28f.mp3" length="47285828" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2954</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we once again talk about AI, and oh boy do we get off topic.</p><p><a href="https://scribe.com/">Here's the AI tool Rick mentioned for recording your screen</a> (we'll talk about that in a future episode)</p><p><a href="https://static1.squarespace.com/static/50363cf324ac8e905e7df861/t/69267317ffc0332dfc580e20/1764127511109/2025+Autumn+AI.pdf">Here's the AI report Rick mentioned</a></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/f500fa5b/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3m76escw6hg25"/>
    </item>
    <item>
      <title>Open Enrollment Woes</title>
      <itunes:episode>193</itunes:episode>
      <podcast:episode>193</podcast:episode>
      <itunes:title>Open Enrollment Woes</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5e3597fa-125c-4925-84c3-d0e6974e2373</guid>
      <link>https://share.transistor.fm/s/6aceba0b</link>
      <description>
        <![CDATA[<p>In this episode, Tyler and Rick discuss the challenges faced by Leg Up Health during open enrollment, including issues with email communication and the impact of AI on consumer behavior. They explore the current health insurance landscape, the importance of product strategy and customer experience, and the role of content in engaging customers. The conversation also touches on shifts in search traffic and marketing strategies as they adapt to changing consumer needs.<br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Tyler and Rick discuss the challenges faced by Leg Up Health during open enrollment, including issues with email communication and the impact of AI on consumer behavior. They explore the current health insurance landscape, the importance of product strategy and customer experience, and the role of content in engaging customers. The conversation also touches on shifts in search traffic and marketing strategies as they adapt to changing consumer needs.<br></p>]]>
      </content:encoded>
      <pubDate>Thu, 20 Nov 2025 12:53:39 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/6aceba0b/d6d9ffec.mp3" length="43061443" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2690</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, Tyler and Rick discuss the challenges faced by Leg Up Health during open enrollment, including issues with email communication and the impact of AI on consumer behavior. They explore the current health insurance landscape, the importance of product strategy and customer experience, and the role of content in engaging customers. The conversation also touches on shifts in search traffic and marketing strategies as they adapt to changing consumer needs.<br></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/6aceba0b/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3m63gw6uhz62r"/>
    </item>
    <item>
      <title>Does OG inbound marketing still work?</title>
      <itunes:episode>192</itunes:episode>
      <podcast:episode>192</podcast:episode>
      <itunes:title>Does OG inbound marketing still work?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f7665b74-9e3c-4c8b-8330-526e2f4602b8</guid>
      <link>https://share.transistor.fm/s/7a1a4945</link>
      <description>
        <![CDATA[<p>In this episode, we talk about whether Rick’s expertise with traditional inbound marketing will work for LegUp Health.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about whether Rick’s expertise with traditional inbound marketing will work for LegUp Health.</p>]]>
      </content:encoded>
      <pubDate>Thu, 06 Nov 2025 10:16:17 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7a1a4945/cfb5e59b.mp3" length="48005499" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2999</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about whether Rick’s expertise with traditional inbound marketing will work for LegUp Health.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/7a1a4945/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3m4xxlwxy2c2v"/>
    </item>
    <item>
      <title>ICP ICP ICP</title>
      <itunes:episode>191</itunes:episode>
      <podcast:episode>191</podcast:episode>
      <itunes:title>ICP ICP ICP</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">36bd52b9-76d8-49a2-ad97-8ba37ee3a04f</guid>
      <link>https://share.transistor.fm/s/9e7b549c</link>
      <description>
        <![CDATA[<p>We spend the entire episode diving into how we can better define Less Annoying CRM’s ideal customer profile, and what that would mean for the product and marketing.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>We spend the entire episode diving into how we can better define Less Annoying CRM’s ideal customer profile, and what that would mean for the product and marketing.</p>]]>
      </content:encoded>
      <pubDate>Thu, 09 Oct 2025 11:05:01 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/9e7b549c/3aa7a0ee.mp3" length="52667389" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3291</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>We spend the entire episode diving into how we can better define Less Annoying CRM’s ideal customer profile, and what that would mean for the product and marketing.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/9e7b549c/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3m2rjvu3aei2h"/>
    </item>
    <item>
      <title>What to do while you’re waiting for results</title>
      <itunes:episode>190</itunes:episode>
      <podcast:episode>190</podcast:episode>
      <itunes:title>What to do while you’re waiting for results</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">da47e336-3a0c-4b2b-924b-709c2d8f5be7</guid>
      <link>https://share.transistor.fm/s/f34bea52</link>
      <description>
        <![CDATA[<p>In this episode, we talk about what the Less Annoying team should be working on while waiting to see if the last bet actually pays off.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about what the Less Annoying team should be working on while waiting to see if the last bet actually pays off.</p>]]>
      </content:encoded>
      <pubDate>Thu, 25 Sep 2025 12:00:46 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f34bea52/37d14f8e.mp3" length="52598085" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3286</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about what the Less Annoying team should be working on while waiting to see if the last bet actually pays off.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/f34bea52/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lzogmke3yp2o"/>
    </item>
    <item>
      <title>Website overhaul </title>
      <itunes:episode>189</itunes:episode>
      <podcast:episode>189</podcast:episode>
      <itunes:title>Website overhaul </itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0a22de54-f918-48ca-8ae0-00f5b94c949e</guid>
      <link>https://share.transistor.fm/s/b7017dac</link>
      <description>
        <![CDATA[<p>In this episode, we talk about how Rick can overhaul the LegUp Health website to fit their new positioning.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about how Rick can overhaul the LegUp Health website to fit their new positioning.</p>]]>
      </content:encoded>
      <pubDate>Thu, 11 Sep 2025 10:15:47 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/b7017dac/22f1db30.mp3" length="54238922" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3389</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about how Rick can overhaul the LegUp Health website to fit their new positioning.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/b7017dac/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lyl244k6fy2r"/>
    </item>
    <item>
      <title>We're profitable, now what?</title>
      <itunes:episode>188</itunes:episode>
      <podcast:episode>188</podcast:episode>
      <itunes:title>We're profitable, now what?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d62ff89e-0d6b-44f1-a328-9bc74d284659</guid>
      <link>https://share.transistor.fm/s/7f34692c</link>
      <description>
        <![CDATA[<p>In this episode, Rick shares how he approached thinking about what to do with his first meaningful profit.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Rick shares how he approached thinking about what to do with his first meaningful profit.</p>]]>
      </content:encoded>
      <pubDate>Thu, 14 Aug 2025 10:15:29 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7f34692c/19e74c44.mp3" length="51472042" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3216</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, Rick shares how he approached thinking about what to do with his first meaningful profit.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/7f34692c/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lwemzlre2j2k"/>
    </item>
    <item>
      <title>Tiers, add-ons or standalone products?</title>
      <itunes:episode>187</itunes:episode>
      <podcast:episode>187</podcast:episode>
      <itunes:title>Tiers, add-ons or standalone products?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">bcbe9d52-1c11-4e82-bf31-e51e6b4c38d4</guid>
      <link>https://share.transistor.fm/s/9f5b2052</link>
      <description>
        <![CDATA[<p>In this episode, we dive into where things stand with Less Annoying CRM’s potential new product.</p><p>Here's the blog post about <a href="https://www.ricklindquist.com/blog/first-team-principles">First Team Principles</a> Rick mentioned.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we dive into where things stand with Less Annoying CRM’s potential new product.</p><p>Here's the blog post about <a href="https://www.ricklindquist.com/blog/first-team-principles">First Team Principles</a> Rick mentioned.</p>]]>
      </content:encoded>
      <pubDate>Thu, 31 Jul 2025 10:19:44 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/9f5b2052/8c30521e.mp3" length="54837461" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3426</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we dive into where things stand with Less Annoying CRM’s potential new product.</p><p>Here's the blog post about <a href="https://www.ricklindquist.com/blog/first-team-principles">First Team Principles</a> Rick mentioned.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/9f5b2052/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lvbgqrzic22c"/>
    </item>
    <item>
      <title>User communities</title>
      <itunes:episode>186</itunes:episode>
      <podcast:episode>186</podcast:episode>
      <itunes:title>User communities</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">67d346c2-07bb-4b91-8052-2d000aa0889c</guid>
      <link>https://share.transistor.fm/s/cc3fcad3</link>
      <description>
        <![CDATA[<p>In this episode, we talk about trying to create a forum for Less Annoying CRM’s users.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about trying to create a forum for Less Annoying CRM’s users.</p>]]>
      </content:encoded>
      <pubDate>Thu, 17 Jul 2025 10:12:11 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/cc3fcad3/103a34c9.mp3" length="51095032" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3193</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about trying to create a forum for Less Annoying CRM’s users.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/cc3fcad3/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lu67sad3w52k"/>
    </item>
    <item>
      <title>SIP trunks</title>
      <itunes:episode>185</itunes:episode>
      <podcast:episode>185</podcast:episode>
      <itunes:title>SIP trunks</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c910b00c-a775-4c83-ba30-6180006c9d60</guid>
      <link>https://share.transistor.fm/s/1a4a1f5a</link>
      <description>
        <![CDATA[<p>In this conversation, Rick and Tyler explore various topics ranging from smoking techniques and the evolution of grilling methods to the challenges and benefits of a four-day work week. They discuss business growth strategies, particularly focusing on customer retention and the importance of securing renewals. The conversation shifts to the technical aspects of VoIP systems, including SIP trunking, and the implications of AI on search optimization. Finally, they delve into potential new product opportunities and the strategic considerations of acquiring existing products to enhance their offerings.<br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this conversation, Rick and Tyler explore various topics ranging from smoking techniques and the evolution of grilling methods to the challenges and benefits of a four-day work week. They discuss business growth strategies, particularly focusing on customer retention and the importance of securing renewals. The conversation shifts to the technical aspects of VoIP systems, including SIP trunking, and the implications of AI on search optimization. Finally, they delve into potential new product opportunities and the strategic considerations of acquiring existing products to enhance their offerings.<br></p>]]>
      </content:encoded>
      <pubDate>Fri, 04 Jul 2025 13:55:30 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1a4a1f5a/f549c765.mp3" length="46155584" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2884</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this conversation, Rick and Tyler explore various topics ranging from smoking techniques and the evolution of grilling methods to the challenges and benefits of a four-day work week. They discuss business growth strategies, particularly focusing on customer retention and the importance of securing renewals. The conversation shifts to the technical aspects of VoIP systems, including SIP trunking, and the implications of AI on search optimization. Finally, they delve into potential new product opportunities and the strategic considerations of acquiring existing products to enhance their offerings.<br></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lt5w7nxql42q"/>
    </item>
    <item>
      <title>Add-on product</title>
      <itunes:episode>184</itunes:episode>
      <podcast:episode>184</podcast:episode>
      <itunes:title>Add-on product</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">32457b49-3039-4341-bc7c-fa149dfc31bb</guid>
      <link>https://share.transistor.fm/s/0e8209f8</link>
      <description>
        <![CDATA[<p>In this conversation, Rick and Tyler discuss various topics ranging from their beverage preferences to the latest trends in podcasts, business growth, and the integration of AI in their operations. They explore the significance of setting revenue goals, the role of AI agents in customer outreach, and the development of internal tools to enhance efficiency. Additionally, they delve into potential new product opportunities, customer feedback, and pricing strategies for future offerings, concluding with reflections on their business direction.</p><p>Takeaways</p><ul><li>Tyler prefers soda over coffee for his morning routine.</li><li>Rick has re-engaged with podcasts, discovering new content.</li><li>Leg Up Health achieved a record revenue month, nearing their goal.</li><li>Setting realistic revenue goals can provide relief and stability.</li><li>AI integration is becoming crucial for business operations.</li><li>Internal tools can significantly improve team efficiency.</li><li>Customer feedback is essential for product development.</li><li>Pricing strategies need careful consideration for new offerings.</li><li>Exploring new product opportunities can enhance revenue per user.</li><li>Authenticity in customer outreach is vital for engagement.</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this conversation, Rick and Tyler discuss various topics ranging from their beverage preferences to the latest trends in podcasts, business growth, and the integration of AI in their operations. They explore the significance of setting revenue goals, the role of AI agents in customer outreach, and the development of internal tools to enhance efficiency. Additionally, they delve into potential new product opportunities, customer feedback, and pricing strategies for future offerings, concluding with reflections on their business direction.</p><p>Takeaways</p><ul><li>Tyler prefers soda over coffee for his morning routine.</li><li>Rick has re-engaged with podcasts, discovering new content.</li><li>Leg Up Health achieved a record revenue month, nearing their goal.</li><li>Setting realistic revenue goals can provide relief and stability.</li><li>AI integration is becoming crucial for business operations.</li><li>Internal tools can significantly improve team efficiency.</li><li>Customer feedback is essential for product development.</li><li>Pricing strategies need careful consideration for new offerings.</li><li>Exploring new product opportunities can enhance revenue per user.</li><li>Authenticity in customer outreach is vital for engagement.</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 19 Jun 2025 10:25:07 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/0e8209f8/dbb31950.mp3" length="52310037" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3268</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this conversation, Rick and Tyler discuss various topics ranging from their beverage preferences to the latest trends in podcasts, business growth, and the integration of AI in their operations. They explore the significance of setting revenue goals, the role of AI agents in customer outreach, and the development of internal tools to enhance efficiency. Additionally, they delve into potential new product opportunities, customer feedback, and pricing strategies for future offerings, concluding with reflections on their business direction.</p><p>Takeaways</p><ul><li>Tyler prefers soda over coffee for his morning routine.</li><li>Rick has re-engaged with podcasts, discovering new content.</li><li>Leg Up Health achieved a record revenue month, nearing their goal.</li><li>Setting realistic revenue goals can provide relief and stability.</li><li>AI integration is becoming crucial for business operations.</li><li>Internal tools can significantly improve team efficiency.</li><li>Customer feedback is essential for product development.</li><li>Pricing strategies need careful consideration for new offerings.</li><li>Exploring new product opportunities can enhance revenue per user.</li><li>Authenticity in customer outreach is vital for engagement.</li></ul><p><br></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/0e8209f8/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lrxthjuh6s2y"/>
    </item>
    <item>
      <title>Will these guys please stop talking about AI</title>
      <itunes:episode>183</itunes:episode>
      <podcast:episode>183</podcast:episode>
      <itunes:title>Will these guys please stop talking about AI</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">471b7efa-5337-4eaf-8f4d-fd3300ea951f</guid>
      <link>https://share.transistor.fm/s/d5d91504</link>
      <description>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss various topics ranging from personal experiences with parenting and reading habits to business growth strategies and the integration of AI in their respective companies. They explore the challenges of managing growth, the importance of understanding customer needs, and the potential of AI to enhance efficiency and customer experience. The discussion also touches on the significance of vertical integration and the future of AI in business, emphasizing the need for companies to be prepared for technological advancements while maintaining a focus on customer service.</p><p>Chapters<br>00:00 Parenting and Sleep Challenges<br>03:29 Reading Habits and Fantasy Literature<br>06:32 Business Growth and Revenue Updates<br>09:21 Form Metrics and Marketing Strategies<br>12:17 Internal Use Cases and New Features<br>15:23 Exploring Industry-Specific CRM Opportunities<br>21:22 Future of CRM and Industry Integration<br>28:57 Navigating Software Integration Challenges<br>32:34 The AI Dilemma: To Adopt or Not?<br>37:13 AI Readiness: Preparing for the Future<br>39:38 Revenue Metrics and AI Efficiency<br>50:28 Exploring AI Opportunities in Customer Experience</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss various topics ranging from personal experiences with parenting and reading habits to business growth strategies and the integration of AI in their respective companies. They explore the challenges of managing growth, the importance of understanding customer needs, and the potential of AI to enhance efficiency and customer experience. The discussion also touches on the significance of vertical integration and the future of AI in business, emphasizing the need for companies to be prepared for technological advancements while maintaining a focus on customer service.</p><p>Chapters<br>00:00 Parenting and Sleep Challenges<br>03:29 Reading Habits and Fantasy Literature<br>06:32 Business Growth and Revenue Updates<br>09:21 Form Metrics and Marketing Strategies<br>12:17 Internal Use Cases and New Features<br>15:23 Exploring Industry-Specific CRM Opportunities<br>21:22 Future of CRM and Industry Integration<br>28:57 Navigating Software Integration Challenges<br>32:34 The AI Dilemma: To Adopt or Not?<br>37:13 AI Readiness: Preparing for the Future<br>39:38 Revenue Metrics and AI Efficiency<br>50:28 Exploring AI Opportunities in Customer Experience</p>]]>
      </content:encoded>
      <pubDate>Thu, 05 Jun 2025 10:17:35 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/d5d91504/3b21b409.mp3" length="52608072" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3287</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss various topics ranging from personal experiences with parenting and reading habits to business growth strategies and the integration of AI in their respective companies. They explore the challenges of managing growth, the importance of understanding customer needs, and the potential of AI to enhance efficiency and customer experience. The discussion also touches on the significance of vertical integration and the future of AI in business, emphasizing the need for companies to be prepared for technological advancements while maintaining a focus on customer service.</p><p>Chapters<br>00:00 Parenting and Sleep Challenges<br>03:29 Reading Habits and Fantasy Literature<br>06:32 Business Growth and Revenue Updates<br>09:21 Form Metrics and Marketing Strategies<br>12:17 Internal Use Cases and New Features<br>15:23 Exploring Industry-Specific CRM Opportunities<br>21:22 Future of CRM and Industry Integration<br>28:57 Navigating Software Integration Challenges<br>32:34 The AI Dilemma: To Adopt or Not?<br>37:13 AI Readiness: Preparing for the Future<br>39:38 Revenue Metrics and AI Efficiency<br>50:28 Exploring AI Opportunities in Customer Experience</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/d5d91504/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lqumj2dnar2x"/>
    </item>
    <item>
      <title>Acquisition vs Expansion</title>
      <itunes:episode>182</itunes:episode>
      <podcast:episode>182</podcast:episode>
      <itunes:title>Acquisition vs Expansion</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f54594d2-7620-4a68-b2b9-f8268cba6b19</guid>
      <link>https://share.transistor.fm/s/39c7d0ab</link>
      <description>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss the challenges and adjustments of parenthood, particularly Tyler's experience as a new father. They explore the balance between work and family life, the dynamics of business growth, and the implications of freemium models in their respective companies. The discussion delves into the importance of customer retention versus acquisition, the value of free users, and the efficiency required in service-heavy business models. Throughout the conversation, they share insights on navigating these complexities while maintaining a focus on long-term success. In this conversation, Tyler King and Rick discuss various topics including the implications of free trials on conversion rates, the integration of AI in coding practices with tools like Cursor, and the evolving landscape of client retention and revenue trends. They also delve into the recent changes in Apple's App Store pricing policies and their impact on developers, as well as the importance of understanding customer segmentation in business strategy.<br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss the challenges and adjustments of parenthood, particularly Tyler's experience as a new father. They explore the balance between work and family life, the dynamics of business growth, and the implications of freemium models in their respective companies. The discussion delves into the importance of customer retention versus acquisition, the value of free users, and the efficiency required in service-heavy business models. Throughout the conversation, they share insights on navigating these complexities while maintaining a focus on long-term success. In this conversation, Tyler King and Rick discuss various topics including the implications of free trials on conversion rates, the integration of AI in coding practices with tools like Cursor, and the evolving landscape of client retention and revenue trends. They also delve into the recent changes in Apple's App Store pricing policies and their impact on developers, as well as the importance of understanding customer segmentation in business strategy.<br></p>]]>
      </content:encoded>
      <pubDate>Thu, 22 May 2025 15:23:04 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/39c7d0ab/cfe07b9a.mp3" length="50702158" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3168</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss the challenges and adjustments of parenthood, particularly Tyler's experience as a new father. They explore the balance between work and family life, the dynamics of business growth, and the implications of freemium models in their respective companies. The discussion delves into the importance of customer retention versus acquisition, the value of free users, and the efficiency required in service-heavy business models. Throughout the conversation, they share insights on navigating these complexities while maintaining a focus on long-term success. In this conversation, Tyler King and Rick discuss various topics including the implications of free trials on conversion rates, the integration of AI in coding practices with tools like Cursor, and the evolving landscape of client retention and revenue trends. They also delve into the recent changes in Apple's App Store pricing policies and their impact on developers, as well as the importance of understanding customer segmentation in business strategy.<br></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/39c7d0ab/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lprx2voeki2q"/>
    </item>
    <item>
      <title>Vibe coding</title>
      <itunes:episode>181</itunes:episode>
      <podcast:episode>181</podcast:episode>
      <itunes:title>Vibe coding</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0e55822e-a67c-4f2d-8fba-8c7aa562f52b</guid>
      <link>https://share.transistor.fm/s/3a491971</link>
      <description>
        <![CDATA[<p>In this conversation, Tyler King shares his experiences as a new father while balancing work responsibilities. The discussion transitions into Tyler's recent work on LegUp Health, focusing on the challenges and opportunities in building a health insurance platform. They explore the concept of 'vibe coding' and how AI is reshaping software development and content creation. The conversation concludes with a brainstorming session on packaging benefits for LegUp Health, emphasizing the importance of clear communication and demonstrating value to potential clients.</p><p>Takeaways</p><p>Fatherhood brings unexpected challenges and joys.<br>Work-life balance is crucial for new parents.<br>Fundraising milestones can be a time for reflection.<br>Vibe coding allows for rapid development with AI assistance.<br>AI can enhance productivity but may lead to fragility in code.<br>Clear communication is key in demonstrating value to clients.<br>Packaging benefits effectively can unlock new opportunities.<br>Understanding the market is essential for product success.<br>AI tools can streamline content creation processes.<br>The future of work may require new skills and adaptability.</p><p>Chapters</p><p>00:00 The Journey of Fatherhood<br>03:16 Navigating Work-Life Balance<br>06:21 Milestones in Professional Growth<br>09:09 The Dynamics of Startups<br>12:11 Innovations in Health Tech<br>15:20 Vibe Coding and AI in Development<br>18:19 The Future of Software Development<br>21:11 Content Creation with AI<br>25:43 Navigating the AI Landscape<br>32:56 The Future of Learning in an AI World<br>37:26 Innovating Benefit Programs<br>49:06 Packaging Value in Health Benefits</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this conversation, Tyler King shares his experiences as a new father while balancing work responsibilities. The discussion transitions into Tyler's recent work on LegUp Health, focusing on the challenges and opportunities in building a health insurance platform. They explore the concept of 'vibe coding' and how AI is reshaping software development and content creation. The conversation concludes with a brainstorming session on packaging benefits for LegUp Health, emphasizing the importance of clear communication and demonstrating value to potential clients.</p><p>Takeaways</p><p>Fatherhood brings unexpected challenges and joys.<br>Work-life balance is crucial for new parents.<br>Fundraising milestones can be a time for reflection.<br>Vibe coding allows for rapid development with AI assistance.<br>AI can enhance productivity but may lead to fragility in code.<br>Clear communication is key in demonstrating value to clients.<br>Packaging benefits effectively can unlock new opportunities.<br>Understanding the market is essential for product success.<br>AI tools can streamline content creation processes.<br>The future of work may require new skills and adaptability.</p><p>Chapters</p><p>00:00 The Journey of Fatherhood<br>03:16 Navigating Work-Life Balance<br>06:21 Milestones in Professional Growth<br>09:09 The Dynamics of Startups<br>12:11 Innovations in Health Tech<br>15:20 Vibe Coding and AI in Development<br>18:19 The Future of Software Development<br>21:11 Content Creation with AI<br>25:43 Navigating the AI Landscape<br>32:56 The Future of Learning in an AI World<br>37:26 Innovating Benefit Programs<br>49:06 Packaging Value in Health Benefits</p>]]>
      </content:encoded>
      <pubDate>Fri, 25 Apr 2025 20:32:24 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/3a491971/4b401c93.mp3" length="55128333" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3445</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this conversation, Tyler King shares his experiences as a new father while balancing work responsibilities. The discussion transitions into Tyler's recent work on LegUp Health, focusing on the challenges and opportunities in building a health insurance platform. They explore the concept of 'vibe coding' and how AI is reshaping software development and content creation. The conversation concludes with a brainstorming session on packaging benefits for LegUp Health, emphasizing the importance of clear communication and demonstrating value to potential clients.</p><p>Takeaways</p><p>Fatherhood brings unexpected challenges and joys.<br>Work-life balance is crucial for new parents.<br>Fundraising milestones can be a time for reflection.<br>Vibe coding allows for rapid development with AI assistance.<br>AI can enhance productivity but may lead to fragility in code.<br>Clear communication is key in demonstrating value to clients.<br>Packaging benefits effectively can unlock new opportunities.<br>Understanding the market is essential for product success.<br>AI tools can streamline content creation processes.<br>The future of work may require new skills and adaptability.</p><p>Chapters</p><p>00:00 The Journey of Fatherhood<br>03:16 Navigating Work-Life Balance<br>06:21 Milestones in Professional Growth<br>09:09 The Dynamics of Startups<br>12:11 Innovations in Health Tech<br>15:20 Vibe Coding and AI in Development<br>18:19 The Future of Software Development<br>21:11 Content Creation with AI<br>25:43 Navigating the AI Landscape<br>32:56 The Future of Learning in an AI World<br>37:26 Innovating Benefit Programs<br>49:06 Packaging Value in Health Benefits</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/3a491971/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lnolqktvai2z"/>
    </item>
    <item>
      <title>What do all these customers have in common?</title>
      <itunes:episode>180</itunes:episode>
      <podcast:episode>180</podcast:episode>
      <itunes:title>What do all these customers have in common?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0d780f96-9b28-441c-9d67-2c9313d4d86a</guid>
      <link>https://share.transistor.fm/s/0cdd8256</link>
      <description>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss various aspects of long-term product strategy at Less Annoying CRM, including personal updates, business growth, customer retention challenges, economic concerns, product development, and the importance of identifying ideal customer personas. They explore the balance between adding features and maintaining simplicity, as well as the need to adapt to changing market conditions.<br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss various aspects of long-term product strategy at Less Annoying CRM, including personal updates, business growth, customer retention challenges, economic concerns, product development, and the importance of identifying ideal customer personas. They explore the balance between adding features and maintaining simplicity, as well as the need to adapt to changing market conditions.<br></p>]]>
      </content:encoded>
      <pubDate>Thu, 10 Apr 2025 10:29:08 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/0cdd8256/7ae15667.mp3" length="26751420" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3342</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss various aspects of long-term product strategy at Less Annoying CRM, including personal updates, business growth, customer retention challenges, economic concerns, product development, and the importance of identifying ideal customer personas. They explore the balance between adding features and maintaining simplicity, as well as the need to adapt to changing market conditions.<br></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/0cdd8256/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lmhszpuoy626"/>
    </item>
    <item>
      <title>Dipping a toe in the AI waters</title>
      <itunes:episode>179</itunes:episode>
      <podcast:episode>179</podcast:episode>
      <itunes:title>Dipping a toe in the AI waters</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">2877f26d-d9ed-4f48-ac65-13b02e0838f5</guid>
      <link>https://share.transistor.fm/s/681baf93</link>
      <description>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss the challenges and triumphs of managing projects within SaaS companies, particularly focusing on the effective use of AI, sales pipeline dynamics, and the balance between calm and chaos in business operations. They explore the importance of setting realistic goals, the role of automation in enhancing user experience, and the impact of parental leave on work dynamics. The discussion emphasizes the need for focused opportunities in sales and the potential of AI to streamline processes and improve customer service.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss the challenges and triumphs of managing projects within SaaS companies, particularly focusing on the effective use of AI, sales pipeline dynamics, and the balance between calm and chaos in business operations. They explore the importance of setting realistic goals, the role of automation in enhancing user experience, and the impact of parental leave on work dynamics. The discussion emphasizes the need for focused opportunities in sales and the potential of AI to streamline processes and improve customer service.</p>]]>
      </content:encoded>
      <pubDate>Thu, 27 Mar 2025 13:28:13 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/681baf93/350ab675.mp3" length="52478073" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3279</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this conversation, Tyler and Rick discuss the challenges and triumphs of managing projects within SaaS companies, particularly focusing on the effective use of AI, sales pipeline dynamics, and the balance between calm and chaos in business operations. They explore the importance of setting realistic goals, the role of automation in enhancing user experience, and the impact of parental leave on work dynamics. The discussion emphasizes the need for focused opportunities in sales and the potential of AI to streamline processes and improve customer service.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/681baf93/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3llewj2gw6h24"/>
    </item>
    <item>
      <title>Consultative sales</title>
      <itunes:episode>178</itunes:episode>
      <podcast:episode>178</podcast:episode>
      <itunes:title>Consultative sales</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0d9be81c-0876-4153-a5e0-ccde3e51709f</guid>
      <link>https://share.transistor.fm/s/bfdf382f</link>
      <description>
        <![CDATA[<p>In this episode, Tyler and Rick discuss various sales best practices, focusing on the importance of maintaining a clean sales pipeline, optimizing CRM usage, and enhancing marketing strategies. They delve into the challenges of customer service and the need for a consultative approach to selling, emphasizing the value of understanding customer needs and providing tailored solutions. The conversation also touches on the updates to their form builder and the strategies being implemented to increase user engagement and satisfaction.<br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Tyler and Rick discuss various sales best practices, focusing on the importance of maintaining a clean sales pipeline, optimizing CRM usage, and enhancing marketing strategies. They delve into the challenges of customer service and the need for a consultative approach to selling, emphasizing the value of understanding customer needs and providing tailored solutions. The conversation also touches on the updates to their form builder and the strategies being implemented to increase user engagement and satisfaction.<br></p>]]>
      </content:encoded>
      <pubDate>Thu, 13 Mar 2025 10:38:05 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/bfdf382f/5f093a33.mp3" length="49699050" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3105</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, Tyler and Rick discuss various sales best practices, focusing on the importance of maintaining a clean sales pipeline, optimizing CRM usage, and enhancing marketing strategies. They delve into the challenges of customer service and the need for a consultative approach to selling, emphasizing the value of understanding customer needs and providing tailored solutions. The conversation also touches on the updates to their form builder and the strategies being implemented to increase user engagement and satisfaction.<br></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/bfdf382f/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lkbghwz6ap24"/>
    </item>
    <item>
      <title>Lowering the bar</title>
      <itunes:episode>177</itunes:episode>
      <podcast:episode>177</podcast:episode>
      <itunes:title>Lowering the bar</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c08b4d1a-d85b-4d8b-8288-107a6622779a</guid>
      <link>https://share.transistor.fm/s/e618103b</link>
      <description>
        <![CDATA[<p>In this episode, we talk about how Rick has given himself some breathing room, and how that’s impacted his outlook on the business. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about how Rick has given himself some breathing room, and how that’s impacted his outlook on the business. </p>]]>
      </content:encoded>
      <pubDate>Thu, 20 Feb 2025 15:17:51 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e618103b/6c61e719.mp3" length="48818391" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2861</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about how Rick has given himself some breathing room, and how that’s impacted his outlook on the business. </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/e618103b/transcript.txt" type="text/plain"/>
      <podcast:socialInteract protocol="atproto" uri="at://did:plc:ozdpvolslhf5lh4575mqzhv4/app.bsky.feed.post/3lin7o5v4qs2u"/>
    </item>
    <item>
      <title>Line go up</title>
      <itunes:episode>176</itunes:episode>
      <podcast:episode>176</podcast:episode>
      <itunes:title>Line go up</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0878b44d-2242-4054-a259-8b59f2b28387</guid>
      <link>https://share.transistor.fm/s/5145aced</link>
      <description>
        <![CDATA[<p>In this episode, we talk about some metrics that are headed in the right direction. Let’s go</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about some metrics that are headed in the right direction. Let’s go</p>]]>
      </content:encoded>
      <pubDate>Thu, 16 Jan 2025 10:25:36 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/5145aced/c6b49b91.mp3" length="45885225" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2680</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about some metrics that are headed in the right direction. Let’s go</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Rating growth channels</title>
      <itunes:episode>175</itunes:episode>
      <podcast:episode>175</podcast:episode>
      <itunes:title>Rating growth channels</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0c9e4f62-3bfb-44fa-8f53-38943e25059b</guid>
      <link>https://share.transistor.fm/s/de718f50</link>
      <description>
        <![CDATA[<p>In this episode, we try to prioritize some of the different growth channels Rick is considering for 2025.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we try to prioritize some of the different growth channels Rick is considering for 2025.</p>]]>
      </content:encoded>
      <pubDate>Thu, 02 Jan 2025 12:47:55 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/de718f50/1b998681.mp3" length="50997237" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2909</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we try to prioritize some of the different growth channels Rick is considering for 2025.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/de718f50/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>2024 Recap</title>
      <itunes:episode>174</itunes:episode>
      <podcast:episode>174</podcast:episode>
      <itunes:title>2024 Recap</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">72189576-c97f-475e-8574-0253b067ef13</guid>
      <link>https://share.transistor.fm/s/2524829f</link>
      <description>
        <![CDATA[<p>In this episode, we recap 2024 and set goals for 2025:</p><p><strong>Personal goals for 2025:</strong></p><ul><li>Rick: Primary theme: Buy back time<ul><li>Take 1 personal day every 1-2 months</li><li>Get time back for things I love (skiing, basketball, be present on vacations, reading/writing, local networking)</li><li>Have a familiy vacation on the calendar to look forward to at all times</li></ul></li><li>Tyler<ul><li>Baby stuff<ul><li>Remain flexible and do whatever needs to be done</li><li>Create space for Shelly to have a life outside of just parenting</li><li>Take advantage of the calm life I've built</li></ul></li><li>Don't hold myself to all my pre-baby health goals, but don't totally give them up either</li></ul></li></ul><p><strong>Professional goals for 2025:</strong></p><ul><li>Rick<ul><li>Legup Health: I don't know yet, but most likely...<ul><li>2x revenue (maybe less)</li><li>Make sure JD's role is sustainable</li><li>Make sure the business is properly financed</li></ul></li><li>Windfall: Scale myself. Level up, and make sure the team levels up with me</li></ul></li><li>Tyler<ul><li>Don't worry about growth. Focus on input, not output.</li><li>Product<ul><li>Tie off the big 2024 projects</li><li>Definitely ship kanban and a mobile app</li><li>Stretch goal: Ship one other big thing (sending email, automations, or reports)</li></ul></li><li>Reduce the set of things I'm responsible for so I can focus on the things I'm best at</li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we recap 2024 and set goals for 2025:</p><p><strong>Personal goals for 2025:</strong></p><ul><li>Rick: Primary theme: Buy back time<ul><li>Take 1 personal day every 1-2 months</li><li>Get time back for things I love (skiing, basketball, be present on vacations, reading/writing, local networking)</li><li>Have a familiy vacation on the calendar to look forward to at all times</li></ul></li><li>Tyler<ul><li>Baby stuff<ul><li>Remain flexible and do whatever needs to be done</li><li>Create space for Shelly to have a life outside of just parenting</li><li>Take advantage of the calm life I've built</li></ul></li><li>Don't hold myself to all my pre-baby health goals, but don't totally give them up either</li></ul></li></ul><p><strong>Professional goals for 2025:</strong></p><ul><li>Rick<ul><li>Legup Health: I don't know yet, but most likely...<ul><li>2x revenue (maybe less)</li><li>Make sure JD's role is sustainable</li><li>Make sure the business is properly financed</li></ul></li><li>Windfall: Scale myself. Level up, and make sure the team levels up with me</li></ul></li><li>Tyler<ul><li>Don't worry about growth. Focus on input, not output.</li><li>Product<ul><li>Tie off the big 2024 projects</li><li>Definitely ship kanban and a mobile app</li><li>Stretch goal: Ship one other big thing (sending email, automations, or reports)</li></ul></li><li>Reduce the set of things I'm responsible for so I can focus on the things I'm best at</li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 19 Dec 2024 10:44:58 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/2524829f/4ce50a46.mp3" length="74296601" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4286</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we recap 2024 and set goals for 2025:</p><p><strong>Personal goals for 2025:</strong></p><ul><li>Rick: Primary theme: Buy back time<ul><li>Take 1 personal day every 1-2 months</li><li>Get time back for things I love (skiing, basketball, be present on vacations, reading/writing, local networking)</li><li>Have a familiy vacation on the calendar to look forward to at all times</li></ul></li><li>Tyler<ul><li>Baby stuff<ul><li>Remain flexible and do whatever needs to be done</li><li>Create space for Shelly to have a life outside of just parenting</li><li>Take advantage of the calm life I've built</li></ul></li><li>Don't hold myself to all my pre-baby health goals, but don't totally give them up either</li></ul></li></ul><p><strong>Professional goals for 2025:</strong></p><ul><li>Rick<ul><li>Legup Health: I don't know yet, but most likely...<ul><li>2x revenue (maybe less)</li><li>Make sure JD's role is sustainable</li><li>Make sure the business is properly financed</li></ul></li><li>Windfall: Scale myself. Level up, and make sure the team levels up with me</li></ul></li><li>Tyler<ul><li>Don't worry about growth. Focus on input, not output.</li><li>Product<ul><li>Tie off the big 2024 projects</li><li>Definitely ship kanban and a mobile app</li><li>Stretch goal: Ship one other big thing (sending email, automations, or reports)</li></ul></li><li>Reduce the set of things I'm responsible for so I can focus on the things I'm best at</li></ul></li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/2524829f/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Different types of hiring</title>
      <itunes:episode>173</itunes:episode>
      <podcast:episode>173</podcast:episode>
      <itunes:title>Different types of hiring</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">1afedbf9-e8ef-42de-b458-3873486f3790</guid>
      <link>https://share.transistor.fm/s/fd7ed733</link>
      <description>
        <![CDATA[<p>In this episode, we discuss how there are multiple different approaches to take when a startup needs to grow the team.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss how there are multiple different approaches to take when a startup needs to grow the team.</p>]]>
      </content:encoded>
      <pubDate>Thu, 05 Dec 2024 10:16:41 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/fd7ed733/6a101eb5.mp3" length="53675096" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3111</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss how there are multiple different approaches to take when a startup needs to grow the team.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/fd7ed733/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Bluesky is back</title>
      <itunes:episode>172</itunes:episode>
      <podcast:episode>172</podcast:episode>
      <itunes:title>Bluesky is back</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5b8cd0cd-0993-4b3d-91ed-8b3315a39078</guid>
      <link>https://share.transistor.fm/s/4ba5fad6</link>
      <description>
        <![CDATA[<p>In this episode, we discuss Bluesky as the new Twitter, how Rick’s busiest time of year is surprisingly calm, and more.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss Bluesky as the new Twitter, how Rick’s busiest time of year is surprisingly calm, and more.</p>]]>
      </content:encoded>
      <pubDate>Thu, 21 Nov 2024 10:08:55 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/4ba5fad6/24b057d9.mp3" length="48525259" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2829</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss Bluesky as the new Twitter, how Rick’s busiest time of year is surprisingly calm, and more.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/4ba5fad6/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How we know if a feature is ambitious enough</title>
      <itunes:episode>171</itunes:episode>
      <podcast:episode>171</podcast:episode>
      <itunes:title>How we know if a feature is ambitious enough</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">bc6ef7e4-6f59-43dc-a0fb-4840a8b29887</guid>
      <link>https://share.transistor.fm/s/7019e4d0</link>
      <description>
        <![CDATA[<p>Less Annoying CRM is working on some big features, and in this episode, we discuss what we’re learning as a result.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Less Annoying CRM is working on some big features, and in this episode, we discuss what we’re learning as a result.</p>]]>
      </content:encoded>
      <pubDate>Thu, 07 Nov 2024 10:14:02 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7019e4d0/760fe60b.mp3" length="48135859" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2809</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Less Annoying CRM is working on some big features, and in this episode, we discuss what we’re learning as a result.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/7019e4d0/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Everybody’s marketing</title>
      <itunes:episode>170</itunes:episode>
      <podcast:episode>170</podcast:episode>
      <itunes:title>Everybody’s marketing</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ad2c1d36-7b4a-4b34-a29a-981556000287</guid>
      <link>https://share.transistor.fm/s/61caafbb</link>
      <description>
        <![CDATA[<p>We’re both in marketing mode right now. In this episode, we dive into the specifics of what we’re trying.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>We’re both in marketing mode right now. In this episode, we dive into the specifics of what we’re trying.</p>]]>
      </content:encoded>
      <pubDate>Thu, 10 Oct 2024 10:13:05 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/61caafbb/333fa4e2.mp3" length="53745579" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3222</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>We’re both in marketing mode right now. In this episode, we dive into the specifics of what we’re trying.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/61caafbb/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How’s 2024 going</title>
      <itunes:episode>169</itunes:episode>
      <podcast:episode>169</podcast:episode>
      <itunes:title>How’s 2024 going</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">cc2f5604-ee31-4803-9127-dd092402a94a</guid>
      <link>https://share.transistor.fm/s/5395a9dd</link>
      <description>
        <![CDATA[<p>In this episode, we review our yearly goals, talk about some new AI tools we’re trying out, and more.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we review our yearly goals, talk about some new AI tools we’re trying out, and more.</p>]]>
      </content:encoded>
      <pubDate>Thu, 26 Sep 2024 10:12:29 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/5395a9dd/289d2187.mp3" length="55984769" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3324</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we review our yearly goals, talk about some new AI tools we’re trying out, and more.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/5395a9dd/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How AI might impact customer service</title>
      <itunes:episode>168</itunes:episode>
      <podcast:episode>168</podcast:episode>
      <itunes:title>How AI might impact customer service</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">a38a552b-46ac-4dc0-bc94-57eaa9d3751c</guid>
      <link>https://share.transistor.fm/s/56364475</link>
      <description>
        <![CDATA[<p>In this episode, we talk about how we’re thinking about customer service in a world of AI*, and we do a deep dive into a customer interview Rick did recently.</p><p>*Clickbait warning: We don't actually spend much time on this topic, I just wanted a catchy title for the episode. Did it work? Did you listen because of my misleading title? Let me know in the comments**</p><p>**There are no comments. This is a podcast.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about how we’re thinking about customer service in a world of AI*, and we do a deep dive into a customer interview Rick did recently.</p><p>*Clickbait warning: We don't actually spend much time on this topic, I just wanted a catchy title for the episode. Did it work? Did you listen because of my misleading title? Let me know in the comments**</p><p>**There are no comments. This is a podcast.</p>]]>
      </content:encoded>
      <pubDate>Thu, 29 Aug 2024 10:14:19 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/56364475/f131a394.mp3" length="53107739" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3025</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about how we’re thinking about customer service in a world of AI*, and we do a deep dive into a customer interview Rick did recently.</p><p>*Clickbait warning: We don't actually spend much time on this topic, I just wanted a catchy title for the episode. Did it work? Did you listen because of my misleading title? Let me know in the comments**</p><p>**There are no comments. This is a podcast.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/56364475/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>The internet isn’t fun anymore</title>
      <itunes:episode>167</itunes:episode>
      <podcast:episode>167</podcast:episode>
      <itunes:title>The internet isn’t fun anymore</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">4cb784b2-4da3-4825-ad38-d84bc46bc1d7</guid>
      <link>https://share.transistor.fm/s/06c5310d</link>
      <description>
        <![CDATA[<p>In this episode, we talk about the value of a podcast community, and generally how we’re trying to protect ourselves from the internet.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about the value of a podcast community, and generally how we’re trying to protect ourselves from the internet.</p>]]>
      </content:encoded>
      <pubDate>Thu, 15 Aug 2024 13:09:28 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/06c5310d/14287661.mp3" length="51533797" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2941</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about the value of a podcast community, and generally how we’re trying to protect ourselves from the internet.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/06c5310d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How to raise revenue by 20% in one day</title>
      <itunes:episode>166</itunes:episode>
      <podcast:episode>166</podcast:episode>
      <itunes:title>How to raise revenue by 20% in one day</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">4a6c61de-ff12-4c9d-a310-ca8f9e58a607</guid>
      <link>https://share.transistor.fm/s/e2fa8e9a</link>
      <description>
        <![CDATA[<p>In this episode, we talk about about the impact a recent price change is having on Less Annoying CRM’s finances. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about about the impact a recent price change is having on Less Annoying CRM’s finances. </p>]]>
      </content:encoded>
      <pubDate>Thu, 01 Aug 2024 10:20:11 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e2fa8e9a/abd685b8.mp3" length="44126930" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2757</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about about the impact a recent price change is having on Less Annoying CRM’s finances. </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/e2fa8e9a/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Small bets vs going deep</title>
      <itunes:episode>165</itunes:episode>
      <podcast:episode>165</podcast:episode>
      <itunes:title>Small bets vs going deep</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e88c2d31-1125-4545-b14d-16083958bb8e</guid>
      <link>https://share.transistor.fm/s/dc035bd8</link>
      <description>
        <![CDATA[<p>The internet loves to talk about whether to focus on a single business or build a portfolio of small bets. I’m sure you’re sick of hearing about it. But in this episode, we have a twist on that topic. For an established business thinking about launching complimentary products, is it better to build one great one, or a series of only ok ones. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>The internet loves to talk about whether to focus on a single business or build a portfolio of small bets. I’m sure you’re sick of hearing about it. But in this episode, we have a twist on that topic. For an established business thinking about launching complimentary products, is it better to build one great one, or a series of only ok ones. </p>]]>
      </content:encoded>
      <pubDate>Fri, 05 Jul 2024 10:34:15 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/dc035bd8/f1e56bac.mp3" length="44779640" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2603</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>The internet loves to talk about whether to focus on a single business or build a portfolio of small bets. I’m sure you’re sick of hearing about it. But in this episode, we have a twist on that topic. For an established business thinking about launching complimentary products, is it better to build one great one, or a series of only ok ones. </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/dc035bd8/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Pick one thing and max it out</title>
      <itunes:episode>164</itunes:episode>
      <podcast:episode>164</podcast:episode>
      <itunes:title>Pick one thing and max it out</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">2855afa0-278f-483e-870a-867175a543c1</guid>
      <link>https://share.transistor.fm/s/931f37b3</link>
      <description>
        <![CDATA[<p> In this episode, we talk about how the job of an entrepreneur isn’t to decide which ideas are good and which are bad. It’s to pick the single best idea out of a sea of good ideas. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, we talk about how the job of an entrepreneur isn’t to decide which ideas are good and which are bad. It’s to pick the single best idea out of a sea of good ideas. </p>]]>
      </content:encoded>
      <pubDate>Tue, 25 Jun 2024 18:58:09 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/931f37b3/5a4e514c.mp3" length="46008661" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2819</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, we talk about how the job of an entrepreneur isn’t to decide which ideas are good and which are bad. It’s to pick the single best idea out of a sea of good ideas. </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/931f37b3/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Step on the gas, or pull back?</title>
      <itunes:episode>163</itunes:episode>
      <podcast:episode>163</podcast:episode>
      <itunes:title>Step on the gas, or pull back?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f288051e-c9ce-44e3-ae0a-bddd8f2e02e3</guid>
      <link>https://share.transistor.fm/s/bedc470b</link>
      <description>
        <![CDATA[<p>In this episode, we talk about a decision Rick needs to make with LegUp Health. Should he treat it like a high-growth startup, or a lifestyle business? </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about a decision Rick needs to make with LegUp Health. Should he treat it like a high-growth startup, or a lifestyle business? </p>]]>
      </content:encoded>
      <pubDate>Thu, 06 Jun 2024 15:45:11 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/bedc470b/edff8a45.mp3" length="51682366" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3075</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about a decision Rick needs to make with LegUp Health. Should he treat it like a high-growth startup, or a lifestyle business? </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/bedc470b/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>We ain't talking about zero to one</title>
      <itunes:episode>162</itunes:episode>
      <podcast:episode>162</podcast:episode>
      <itunes:title>We ain't talking about zero to one</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">1305593c-1440-4c03-958b-d9d1a7b7b750</guid>
      <link>https://share.transistor.fm/s/e5f86393</link>
      <description>
        <![CDATA[<p>In this episode, we talk about how a lot of startup advice is focused on businesses going from zero to one, and how we have to be careful not to assume that all applies to us.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about how a lot of startup advice is focused on businesses going from zero to one, and how we have to be careful not to assume that all applies to us.</p>]]>
      </content:encoded>
      <pubDate>Thu, 16 May 2024 16:53:53 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e5f86393/04afb03f.mp3" length="52882514" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3149</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about how a lot of startup advice is focused on businesses going from zero to one, and how we have to be careful not to assume that all applies to us.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/e5f86393/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Forms forms forms</title>
      <itunes:episode>161</itunes:episode>
      <podcast:episode>161</podcast:episode>
      <itunes:title>Forms forms forms</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">bb4da5e0-1bf7-4de1-b007-e2018ae1df0b</guid>
      <link>https://share.transistor.fm/s/9dfe8f8e</link>
      <description>
        <![CDATA[<p> In this episode, we talk about Less Annoying CRM’s new form builder, and what it means for the business </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, we talk about Less Annoying CRM’s new form builder, and what it means for the business </p>]]>
      </content:encoded>
      <pubDate>Thu, 09 May 2024 12:07:04 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/9dfe8f8e/6a013003.mp3" length="49439673" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2941</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, we talk about Less Annoying CRM’s new form builder, and what it means for the business </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/9dfe8f8e/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Leveling up the team</title>
      <itunes:episode>160</itunes:episode>
      <podcast:episode>160</podcast:episode>
      <itunes:title>Leveling up the team</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f94047c5-7b81-4552-9f54-6dec2ad00a0c</guid>
      <link>https://share.transistor.fm/s/36e97df3</link>
      <description>
        <![CDATA[<p>In this episode, we discuss using consultants to level up your team.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss using consultants to level up your team.</p>]]>
      </content:encoded>
      <pubDate>Thu, 25 Apr 2024 18:38:57 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/36e97df3/5b9eb576.mp3" length="41027508" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2448</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss using consultants to level up your team.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/36e97df3/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>The first step of a flywheel</title>
      <itunes:episode>159</itunes:episode>
      <podcast:episode>159</podcast:episode>
      <itunes:title>The first step of a flywheel</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">9d3bb53c-198b-42dd-ad25-547048d915ad</guid>
      <link>https://share.transistor.fm/s/7794fdad</link>
      <description>
        <![CDATA[<p> In this episode, Rick explains how he’s getting more hands on with marketing. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, Rick explains how he’s getting more hands on with marketing. </p>]]>
      </content:encoded>
      <pubDate>Thu, 11 Apr 2024 12:47:04 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7794fdad/73fb2187.mp3" length="56439692" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3278</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, Rick explains how he’s getting more hands on with marketing. </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/7794fdad/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Sometimes you need to touch the hot stove</title>
      <itunes:episode>158</itunes:episode>
      <podcast:episode>158</podcast:episode>
      <itunes:title>Sometimes you need to touch the hot stove</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">88eb99f3-dec1-4bdb-8d41-336f7c597899</guid>
      <link>https://share.transistor.fm/s/79e2d1c2</link>
      <description>
        <![CDATA[<p>In this episode, we discuss how some lessons can't be taught, they have to be learned through experience. What does that mean for mentoring less experienced employees?</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss how some lessons can't be taught, they have to be learned through experience. What does that mean for mentoring less experienced employees?</p>]]>
      </content:encoded>
      <pubDate>Thu, 28 Mar 2024 16:28:21 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/79e2d1c2/44d501a3.mp3" length="52158564" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3146</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss how some lessons can't be taught, they have to be learned through experience. What does that mean for mentoring less experienced employees?</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/79e2d1c2/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>When to outsource</title>
      <itunes:episode>157</itunes:episode>
      <podcast:episode>157</podcast:episode>
      <itunes:title>When to outsource</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">faa6ef58-7cb1-4150-98c1-b440fc588fd0</guid>
      <link>https://share.transistor.fm/s/02e03c3d</link>
      <description>
        <![CDATA[<p> In this episode, we talk about when it makes sense to outsource work to contractors and agencies, vs when it makes sense to do something in-house.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, we talk about when it makes sense to outsource work to contractors and agencies, vs when it makes sense to do something in-house.</p>]]>
      </content:encoded>
      <pubDate>Thu, 29 Feb 2024 12:33:36 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/02e03c3d/728585d7.mp3" length="50703084" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2948</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, we talk about when it makes sense to outsource work to contractors and agencies, vs when it makes sense to do something in-house.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/02e03c3d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Talk to sales</title>
      <itunes:episode>156</itunes:episode>
      <podcast:episode>156</podcast:episode>
      <itunes:title>Talk to sales</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">567b9bdc-5f42-4640-a038-b131ba4de01a</guid>
      <link>https://share.transistor.fm/s/62410f72</link>
      <description>
        <![CDATA[<p> In this episode, we talk about Less Annoying CRM’s latest sales experiment. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, we talk about Less Annoying CRM’s latest sales experiment. </p>]]>
      </content:encoded>
      <pubDate>Thu, 15 Feb 2024 15:20:28 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/62410f72/98a2ed59.mp3" length="40268936" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2373</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, we talk about Less Annoying CRM’s latest sales experiment. </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/62410f72/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Learnings from a few days of snowboarding</title>
      <itunes:episode>155</itunes:episode>
      <podcast:episode>155</podcast:episode>
      <itunes:title>Learnings from a few days of snowboarding</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">2d795acf-4708-45d6-a316-7b72b1d3c1dd</guid>
      <link>https://share.transistor.fm/s/b83f3558</link>
      <description>
        <![CDATA[<p>In this episode, we talk about takeaways from big snow tiny conf, and more.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about takeaways from big snow tiny conf, and more.</p>]]>
      </content:encoded>
      <pubDate>Thu, 01 Feb 2024 13:25:31 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/b83f3558/5507e12e.mp3" length="47119366" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2781</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about takeaways from big snow tiny conf, and more.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/b83f3558/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Profit first</title>
      <itunes:episode>154</itunes:episode>
      <podcast:episode>154</podcast:episode>
      <itunes:title>Profit first</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e2d7bd8a-c3f9-42db-8657-1daa51dffabb</guid>
      <link>https://share.transistor.fm/s/3fbe9743</link>
      <description>
        <![CDATA[<p>In this episode, we discuss how Rick is using the “profit first” mindset to manage company finances. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss how Rick is using the “profit first” mindset to manage company finances. </p>]]>
      </content:encoded>
      <pubDate>Thu, 18 Jan 2024 15:17:36 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/3fbe9743/9cdf9e53.mp3" length="49455055" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3005</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss how Rick is using the “profit first” mindset to manage company finances. </p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/3fbe9743/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Looking back at 2023 and forward to 2024</title>
      <itunes:episode>153</itunes:episode>
      <podcast:episode>153</podcast:episode>
      <itunes:title>Looking back at 2023 and forward to 2024</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">4bd3bd4e-5a63-4f32-8e55-05cf52364faf</guid>
      <link>https://share.transistor.fm/s/bc77d9e5</link>
      <description>
        <![CDATA[<p>This is our yearly recap episode!</p><p><strong>Personal updates from 2023</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>🆗 Take more vacation and make up with with extra work off-hours work</li><li>🆗 Renovate the house</li></ul></li><li>Other updates<ul><li>Found a band I like: Caligula's Horse</li><li>First time as an adult I feel good about my exercise routine</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>❌ Get weight below 200lbs</li><li>❌ Write a newsletter most Sundays (27 total)</li></ul></li><li>Other updates<ul><li>Built a new house and moved in</li><li>Had another baby (daughter)</li></ul></li></ul></li></ul><p><strong>Personal goals for 2024</strong></p><ul><li>Tyler<ul><li>Maintain exercise routine: 9k steps/day + 2 rucks/week + 200 pushups/week</li><li>Finish house remodel</li></ul></li><li>Rick<ul><li>Rebuild daily exercise and writing habit</li><li>Be more present with family when I’m with them</li><li>Regular dates with Sable (2 per month minimum)</li><li>4 vacations, with at least the next one scheduled at all times to look forward to</li></ul></li></ul><p><strong>Professional updates from 2023</strong></p><ul><li>Themes of the podcast<ul><li>You can't optimize nothing (mostly applies to Rick)</li><li>Back to the basics (mostly applies to Tyler)</li></ul></li><li>Tyler<ul><li>Goals from last year<ul><li>❌ Get back to decent growth: $36k ARR/ $3k MRR per month</li><li>✅ Sense of urgency on the dev team. No more 2-week projects that end up taking six months.</li><li>🆗 End the year with three major product wins</li></ul></li><li>Other updates<ul><li> Announced the price increase for legacy customers </li><li> ~3 new devs sort of. Dev team is feeling way better than ever before.</li><li> Improved money management </li><li>Coded a lot</li><li>Joined LegUp Health as a side project</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Retain JD full-time for another year</li><li>🆗 Double the client base again (~200 clients) - 160 clients</li><li>❌ Build V1 of LegUp Benefits and generate $1K per month in MRR from it (3-4 customers)</li></ul></li><li>Other updates<ul><li>Tyler joined LegUp Health as a partner</li><li> Expanded services to group health insurance, and started figuring that out</li><li> Made it to $100K annual revenue run rate + profitability in December</li></ul></li></ul></li></ul><p><strong>Professional goals for 2024</strong></p><ul><li>Tyler<ul><li>Don't worry about growth unless something unexpected happens</li><li>Focus on customer delight: If you ask a typical customer whether LACRM improved in 2024, their answer should be "hell yeah"</li><li>Maintain stability related to the team, culture, etc.</li><li>Protect coding time. Should be averaging &gt;1 full day of coding per week</li></ul></li><li>Rick<ul><li>Get LegUp Health to $200K ARR</li><li>Apply Profit First Framework / Pay partner distributions, even if small</li><li>Get JD to his target compensation</li><li>Prioritize better at Windfall / leverage over optimization</li></ul></li></ul><p><strong>Biggest worry</strong></p><ul><li>Tyler: Our execution on the product side won't be enough to close the gap with competitors</li><li>Rick:  I won’t figure out how to prioritize and manage my personal health as I build a family </li></ul><p><strong>What we want to learn</strong></p><ul><li>Tyler: How to code like it's 2024. Should be able to do everything the other LACRM devs can do with no blind spots</li><li>Rick: Nothing specific. 2024 is about execution</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This is our yearly recap episode!</p><p><strong>Personal updates from 2023</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>🆗 Take more vacation and make up with with extra work off-hours work</li><li>🆗 Renovate the house</li></ul></li><li>Other updates<ul><li>Found a band I like: Caligula's Horse</li><li>First time as an adult I feel good about my exercise routine</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>❌ Get weight below 200lbs</li><li>❌ Write a newsletter most Sundays (27 total)</li></ul></li><li>Other updates<ul><li>Built a new house and moved in</li><li>Had another baby (daughter)</li></ul></li></ul></li></ul><p><strong>Personal goals for 2024</strong></p><ul><li>Tyler<ul><li>Maintain exercise routine: 9k steps/day + 2 rucks/week + 200 pushups/week</li><li>Finish house remodel</li></ul></li><li>Rick<ul><li>Rebuild daily exercise and writing habit</li><li>Be more present with family when I’m with them</li><li>Regular dates with Sable (2 per month minimum)</li><li>4 vacations, with at least the next one scheduled at all times to look forward to</li></ul></li></ul><p><strong>Professional updates from 2023</strong></p><ul><li>Themes of the podcast<ul><li>You can't optimize nothing (mostly applies to Rick)</li><li>Back to the basics (mostly applies to Tyler)</li></ul></li><li>Tyler<ul><li>Goals from last year<ul><li>❌ Get back to decent growth: $36k ARR/ $3k MRR per month</li><li>✅ Sense of urgency on the dev team. No more 2-week projects that end up taking six months.</li><li>🆗 End the year with three major product wins</li></ul></li><li>Other updates<ul><li> Announced the price increase for legacy customers </li><li> ~3 new devs sort of. Dev team is feeling way better than ever before.</li><li> Improved money management </li><li>Coded a lot</li><li>Joined LegUp Health as a side project</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Retain JD full-time for another year</li><li>🆗 Double the client base again (~200 clients) - 160 clients</li><li>❌ Build V1 of LegUp Benefits and generate $1K per month in MRR from it (3-4 customers)</li></ul></li><li>Other updates<ul><li>Tyler joined LegUp Health as a partner</li><li> Expanded services to group health insurance, and started figuring that out</li><li> Made it to $100K annual revenue run rate + profitability in December</li></ul></li></ul></li></ul><p><strong>Professional goals for 2024</strong></p><ul><li>Tyler<ul><li>Don't worry about growth unless something unexpected happens</li><li>Focus on customer delight: If you ask a typical customer whether LACRM improved in 2024, their answer should be "hell yeah"</li><li>Maintain stability related to the team, culture, etc.</li><li>Protect coding time. Should be averaging &gt;1 full day of coding per week</li></ul></li><li>Rick<ul><li>Get LegUp Health to $200K ARR</li><li>Apply Profit First Framework / Pay partner distributions, even if small</li><li>Get JD to his target compensation</li><li>Prioritize better at Windfall / leverage over optimization</li></ul></li></ul><p><strong>Biggest worry</strong></p><ul><li>Tyler: Our execution on the product side won't be enough to close the gap with competitors</li><li>Rick:  I won’t figure out how to prioritize and manage my personal health as I build a family </li></ul><p><strong>What we want to learn</strong></p><ul><li>Tyler: How to code like it's 2024. Should be able to do everything the other LACRM devs can do with no blind spots</li><li>Rick: Nothing specific. 2024 is about execution</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 28 Dec 2023 20:10:55 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/bc77d9e5/bb557f9d.mp3" length="85577387" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>5295</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>This is our yearly recap episode!</p><p><strong>Personal updates from 2023</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>🆗 Take more vacation and make up with with extra work off-hours work</li><li>🆗 Renovate the house</li></ul></li><li>Other updates<ul><li>Found a band I like: Caligula's Horse</li><li>First time as an adult I feel good about my exercise routine</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>❌ Get weight below 200lbs</li><li>❌ Write a newsletter most Sundays (27 total)</li></ul></li><li>Other updates<ul><li>Built a new house and moved in</li><li>Had another baby (daughter)</li></ul></li></ul></li></ul><p><strong>Personal goals for 2024</strong></p><ul><li>Tyler<ul><li>Maintain exercise routine: 9k steps/day + 2 rucks/week + 200 pushups/week</li><li>Finish house remodel</li></ul></li><li>Rick<ul><li>Rebuild daily exercise and writing habit</li><li>Be more present with family when I’m with them</li><li>Regular dates with Sable (2 per month minimum)</li><li>4 vacations, with at least the next one scheduled at all times to look forward to</li></ul></li></ul><p><strong>Professional updates from 2023</strong></p><ul><li>Themes of the podcast<ul><li>You can't optimize nothing (mostly applies to Rick)</li><li>Back to the basics (mostly applies to Tyler)</li></ul></li><li>Tyler<ul><li>Goals from last year<ul><li>❌ Get back to decent growth: $36k ARR/ $3k MRR per month</li><li>✅ Sense of urgency on the dev team. No more 2-week projects that end up taking six months.</li><li>🆗 End the year with three major product wins</li></ul></li><li>Other updates<ul><li> Announced the price increase for legacy customers </li><li> ~3 new devs sort of. Dev team is feeling way better than ever before.</li><li> Improved money management </li><li>Coded a lot</li><li>Joined LegUp Health as a side project</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Retain JD full-time for another year</li><li>🆗 Double the client base again (~200 clients) - 160 clients</li><li>❌ Build V1 of LegUp Benefits and generate $1K per month in MRR from it (3-4 customers)</li></ul></li><li>Other updates<ul><li>Tyler joined LegUp Health as a partner</li><li> Expanded services to group health insurance, and started figuring that out</li><li> Made it to $100K annual revenue run rate + profitability in December</li></ul></li></ul></li></ul><p><strong>Professional goals for 2024</strong></p><ul><li>Tyler<ul><li>Don't worry about growth unless something unexpected happens</li><li>Focus on customer delight: If you ask a typical customer whether LACRM improved in 2024, their answer should be "hell yeah"</li><li>Maintain stability related to the team, culture, etc.</li><li>Protect coding time. Should be averaging &gt;1 full day of coding per week</li></ul></li><li>Rick<ul><li>Get LegUp Health to $200K ARR</li><li>Apply Profit First Framework / Pay partner distributions, even if small</li><li>Get JD to his target compensation</li><li>Prioritize better at Windfall / leverage over optimization</li></ul></li></ul><p><strong>Biggest worry</strong></p><ul><li>Tyler: Our execution on the product side won't be enough to close the gap with competitors</li><li>Rick:  I won’t figure out how to prioritize and manage my personal health as I build a family </li></ul><p><strong>What we want to learn</strong></p><ul><li>Tyler: How to code like it's 2024. Should be able to do everything the other LACRM devs can do with no blind spots</li><li>Rick: Nothing specific. 2024 is about execution</li></ul><p><br></p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/bc77d9e5/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>DEI isn't dead</title>
      <itunes:episode>152</itunes:episode>
      <podcast:episode>152</podcast:episode>
      <itunes:title>DEI isn't dead</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">66f64bf0-b2cb-4530-ba2e-fc208cc67013</guid>
      <link>https://share.transistor.fm/s/56145aca</link>
      <description>
        <![CDATA[<p>In this episode, we talk about Rick's open enrollment experience, and what LACRM is doing related to DEI (diversity, equity, and inclusion)</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about Rick's open enrollment experience, and what LACRM is doing related to DEI (diversity, equity, and inclusion)</p>]]>
      </content:encoded>
      <pubDate>Fri, 15 Dec 2023 14:03:21 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/56145aca/94f7dac3.mp3" length="50044680" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3001</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about Rick's open enrollment experience, and what LACRM is doing related to DEI (diversity, equity, and inclusion)</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/56145aca/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Growth is hard</title>
      <itunes:episode>151</itunes:episode>
      <podcast:episode>151</podcast:episode>
      <itunes:title>Growth is hard</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d0ec887c-37b4-4d7e-934c-779542600bf2</guid>
      <link>https://share.transistor.fm/s/7e67f1ee</link>
      <description>
        <![CDATA[<p> In this episode, Rick tries to explain to me that there are people who know how to grow businesses, and I stubbornly insist otherwise.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, Rick tries to explain to me that there are people who know how to grow businesses, and I stubbornly insist otherwise.</p>]]>
      </content:encoded>
      <pubDate>Thu, 30 Nov 2023 19:24:16 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7e67f1ee/9a3abb90.mp3" length="56316429" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3468</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, Rick tries to explain to me that there are people who know how to grow businesses, and I stubbornly insist otherwise.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/7e67f1ee/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Inflection point</title>
      <itunes:episode>150</itunes:episode>
      <podcast:episode>150</podcast:episode>
      <itunes:title>Inflection point</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">dc870486-8803-4c83-93db-0396c5352569</guid>
      <link>https://share.transistor.fm/s/284bd62b</link>
      <description>
        <![CDATA[<p>In this episode, we discuss what feels like an inflection point in Rick's business.</p><p>Full topic list:</p><ul><li>LegUp Health has a new website.</li><li>Rick thinks he's feeling an inflection point.</li><li>We daydream about the future of LegUp Health a bit.</li><li>Things are calm at LACRM, and the employees are all increasingly experienced.</li><li>Tyler is coding again.</li><li>There's a new buzzword at LACRM.</li><li>We complain about X/Twitter.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss what feels like an inflection point in Rick's business.</p><p>Full topic list:</p><ul><li>LegUp Health has a new website.</li><li>Rick thinks he's feeling an inflection point.</li><li>We daydream about the future of LegUp Health a bit.</li><li>Things are calm at LACRM, and the employees are all increasingly experienced.</li><li>Tyler is coding again.</li><li>There's a new buzzword at LACRM.</li><li>We complain about X/Twitter.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 09 Nov 2023 16:35:55 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/284bd62b/cae90f7c.mp3" length="49088351" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3106</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss what feels like an inflection point in Rick's business.</p><p>Full topic list:</p><ul><li>LegUp Health has a new website.</li><li>Rick thinks he's feeling an inflection point.</li><li>We daydream about the future of LegUp Health a bit.</li><li>Things are calm at LACRM, and the employees are all increasingly experienced.</li><li>Tyler is coding again.</li><li>There's a new buzzword at LACRM.</li><li>We complain about X/Twitter.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/284bd62b/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Reducing Friction</title>
      <itunes:episode>149</itunes:episode>
      <podcast:episode>149</podcast:episode>
      <itunes:title>Reducing Friction</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">44924c7e-87cb-4672-a6d4-10f2d55232aa</guid>
      <link>https://share.transistor.fm/s/16db174d</link>
      <description>
        <![CDATA[<p>This week, we discuss how LegUp Health reduced a major point of friction when selling to employers.</p><p>Here's the full topic list:</p><ul><li>Rick is finally in his new house, and a major stress has been removed.</li><li>Rick gives updates on LegUp Health, including a major unlock to getting employers onboard.</li><li>Rick talks about progress towards hitting annual sales goals.</li><li>Tyler talks about other ways he's been able to simplify LACRM's operations.</li><li>Tyler has a coughing fit and we give up early.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This week, we discuss how LegUp Health reduced a major point of friction when selling to employers.</p><p>Here's the full topic list:</p><ul><li>Rick is finally in his new house, and a major stress has been removed.</li><li>Rick gives updates on LegUp Health, including a major unlock to getting employers onboard.</li><li>Rick talks about progress towards hitting annual sales goals.</li><li>Tyler talks about other ways he's been able to simplify LACRM's operations.</li><li>Tyler has a coughing fit and we give up early.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 26 Oct 2023 19:09:46 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/16db174d/8962aee9.mp3" length="33457898" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2056</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>This week, we discuss how LegUp Health reduced a major point of friction when selling to employers.</p><p>Here's the full topic list:</p><ul><li>Rick is finally in his new house, and a major stress has been removed.</li><li>Rick gives updates on LegUp Health, including a major unlock to getting employers onboard.</li><li>Rick talks about progress towards hitting annual sales goals.</li><li>Tyler talks about other ways he's been able to simplify LACRM's operations.</li><li>Tyler has a coughing fit and we give up early.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/16db174d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Build it and they will come</title>
      <itunes:episode>148</itunes:episode>
      <podcast:episode>148</podcast:episode>
      <itunes:title>Build it and they will come</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">64d8c62c-7048-4f30-866d-0f37429097fe</guid>
      <link>https://share.transistor.fm/s/c06f9316</link>
      <description>
        <![CDATA[<p>In this episode, we discuss whether or not building features customers ask for is a valid path toward growth.</p><p>Here are all the topics:</p><ul><li>LACRM has started migrating to Paddle.</li><li>LegUp Benefits has its first official customer!</li><li>We discuss how LACRM's free trial pipeline isn't as correlated with paying user growth as you'd expect.</li><li>We dive deep into the history of LACRM's product strategy, and what comes next.</li><li>Rick has a major milestone to share.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss whether or not building features customers ask for is a valid path toward growth.</p><p>Here are all the topics:</p><ul><li>LACRM has started migrating to Paddle.</li><li>LegUp Benefits has its first official customer!</li><li>We discuss how LACRM's free trial pipeline isn't as correlated with paying user growth as you'd expect.</li><li>We dive deep into the history of LACRM's product strategy, and what comes next.</li><li>Rick has a major milestone to share.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 12 Oct 2023 19:49:49 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/c06f9316/952150d7.mp3" length="51812602" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3207</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss whether or not building features customers ask for is a valid path toward growth.</p><p>Here are all the topics:</p><ul><li>LACRM has started migrating to Paddle.</li><li>LegUp Benefits has its first official customer!</li><li>We discuss how LACRM's free trial pipeline isn't as correlated with paying user growth as you'd expect.</li><li>We dive deep into the history of LACRM's product strategy, and what comes next.</li><li>Rick has a major milestone to share.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/c06f9316/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>The pricing change I didn’t want to make</title>
      <itunes:episode>147</itunes:episode>
      <podcast:episode>147</podcast:episode>
      <itunes:title>The pricing change I didn’t want to make</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">122fe043-358a-4741-8b55-200dc058133a</guid>
      <link>https://share.transistor.fm/s/fb0f3eac</link>
      <description>
        <![CDATA[<p>This week, we talk about a pricing change we recently announced at Less Annoying CRM. We dive into the history behind the decision, how it was communicated, what it means for the finances of the business, and more.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This week, we talk about a pricing change we recently announced at Less Annoying CRM. We dive into the history behind the decision, how it was communicated, what it means for the finances of the business, and more.</p>]]>
      </content:encoded>
      <pubDate>Thu, 28 Sep 2023 14:22:02 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/fb0f3eac/6e5978cb.mp3" length="42630653" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2540</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>This week, we talk about a pricing change we recently announced at Less Annoying CRM. We dive into the history behind the decision, how it was communicated, what it means for the finances of the business, and more.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/fb0f3eac/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Reorg</title>
      <itunes:episode>146</itunes:episode>
      <podcast:episode>146</podcast:episode>
      <itunes:title>Reorg</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d19db3f0-b776-4864-8a9c-a51cf0f8a642</guid>
      <link>https://share.transistor.fm/s/3ec12e44</link>
      <description>
        <![CDATA[<p>In this episode, we discuss a hodgepodge of things including a company reorg, growth tactics, and more.</p><p>Here are all the topics:</p><ul><li>Rick updates us on LegUp Health's progress. He talks about working on the sales pitch, building momentum, staying focused, and more.</li><li>Tyler is merging two teams at LACRM. We discuss what the impact of that change might be.</li><li>We spend a while discussing different growth ideas, especially related to sales and outbound marketing.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss a hodgepodge of things including a company reorg, growth tactics, and more.</p><p>Here are all the topics:</p><ul><li>Rick updates us on LegUp Health's progress. He talks about working on the sales pitch, building momentum, staying focused, and more.</li><li>Tyler is merging two teams at LACRM. We discuss what the impact of that change might be.</li><li>We spend a while discussing different growth ideas, especially related to sales and outbound marketing.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 31 Aug 2023 17:45:53 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/3ec12e44/86398c84.mp3" length="42000130" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2557</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss a hodgepodge of things including a company reorg, growth tactics, and more.</p><p>Here are all the topics:</p><ul><li>Rick updates us on LegUp Health's progress. He talks about working on the sales pitch, building momentum, staying focused, and more.</li><li>Tyler is merging two teams at LACRM. We discuss what the impact of that change might be.</li><li>We spend a while discussing different growth ideas, especially related to sales and outbound marketing.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/3ec12e44/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Execution eats strategy for breakfast</title>
      <itunes:episode>145</itunes:episode>
      <podcast:episode>145</podcast:episode>
      <itunes:title>Execution eats strategy for breakfast</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ff67c1e1-ebb9-46d5-b23c-04570d60c330</guid>
      <link>https://share.transistor.fm/s/6012ef24</link>
      <description>
        <![CDATA[<p> In this episode, we talk about how both of us are refocusing on execution. Here's the full topic list:</p><ul><li>Tyler is trying to focus everyone at LACRM on the top priorities including:<ul><li>Having the devOps team do a bit more normal software engineering work.</li><li>Offering customer service people a chance to work on marketing and sales.</li><li>He himself is starting to code again.</li></ul></li><li>Rick explains how LegUp Health is focused on execution and it seems to be working.</li><li>Rick/JD hired a sales coach.</li><li>Rick talks about what he learned from the book Amp It Up.</li><li>Tyler poorly explains why LACRM is going to work on a feature that isn't the top priority.</li><li>We talk a bit about how to optimize a support team</li><li>Rick is starting to think about how he can contribute to marketing.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, we talk about how both of us are refocusing on execution. Here's the full topic list:</p><ul><li>Tyler is trying to focus everyone at LACRM on the top priorities including:<ul><li>Having the devOps team do a bit more normal software engineering work.</li><li>Offering customer service people a chance to work on marketing and sales.</li><li>He himself is starting to code again.</li></ul></li><li>Rick explains how LegUp Health is focused on execution and it seems to be working.</li><li>Rick/JD hired a sales coach.</li><li>Rick talks about what he learned from the book Amp It Up.</li><li>Tyler poorly explains why LACRM is going to work on a feature that isn't the top priority.</li><li>We talk a bit about how to optimize a support team</li><li>Rick is starting to think about how he can contribute to marketing.</li></ul>]]>
      </content:encoded>
      <pubDate>Mon, 14 Aug 2023 19:27:17 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/6012ef24/73b5dd69.mp3" length="49129081" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2933</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, we talk about how both of us are refocusing on execution. Here's the full topic list:</p><ul><li>Tyler is trying to focus everyone at LACRM on the top priorities including:<ul><li>Having the devOps team do a bit more normal software engineering work.</li><li>Offering customer service people a chance to work on marketing and sales.</li><li>He himself is starting to code again.</li></ul></li><li>Rick explains how LegUp Health is focused on execution and it seems to be working.</li><li>Rick/JD hired a sales coach.</li><li>Rick talks about what he learned from the book Amp It Up.</li><li>Tyler poorly explains why LACRM is going to work on a feature that isn't the top priority.</li><li>We talk a bit about how to optimize a support team</li><li>Rick is starting to think about how he can contribute to marketing.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/6012ef24/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Getting unstuck</title>
      <itunes:episode>144</itunes:episode>
      <podcast:episode>144</podcast:episode>
      <itunes:title>Getting unstuck</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">51f36266-c0e2-409f-b753-efa997d9e45c</guid>
      <link>https://share.transistor.fm/s/50512b46</link>
      <description>
        <![CDATA[<p>In this episode, we talk about Rick’s early signs of success getting out a sales rut, and much more.</p><p>Full topic list:</p><ul><li>Rick gives an update on how he and JD are getting out of a sales rut.</li><li>Rick is busy and has absolutely zero free time.</li><li>Tyler talks about how he's considering web forms and automations as possible features for LACRM.</li><li>We discuss an alternative approach to freemium.</li><li>We brainstorm how to use the "engineering as marketing" approach for LegUp Health, but don't really get anywhere.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about Rick’s early signs of success getting out a sales rut, and much more.</p><p>Full topic list:</p><ul><li>Rick gives an update on how he and JD are getting out of a sales rut.</li><li>Rick is busy and has absolutely zero free time.</li><li>Tyler talks about how he's considering web forms and automations as possible features for LACRM.</li><li>We discuss an alternative approach to freemium.</li><li>We brainstorm how to use the "engineering as marketing" approach for LegUp Health, but don't really get anywhere.</li></ul>]]>
      </content:encoded>
      <pubDate>Sun, 23 Jul 2023 15:34:17 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/50512b46/80e1d899.mp3" length="53415857" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3268</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about Rick’s early signs of success getting out a sales rut, and much more.</p><p>Full topic list:</p><ul><li>Rick gives an update on how he and JD are getting out of a sales rut.</li><li>Rick is busy and has absolutely zero free time.</li><li>Tyler talks about how he's considering web forms and automations as possible features for LACRM.</li><li>We discuss an alternative approach to freemium.</li><li>We brainstorm how to use the "engineering as marketing" approach for LegUp Health, but don't really get anywhere.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/50512b46/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>You can't optimize nothing</title>
      <itunes:episode>143</itunes:episode>
      <podcast:episode>143</podcast:episode>
      <itunes:title>You can't optimize nothing</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">371a2712-9f22-4c2b-9eb8-8776511b3578</guid>
      <link>https://share.transistor.fm/s/d08d2edc</link>
      <description>
        <![CDATA[<p>In this episode, we talk about how much optimization should be done before you have demand generation figured out.</p><p>Here's the full topic list:</p><ul><li>Rick is back from parental leave, and he has things to say about what it's like to take care of two kids at once.</li><li>We discuss what our perfect days look like.</li><li>Tyler talks about how LACRM had a bit of crunch mode, and how they stayed calm.</li><li>Rick talks about a sales slump, and what he's doing about it.</li><li>We talk about how LegUp Health migrated from no-code to full-code.</li><li>Tyler gives an update on LACRM's growth the first half of the year.</li><li>We talk about switching from Google Analytics to Fathom.</li><li>LACRM is considering how to price a feature that has some extra infrastructure costs.</li><li>Tyler is reconsidering a feature he's been talking about for years. Literally. Years.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about how much optimization should be done before you have demand generation figured out.</p><p>Here's the full topic list:</p><ul><li>Rick is back from parental leave, and he has things to say about what it's like to take care of two kids at once.</li><li>We discuss what our perfect days look like.</li><li>Tyler talks about how LACRM had a bit of crunch mode, and how they stayed calm.</li><li>Rick talks about a sales slump, and what he's doing about it.</li><li>We talk about how LegUp Health migrated from no-code to full-code.</li><li>Tyler gives an update on LACRM's growth the first half of the year.</li><li>We talk about switching from Google Analytics to Fathom.</li><li>LACRM is considering how to price a feature that has some extra infrastructure costs.</li><li>Tyler is reconsidering a feature he's been talking about for years. Literally. Years.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 06 Jul 2023 18:50:45 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/d08d2edc/b323815c.mp3" length="58393726" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3600</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about how much optimization should be done before you have demand generation figured out.</p><p>Here's the full topic list:</p><ul><li>Rick is back from parental leave, and he has things to say about what it's like to take care of two kids at once.</li><li>We discuss what our perfect days look like.</li><li>Tyler talks about how LACRM had a bit of crunch mode, and how they stayed calm.</li><li>Rick talks about a sales slump, and what he's doing about it.</li><li>We talk about how LegUp Health migrated from no-code to full-code.</li><li>Tyler gives an update on LACRM's growth the first half of the year.</li><li>We talk about switching from Google Analytics to Fathom.</li><li>LACRM is considering how to price a feature that has some extra infrastructure costs.</li><li>Tyler is reconsidering a feature he's been talking about for years. Literally. Years.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/d08d2edc/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Handling sales tax as a SaaS</title>
      <itunes:episode>142</itunes:episode>
      <podcast:episode>142</podcast:episode>
      <itunes:title>Handling sales tax as a SaaS</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ffc2abcf-39c7-4391-a416-9f4acea0de8c</guid>
      <link>https://share.transistor.fm/s/c0479761</link>
      <description>
        <![CDATA[<p>In this episode, we talk about what Less Annoying CRM is doing to handle sales tax compliance worldwide.</p><p>Here are all the topics:</p><ul><li>Tyler has officially signed the partnership agreement with Rick and LegUp Health!</li><li>Rick is wrapping up a position/brand/story project</li><li>LegUp Health has updated their mission and core values</li><li>Things are a bit hectic at LACRM</li><li>Tyler is considering merging his personal blog back into the LACRM blog</li><li>LACRM is probably switching from Stripe to Paddle</li><li>Rick shares what he's learned servicing the early LegUp Health group insurance clients</li><li>We talk a bit about ChatGPT and how it can be useful for no-code/low-code apps</li><li>Tyler rants about how we talk about priorities</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about what Less Annoying CRM is doing to handle sales tax compliance worldwide.</p><p>Here are all the topics:</p><ul><li>Tyler has officially signed the partnership agreement with Rick and LegUp Health!</li><li>Rick is wrapping up a position/brand/story project</li><li>LegUp Health has updated their mission and core values</li><li>Things are a bit hectic at LACRM</li><li>Tyler is considering merging his personal blog back into the LACRM blog</li><li>LACRM is probably switching from Stripe to Paddle</li><li>Rick shares what he's learned servicing the early LegUp Health group insurance clients</li><li>We talk a bit about ChatGPT and how it can be useful for no-code/low-code apps</li><li>Tyler rants about how we talk about priorities</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 08 Jun 2023 18:54:06 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/c0479761/7a9f6659.mp3" length="53792536" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3346</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about what Less Annoying CRM is doing to handle sales tax compliance worldwide.</p><p>Here are all the topics:</p><ul><li>Tyler has officially signed the partnership agreement with Rick and LegUp Health!</li><li>Rick is wrapping up a position/brand/story project</li><li>LegUp Health has updated their mission and core values</li><li>Things are a bit hectic at LACRM</li><li>Tyler is considering merging his personal blog back into the LACRM blog</li><li>LACRM is probably switching from Stripe to Paddle</li><li>Rick shares what he's learned servicing the early LegUp Health group insurance clients</li><li>We talk a bit about ChatGPT and how it can be useful for no-code/low-code apps</li><li>Tyler rants about how we talk about priorities</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/c0479761/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Recapping the Product Hunt launch</title>
      <itunes:episode>141</itunes:episode>
      <podcast:episode>141</podcast:episode>
      <itunes:title>Recapping the Product Hunt launch</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">7875f9f4-2bc6-4250-8b7c-016c289f4666</guid>
      <link>https://share.transistor.fm/s/f6dea528</link>
      <description>
        <![CDATA[<p>In this episode, we talk about Less Annoying CRM’s producthunt launch, and a lot more.</p><p>Here's the full topic list:</p><ul><li>Tyler takes a look back at LACRM's growth history, and explains their new approach to growth.</li><li>Tyler explains how the recent Product Hunt launch went.</li><li>Rick has cleared a lot off his LegUp Health plate and is starting to focus on new types of work.</li><li>LegUp Health had its first partner meeting.</li><li>April was a record month for LegUp Health.</li><li>LACRM has their designer back with more hours than ever.</li><li>Rick is looking to target CPAs as customers.</li><li>The LACRM coding fellows have started.</li><li>We discuss how to deal with the low points of being an entrepreneur.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about Less Annoying CRM’s producthunt launch, and a lot more.</p><p>Here's the full topic list:</p><ul><li>Tyler takes a look back at LACRM's growth history, and explains their new approach to growth.</li><li>Tyler explains how the recent Product Hunt launch went.</li><li>Rick has cleared a lot off his LegUp Health plate and is starting to focus on new types of work.</li><li>LegUp Health had its first partner meeting.</li><li>April was a record month for LegUp Health.</li><li>LACRM has their designer back with more hours than ever.</li><li>Rick is looking to target CPAs as customers.</li><li>The LACRM coding fellows have started.</li><li>We discuss how to deal with the low points of being an entrepreneur.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 25 May 2023 19:03:46 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f6dea528/6f5ed4c6.mp3" length="63994372" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3879</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about Less Annoying CRM’s producthunt launch, and a lot more.</p><p>Here's the full topic list:</p><ul><li>Tyler takes a look back at LACRM's growth history, and explains their new approach to growth.</li><li>Tyler explains how the recent Product Hunt launch went.</li><li>Rick has cleared a lot off his LegUp Health plate and is starting to focus on new types of work.</li><li>LegUp Health had its first partner meeting.</li><li>April was a record month for LegUp Health.</li><li>LACRM has their designer back with more hours than ever.</li><li>Rick is looking to target CPAs as customers.</li><li>The LACRM coding fellows have started.</li><li>We discuss how to deal with the low points of being an entrepreneur.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/f6dea528/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Pivots and renegotiations</title>
      <itunes:episode>140</itunes:episode>
      <podcast:episode>140</podcast:episode>
      <itunes:title>Pivots and renegotiations</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">7a4db952-5205-4633-948f-fd7c09e8f840</guid>
      <link>https://share.transistor.fm/s/676024fa</link>
      <description>
        <![CDATA[<p>In this episode, we discuss some changes to LegUp Health, the end of Tyler's sabbatical, and more.</p><p>Topics in this episode:</p><ul><li>Tyler is back from his sabbatical</li><li>LACRM is getting ready to launch a major redesign</li><li>Rick gives updates on how the LegUp Health/Benefits plan has changed</li><li>Because of the changes, we renegotiated Tyler's compensation and involvement in the company</li><li>Tyler talks about the difference building a product that customers don't expect to use regularly vs and every-day productivity tool.</li><li>Rick gives an update on working with a marketing coach</li><li>We talk about <a href="https://seeyafuture.me/">Seeyafuture.me</a></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss some changes to LegUp Health, the end of Tyler's sabbatical, and more.</p><p>Topics in this episode:</p><ul><li>Tyler is back from his sabbatical</li><li>LACRM is getting ready to launch a major redesign</li><li>Rick gives updates on how the LegUp Health/Benefits plan has changed</li><li>Because of the changes, we renegotiated Tyler's compensation and involvement in the company</li><li>Tyler talks about the difference building a product that customers don't expect to use regularly vs and every-day productivity tool.</li><li>Rick gives an update on working with a marketing coach</li><li>We talk about <a href="https://seeyafuture.me/">Seeyafuture.me</a></li></ul>]]>
      </content:encoded>
      <pubDate>Sun, 23 Apr 2023 11:06:34 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/676024fa/da75c746.mp3" length="63825818" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3868</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we discuss some changes to LegUp Health, the end of Tyler's sabbatical, and more.</p><p>Topics in this episode:</p><ul><li>Tyler is back from his sabbatical</li><li>LACRM is getting ready to launch a major redesign</li><li>Rick gives updates on how the LegUp Health/Benefits plan has changed</li><li>Because of the changes, we renegotiated Tyler's compensation and involvement in the company</li><li>Tyler talks about the difference building a product that customers don't expect to use regularly vs and every-day productivity tool.</li><li>Rick gives an update on working with a marketing coach</li><li>We talk about <a href="https://seeyafuture.me/">Seeyafuture.me</a></li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/676024fa/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Yet another podcast about AI</title>
      <itunes:episode>139</itunes:episode>
      <podcast:episode>139</podcast:episode>
      <itunes:title>Yet another podcast about AI</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">6e6e9364-3ab2-46c1-abbc-ce82940931c2</guid>
      <link>https://share.transistor.fm/s/f1f41f4d</link>
      <description>
        <![CDATA[<p>Come on, you know what we're talking about. It's all anyone is talking about. Sorry, we don't make the rules.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Come on, you know what we're talking about. It's all anyone is talking about. Sorry, we don't make the rules.</p>]]>
      </content:encoded>
      <pubDate>Mon, 03 Apr 2023 18:39:24 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f1f41f4d/619c882a.mp3" length="43395704" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2643</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Come on, you know what we're talking about. It's all anyone is talking about. Sorry, we don't make the rules.</p>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/f1f41f4d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>An inside look at building a new product</title>
      <itunes:episode>138</itunes:episode>
      <podcast:episode>138</podcast:episode>
      <itunes:title>An inside look at building a new product</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">13a0fac9-7dfd-402c-8fc0-3f09c21065be</guid>
      <link>https://share.transistor.fm/s/96673718</link>
      <description>
        <![CDATA[<p>In this episode, we talk about the very early stages of building LegUp Benefits, and a bunch of other stuff. </p><p>Topics:</p><ul><li>Rick has hired a marketing coach for LegUp, and we discuss how to get the team talking to each other more instead of having everything flow through Rick.</li><li>Tyler gives some reflections on leaving LACRM for 6 weeks, and the early days of his sabbatical.</li><li>Tyler describes a new positioning idea at LACRM.</li><li>We discuss the early work on LegUp Benefits including customer validation and learning a new tech stack.</li><li>Rick gives an update on his new group insurance efforts.</li><li>We talk about Silicon Valley Bank even though we don't have anything to say that hasn't already been said.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about the very early stages of building LegUp Benefits, and a bunch of other stuff. </p><p>Topics:</p><ul><li>Rick has hired a marketing coach for LegUp, and we discuss how to get the team talking to each other more instead of having everything flow through Rick.</li><li>Tyler gives some reflections on leaving LACRM for 6 weeks, and the early days of his sabbatical.</li><li>Tyler describes a new positioning idea at LACRM.</li><li>We discuss the early work on LegUp Benefits including customer validation and learning a new tech stack.</li><li>Rick gives an update on his new group insurance efforts.</li><li>We talk about Silicon Valley Bank even though we don't have anything to say that hasn't already been said.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 23 Mar 2023 11:06:30 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/96673718/4c44084e.mp3" length="57942085" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3452</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>In this episode, we talk about the very early stages of building LegUp Benefits, and a bunch of other stuff. </p><p>Topics:</p><ul><li>Rick has hired a marketing coach for LegUp, and we discuss how to get the team talking to each other more instead of having everything flow through Rick.</li><li>Tyler gives some reflections on leaving LACRM for 6 weeks, and the early days of his sabbatical.</li><li>Tyler describes a new positioning idea at LACRM.</li><li>We discuss the early work on LegUp Benefits including customer validation and learning a new tech stack.</li><li>Rick gives an update on his new group insurance efforts.</li><li>We talk about Silicon Valley Bank even though we don't have anything to say that hasn't already been said.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/96673718/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How to win against well-funded competitors</title>
      <itunes:episode>137</itunes:episode>
      <podcast:episode>137</podcast:episode>
      <itunes:title>How to win against well-funded competitors</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b169527e-136d-4986-9ca3-fe78ad33f434</guid>
      <link>https://share.transistor.fm/s/1384de60</link>
      <description>
        <![CDATA[<p> In this episode, we talk about how bootstrappers can win against companies that have raised massive amounts of money.</p><p>Full topic list:</p><ul><li>We give an update on the compensation negotiations we discussed last episode. We've agreed on terms for Tyler to work for Rick on LegUp Benefits!</li><li>Rick had his first annual offsite and shares a ton of great learnings.</li><li>LACRM had a great month in February. There was absolutely nothing to learn from it.</li><li>LACRM's major redesign is getting closer.</li><li>Rick has streamlined bookkeeping and other financial tasks to save time.</li><li>Tyler is thinking through when it makes sense to do custom work for a large client.</li><li>We tackle a listener question: How do bootstrapped companies compete with funded competitors.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, we talk about how bootstrappers can win against companies that have raised massive amounts of money.</p><p>Full topic list:</p><ul><li>We give an update on the compensation negotiations we discussed last episode. We've agreed on terms for Tyler to work for Rick on LegUp Benefits!</li><li>Rick had his first annual offsite and shares a ton of great learnings.</li><li>LACRM had a great month in February. There was absolutely nothing to learn from it.</li><li>LACRM's major redesign is getting closer.</li><li>Rick has streamlined bookkeeping and other financial tasks to save time.</li><li>Tyler is thinking through when it makes sense to do custom work for a large client.</li><li>We tackle a listener question: How do bootstrapped companies compete with funded competitors.</li></ul>]]>
      </content:encoded>
      <pubDate>Fri, 03 Mar 2023 09:29:41 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1384de60/d84a0abf.mp3" length="64567923" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3887</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> In this episode, we talk about how bootstrappers can win against companies that have raised massive amounts of money.</p><p>Full topic list:</p><ul><li>We give an update on the compensation negotiations we discussed last episode. We've agreed on terms for Tyler to work for Rick on LegUp Benefits!</li><li>Rick had his first annual offsite and shares a ton of great learnings.</li><li>LACRM had a great month in February. There was absolutely nothing to learn from it.</li><li>LACRM's major redesign is getting closer.</li><li>Rick has streamlined bookkeeping and other financial tasks to save time.</li><li>Tyler is thinking through when it makes sense to do custom work for a large client.</li><li>We tackle a listener question: How do bootstrapped companies compete with funded competitors.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The one where we negotiate Tyler’s compensation</title>
      <itunes:episode>136</itunes:episode>
      <podcast:episode>136</podcast:episode>
      <itunes:title>The one where we negotiate Tyler’s compensation</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">9eea14cd-5694-4889-8b6a-c8c7bf5b0363</guid>
      <link>https://share.transistor.fm/s/04349eff</link>
      <description>
        <![CDATA[<p>If you’ve been following along, you know that Tyler is about to temporarily join Rick’s startup to help build their new app. In this episode, we talk about the compensation proposal Rick just came up with. </p><p>Full topic list:</p><ul><li>Rick already has a new group insurance client after deciding to give that a shot in the last episode.</li><li>JD is visiting Rick in Utah next weekend.</li><li>Tyler is having success with delegation, and finds himself with a lot of unstructured time on his hands...</li><li>...and Tyler is having to re-learn what to do with unstructured time.</li><li>LegUp Health got hit with a bunch of spam contact forms.</li><li>Tyler is planning the new office layout for LACRM.</li><li>Apparently design debt is a thing.</li><li>Tyler is having trouble getting started on the LegUp Benefits project. Side projects are hard.</li><li>Rick brings up Youtube Premium, Quora, and NotionAI</li><li>Big topic: We discuss the compensation proposal that Rick just sent Tyler.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>If you’ve been following along, you know that Tyler is about to temporarily join Rick’s startup to help build their new app. In this episode, we talk about the compensation proposal Rick just came up with. </p><p>Full topic list:</p><ul><li>Rick already has a new group insurance client after deciding to give that a shot in the last episode.</li><li>JD is visiting Rick in Utah next weekend.</li><li>Tyler is having success with delegation, and finds himself with a lot of unstructured time on his hands...</li><li>...and Tyler is having to re-learn what to do with unstructured time.</li><li>LegUp Health got hit with a bunch of spam contact forms.</li><li>Tyler is planning the new office layout for LACRM.</li><li>Apparently design debt is a thing.</li><li>Tyler is having trouble getting started on the LegUp Benefits project. Side projects are hard.</li><li>Rick brings up Youtube Premium, Quora, and NotionAI</li><li>Big topic: We discuss the compensation proposal that Rick just sent Tyler.</li></ul>]]>
      </content:encoded>
      <pubDate>Fri, 17 Feb 2023 09:08:04 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/04349eff/29bc5b2f.mp3" length="64548718" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3910</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>If you’ve been following along, you know that Tyler is about to temporarily join Rick’s startup to help build their new app. In this episode, we talk about the compensation proposal Rick just came up with. </p><p>Full topic list:</p><ul><li>Rick already has a new group insurance client after deciding to give that a shot in the last episode.</li><li>JD is visiting Rick in Utah next weekend.</li><li>Tyler is having success with delegation, and finds himself with a lot of unstructured time on his hands...</li><li>...and Tyler is having to re-learn what to do with unstructured time.</li><li>LegUp Health got hit with a bunch of spam contact forms.</li><li>Tyler is planning the new office layout for LACRM.</li><li>Apparently design debt is a thing.</li><li>Tyler is having trouble getting started on the LegUp Benefits project. Side projects are hard.</li><li>Rick brings up Youtube Premium, Quora, and NotionAI</li><li>Big topic: We discuss the compensation proposal that Rick just sent Tyler.</li></ul>]]>
      </itunes:summary>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/04349eff/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How we deal with security questionnaires</title>
      <itunes:episode>135</itunes:episode>
      <podcast:episode>135</podcast:episode>
      <itunes:title>How we deal with security questionnaires</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">4c2aaebb-b3c6-4577-b96c-be5a0624f290</guid>
      <link>https://share.transistor.fm/s/436603da</link>
      <description>
        <![CDATA[<p> In this episode, we discuss what we do when a customer has security and compliance questions, plus, a whole lot more.</p><p>Topics in this episode:</p><ul><li>Tyler shares his experience at Big Snow Tiny Conf</li><li>Tyler is getting ready for a sabbatical which means delegating a lot of work to other people</li><li>Rick talks about gather customer profiles at LegUp Health</li><li>Rick explains what "aged leads" are</li><li>We discuss whether or not it makes sense for Rick to go after group health insurance clients</li><li>Tyler talks about an LACRM company tradition</li><li>LACRM launched their Zapier integration!</li><li>Tyler is preparing to do more design work</li><li>We have some rants and shoutouts</li><li>We talk about what to do when a lead asks for security certifications and/or asks you to fill out a questionnaire </li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> In this episode, we discuss what we do when a customer has security and compliance questions, plus, a whole lot more.</p><p>Topics in this episode:</p><ul><li>Tyler shares his experience at Big Snow Tiny Conf</li><li>Tyler is getting ready for a sabbatical which means delegating a lot of work to other people</li><li>Rick talks about gather customer profiles at LegUp Health</li><li>Rick explains what "aged leads" are</li><li>We discuss whether or not it makes sense for Rick to go after group health insurance clients</li><li>Tyler talks about an LACRM company tradition</li><li>LACRM launched their Zapier integration!</li><li>Tyler is preparing to do more design work</li><li>We have some rants and shoutouts</li><li>We talk about what to do when a lead asks for security certifications and/or asks you to fill out a questionnaire </li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 02 Feb 2023 19:55:25 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/436603da/de922fb6.mp3" length="62165619" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3809</itunes:duration>
      <itunes:summary>In this episode, we discuss what we do when a customer has security and compliance questions, plus, a whole lot more.</itunes:summary>
      <itunes:subtitle>In this episode, we discuss what we do when a customer has security and compliance questions, plus, a whole lot more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/436603da/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Something new to announce</title>
      <itunes:episode>134</itunes:episode>
      <podcast:episode>134</podcast:episode>
      <itunes:title>Something new to announce</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">104a1e1a-87f5-4856-afc5-651b0f03cfb8</guid>
      <link>https://share.transistor.fm/s/06dc3af6</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is going to work with Rick to build the new LegUp Benefits SaaS product</li><li>Rick has officially transitioned LegUp to 2023</li><li>Rick talks about how Airtable Interfaces are useful</li><li>Rick talks about an annual retreat with JD, and we discuss rituals and traditions</li><li>Tyler is going to Big Snow Tiny Conf</li><li>LACRM launched their new API, and are almost ready to launch Zapier integration</li><li>We talk about the value of podcasting</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is going to work with Rick to build the new LegUp Benefits SaaS product</li><li>Rick has officially transitioned LegUp to 2023</li><li>Rick talks about how Airtable Interfaces are useful</li><li>Rick talks about an annual retreat with JD, and we discuss rituals and traditions</li><li>Tyler is going to Big Snow Tiny Conf</li><li>LACRM launched their new API, and are almost ready to launch Zapier integration</li><li>We talk about the value of podcasting</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 19 Jan 2023 19:34:54 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/06dc3af6/9bfad1c8.mp3" length="58995037" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3712</itunes:duration>
      <itunes:summary>This week, we share some exciting news that impacts both of us.</itunes:summary>
      <itunes:subtitle>This week, we share some exciting news that impacts both of us.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/06dc3af6/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Looking back at 2022 and forward to 2023</title>
      <itunes:episode>133</itunes:episode>
      <podcast:episode>133</podcast:episode>
      <itunes:title>Looking back at 2022 and forward to 2023</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">1e272fb9-0ffb-495a-a910-1ba2f38c5ff1</guid>
      <link>https://share.transistor.fm/s/d8162898</link>
      <description>
        <![CDATA[<p><strong>Personal updates from 2022</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>✅ Plan for travel as part of relationship </li><li>❌ Build more schedule flexibility </li></ul></li><li>Other updates<ul><li>Figured out personal finance plan with Shelly</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Reprioritize daily personal health habits </li><li>❓Spend more quality time with Sable (have a date most weeks) and Oliver (take on errands) </li><li>❌Writing goals</li></ul></li></ul></li></ul><p><strong>Professional updates from 2022</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>❓ Spend more time working, but on my own terms </li><li>❓ Make space to do more individual contributor design work </li><li>❌ Release redesign of LACRM</li><li>❓ Two blog post-worthy updates per quarter</li><li>✅ Shift product priorities to be more focused on growth/strategy and less on low-impact customer requests.</li><li>✅ Run the coding fellowship</li></ul></li><li>Other updates<ul><li>More of a CEO, less of a manager</li><li>Growth was bad, but not as bad as expected</li><li>Product team got more focused</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Structure a partnership and financial plan that enables JD to go full-time</li><li>❌ Grow the business to 400 clients </li><li>❓Fully automate the new user onboarding experience</li><li>✅ Help scale Windfall the right way  </li></ul></li></ul></li></ul><p><strong>2023 personal themes/goals</strong></p><ul><li>Tyler<ul><li> Take more vacation and make up for it with extra work days</li><li> Start working towards my rich life: Renovate the house</li></ul></li><li>Rick<ul><li>Get weight below 200lbs </li><li>Write a newsletter most Sundays (at least 27 Newsletters)</li></ul></li></ul><p><strong>2023 professional themes/goals</strong></p><ul><li>Tyler<ul><li>Reap the rewards we sowed in 2022 (marketing projects and product team productivity)</li><li>Get back to decent growth: +$36k ARR per month</li><li>More of a sense of urgency on the dev team</li><li>Three major product wins<ul><li>Redesign</li><li>Finish all "first round" growth projects (Zapier, API platform, event invites)</li><li>Close the gap between us as other CRMs (email logging and/or kanban view)</li></ul></li><li>If there's a recession, minimize impact on customers and employees</li></ul></li><li>Rick<ul><li>Retain JD for another year</li><li>Double the client base again (~200 clients)</li><li>Build v1 of LegUp Benefits and get to $1k MRR</li></ul></li></ul><p><strong>Biggest worry</strong></p><ul><li>Tyler: Product relevance - Have we lost ground in the CRM market</li><li>Rick: Personal and family health</li></ul><p><strong>What do we want to learn?</strong></p><ul><li>Tyler<ul><li>How to communicate how decisions are made better</li><li>How to simplify policies so they are easier to understand</li></ul></li><li>Rick<ul><li>How to build a SaaS via contractors and self-taught coding (i.e. without giving up equity)</li><li>Further expertise in digital advertising and data</li><li>Best practices for effective leadership (in the home, neighborhood, and workplace)</li></ul></li></ul><p><strong>Predictions</strong></p><ul><li>Tyler<ul><li>Generative AI will advance, but not break through in 2023 (it will still seem more like the future than the present at the end of the year)</li><li>Binance and/or Tether will collapse, and Bitcoin will end the year down</li><li>The recession will get worse<ul><li>S&amp;P500 will be down over the first half of the year</li><li>There will be more tech layoffs in 2023 than there were in 2022</li></ul></li></ul></li><li>Rick<ul><li> Big swing back to co-location as a working requirement </li><li> AI gets embedded into workflows for millennials </li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Personal updates from 2022</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>✅ Plan for travel as part of relationship </li><li>❌ Build more schedule flexibility </li></ul></li><li>Other updates<ul><li>Figured out personal finance plan with Shelly</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Reprioritize daily personal health habits </li><li>❓Spend more quality time with Sable (have a date most weeks) and Oliver (take on errands) </li><li>❌Writing goals</li></ul></li></ul></li></ul><p><strong>Professional updates from 2022</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>❓ Spend more time working, but on my own terms </li><li>❓ Make space to do more individual contributor design work </li><li>❌ Release redesign of LACRM</li><li>❓ Two blog post-worthy updates per quarter</li><li>✅ Shift product priorities to be more focused on growth/strategy and less on low-impact customer requests.</li><li>✅ Run the coding fellowship</li></ul></li><li>Other updates<ul><li>More of a CEO, less of a manager</li><li>Growth was bad, but not as bad as expected</li><li>Product team got more focused</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Structure a partnership and financial plan that enables JD to go full-time</li><li>❌ Grow the business to 400 clients </li><li>❓Fully automate the new user onboarding experience</li><li>✅ Help scale Windfall the right way  </li></ul></li></ul></li></ul><p><strong>2023 personal themes/goals</strong></p><ul><li>Tyler<ul><li> Take more vacation and make up for it with extra work days</li><li> Start working towards my rich life: Renovate the house</li></ul></li><li>Rick<ul><li>Get weight below 200lbs </li><li>Write a newsletter most Sundays (at least 27 Newsletters)</li></ul></li></ul><p><strong>2023 professional themes/goals</strong></p><ul><li>Tyler<ul><li>Reap the rewards we sowed in 2022 (marketing projects and product team productivity)</li><li>Get back to decent growth: +$36k ARR per month</li><li>More of a sense of urgency on the dev team</li><li>Three major product wins<ul><li>Redesign</li><li>Finish all "first round" growth projects (Zapier, API platform, event invites)</li><li>Close the gap between us as other CRMs (email logging and/or kanban view)</li></ul></li><li>If there's a recession, minimize impact on customers and employees</li></ul></li><li>Rick<ul><li>Retain JD for another year</li><li>Double the client base again (~200 clients)</li><li>Build v1 of LegUp Benefits and get to $1k MRR</li></ul></li></ul><p><strong>Biggest worry</strong></p><ul><li>Tyler: Product relevance - Have we lost ground in the CRM market</li><li>Rick: Personal and family health</li></ul><p><strong>What do we want to learn?</strong></p><ul><li>Tyler<ul><li>How to communicate how decisions are made better</li><li>How to simplify policies so they are easier to understand</li></ul></li><li>Rick<ul><li>How to build a SaaS via contractors and self-taught coding (i.e. without giving up equity)</li><li>Further expertise in digital advertising and data</li><li>Best practices for effective leadership (in the home, neighborhood, and workplace)</li></ul></li></ul><p><strong>Predictions</strong></p><ul><li>Tyler<ul><li>Generative AI will advance, but not break through in 2023 (it will still seem more like the future than the present at the end of the year)</li><li>Binance and/or Tether will collapse, and Bitcoin will end the year down</li><li>The recession will get worse<ul><li>S&amp;P500 will be down over the first half of the year</li><li>There will be more tech layoffs in 2023 than there were in 2022</li></ul></li></ul></li><li>Rick<ul><li> Big swing back to co-location as a working requirement </li><li> AI gets embedded into workflows for millennials </li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Sat, 31 Dec 2022 16:40:14 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/d8162898/f693327f.mp3" length="99464830" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>6253</itunes:duration>
      <itunes:summary>This is our yearly recap episode!</itunes:summary>
      <itunes:subtitle>This is our yearly recap episode!</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Big bets vs small bets</title>
      <itunes:episode>132</itunes:episode>
      <podcast:episode>132</podcast:episode>
      <itunes:title>Big bets vs small bets</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e23d80a8-1ea1-4b0e-a5ea-dda0687c5641</guid>
      <link>https://share.transistor.fm/s/02eafa25</link>
      <description>
        <![CDATA[<p>Topics in this episode:</p><ul><li> LACRM is having a good December</li><li>Rick is feeling lots of momentum</li><li>Rick gives an update on LegUp Health's growth</li><li>Rick is reading the Warren Buffet bio: The Snowball</li><li>Tyler explains LACRM's new approach to bug triage</li><li>Rick is thinking about how hard to push for in-person</li><li>Tyler describes a new shorthand: Following daylight</li><li>Rick realizes he's learning a lot about digital marketing</li><li>We discuss how it's good for businesses to be boring and complex</li><li>Ricks suggests having "certifications" for new hires</li><li>We discuss Webflow Logic</li><li>Rick is going on a date!</li><li>Tyler is trying to decide how to prioritize big bets vs. small bets at LACRM.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics in this episode:</p><ul><li> LACRM is having a good December</li><li>Rick is feeling lots of momentum</li><li>Rick gives an update on LegUp Health's growth</li><li>Rick is reading the Warren Buffet bio: The Snowball</li><li>Tyler explains LACRM's new approach to bug triage</li><li>Rick is thinking about how hard to push for in-person</li><li>Tyler describes a new shorthand: Following daylight</li><li>Rick realizes he's learning a lot about digital marketing</li><li>We discuss how it's good for businesses to be boring and complex</li><li>Ricks suggests having "certifications" for new hires</li><li>We discuss Webflow Logic</li><li>Rick is going on a date!</li><li>Tyler is trying to decide how to prioritize big bets vs. small bets at LACRM.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 13 Dec 2022 11:24:20 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/02eafa25/39c4fa17.mp3" length="64211512" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3921</itunes:duration>
      <itunes:summary>In this episode, we talk about prioritizing big revolutionary ideas vs small iterative improvements, and a whole lot more</itunes:summary>
      <itunes:subtitle>In this episode, we talk about prioritizing big revolutionary ideas vs small iterative improvements, and a whole lot more</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/02eafa25/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How can founders use the new AI tech?</title>
      <itunes:episode>131</itunes:episode>
      <podcast:episode>131</podcast:episode>
      <itunes:title>How can founders use the new AI tech?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">04789da8-4a96-4e78-9e72-3eff43f27e0c</guid>
      <link>https://share.transistor.fm/s/afe78d54</link>
      <description>
        <![CDATA[<p>Topics:</p><ul><li>Rick gives an update on open enrollment</li><li>Tyler talks about some upcoming product launches including the new Zapier integration</li><li>Rick is refining his Adwords approach</li><li>Rick is starting to think about 2023</li><li>Tyler talks about project management</li><li>LACRM had a CRM Coach culture refresh</li><li>We talk about the recent wave of AI innovation</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics:</p><ul><li>Rick gives an update on open enrollment</li><li>Tyler talks about some upcoming product launches including the new Zapier integration</li><li>Rick is refining his Adwords approach</li><li>Rick is starting to think about 2023</li><li>Tyler talks about project management</li><li>LACRM had a CRM Coach culture refresh</li><li>We talk about the recent wave of AI innovation</li></ul>]]>
      </content:encoded>
      <pubDate>Fri, 02 Dec 2022 15:17:12 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/afe78d54/f3eca710.mp3" length="59877896" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3649</itunes:duration>
      <itunes:summary>This week we talk about the recent boom in AI, and whether or not founders like us can take advantage of this new wave of innovation.</itunes:summary>
      <itunes:subtitle>This week we talk about the recent boom in AI, and whether or not founders like us can take advantage of this new wave of innovation.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/afe78d54/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Professional hater</title>
      <itunes:episode>130</itunes:episode>
      <podcast:episode>130</podcast:episode>
      <itunes:title>Professional hater</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">48ed12b3-18eb-4fba-ad51-075027502152</guid>
      <link>https://share.transistor.fm/s/0d9950c8</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>I mean, Twitter, obviously</li><li>Rick gives an update on open enrollment including...<ul><li>Sales so far</li><li>His misadventures with Google advertising</li><li>Website positioning and design</li></ul></li><li>Tyler gives an update on LACRM's integration project</li><li>LACRM just went through a process that happens every six months</li><li>We talk fruitlessly about the potential recession and tech layoffs</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>I mean, Twitter, obviously</li><li>Rick gives an update on open enrollment including...<ul><li>Sales so far</li><li>His misadventures with Google advertising</li><li>Website positioning and design</li></ul></li><li>Tyler gives an update on LACRM's integration project</li><li>LACRM just went through a process that happens every six months</li><li>We talk fruitlessly about the potential recession and tech layoffs</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 10 Nov 2022 19:43:42 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/0d9950c8/124064b0.mp3" length="61899178" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3565</itunes:duration>
      <itunes:summary>This week we talk about Twitter melting down, tech layoffs, and other generally unpleasant things that mostly haven’t effected us so far</itunes:summary>
      <itunes:subtitle>This week we talk about Twitter melting down, tech layoffs, and other generally unpleasant things that mostly haven’t effected us so far</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/0d9950c8/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>An opportunity that comes along once per year</title>
      <itunes:episode>129</itunes:episode>
      <podcast:episode>129</podcast:episode>
      <itunes:title>An opportunity that comes along once per year</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">253f00ba-bd1f-4edc-8fb6-70faf4685917</guid>
      <link>https://share.transistor.fm/s/f8362bb2</link>
      <description>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Rick gives a big update on how LegUp Health is prepping for open enrollment<ul><li>His goal is to be long-term patient, but have short-term urgency</li><li>He doesn't have enough traffic for retargeting</li><li>Outreach will be their main lever</li><li>This weekend is his chance to get everything ready for November 1st</li></ul></li><li>Tyler talks about his time at Founder Summit</li><li>LACRM is thinking about brand marketing instead of just performance marketing</li><li>Tyler recounts a churn cohort analysis they did at LACRM</li><li>Rick shares some advice he got from a friend</li><li>Tyler gives an update on LACRM's integration partners</li><li>We discuss "Courses as marketing"</li><li>We talk about the value of sharing what you're working on with other people</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Rick gives a big update on how LegUp Health is prepping for open enrollment<ul><li>His goal is to be long-term patient, but have short-term urgency</li><li>He doesn't have enough traffic for retargeting</li><li>Outreach will be their main lever</li><li>This weekend is his chance to get everything ready for November 1st</li></ul></li><li>Tyler talks about his time at Founder Summit</li><li>LACRM is thinking about brand marketing instead of just performance marketing</li><li>Tyler recounts a churn cohort analysis they did at LACRM</li><li>Rick shares some advice he got from a friend</li><li>Tyler gives an update on LACRM's integration partners</li><li>We discuss "Courses as marketing"</li><li>We talk about the value of sharing what you're working on with other people</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 27 Oct 2022 18:56:06 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f8362bb2/80752602.mp3" length="59197004" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3651</itunes:duration>
      <itunes:summary>Most bootstrapped businesses are all about slow, steady, consistent growth. Rick’s business is different because he gets almost all his customers during one period each year, called open enrollment. In this episode, we talk about what he’s doing to prepare for this huge opportunity.</itunes:summary>
      <itunes:subtitle>Most bootstrapped businesses are all about slow, steady, consistent growth. Rick’s business is different because he gets almost all his customers during one period each year, called open enrollment. In this episode, we talk about what he’s doing to prepar</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/f8362bb2/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>What's priority #1?</title>
      <itunes:episode>128</itunes:episode>
      <podcast:episode>128</podcast:episode>
      <itunes:title>What's priority #1?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">a751e8b1-8248-425a-b00d-b929ca688ae2</guid>
      <link>https://share.transistor.fm/s/c8e49b42</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is getting ready for Founder Summit</li><li>Rick is learning about digital advertising, and we discuss whether tracking people on the internet is a net good or bad thing</li><li>Tyler gives an update on his NPS saga</li><li>Tyler talks about a joint webinar he did with ZipMessage</li><li>Rick describes his chamber of commerce webinar strategy</li><li>Windfall is opening a Utah office</li><li>Rick is getting ready to do outreach, but needs to reduce friction first</li><li>Tyler is making some changes to how he approaches project management and prioritization</li><li>We discuss a possible niche audience</li><li>Rick explains how a major hole in the health insurance laws has been fixed</li><li>Tyler started listening to the <a href="https://shipsaasfaster.com/">ShipSaaSFaster podcast</a></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is getting ready for Founder Summit</li><li>Rick is learning about digital advertising, and we discuss whether tracking people on the internet is a net good or bad thing</li><li>Tyler gives an update on his NPS saga</li><li>Tyler talks about a joint webinar he did with ZipMessage</li><li>Rick describes his chamber of commerce webinar strategy</li><li>Windfall is opening a Utah office</li><li>Rick is getting ready to do outreach, but needs to reduce friction first</li><li>Tyler is making some changes to how he approaches project management and prioritization</li><li>We discuss a possible niche audience</li><li>Rick explains how a major hole in the health insurance laws has been fixed</li><li>Tyler started listening to the <a href="https://shipsaasfaster.com/">ShipSaaSFaster podcast</a></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 13 Oct 2022 19:57:45 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/c8e49b42/1b99f81e.mp3" length="55647766" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3263</itunes:duration>
      <itunes:summary>In this episode, we talk about how easy it is to work on multiple things at once because it lets you avoid making tough prioritization decisions, and what we’re doing to avoid that trap.</itunes:summary>
      <itunes:subtitle>In this episode, we talk about how easy it is to work on multiple things at once because it lets you avoid making tough prioritization decisions, and what we’re doing to avoid that trap.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/c8e49b42/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>The marketing tech stack</title>
      <itunes:episode>127</itunes:episode>
      <podcast:episode>127</podcast:episode>
      <itunes:title>The marketing tech stack</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">54cc5b6a-b65c-4127-8e9c-bef21a5e7516</guid>
      <link>https://share.transistor.fm/s/8b19fbd4</link>
      <description>
        <![CDATA[<p>I (Tyler) am traveling and don't have time to write up show notes, so the other topics in this episode are a mystery. Enjoy!</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>I (Tyler) am traveling and don't have time to write up show notes, so the other topics in this episode are a mystery. Enjoy!</p>]]>
      </content:encoded>
      <pubDate>Fri, 30 Sep 2022 13:36:29 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/8b19fbd4/2287fa9a.mp3" length="56954940" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3440</itunes:duration>
      <itunes:summary>This episode, we talk about whether or not it makes sense to build home-made tools to help with marketing</itunes:summary>
      <itunes:subtitle>This episode, we talk about whether or not it makes sense to build home-made tools to help with marketing</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/8b19fbd4/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How much to spend acquiring a customer</title>
      <itunes:episode>126</itunes:episode>
      <podcast:episode>126</podcast:episode>
      <itunes:title>How much to spend acquiring a customer</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">8e4ab69e-8d49-4049-98b1-14b9ab32737d</guid>
      <link>https://share.transistor.fm/s/9ff6e60d</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Figma got acquired by Adobe AND I DONT WANT TO TALK ABOUT IT I'M NOT CRYING YOU'RE CRYING SHUT UP YOU'RE NOT MY REAL DAD</li><li>Rick spent a week in Cancun and soaked up some sweet business wisdom</li><li>Tyler is experiencing a period of calm at work and has done some coding for the first time in a long time</li><li>LACRM decided not to hire interns next summer</li><li>Rick and JD planned their marketing blitz</li><li>Tyler gives an update on his work to make LACRM into a platform for API integrations</li><li>We discuss how a company should decide what they're willing to spend on customer acquisition</li><li>Tyler heard a new take on what "product-led growth" means from <a href="https://www.lennyspodcast.com/how-to-build-a-powerful-marketing-machine-emily-kramer-asana-carta-mkt1/">this podcast episode</a></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Figma got acquired by Adobe AND I DONT WANT TO TALK ABOUT IT I'M NOT CRYING YOU'RE CRYING SHUT UP YOU'RE NOT MY REAL DAD</li><li>Rick spent a week in Cancun and soaked up some sweet business wisdom</li><li>Tyler is experiencing a period of calm at work and has done some coding for the first time in a long time</li><li>LACRM decided not to hire interns next summer</li><li>Rick and JD planned their marketing blitz</li><li>Tyler gives an update on his work to make LACRM into a platform for API integrations</li><li>We discuss how a company should decide what they're willing to spend on customer acquisition</li><li>Tyler heard a new take on what "product-led growth" means from <a href="https://www.lennyspodcast.com/how-to-build-a-powerful-marketing-machine-emily-kramer-asana-carta-mkt1/">this podcast episode</a></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 15 Sep 2022 19:07:05 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/9ff6e60d/81f9fd93.mp3" length="59565369" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3552</itunes:duration>
      <itunes:summary>In this episode, we talk about CAC, customer acquisition costs, and how a startup can decide how much is too much to spend on acquisition.</itunes:summary>
      <itunes:subtitle>In this episode, we talk about CAC, customer acquisition costs, and how a startup can decide how much is too much to spend on acquisition.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/9ff6e60d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>The great re-org</title>
      <itunes:episode>125</itunes:episode>
      <podcast:episode>125</podcast:episode>
      <itunes:title>The great re-org</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">9e52695a-d814-4679-993f-52d45eee9ffc</guid>
      <link>https://share.transistor.fm/s/1a93bae5</link>
      <description>
        <![CDATA[<p>Topics:</p><ul><li>LACRM had a great growth month in August, mostly because of expansion revenue.</li><li>JD, Rick's business partner, is doing a great job.</li><li>Rick is oscillating between investing in more resources and staying focused.</li><li>Rick gives an update on his recent local marketing blitz.</li><li>Tyler is rethinking the customer onboarding flow.</li><li>LACRM is shifting around their marketing priorities.</li><li>Rick shares some wisdom from Jason Lempkin.</li><li>Rick is learning how it's hard to not have authority.</li><li>Tyler talks about hollow abstraction by mostly just parroting what's said in <a href="https://twitter.com/liron/status/1562589538848874498?s=21&amp;t=sKnDH0IcrZlqZOwnk-f8Fg">this video</a>.</li><li>We talk about "Zucking" (please don't look it up on Urban Dictionary, we're not talking about <em>that</em> kind of Zucking).</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics:</p><ul><li>LACRM had a great growth month in August, mostly because of expansion revenue.</li><li>JD, Rick's business partner, is doing a great job.</li><li>Rick is oscillating between investing in more resources and staying focused.</li><li>Rick gives an update on his recent local marketing blitz.</li><li>Tyler is rethinking the customer onboarding flow.</li><li>LACRM is shifting around their marketing priorities.</li><li>Rick shares some wisdom from Jason Lempkin.</li><li>Rick is learning how it's hard to not have authority.</li><li>Tyler talks about hollow abstraction by mostly just parroting what's said in <a href="https://twitter.com/liron/status/1562589538848874498?s=21&amp;t=sKnDH0IcrZlqZOwnk-f8Fg">this video</a>.</li><li>We talk about "Zucking" (please don't look it up on Urban Dictionary, we're not talking about <em>that</em> kind of Zucking).</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 01 Sep 2022 21:30:24 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1a93bae5/75ffba82.mp3" length="63736741" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3828</itunes:duration>
      <itunes:summary>In this episode, we talk about how we’re thinking about reallocating marketing and sales resources here at Less Annoying CRM.</itunes:summary>
      <itunes:subtitle>In this episode, we talk about how we’re thinking about reallocating marketing and sales resources here at Less Annoying CRM.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/1a93bae5/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Is SaaS getting harder?</title>
      <itunes:episode>124</itunes:episode>
      <podcast:episode>124</podcast:episode>
      <itunes:title>Is SaaS getting harder?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">be1a6453-e0ed-4977-89cd-a997c8bc6db7</guid>
      <link>https://share.transistor.fm/s/854f4a68</link>
      <description>
        <![CDATA[<p>Topics this episode:</p><ul><li>Summer is ending at LACRM and things are going back to normal.</li><li>Rick attended a company offsite last week, and now he's behind.</li><li>LegUp Health is planning a local marketing blitz.</li><li>Tyler gives an update on pay transparency at LACRM.</li><li>Tyler has been doing some cold outreach to try to find API partners.</li><li>There's a new VP at Lucid.</li><li>Tyler talks about how <a href="https://www.defaultalive.fm/72">this episode of Default Alive</a> has an interesting take on no-code.</li><li>Tyler and Rick talk about how it seems like it's getting harder to build a SaaS business, largely inspired by <a href="https://outofbeta.fm/episode/what-kills-a-startup">this episode of Out of Beta</a>.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this episode:</p><ul><li>Summer is ending at LACRM and things are going back to normal.</li><li>Rick attended a company offsite last week, and now he's behind.</li><li>LegUp Health is planning a local marketing blitz.</li><li>Tyler gives an update on pay transparency at LACRM.</li><li>Tyler has been doing some cold outreach to try to find API partners.</li><li>There's a new VP at Lucid.</li><li>Tyler talks about how <a href="https://www.defaultalive.fm/72">this episode of Default Alive</a> has an interesting take on no-code.</li><li>Tyler and Rick talk about how it seems like it's getting harder to build a SaaS business, largely inspired by <a href="https://outofbeta.fm/episode/what-kills-a-startup">this episode of Out of Beta</a>.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 18 Aug 2022 19:32:12 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/854f4a68/3fff42cc.mp3" length="58503462" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3556</itunes:duration>
      <itunes:summary>Sometimes it feels like the tech industry is more of a zero-sum game than it used to be. We discuss that, and a lot more in this episode.</itunes:summary>
      <itunes:subtitle>Sometimes it feels like the tech industry is more of a zero-sum game than it used to be. We discuss that, and a lot more in this episode.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/854f4a68/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Single points of failure</title>
      <itunes:episode>123</itunes:episode>
      <podcast:episode>123</podcast:episode>
      <itunes:title>Single points of failure</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f27ac9f6-1657-42c4-96e8-6da4595ffe7c</guid>
      <link>https://share.transistor.fm/s/366c9551</link>
      <description>
        <![CDATA[<p>Topics in this episode:</p><ul><li>LACRM got DDoSed *again*</li><li>Rick went to some networking events</li><li>Tyler is ending his newsletter</li><li>Rick gives a chamber of commerce update</li><li>LegUp Health is seeing early success with an incentive offer</li><li>We discuss handling an employee who leaves for an extended period and whether the goal should be to have no single points of failure</li><li>Rick talks about how intentional assumptions can combat fear</li><li>Tyler gives an LACRM product-led growth update</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics in this episode:</p><ul><li>LACRM got DDoSed *again*</li><li>Rick went to some networking events</li><li>Tyler is ending his newsletter</li><li>Rick gives a chamber of commerce update</li><li>LegUp Health is seeing early success with an incentive offer</li><li>We discuss handling an employee who leaves for an extended period and whether the goal should be to have no single points of failure</li><li>Rick talks about how intentional assumptions can combat fear</li><li>Tyler gives an LACRM product-led growth update</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 28 Jul 2022 18:59:55 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/366c9551/12650494.mp3" length="64670289" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3934</itunes:duration>
      <itunes:summary>Are single-points of failure sometimes ok? In this episode, we talk about how much redundancy a small company should have. </itunes:summary>
      <itunes:subtitle>Are single-points of failure sometimes ok? In this episode, we talk about how much redundancy a small company should have. </itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/366c9551/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Should you hire a marketing agency?</title>
      <itunes:episode>122</itunes:episode>
      <podcast:episode>122</podcast:episode>
      <itunes:title>Should you hire a marketing agency?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">26e224fe-9036-4e4b-8443-beb95c06f24b</guid>
      <link>https://share.transistor.fm/s/690f39a1</link>
      <description>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Less Annoying CRM hit $3.5 million ARR.</li><li>Rick and LegUp Health have signed up for several in-person networking events as well as a number of chambers of commerce.</li><li>LACRM had a new CRM Coach start.</li><li>Tyler reflects on why his updates haven't been interesting recently, and what that might mean about how he'd feel running a bigger company.</li><li>Rick got a new client who followed the ideal customer journey. Feels good.</li><li>Rick is considering working with an SEO contractor.</li><li>We discuss how to pick a digital marketing agency, and whether it even makes sense to do so.<ul><li>In this episode, we discuss <a href="https://demandmaven.io/">DemandMaven</a> and <a href="https://twitter.com/JHTScherck">JH Scherck</a>.</li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Less Annoying CRM hit $3.5 million ARR.</li><li>Rick and LegUp Health have signed up for several in-person networking events as well as a number of chambers of commerce.</li><li>LACRM had a new CRM Coach start.</li><li>Tyler reflects on why his updates haven't been interesting recently, and what that might mean about how he'd feel running a bigger company.</li><li>Rick got a new client who followed the ideal customer journey. Feels good.</li><li>Rick is considering working with an SEO contractor.</li><li>We discuss how to pick a digital marketing agency, and whether it even makes sense to do so.<ul><li>In this episode, we discuss <a href="https://demandmaven.io/">DemandMaven</a> and <a href="https://twitter.com/JHTScherck">JH Scherck</a>.</li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 14 Jul 2022 18:56:48 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/690f39a1/0668cda6.mp3" length="57872423" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3523</itunes:duration>
      <itunes:summary>In this episode, we talk about whether or not it makes sense for an early stage bootstrapped company to hire a marketing agency for help.</itunes:summary>
      <itunes:subtitle>In this episode, we talk about whether or not it makes sense for an early stage bootstrapped company to hire a marketing agency for help.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/690f39a1/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Healthy urgency</title>
      <itunes:episode>121</itunes:episode>
      <podcast:episode>121</podcast:episode>
      <itunes:title>Healthy urgency</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e405d2e6-5a59-4a14-855c-a155ddb4e8f8</guid>
      <link>https://share.transistor.fm/s/3efec93c</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler thinks he's finally fixed his audio setup.</li><li>Rick and Tyler are both having good sales months. Rick actually knows why!</li><li>We discuss what indicators a SaaS company might look at to tell whether a recession is impacting their business.</li><li>Rick is getting weekly updates from JD in a new format that is working well.</li><li>Rick went to a fancy-pants senator's house to schmooze with the big wigs and now he wants to meet more powerful people so that they can laugh at us common folk.</li><li>Tyler talks about the possibility of LACRM expanding into services.</li><li>Rick is building a list of people he might want to hire/work with one day.</li><li>Rick's CPA ghosted him. CPAs are the worst.</li><li>We discuss health urgency.</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler thinks he's finally fixed his audio setup.</li><li>Rick and Tyler are both having good sales months. Rick actually knows why!</li><li>We discuss what indicators a SaaS company might look at to tell whether a recession is impacting their business.</li><li>Rick is getting weekly updates from JD in a new format that is working well.</li><li>Rick went to a fancy-pants senator's house to schmooze with the big wigs and now he wants to meet more powerful people so that they can laugh at us common folk.</li><li>Tyler talks about the possibility of LACRM expanding into services.</li><li>Rick is building a list of people he might want to hire/work with one day.</li><li>Rick's CPA ghosted him. CPAs are the worst.</li><li>We discuss health urgency.</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Tue, 28 Jun 2022 18:37:20 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/3efec93c/16334919.mp3" length="67582494" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3975</itunes:duration>
      <itunes:summary>In this episode, we talk about healthy vs. unhealthy urgency, and whether it's realistic to hire a team of entirely high-urgency people</itunes:summary>
      <itunes:subtitle>In this episode, we talk about healthy vs. unhealthy urgency, and whether it's realistic to hire a team of entirely high-urgency people</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Prioritizing effectiveness over efficiency</title>
      <itunes:episode>120</itunes:episode>
      <podcast:episode>120</podcast:episode>
      <itunes:title>Prioritizing effectiveness over efficiency</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f547def8-c89d-44b4-9213-5f34eb25950e</guid>
      <link>https://share.transistor.fm/s/dcb1071d</link>
      <description>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Rick has learned more about how to be a good business partner.</li><li>Rick is prioritizing effectiveness over efficiency.</li><li>Tyler asks about how best to track marketing ROI.</li><li>Tyler has an idea for a platform play at LACRM.</li><li>Another company in LegUp Health's space has been aquired.</li><li>Tyler gives an argument against delegation.</li><li>Rick revisits the importance of buffer.</li><li>Tyler recommends listening to <a href="https://share.transistor.fm/s/74b4d31f">this episode</a> of the IndieHackers podcast.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Rick has learned more about how to be a good business partner.</li><li>Rick is prioritizing effectiveness over efficiency.</li><li>Tyler asks about how best to track marketing ROI.</li><li>Tyler has an idea for a platform play at LACRM.</li><li>Another company in LegUp Health's space has been aquired.</li><li>Tyler gives an argument against delegation.</li><li>Rick revisits the importance of buffer.</li><li>Tyler recommends listening to <a href="https://share.transistor.fm/s/74b4d31f">this episode</a> of the IndieHackers podcast.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 09 Jun 2022 19:59:42 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/dcb1071d/9735284a.mp3" length="59848573" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3532</itunes:duration>
      <itunes:summary>In this episode, we've got a grab-bag of topics including when to worry about scaling, an argument against delegation, and a few shoutouts.</itunes:summary>
      <itunes:subtitle>In this episode, we've got a grab-bag of topics including when to worry about scaling, an argument against delegation, and a few shoutouts.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/dcb1071d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Charge Less</title>
      <itunes:episode>119</itunes:episode>
      <podcast:episode>119</podcast:episode>
      <itunes:title>Charge Less</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ceb66da6-526a-4c2e-afed-6944b25ca303</guid>
      <link>https://share.transistor.fm/s/43477f8a</link>
      <description>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Rick is working on updating and simplify LegUp Health's messaging.</li><li>LegUp Health is testing out purchasing leads.</li><li>Rick talks about the next step of his SEO work.</li><li>Tyler has been listening to customer interviews and learned some things about pricing and features with LACRM.</li><li>Tyler isn't listening to as many business podcasts.</li><li>We discuss the blog post: <a href="https://neilthanedar.com/we-need-a-middle-class-for-startups/">We Need A Middle Class For Startups</a></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Rick is working on updating and simplify LegUp Health's messaging.</li><li>LegUp Health is testing out purchasing leads.</li><li>Rick talks about the next step of his SEO work.</li><li>Tyler has been listening to customer interviews and learned some things about pricing and features with LACRM.</li><li>Tyler isn't listening to as many business podcasts.</li><li>We discuss the blog post: <a href="https://neilthanedar.com/we-need-a-middle-class-for-startups/">We Need A Middle Class For Startups</a></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 26 May 2022 19:10:41 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/43477f8a/936faa90.mp3" length="52141097" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3052</itunes:duration>
      <itunes:summary>In this episode, we talk about how conventional wisdom around pricing is sometimes wrong.</itunes:summary>
      <itunes:subtitle>In this episode, we talk about how conventional wisdom around pricing is sometimes wrong.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/43477f8a/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Recession?</title>
      <itunes:episode>118</itunes:episode>
      <podcast:episode>118</podcast:episode>
      <itunes:title>Recession?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">57149c02-c2ba-4ab1-8c26-ef32665d3596</guid>
      <link>https://share.transistor.fm/s/158d82c3</link>
      <description>
        <![CDATA[<p>Topics this week</p><ul><li>The possibility of a recession and how it might impact businesses like ours.</li><li>LegUp Health just had a competitor acquired.</li><li>Less Annoying CRM was DDoSed again.</li><li>Tyler discusses some traction channels he's been considering.</li><li>Rick asks about virtuous vs. vicious cycles.</li><li>We discuss the merits of a multi-product business vs a single-product business.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week</p><ul><li>The possibility of a recession and how it might impact businesses like ours.</li><li>LegUp Health just had a competitor acquired.</li><li>Less Annoying CRM was DDoSed again.</li><li>Tyler discusses some traction channels he's been considering.</li><li>Rick asks about virtuous vs. vicious cycles.</li><li>We discuss the merits of a multi-product business vs a single-product business.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 10 May 2022 09:37:24 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/158d82c3/18fa6142.mp3" length="62444132" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3620</itunes:duration>
      <itunes:summary>In this episode, we discuss how the recent economic uncertainty might impact bootstrapped businesses.</itunes:summary>
      <itunes:subtitle>In this episode, we discuss how the recent economic uncertainty might impact bootstrapped businesses.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/158d82c3/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How to be a mentor when you aren't knowledgeable about a topic</title>
      <itunes:episode>117</itunes:episode>
      <podcast:episode>117</podcast:episode>
      <itunes:title>How to be a mentor when you aren't knowledgeable about a topic</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">fe88efbc-f562-4a9a-886a-557b6f82bf06</guid>
      <link>https://share.transistor.fm/s/84189e8d</link>
      <description>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Tyler bought tickets to attend <a href="https://foundersummit.co/">Founder Summit</a>.</li><li>Tyler is rethinking his investment strategy.</li><li>A competitor of LegUp Health is going out of business.</li><li>Tyler is working on renewing LACRM's office lease.</li><li>LegUp Health is struggling to scale their outreach, so they're going back to basics.</li><li>LACRM's new design is coming along.</li><li>LACRM is making pay more transparent internally.</li><li>Rick wants LegUp to be in the discussion when people talk about health insurance in Utah.</li><li>We discuss how to provide mentorship to employees if no one at your company has expertise in the area they need help with.</li><li>We discuss what future marketing channels might be similar to what SEO was in the early 2000's.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Tyler bought tickets to attend <a href="https://foundersummit.co/">Founder Summit</a>.</li><li>Tyler is rethinking his investment strategy.</li><li>A competitor of LegUp Health is going out of business.</li><li>Tyler is working on renewing LACRM's office lease.</li><li>LegUp Health is struggling to scale their outreach, so they're going back to basics.</li><li>LACRM's new design is coming along.</li><li>LACRM is making pay more transparent internally.</li><li>Rick wants LegUp to be in the discussion when people talk about health insurance in Utah.</li><li>We discuss how to provide mentorship to employees if no one at your company has expertise in the area they need help with.</li><li>We discuss what future marketing channels might be similar to what SEO was in the early 2000's.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 28 Apr 2022 20:07:28 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/84189e8d/03752b4e.mp3" length="66664968" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3890</itunes:duration>
      <itunes:summary>In this episode, we discuss how to connect employees with mentors when there's not already someone at the company with expertise.</itunes:summary>
      <itunes:subtitle>In this episode, we discuss how to connect employees with mentors when there's not already someone at the company with expertise.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/84189e8d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Mission, Vision, and Values</title>
      <itunes:episode>116</itunes:episode>
      <podcast:episode>116</podcast:episode>
      <itunes:title>Mission, Vision, and Values</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f0309bc2-b077-4b50-a975-0d49b45a76db</guid>
      <link>https://share.transistor.fm/s/0b6b020d</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>A new employee started at LACRM</li><li>Tyler is getting ready for lots of interns</li><li>Rick has been struggling to form healthy habits</li><li>Rick gives an update on his business partner's work/life balance</li><li>Tyler finished his cycle of meeting/presentation/1:1s that he does every six months</li><li>Tyler asks Rick about how to define mission, vision, and values</li><li>Rick describes a new marketing funnel he found</li><li>LegUp Health's vision is supported by a recent regulation change</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>A new employee started at LACRM</li><li>Tyler is getting ready for lots of interns</li><li>Rick has been struggling to form healthy habits</li><li>Rick gives an update on his business partner's work/life balance</li><li>Tyler finished his cycle of meeting/presentation/1:1s that he does every six months</li><li>Tyler asks Rick about how to define mission, vision, and values</li><li>Rick describes a new marketing funnel he found</li><li>LegUp Health's vision is supported by a recent regulation change</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 14 Apr 2022 22:14:28 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/0b6b020d/2ec11b6c.mp3" length="52997352" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3182</itunes:duration>
      <itunes:summary>This week, we talk about how to define the purpose and constraints of a business.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to define the purpose and constraints of a business.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/0b6b020d/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Tools don't solve problems</title>
      <itunes:episode>115</itunes:episode>
      <podcast:episode>115</podcast:episode>
      <itunes:title>Tools don't solve problems</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">78f49ffa-f595-4be4-bd0b-d45cc9e8d97c</guid>
      <link>https://share.transistor.fm/s/e43a8b9a</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler has been extremely busy with meetings, interviews, etc.</li><li>LACRM hired two new CRM Coaches.</li><li>Rick took some time off to ski with his family, watched a Duke basketball game, and celebrated his son's 1st birthday.</li><li>LegUp Health has mixed results sending cookies to try to delight customers.</li><li>Tyler gives some updates on product-led growth brainstorming from last episode.</li><li>LegUp Health added some new tools to their workflow to start making things more efficient.</li><li>Rick warns us about the dangers of thinking that tools solve problems.</li><li>Tyler is in discussions with <a href="https://demandmaven.io/">DemandMaven</a>.</li><li>Tyler isn't sure what the future of his blog/newsletter should be.</li><li>We talk about how to be real without being rude.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler has been extremely busy with meetings, interviews, etc.</li><li>LACRM hired two new CRM Coaches.</li><li>Rick took some time off to ski with his family, watched a Duke basketball game, and celebrated his son's 1st birthday.</li><li>LegUp Health has mixed results sending cookies to try to delight customers.</li><li>Tyler gives some updates on product-led growth brainstorming from last episode.</li><li>LegUp Health added some new tools to their workflow to start making things more efficient.</li><li>Rick warns us about the dangers of thinking that tools solve problems.</li><li>Tyler is in discussions with <a href="https://demandmaven.io/">DemandMaven</a>.</li><li>Tyler isn't sure what the future of his blog/newsletter should be.</li><li>We talk about how to be real without being rude.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 31 Mar 2022 20:25:20 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e43a8b9a/144feb38.mp3" length="58735695" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3470</itunes:duration>
      <itunes:summary>This episode, we've got a grab bag of different topics including a product-led growth discussion, what to do with a stagnent content site, and the role tools should play in running a business.</itunes:summary>
      <itunes:subtitle>This episode, we've got a grab bag of different topics including a product-led growth discussion, what to do with a stagnent content site, and the role tools should play in running a business.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/e43a8b9a/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Putting together a growth plan</title>
      <itunes:episode>114</itunes:episode>
      <podcast:episode>114</podcast:episode>
      <itunes:title>Putting together a growth plan</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5fdaf6fe-bdb3-4b36-877b-1fe0a2e0eaea</guid>
      <link>https://share.transistor.fm/s/e942783e</link>
      <description>
        <![CDATA[<p>Topics from this week:</p><ul><li>Tyler explains how bug bounties work.</li><li>Rick discusses the power of incentives.</li><li>LegUp Health is adding new clients every week, and we discuss how prospecting is working.</li><li>Rick brags about his new <a href="https://x1creditcard.com/">X1 credit card</a> (I swear this isn't sponsored, we don't have nearly enough listeners for anyone to bother paying us for product placement)</li><li>We discuss how Rick can thank people who help his business.</li><li>No-work Sunday is a success for Rick.</li><li>We discuss Jason Cohen's blog post: <a href="https://longform.asmartbear.com/docs/exponential-growth/">The Elephant in the room: The myth of exponential hypergrowth</a></li><li>Rick helps Tyler think through his new growth plan.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this week:</p><ul><li>Tyler explains how bug bounties work.</li><li>Rick discusses the power of incentives.</li><li>LegUp Health is adding new clients every week, and we discuss how prospecting is working.</li><li>Rick brags about his new <a href="https://x1creditcard.com/">X1 credit card</a> (I swear this isn't sponsored, we don't have nearly enough listeners for anyone to bother paying us for product placement)</li><li>We discuss how Rick can thank people who help his business.</li><li>No-work Sunday is a success for Rick.</li><li>We discuss Jason Cohen's blog post: <a href="https://longform.asmartbear.com/docs/exponential-growth/">The Elephant in the room: The myth of exponential hypergrowth</a></li><li>Rick helps Tyler think through his new growth plan.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 17 Mar 2022 19:51:21 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e942783e/03ba3b41.mp3" length="63423595" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3867</itunes:duration>
      <itunes:summary>This week, Rick helps Tyler think through a new growth plan for Less Annoying CRM</itunes:summary>
      <itunes:subtitle>This week, Rick helps Tyler think through a new growth plan for Less Annoying CRM</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/e942783e/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>The importance of patience and impatience when hiring</title>
      <itunes:episode>113</itunes:episode>
      <podcast:episode>113</podcast:episode>
      <itunes:title>The importance of patience and impatience when hiring</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">9fbb3ea8-9df9-4a62-a68d-39d1c16aa843</guid>
      <link>https://share.transistor.fm/s/61619e28</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is reading <a href="https://www.amazon.com/Great-CEO-Within-Tactical-Building-ebook/dp/B07ZLGQZYC">The Great CEO Within</a>.</li><li>Rick shares some early sales wins.</li><li>LegUp Health is learning about their ICP (Ideal Customer Profile).</li><li>Tyler has been experiencing ups and downs when it comes to design, but overall has learned a lot the last two weeks.</li><li>Rick is making Sunday a "no work" day.</li><li>Less Annoying CRM is hiring, and Tyler thinks there needs to be more of a sense of urgency.</li><li>Rick has set a quarterly goal, but it's about learning rather than hitting certain metrics.</li><li>Rick has additional responsibilities at Windfall.</li><li>Tyler shouts out a few products from Elgato, especially the <a href="https://www.elgato.com/en/wave-mic-arm-lp">low-profile mic arm</a>.</li><li>We compare starting a business when you're younger vs when you're older.</li><li>Update from last episode: <a href="https://docs.google.com/document/d/1Bbua8lTPBRleSZOONBAQBW5PFjUWe4rh-fxbRY3L0Zs/edit">This is the compensation agreement Rick finalized with his first employee</a>.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is reading <a href="https://www.amazon.com/Great-CEO-Within-Tactical-Building-ebook/dp/B07ZLGQZYC">The Great CEO Within</a>.</li><li>Rick shares some early sales wins.</li><li>LegUp Health is learning about their ICP (Ideal Customer Profile).</li><li>Tyler has been experiencing ups and downs when it comes to design, but overall has learned a lot the last two weeks.</li><li>Rick is making Sunday a "no work" day.</li><li>Less Annoying CRM is hiring, and Tyler thinks there needs to be more of a sense of urgency.</li><li>Rick has set a quarterly goal, but it's about learning rather than hitting certain metrics.</li><li>Rick has additional responsibilities at Windfall.</li><li>Tyler shouts out a few products from Elgato, especially the <a href="https://www.elgato.com/en/wave-mic-arm-lp">low-profile mic arm</a>.</li><li>We compare starting a business when you're younger vs when you're older.</li><li>Update from last episode: <a href="https://docs.google.com/document/d/1Bbua8lTPBRleSZOONBAQBW5PFjUWe4rh-fxbRY3L0Zs/edit">This is the compensation agreement Rick finalized with his first employee</a>.</li></ul>]]>
      </content:encoded>
      <pubDate>Mon, 28 Feb 2022 19:22:26 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/61619e28/85b399fb.mp3" length="58475018" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3573</itunes:duration>
      <itunes:summary>This week, we talk about how both patience and impatience are important when hiring, how to learn new things, and more.</itunes:summary>
      <itunes:subtitle>This week, we talk about how both patience and impatience are important when hiring, how to learn new things, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/61619e28/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Funding your startup with a day job</title>
      <itunes:episode>112</itunes:episode>
      <podcast:episode>112</podcast:episode>
      <itunes:title>Funding your startup with a day job</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">8d0087c1-c733-4e94-ae51-2056a8fc754b</guid>
      <link>https://share.transistor.fm/s/cfd24049</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick is close to finalizing a partnership agreement with his first team member.</li><li>Tyler is excited that LACRM has been shipping a lot of product improvements lately.</li><li>Tyler has a new productivity hack he's trying.</li><li>LegUp Health is doing some cold outreach and so far it's working.</li><li>LegUp Health joined a new business association.</li><li>Tyler is nervous about some marketing trends even though they haven't become a problem yet.</li><li>NFTs. What are they? Why aren't we able to understand them? Why do we keep talking about them despite not understanding them? Because we're podcasters so we're obviously very comfortable acting like experts on topics we know nothing about.</li><li>We respond to a listener question about how Rick balances his full-time job with running LegUp Health.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick is close to finalizing a partnership agreement with his first team member.</li><li>Tyler is excited that LACRM has been shipping a lot of product improvements lately.</li><li>Tyler has a new productivity hack he's trying.</li><li>LegUp Health is doing some cold outreach and so far it's working.</li><li>LegUp Health joined a new business association.</li><li>Tyler is nervous about some marketing trends even though they haven't become a problem yet.</li><li>NFTs. What are they? Why aren't we able to understand them? Why do we keep talking about them despite not understanding them? Because we're podcasters so we're obviously very comfortable acting like experts on topics we know nothing about.</li><li>We respond to a listener question about how Rick balances his full-time job with running LegUp Health.</li></ul>]]>
      </content:encoded>
      <pubDate>Mon, 14 Feb 2022 18:51:20 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/cfd24049/1094c4ed.mp3" length="59206128" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3445</itunes:duration>
      <itunes:summary>This week, we talk about balancing a full-time job with running a startup, and a bunch of other stuff.</itunes:summary>
      <itunes:subtitle>This week, we talk about balancing a full-time job with running a startup, and a bunch of other stuff.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/cfd24049/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Giving early hires skin in the game</title>
      <itunes:episode>111</itunes:episode>
      <podcast:episode>111</podcast:episode>
      <itunes:title>Giving early hires skin in the game</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">626460ac-bf41-4009-b1ec-98102e53bbf2</guid>
      <link>https://share.transistor.fm/s/267358ba</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is considering going to <a href="https://foundersummit.co/">Founder Summit</a> in Ashville this fall.</li><li>LegUp Health signed a partnership deal with <a href="https://www.joinpando.org/">Pando Labs</a>.</li><li>LACRM is on a hiring spree.</li><li>LACRM has a new thriving wage.</li><li>We discuss whether video testimonials are a good idea.</li><li>Tyler heard a podcast which made fun of LACRM's design, and this resulted in him getting some design coaching.</li><li>We discuss how Rick can structure a partnership agreement with his first hire.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is considering going to <a href="https://foundersummit.co/">Founder Summit</a> in Ashville this fall.</li><li>LegUp Health signed a partnership deal with <a href="https://www.joinpando.org/">Pando Labs</a>.</li><li>LACRM is on a hiring spree.</li><li>LACRM has a new thriving wage.</li><li>We discuss whether video testimonials are a good idea.</li><li>Tyler heard a podcast which made fun of LACRM's design, and this resulted in him getting some design coaching.</li><li>We discuss how Rick can structure a partnership agreement with his first hire.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 03 Feb 2022 18:56:55 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/267358ba/3bca93d4.mp3" length="62775364" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3823</itunes:duration>
      <itunes:summary>This week, we talk about how Rick can structure a compensation plan with his first hire to make them feel like a true partner. Most startups give equity, but that isn’t a very compelling perk for a company that doesn’t plan on exiting. </itunes:summary>
      <itunes:subtitle>This week, we talk about how Rick can structure a compensation plan with his first hire to make them feel like a true partner. Most startups give equity, but that isn’t a very compelling perk for a company that doesn’t plan on exiting. </itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/267358ba/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>Rebirth / Welcoming 2022</title>
      <itunes:episode>110</itunes:episode>
      <podcast:episode>110</podcast:episode>
      <itunes:title>Rebirth / Welcoming 2022</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">cc0da1cc-be42-4f15-b5ab-f7f416ed235f</guid>
      <link>https://share.transistor.fm/s/abcc4c86</link>
      <description>
        <![CDATA[<p>This is our annual retro/goal-setting episode. Here's what we cover:</p><p><strong>Personal updates from 2021</strong></p><ul><li>Tyler<ul><li>Goal from last year: ✅Spend more time with family and friends once vaccinated</li><li>Other updates<ul><li>Started exercising</li><li>Froze embryos</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Get sleep under control</li><li>✅ Adjust to being a dad</li></ul></li><li>Other updates<ul><li>Wasn't good about exercising</li><li>Has only been on one date with Sable</li></ul></li></ul></li></ul><p><strong>Professional updates from 2021</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>✅ Get marketing to a point where if can be delegated</li><li>❓ Design a new appointment scheduler product</li><li>✅ Biggest worry: Growth leveling off</li><li>❓ Want to learn: Re-learn how to iterate and move fast</li></ul></li><li>Biggest disappointment: Losing a developer right when the product team was building momentum</li><li>Biggest learning: Wants to be a product designer</li><li>Other updates:<ul><li>Fewer management responsibilities</li><li>Signed biggest client to-date</li><li>Full-funded the treasury</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>❌ Get to $10k MRR. </li><li>✅ Automate/delegate so service can be scalable. </li><li>✅ Biggest worry: Being able to scale service. </li><li>✅ Want to learn: Learn more coding, especially working with API data and generating dynamic emails.</li></ul></li><li>Biggest disappointment:  Not being able to work on LegUp Health full time</li><li>Biggest learning:  Sharing the journey at LegUp Health is better than going solo </li><li>Other updates:<ul><li> Tried bringing on another friend as a Marketing contractor, but he decided to take a full-time job before he ramped up </li></ul></li></ul></li></ul><p><strong>2022 Personal themes/goals</strong></p><ul><li>Tyler<ul><li>Plan for travel as part of relationship</li><li>Build more schedule flexibility so things can be done without needing willpower (e.g. exercise mid-day)</li></ul></li><li>Rick<ul><li>Reprioritize daily personal health habits (write/exercise before family wakes up, daily calorie tracking)</li><li>Spend more quality time with Sable (have a date most weeks) and Oliver (take on errands)</li></ul></li></ul><p><strong>2022 Professional themes/goals</strong></p><ul><li>Tyler<ul><li>Theme: Spend more time working, but on my own terms</li><li>Make space to do more individual contributor design work</li><li>Other things<ul><li>Release 3.9 design</li><li>Two blog post-worthy releases per quarter</li><li>By end of year, have an equal balance of tech debt, core CRM, strategy, and product-led growth work on the dev team</li><li>Run the coding fellowship</li></ul></li></ul></li><li>Rick<ul><li>Support the growth of LeUp Health<ul><li>Structure a partnership and financial plan that enables JD to go full-time</li><li>Grow the business to 400 clients</li><li>Fully automate the new user onboarding experience</li></ul></li><li>Help scale Windfall the right way <ul><li>Prioritize both performance and people</li><li>Be a team player</li><li>Deliver on my responsibilities</li></ul></li></ul></li></ul><p><strong>Biggest worry</strong></p><ul><li>Tyler: Growth slowed in 2021. Will it come back?</li><li>Rick: Retaining JD for the long term</li></ul><p><strong>What do we want to learn?</strong></p><ul><li>Tyler: More professional visual design</li><li>Rick: First principles of leading others (e.g. influence, motivation, habits, trust, negotiation, communication, and decision-making)</li></ul><p><strong>Predictions</strong></p><ul><li>Last year<ul><li>Tyler: ❌ San Francisco will become a good place for early-stage startups again</li><li>Rick: ❓ Asynchronous video will become big in professional settings</li></ul></li><li>Next year<ul><li>Tyler: The world will be less interested in speculative bubbles (NFTs, meme stocks, etc.)</li><li>Rick: VR headset use is going to become as common as playing a Wii</li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This is our annual retro/goal-setting episode. Here's what we cover:</p><p><strong>Personal updates from 2021</strong></p><ul><li>Tyler<ul><li>Goal from last year: ✅Spend more time with family and friends once vaccinated</li><li>Other updates<ul><li>Started exercising</li><li>Froze embryos</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>✅ Get sleep under control</li><li>✅ Adjust to being a dad</li></ul></li><li>Other updates<ul><li>Wasn't good about exercising</li><li>Has only been on one date with Sable</li></ul></li></ul></li></ul><p><strong>Professional updates from 2021</strong></p><ul><li>Tyler<ul><li>Goals from last year<ul><li>✅ Get marketing to a point where if can be delegated</li><li>❓ Design a new appointment scheduler product</li><li>✅ Biggest worry: Growth leveling off</li><li>❓ Want to learn: Re-learn how to iterate and move fast</li></ul></li><li>Biggest disappointment: Losing a developer right when the product team was building momentum</li><li>Biggest learning: Wants to be a product designer</li><li>Other updates:<ul><li>Fewer management responsibilities</li><li>Signed biggest client to-date</li><li>Full-funded the treasury</li></ul></li></ul></li><li>Rick<ul><li>Goals from last year<ul><li>❌ Get to $10k MRR. </li><li>✅ Automate/delegate so service can be scalable. </li><li>✅ Biggest worry: Being able to scale service. </li><li>✅ Want to learn: Learn more coding, especially working with API data and generating dynamic emails.</li></ul></li><li>Biggest disappointment:  Not being able to work on LegUp Health full time</li><li>Biggest learning:  Sharing the journey at LegUp Health is better than going solo </li><li>Other updates:<ul><li> Tried bringing on another friend as a Marketing contractor, but he decided to take a full-time job before he ramped up </li></ul></li></ul></li></ul><p><strong>2022 Personal themes/goals</strong></p><ul><li>Tyler<ul><li>Plan for travel as part of relationship</li><li>Build more schedule flexibility so things can be done without needing willpower (e.g. exercise mid-day)</li></ul></li><li>Rick<ul><li>Reprioritize daily personal health habits (write/exercise before family wakes up, daily calorie tracking)</li><li>Spend more quality time with Sable (have a date most weeks) and Oliver (take on errands)</li></ul></li></ul><p><strong>2022 Professional themes/goals</strong></p><ul><li>Tyler<ul><li>Theme: Spend more time working, but on my own terms</li><li>Make space to do more individual contributor design work</li><li>Other things<ul><li>Release 3.9 design</li><li>Two blog post-worthy releases per quarter</li><li>By end of year, have an equal balance of tech debt, core CRM, strategy, and product-led growth work on the dev team</li><li>Run the coding fellowship</li></ul></li></ul></li><li>Rick<ul><li>Support the growth of LeUp Health<ul><li>Structure a partnership and financial plan that enables JD to go full-time</li><li>Grow the business to 400 clients</li><li>Fully automate the new user onboarding experience</li></ul></li><li>Help scale Windfall the right way <ul><li>Prioritize both performance and people</li><li>Be a team player</li><li>Deliver on my responsibilities</li></ul></li></ul></li></ul><p><strong>Biggest worry</strong></p><ul><li>Tyler: Growth slowed in 2021. Will it come back?</li><li>Rick: Retaining JD for the long term</li></ul><p><strong>What do we want to learn?</strong></p><ul><li>Tyler: More professional visual design</li><li>Rick: First principles of leading others (e.g. influence, motivation, habits, trust, negotiation, communication, and decision-making)</li></ul><p><strong>Predictions</strong></p><ul><li>Last year<ul><li>Tyler: ❌ San Francisco will become a good place for early-stage startups again</li><li>Rick: ❓ Asynchronous video will become big in professional settings</li></ul></li><li>Next year<ul><li>Tyler: The world will be less interested in speculative bubbles (NFTs, meme stocks, etc.)</li><li>Rick: VR headset use is going to become as common as playing a Wii</li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 20 Jan 2022 19:27:09 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/abcc4c86/58cbcdb9.mp3" length="83366095" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>5055</itunes:duration>
      <itunes:summary>The rumors were true. Startup to Last is back, and we're starting out with a recap of 2021 and a look forward to 2022.</itunes:summary>
      <itunes:subtitle>The rumors were true. Startup to Last is back, and we're starting out with a recap of 2021 and a look forward to 2022.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The final episode</title>
      <itunes:episode>109</itunes:episode>
      <podcast:episode>109</podcast:episode>
      <itunes:title>The final episode</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">85c22cef-9137-43fa-91c3-9b2858dd9332</guid>
      <link>https://share.transistor.fm/s/2367386f</link>
      <description>
        <![CDATA[<p>This is our last episode. Thanks to everyone who has listened and supported us over the last couple years. We're going to miss you 😢</p><p>Topics in this episode:</p><ul><li>Rick accepted a new job. What does that mean for LegUp Health?</li><li>Rick finished migrating his help site to Webflow.</li><li>Rick notified his free users that the free service is shutting down.</li><li>Tyler talks about compounding and what it means for thinking about the future.</li><li>We discuss how it might be harder to start a company these days because there are so many success stories that are hard to live up to.</li><li>We discuss <a href="https://datafetcher.com/">Datafetcher.com</a> as a nice no-code tool.</li><li>We discuss the build vs. buy tradeoffs.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This is our last episode. Thanks to everyone who has listened and supported us over the last couple years. We're going to miss you 😢</p><p>Topics in this episode:</p><ul><li>Rick accepted a new job. What does that mean for LegUp Health?</li><li>Rick finished migrating his help site to Webflow.</li><li>Rick notified his free users that the free service is shutting down.</li><li>Tyler talks about compounding and what it means for thinking about the future.</li><li>We discuss how it might be harder to start a company these days because there are so many success stories that are hard to live up to.</li><li>We discuss <a href="https://datafetcher.com/">Datafetcher.com</a> as a nice no-code tool.</li><li>We discuss the build vs. buy tradeoffs.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 17 Aug 2021 17:13:37 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/2367386f/5405f0b9.mp3" length="55378261" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3128</itunes:duration>
      <itunes:summary>We've got some bittersweet news. Rick has accepted a new job which isn't really a fit for the topics we discuss on this podcast. Because of that, we've decided that this will be our last week recording. We'll dive into all of that during this episode.</itunes:summary>
      <itunes:subtitle>We've got some bittersweet news. Rick has accepted a new job which isn't really a fit for the topics we discuss on this podcast. Because of that, we've decided that this will be our last week recording. We'll dive into all of that during this episode.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Sustainability starts with planning</title>
      <itunes:episode>108</itunes:episode>
      <podcast:episode>108</podcast:episode>
      <itunes:title>Sustainability starts with planning</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">fc161a5b-e776-4449-84bc-c483c204257d</guid>
      <link>https://share.transistor.fm/s/ad4c20a9</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick is canceling his CRM subscription.</li><li>Tyler is considering where his newsletter fits into his overall plan.</li><li>Based on our conversation last week, Rick has new clarity around the future of LegUp Health.</li><li>Tyler explains how LACRM came up with their long-term product roadmap.</li><li>Rick is going through continuing education.</li><li>We discuss some touchy feely things related to the passage of time.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick is canceling his CRM subscription.</li><li>Tyler is considering where his newsletter fits into his overall plan.</li><li>Based on our conversation last week, Rick has new clarity around the future of LegUp Health.</li><li>Tyler explains how LACRM came up with their long-term product roadmap.</li><li>Rick is going through continuing education.</li><li>We discuss some touchy feely things related to the passage of time.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 10 Aug 2021 18:00:49 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/ad4c20a9/c5af6997.mp3" length="56304428" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3219</itunes:duration>
      <itunes:summary>This week, many of our topics have a common theme: How do you put a plan together to run a sustainable company? I mean, this podcast is called "Startup to last" so I guess it makes sense for us to talk about that from time to time.</itunes:summary>
      <itunes:subtitle>This week, many of our topics have a common theme: How do you put a plan together to run a sustainable company? I mean, this podcast is called "Startup to last" so I guess it makes sense for us to talk about that from time to time.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What to cut and what to keep</title>
      <itunes:episode>107</itunes:episode>
      <podcast:episode>107</podcast:episode>
      <itunes:title>What to cut and what to keep</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ac2b795c-38f5-47fb-ba32-3ebb7ba0db47</guid>
      <link>https://share.transistor.fm/s/33bb31fd</link>
      <description>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Less Annoying CRM is back to remote-first because of the new wave of the virus.</li><li>LACRM had a new developer start this week.</li><li>Rick is thinking about how to simplify his business. Specifically, what can he cut?</li><li>We discuss what it means to be a calm company. Or is that even the goal?</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Less Annoying CRM is back to remote-first because of the new wave of the virus.</li><li>LACRM had a new developer start this week.</li><li>Rick is thinking about how to simplify his business. Specifically, what can he cut?</li><li>We discuss what it means to be a calm company. Or is that even the goal?</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 05 Aug 2021 17:18:13 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/33bb31fd/b0ba6dcf.mp3" length="61491168" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3481</itunes:duration>
      <itunes:summary>This week, we talk about simplifying a business. How do you know what complexity is important to the business, and what can get cut?</itunes:summary>
      <itunes:subtitle>This week, we talk about simplifying a business. How do you know what complexity is important to the business, and what can get cut?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Home runs vs. consistency</title>
      <itunes:episode>106</itunes:episode>
      <podcast:episode>106</podcast:episode>
      <itunes:title>Home runs vs. consistency</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0f2cbbfc-6e0c-4c5e-b12c-aa415cd92e55</guid>
      <link>https://share.transistor.fm/s/8a751ec0</link>
      <description>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Tyler hit 2,000 Twitter followers, and we discuss how Twitter is a hits-based business which doesn't suit Tyler's strengths.</li><li>Rick gives an update on his personal website and newsletter optimization efforts.</li><li>Rick reached the first page on an important search term.</li><li>Less Annoying CRM is tweaking the format of help articles to appeal more the the easily distractible internet user.</li><li>Rick has finished his javascript course.</li><li>Tyler discusses the LACRM product roadmap.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this episode:</p><ul><li>Tyler hit 2,000 Twitter followers, and we discuss how Twitter is a hits-based business which doesn't suit Tyler's strengths.</li><li>Rick gives an update on his personal website and newsletter optimization efforts.</li><li>Rick reached the first page on an important search term.</li><li>Less Annoying CRM is tweaking the format of help articles to appeal more the the easily distractible internet user.</li><li>Rick has finished his javascript course.</li><li>Tyler discusses the LACRM product roadmap.</li></ul>]]>
      </content:encoded>
      <pubDate>Mon, 26 Jul 2021 17:03:17 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/8a751ec0/57016d81.mp3" length="45867104" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2514</itunes:duration>
      <itunes:summary>This week, we discuss the difference between things that require big one-time achievements vs things that require lots of gradual, consistent improvement. Let's go.</itunes:summary>
      <itunes:subtitle>This week, we discuss the difference between things that require big one-time achievements vs things that require lots of gradual, consistent improvement. Let's go.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Throwing things at the wall to see what sticks</title>
      <itunes:episode>105</itunes:episode>
      <podcast:episode>105</podcast:episode>
      <itunes:title>Throwing things at the wall to see what sticks</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">13ae37bb-9ea0-461b-b7ea-7d55cd45ac2a</guid>
      <link>https://share.transistor.fm/s/31bf716f</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler had fun with a once-per-year football bet, and Rick had to put in a full day of dad duty.</li><li>Tyler is considering taking the ShiftNudge design course to get better at design. He also purchased a license to <a href="https://tailwindui.com/">Tailwind UI</a> so he can copy from better designers.</li><li>LACRM is tweaking it's policy that everyone at the company must do an hour or support each week.</li><li>Rick reflects on the value he gets from both writing and reading personal newsletters.</li><li>LACRM is tweaking it's policy around employee conversation, partially based on a conversation we had on this podcast a couple weeks ago.</li><li><a href="https://mixergy.com/interviews/less-annoying-crm-with-tyler-king/">Tyler's Mixergy interview</a> is live.</li><li>Now that Rick has a sense of what is and isn't working at his business, he wants to simplify which will mean cutting some current complexity away.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler had fun with a once-per-year football bet, and Rick had to put in a full day of dad duty.</li><li>Tyler is considering taking the ShiftNudge design course to get better at design. He also purchased a license to <a href="https://tailwindui.com/">Tailwind UI</a> so he can copy from better designers.</li><li>LACRM is tweaking it's policy that everyone at the company must do an hour or support each week.</li><li>Rick reflects on the value he gets from both writing and reading personal newsletters.</li><li>LACRM is tweaking it's policy around employee conversation, partially based on a conversation we had on this podcast a couple weeks ago.</li><li><a href="https://mixergy.com/interviews/less-annoying-crm-with-tyler-king/">Tyler's Mixergy interview</a> is live.</li><li>Now that Rick has a sense of what is and isn't working at his business, he wants to simplify which will mean cutting some current complexity away.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 20 Jul 2021 18:26:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/31bf716f/edf62f91.mp3" length="65033696" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3638</itunes:duration>
      <itunes:summary>This week, we discuss whether or not Rick can cut out some of the complexity from his business now that he knows what's working and what's not.</itunes:summary>
      <itunes:subtitle>This week, we discuss whether or not Rick can cut out some of the complexity from his business now that he knows what's working and what's not.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The thing about utopias is that they're not real</title>
      <itunes:episode>104</itunes:episode>
      <podcast:episode>104</podcast:episode>
      <itunes:title>The thing about utopias is that they're not real</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">bbeaf77b-8095-4b7c-8071-6a4e686cee0e</guid>
      <link>https://share.transistor.fm/s/391e4942</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick launched <a href="https://www.legupbenefits.com/">LegUpBenefits.com</a>.</li><li>We discuss Rick's new no-code tool: Outseta.</li><li>Less Annoying CRM has a new developer starting next month.</li><li>Tyler has refined his approach to writing internal documentation, and Rick makes a fantastic analogy.</li><li>Tyler's co-founder/brother will be in town next week.</li><li>Rick wants to keep practicing coding so his skills don't deteriorate.</li><li>Rick is taking a break from podcasts.</li><li>Tyler wants Rick's help to teach the coding fellows about no-code use cases.</li><li>We discuss Rick's notes on <a href="https://www.ricklindquist.com/notes/anything-you-want">Anything You Want</a> which leads to a conversation about whether startup utopias are real.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick launched <a href="https://www.legupbenefits.com/">LegUpBenefits.com</a>.</li><li>We discuss Rick's new no-code tool: Outseta.</li><li>Less Annoying CRM has a new developer starting next month.</li><li>Tyler has refined his approach to writing internal documentation, and Rick makes a fantastic analogy.</li><li>Tyler's co-founder/brother will be in town next week.</li><li>Rick wants to keep practicing coding so his skills don't deteriorate.</li><li>Rick is taking a break from podcasts.</li><li>Tyler wants Rick's help to teach the coding fellows about no-code use cases.</li><li>We discuss Rick's notes on <a href="https://www.ricklindquist.com/notes/anything-you-want">Anything You Want</a> which leads to a conversation about whether startup utopias are real.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 13 Jul 2021 17:23:11 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/391e4942/13234943.mp3" length="63585775" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3667</itunes:duration>
      <itunes:summary>This week, we discuss how building a business is like building your own personal utopia. Or maybe that's a fantasy.</itunes:summary>
      <itunes:subtitle>This week, we discuss how building a business is like building your own personal utopia. Or maybe that's a fantasy.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Sharing profit with employees</title>
      <itunes:episode>103</itunes:episode>
      <podcast:episode>103</podcast:episode>
      <itunes:title>Sharing profit with employees</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">fa2d5228-1cbb-4324-81af-841bbab9cc45</guid>
      <link>https://share.transistor.fm/s/a7f53cd6</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick took some time off, but is wondering if he earned it.</li><li>Tyler wrote five blog posts in one day, and wonders if this should be the new approach to blogging.</li><li>Rick decided to wait for Memberstack updates before taking on a coding project he was planning.</li><li>Rick is using <a href="https://www.outseta.com/">Outseta</a> for his next technical project to diversify away from Memberstack. He plans to have the done in the next week.</li><li>Rick is still waiting to decide how to handle the API vendor that closed down his account.</li><li>Tyler is diving into design and is interested in improving his skills.</li><li>Tyler has found a couple promising use cases for his new iPad which he mostly hates.</li><li>The big topic for this week: What are ways a company can fairly share profits with employees? Specifically, is it better to pay current employees more, or hire more people to spread the wealth around.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick took some time off, but is wondering if he earned it.</li><li>Tyler wrote five blog posts in one day, and wonders if this should be the new approach to blogging.</li><li>Rick decided to wait for Memberstack updates before taking on a coding project he was planning.</li><li>Rick is using <a href="https://www.outseta.com/">Outseta</a> for his next technical project to diversify away from Memberstack. He plans to have the done in the next week.</li><li>Rick is still waiting to decide how to handle the API vendor that closed down his account.</li><li>Tyler is diving into design and is interested in improving his skills.</li><li>Tyler has found a couple promising use cases for his new iPad which he mostly hates.</li><li>The big topic for this week: What are ways a company can fairly share profits with employees? Specifically, is it better to pay current employees more, or hire more people to spread the wealth around.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 06 Jul 2021 17:15:33 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/a7f53cd6/96b86759.mp3" length="55631119" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3231</itunes:duration>
      <itunes:summary>This week we get a bit philosophical. If a business has extra profits, how can they be fairly shared with employees and other stakeholders?</itunes:summary>
      <itunes:subtitle>This week we get a bit philosophical. If a business has extra profits, how can they be fairly shared with employees and other stakeholders?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>When platform risk goes wrong</title>
      <itunes:episode>102</itunes:episode>
      <podcast:episode>102</podcast:episode>
      <itunes:title>When platform risk goes wrong</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c220d273-24b3-40c3-840c-6f6422f31831</guid>
      <link>https://share.transistor.fm/s/b00e82e7</link>
      <description>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Tyler was interviewed to be on Mixergy, but didn't think he did a great job.</li><li>Rick is adjusting his routine now that he has a kid to take care of.</li><li>Rick enrolled in a new javascript course to hone his skills.</li><li>Tyler's previous positive results converting website visitors to his newsletter have turned to failure. No one is signing up.</li><li>Tyler attended Less Annoying CRM's first leadership team meeting.</li><li>Tyler had his first person finish building a website based on his online course.</li><li>Tyler (geez, enough with updates from Tyler, right?) is thinking through putting a limitation on LACRM.</li><li>Tyler (seriously, stop) took a day to help his dad with a new project.</li><li>Rick had a big coding win and finished two projects...</li><li>...just in time for one of his API vendors to close down his account, so the projects don't really work anymore. We discuss how Rick should respond.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Tyler was interviewed to be on Mixergy, but didn't think he did a great job.</li><li>Rick is adjusting his routine now that he has a kid to take care of.</li><li>Rick enrolled in a new javascript course to hone his skills.</li><li>Tyler's previous positive results converting website visitors to his newsletter have turned to failure. No one is signing up.</li><li>Tyler attended Less Annoying CRM's first leadership team meeting.</li><li>Tyler had his first person finish building a website based on his online course.</li><li>Tyler (geez, enough with updates from Tyler, right?) is thinking through putting a limitation on LACRM.</li><li>Tyler (seriously, stop) took a day to help his dad with a new project.</li><li>Rick had a big coding win and finished two projects...</li><li>...just in time for one of his API vendors to close down his account, so the projects don't really work anymore. We discuss how Rick should respond.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 29 Jun 2021 17:17:28 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/b00e82e7/f8f3361a.mp3" length="63765538" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3726</itunes:duration>
      <itunes:summary>One of Rick's API vendors shut down his account without warning, which throws a wrench in his productized service. This week, we discuss how he should respond.</itunes:summary>
      <itunes:subtitle>One of Rick's API vendors shut down his account without warning, which throws a wrench in his productized service. This week, we discuss how he should respond.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>When churn and word of mouth cancel each other out</title>
      <itunes:episode>101</itunes:episode>
      <podcast:episode>101</podcast:episode>
      <itunes:title>When churn and word of mouth cancel each other out</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">180b479a-b22b-4a7a-a522-3a5614ddf947</guid>
      <link>https://share.transistor.fm/s/1153f87a</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler has a new iPad and doesn't know what it's good for.</li><li>Rick has added a client through word of mouth, and we discuss how churn and word of mouth are constantly battling with one another.</li><li>Rick has resolved a major issue one of his clients had with their dental insurance. Crisis averted.</li><li>Tyler has been working on the wrong things, and is trying to correct that.</li><li>We discuss Less Annoying CRM's new leadership team.</li><li>Rick is applying his new javascript skills to his Airtable data.</li><li>Tyler is writing blog posts in a new way: First write the tweet storm, then write the blog post.</li><li>We discuss Earnest Capital's rebranding to <a href="https://calmfund.com/">Calm Company Fund</a>.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler has a new iPad and doesn't know what it's good for.</li><li>Rick has added a client through word of mouth, and we discuss how churn and word of mouth are constantly battling with one another.</li><li>Rick has resolved a major issue one of his clients had with their dental insurance. Crisis averted.</li><li>Tyler has been working on the wrong things, and is trying to correct that.</li><li>We discuss Less Annoying CRM's new leadership team.</li><li>Rick is applying his new javascript skills to his Airtable data.</li><li>Tyler is writing blog posts in a new way: First write the tweet storm, then write the blog post.</li><li>We discuss Earnest Capital's rebranding to <a href="https://calmfund.com/">Calm Company Fund</a>.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 22 Jun 2021 17:01:58 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1153f87a/bd77df72.mp3" length="49050906" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2769</itunes:duration>
      <itunes:summary>This week, we talking about what happens when churn and word of mouth cancel each other out, what we're doing to focus on the right types of work, and more.</itunes:summary>
      <itunes:subtitle>This week, we talking about what happens when churn and word of mouth cancel each other out, what we're doing to focus on the right types of work, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What we've learned about podcasting after 100 episodes</title>
      <itunes:episode>100</itunes:episode>
      <podcast:episode>100</podcast:episode>
      <itunes:title>What we've learned about podcasting after 100 episodes</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5b18413f-6e58-408e-922d-23f85b10e3a8</guid>
      <link>https://share.transistor.fm/s/563f2572</link>
      <description>
        <![CDATA[<ul><li>Tyler has a new mic.</li><li>Tyler is in the middle of the final round of interviews for his new dev hire, and he's starting to plan onboarding.</li><li>We discuss whether to put a new LACRM content project on the main lessannoyingcrm.com domain, or a separate mini-site.</li><li>Rick finished taking his javascript course.</li><li>Rick's dad is in town, and he's taking a bit of time off work.</li><li>We discuss a trick for getting people to complete online courses.</li><li>We reflect on what we've learned after recording 100 episodes of this podcast.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<ul><li>Tyler has a new mic.</li><li>Tyler is in the middle of the final round of interviews for his new dev hire, and he's starting to plan onboarding.</li><li>We discuss whether to put a new LACRM content project on the main lessannoyingcrm.com domain, or a separate mini-site.</li><li>Rick finished taking his javascript course.</li><li>Rick's dad is in town, and he's taking a bit of time off work.</li><li>We discuss a trick for getting people to complete online courses.</li><li>We reflect on what we've learned after recording 100 episodes of this podcast.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 15 Jun 2021 17:34:18 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/563f2572/3409c38d.mp3" length="62371540" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3809</itunes:duration>
      <itunes:summary>We're going to be a bit self-indulgent this week. This is our 100th episode, and so in this episode, we reflect on the experience and share what we've learned.</itunes:summary>
      <itunes:subtitle>We're going to be a bit self-indulgent this week. This is our 100th episode, and so in this episode, we reflect on the experience and share what we've learned.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Content marketing: Putting all our eggs in one basket</title>
      <itunes:episode>99</itunes:episode>
      <podcast:episode>99</podcast:episode>
      <itunes:title>Content marketing: Putting all our eggs in one basket</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">849a96b2-1fe2-4bb0-baba-2563bb78241a</guid>
      <link>https://share.transistor.fm/s/6fb39fa3</link>
      <description>
        <![CDATA[<p>Topics covered this week:</p><ul><li>We selfishly discuss larger themes we've covered on the podcast which might make for good topics on the Indie Hackers podcast.</li><li>Tyler's newsletter signups have increased since changing the call-to-action.</li><li>Rick lost another LegUp Health client due to unavoidable churn.</li><li>Tyler has a content idea centered around CRM pricing.</li><li>Tyler wants to do engineering as marketing but doesn't have any good ideas.</li><li>Rick is almost done learning javascript.</li><li>Rick has his first coding projects lined up.</li><li>We discuss the new Stripe payment links.</li><li>We revisit last week's topic because a listener called in with a new thought on the topic.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics covered this week:</p><ul><li>We selfishly discuss larger themes we've covered on the podcast which might make for good topics on the Indie Hackers podcast.</li><li>Tyler's newsletter signups have increased since changing the call-to-action.</li><li>Rick lost another LegUp Health client due to unavoidable churn.</li><li>Tyler has a content idea centered around CRM pricing.</li><li>Tyler wants to do engineering as marketing but doesn't have any good ideas.</li><li>Rick is almost done learning javascript.</li><li>Rick has his first coding projects lined up.</li><li>We discuss the new Stripe payment links.</li><li>We revisit last week's topic because a listener called in with a new thought on the topic.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 08 Jun 2021 17:17:20 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/6fb39fa3/00ce5291.mp3" length="53827197" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3273</itunes:duration>
      <itunes:summary>This week, we talk about an idea we have at Less Annoying CRM to do content marketing all focused around one really good piece of content rather than our normal strategy of putting out lots of little stuff. </itunes:summary>
      <itunes:subtitle>This week, we talk about an idea we have at Less Annoying CRM to do content marketing all focused around one really good piece of content rather than our normal strategy of putting out lots of little stuff. </itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What does a $100k/year support person look like?</title>
      <itunes:episode>98</itunes:episode>
      <podcast:episode>98</podcast:episode>
      <itunes:title>What does a $100k/year support person look like?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">41151052-e52f-4e1e-ab62-cf138941f9ed</guid>
      <link>https://share.transistor.fm/s/330ed055</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler asks Rick how he configured the call-to-action for his newsletter on his blog.</li><li>Tyler is adding a curated list of links to his newsletter.</li><li>Tyler overcame writers block and wrote his first support-focused blog post.</li><li>Rick is curious what a highly-compensated support rep might look like at LegUp Health.</li><li>Rick started paying for Notion.</li><li>Tyler gives a shout-out to <a href="https://savvycal.com/">SavvyCal</a>.</li><li>We take a listener question about how to reach customers who don't have online communities.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler asks Rick how he configured the call-to-action for his newsletter on his blog.</li><li>Tyler is adding a curated list of links to his newsletter.</li><li>Tyler overcame writers block and wrote his first support-focused blog post.</li><li>Rick is curious what a highly-compensated support rep might look like at LegUp Health.</li><li>Rick started paying for Notion.</li><li>Tyler gives a shout-out to <a href="https://savvycal.com/">SavvyCal</a>.</li><li>We take a listener question about how to reach customers who don't have online communities.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 01 Jun 2021 17:18:42 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/330ed055/1c40b185.mp3" length="53670736" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3166</itunes:duration>
      <itunes:summary>This week, we discuss what the role of a highly skilled, highly compensated support person would be. Let's go.</itunes:summary>
      <itunes:subtitle>This week, we discuss what the role of a highly skilled, highly compensated support person would be. Let's go.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Can a course business succeed even if no one finishes them?</title>
      <itunes:episode>97</itunes:episode>
      <podcast:episode>97</podcast:episode>
      <itunes:title>Can a course business succeed even if no one finishes them?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">1ba9f06b-2000-4eab-a571-4c53d51ab2f7</guid>
      <link>https://share.transistor.fm/s/238afc57</link>
      <description>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Apparently online courses have a very low completion rate, but maybe that's ok?</li><li>Rick is learning more about javascript and has a few questions.</li><li>Rick is taking a vacation where he'll fully unplug.</li><li>Tyler gives some learnings from the recent enterprise deal that LACRM closed.</li><li>Tyler has the interview process figured out for LACRM's next hire.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics in this episode:</p><ul><li>Apparently online courses have a very low completion rate, but maybe that's ok?</li><li>Rick is learning more about javascript and has a few questions.</li><li>Rick is taking a vacation where he'll fully unplug.</li><li>Tyler gives some learnings from the recent enterprise deal that LACRM closed.</li><li>Tyler has the interview process figured out for LACRM's next hire.</li></ul>]]>
      </content:encoded>
      <pubDate>Tue, 25 May 2021 16:53:19 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/238afc57/23f4d913.mp3" length="37711296" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2300</itunes:duration>
      <itunes:summary>This week, we dive into one of the big drawbacks of online courses: That not very many people actually complete them.</itunes:summary>
      <itunes:subtitle>This week, we dive into one of the big drawbacks of online courses: That not very many people actually complete them.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Making your first hire</title>
      <itunes:episode>96</itunes:episode>
      <podcast:episode>96</podcast:episode>
      <itunes:title>Making your first hire</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">71055600-f1e1-455f-afd4-347e55276cd3</guid>
      <link>https://share.transistor.fm/s/da2fa55c</link>
      <description>
        <![CDATA[This week, we answer a few listener questions about how to make your first hire.]]>
      </description>
      <content:encoded>
        <![CDATA[This week, we answer a few listener questions about how to make your first hire.]]>
      </content:encoded>
      <pubDate>Tue, 18 May 2021 18:37:33 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/da2fa55c/3313cf97.mp3" length="58927905" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3579</itunes:duration>
      <itunes:summary>This week, we answer a few listener questions about how to make your first hire.</itunes:summary>
      <itunes:subtitle>This week, we answer a few listener questions about how to make your first hire.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>When customer expectations aren't met</title>
      <itunes:episode>95</itunes:episode>
      <podcast:episode>95</podcast:episode>
      <itunes:title>When customer expectations aren't met</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">639baa4f-5726-4c86-ba03-6cdc323b6d64</guid>
      <link>https://share.transistor.fm/s/3a6998e6</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick crossed 200 subscribers for his personal newsletter.</li><li>Rick gives an update on some recent milestones related to this podcast.</li><li>Rick has been doing <a href="https://beginnerjavascript.com/">Wes Bos's beginner javascript course</a> and is learning a lot.</li><li>Tyler is on vacation, and is mostly just taking it easy.</li><li>We discuss Notion's new API.</li><li>Rick seriously sprained his ankle.</li><li>Rick is dealing with a customer who is disappointed.</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick crossed 200 subscribers for his personal newsletter.</li><li>Rick gives an update on some recent milestones related to this podcast.</li><li>Rick has been doing <a href="https://beginnerjavascript.com/">Wes Bos's beginner javascript course</a> and is learning a lot.</li><li>Tyler is on vacation, and is mostly just taking it easy.</li><li>We discuss Notion's new API.</li><li>Rick seriously sprained his ankle.</li><li>Rick is dealing with a customer who is disappointed.</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 13 May 2021 17:17:38 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/3a6998e6/e37f95fc.mp3" length="42680608" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2482</itunes:duration>
      <itunes:summary>This week, we discuss a situation Rick is dealing with where a customer is disappointed and feels that their expectations weren't met.</itunes:summary>
      <itunes:subtitle>This week, we discuss a situation Rick is dealing with where a customer is disappointed and feels that their expectations weren't met.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The Theory of Constraints</title>
      <itunes:episode>94</itunes:episode>
      <podcast:episode>94</podcast:episode>
      <itunes:title>The Theory of Constraints</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">56d2e633-e0c6-4cb4-8ff9-2cde83537337</guid>
      <link>https://share.transistor.fm/s/f652bbfa</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>We're using a tool called ZipMessage to collect listener questions. If there's something you'd like us to discuss on the podcast, leave us an audio recording of your question at <a href="https://zipmessage.com/tyler">zipmessage.com/tyler</a></li><li>Less Annoying CRM had a good April.</li><li>LACRM's average account size is going up slightly, but it's having a significant impact on revenue.</li><li>We discuss the theory of constraints, and how Rick can apply it to his next project.</li><li>We talk about interviewing software engineers, especially when people with different experience levels will be applying for the same position.</li><li>Rick finished a book on taking notes, and he gets it now.</li><li>Rick is enjoying the "two co-founders chatting" style podcasts (like this one)</li><li>Rick set up Coinbase and Robinhood accounts for fun.</li><li>We talk a bit more about the basecamp drama now that more news has come out.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>We're using a tool called ZipMessage to collect listener questions. If there's something you'd like us to discuss on the podcast, leave us an audio recording of your question at <a href="https://zipmessage.com/tyler">zipmessage.com/tyler</a></li><li>Less Annoying CRM had a good April.</li><li>LACRM's average account size is going up slightly, but it's having a significant impact on revenue.</li><li>We discuss the theory of constraints, and how Rick can apply it to his next project.</li><li>We talk about interviewing software engineers, especially when people with different experience levels will be applying for the same position.</li><li>Rick finished a book on taking notes, and he gets it now.</li><li>Rick is enjoying the "two co-founders chatting" style podcasts (like this one)</li><li>Rick set up Coinbase and Robinhood accounts for fun.</li><li>We talk a bit more about the basecamp drama now that more news has come out.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 06 May 2021 17:34:44 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f652bbfa/a9ae6675.mp3" length="68441602" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3886</itunes:duration>
      <itunes:summary>This week, we discuss the theory of constraints: A mental model for deciding what to focus on as an entrepreneur.</itunes:summary>
      <itunes:subtitle>This week, we discuss the theory of constraints: A mental model for deciding what to focus on as an entrepreneur.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The importance of internal communication</title>
      <itunes:episode>93</itunes:episode>
      <podcast:episode>93</podcast:episode>
      <itunes:title>The importance of internal communication</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">8993ac34-8225-48f5-aa56-2562a6c884f3</guid>
      <link>https://share.transistor.fm/s/2216462e</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>An effective, but maybe sleazy tactic for cold emails.</li><li><a href="https://www.legupbenefits.com/">LegUp Benefits</a> got its second paying customer.</li><li>Rick is done with SEO for now, and wrote 35 new pieces of content in April (holy shit!)</li><li>Rick is focusing on LegUp Benefits for the next six weeks.</li><li>Less Annoying CRM has <em>finally</em> closed a big enterprise deal they've been working on.</li><li>Tyler is about to start trying to hire a developer.</li><li>Less Annoying CRM's office setup is changing, and we discuss the importance of communicating changes carefully.</li><li>We discuss how to write content when you hit a wall.</li><li>Rick is dealing with unavoidable churn.</li><li>We talk for way too long about Basecamp's recent drama. We reach no conclusions. You can have a full refund for the amount you paid for this podcast if you're disappointed by that.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>An effective, but maybe sleazy tactic for cold emails.</li><li><a href="https://www.legupbenefits.com/">LegUp Benefits</a> got its second paying customer.</li><li>Rick is done with SEO for now, and wrote 35 new pieces of content in April (holy shit!)</li><li>Rick is focusing on LegUp Benefits for the next six weeks.</li><li>Less Annoying CRM has <em>finally</em> closed a big enterprise deal they've been working on.</li><li>Tyler is about to start trying to hire a developer.</li><li>Less Annoying CRM's office setup is changing, and we discuss the importance of communicating changes carefully.</li><li>We discuss how to write content when you hit a wall.</li><li>Rick is dealing with unavoidable churn.</li><li>We talk for way too long about Basecamp's recent drama. We reach no conclusions. You can have a full refund for the amount you paid for this podcast if you're disappointed by that.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 29 Apr 2021 17:30:14 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/2216462e/2fc3023b.mp3" length="70666510" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4033</itunes:duration>
      <itunes:summary>This week, we give a bunch of updates on what we're working on, and end with a long, rambly, inconclusive discussion about the recent Basecamp drama.</itunes:summary>
      <itunes:subtitle>This week, we give a bunch of updates on what we're working on, and end with a long, rambly, inconclusive discussion about the recent Basecamp drama.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Empowering employees to be leaders</title>
      <itunes:episode>92</itunes:episode>
      <podcast:episode>92</podcast:episode>
      <itunes:title>Empowering employees to be leaders</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">883a6fc4-ee5b-4fc1-8a21-5f7a097c00ae</guid>
      <link>https://share.transistor.fm/s/f3fb58db</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler gave an internal presentation at Less Annoying CRM and announced a few new things...</li><li>The office is being reopened in May.</li><li>There will be a new remote work policy in place.</li><li>A deep dive into how DEI (diversity, equity, and inclusion) fits into Less Annoying CRM's structure.</li><li>A new leadership team.</li><li>Rick is working on content and had a big SEO win.</li><li>We discuss Roam Research as a possible note-taking tool for Rick.</li><li>Rick recommends <a href="https://readwise.io/">Readwise.io</a> for converting Kindle notes into text.</li><li>We discuss schema markup as an SEO strategy.</li><li>Rick has made some improvements to <a href="https://www.ricklindquist.com/">ricklindquist.com</a>.</li><li>Tyler might have more free time soon and needs to figure out what to work on.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler gave an internal presentation at Less Annoying CRM and announced a few new things...</li><li>The office is being reopened in May.</li><li>There will be a new remote work policy in place.</li><li>A deep dive into how DEI (diversity, equity, and inclusion) fits into Less Annoying CRM's structure.</li><li>A new leadership team.</li><li>Rick is working on content and had a big SEO win.</li><li>We discuss Roam Research as a possible note-taking tool for Rick.</li><li>Rick recommends <a href="https://readwise.io/">Readwise.io</a> for converting Kindle notes into text.</li><li>We discuss schema markup as an SEO strategy.</li><li>Rick has made some improvements to <a href="https://www.ricklindquist.com/">ricklindquist.com</a>.</li><li>Tyler might have more free time soon and needs to figure out what to work on.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 22 Apr 2021 17:20:59 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f3fb58db/fcd5848f.mp3" length="67175480" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3821</itunes:duration>
      <itunes:summary>This week, we talk about some new announcements Tyler just made at Less Annoying CRM, including a new leadership team.</itunes:summary>
      <itunes:subtitle>This week, we talk about some new announcements Tyler just made at Less Annoying CRM, including a new leadership team.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Time management</title>
      <itunes:episode>91</itunes:episode>
      <podcast:episode>91</podcast:episode>
      <itunes:title>Time management</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">1233f11e-fc87-4637-adcf-51018385a920</guid>
      <link>https://share.transistor.fm/s/958975ec</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is reading a book called <a href="http://killingmarketing.com/">Killing Marketing</a>.</li><li>Rick is trying some time management hacks.</li><li>Tyler has a potential job candidate using his new approach to recruiting.</li><li>Less Annoying CRM had their "day of rest" where developers take over customer service for a day.</li><li>Rick is working on content and SEO for LegUp Health.</li><li>Rick has filed his taxes.</li><li>Rick gives a shoutout to a listener that makes <a href="https://mytracer.ai/">software that verifies financial transactions</a> who helped him with a question from last week.</li><li>We discuss Webflow's product roadmap.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Tyler is reading a book called <a href="http://killingmarketing.com/">Killing Marketing</a>.</li><li>Rick is trying some time management hacks.</li><li>Tyler has a potential job candidate using his new approach to recruiting.</li><li>Less Annoying CRM had their "day of rest" where developers take over customer service for a day.</li><li>Rick is working on content and SEO for LegUp Health.</li><li>Rick has filed his taxes.</li><li>Rick gives a shoutout to a listener that makes <a href="https://mytracer.ai/">software that verifies financial transactions</a> who helped him with a question from last week.</li><li>We discuss Webflow's product roadmap.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 15 Apr 2021 17:17:41 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/958975ec/16d60232.mp3" length="58061146" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3316</itunes:duration>
      <itunes:summary>This week, we talk about some time management hacks Rick is trying now that he has a baby to take care of.</itunes:summary>
      <itunes:subtitle>This week, we talk about some time management hacks Rick is trying now that he has a baby to take care of.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>$2k MRR</title>
      <itunes:episode>90</itunes:episode>
      <podcast:episode>90</podcast:episode>
      <itunes:title>$2k MRR</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">63270b1c-9c4a-4615-9f9a-a3652a6a9728</guid>
      <link>https://share.transistor.fm/s/44a09795</link>
      <description>
        <![CDATA[<p>Topics from this week:</p><ul><li>Rick has a baby!</li><li>Rick broke $2k MRR in March.</li><li>Tyler gives an update on his content marketing site.</li><li>Tyler is about to start recruiting a developer.</li><li>We talk about all the speculative bullshit going on right now (NFTs, GME, bitclout, etc.).</li><li>Rick feels pressure to narrow his focus now that he's a father.</li><li>We discuss how to implement an internal tool with no-code.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this week:</p><ul><li>Rick has a baby!</li><li>Rick broke $2k MRR in March.</li><li>Tyler gives an update on his content marketing site.</li><li>Tyler is about to start recruiting a developer.</li><li>We talk about all the speculative bullshit going on right now (NFTs, GME, bitclout, etc.).</li><li>Rick feels pressure to narrow his focus now that he's a father.</li><li>We discuss how to implement an internal tool with no-code.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 08 Apr 2021 17:14:55 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/44a09795/d19b2e74.mp3" length="59782317" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3390</itunes:duration>
      <itunes:summary>This week, we talk about Rick's latest milestone, how to hire a developer, and more.</itunes:summary>
      <itunes:subtitle>This week, we talk about Rick's latest milestone, how to hire a developer, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Jamming with Dru Riley from Trends.vc</title>
      <itunes:episode>89</itunes:episode>
      <podcast:episode>89</podcast:episode>
      <itunes:title>Jamming with Dru Riley from Trends.vc</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ae901aef-d357-43b0-b8bc-39145e2a6376</guid>
      <link>https://share.transistor.fm/s/5167e16b</link>
      <description>
        <![CDATA[<p>You can learn more about what Dru's working on on <a href="https://twitter.com/DruRly">Twitter</a> or at <a href="https://join.trends.vc/">Trends.vc</a>.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>You can learn more about what Dru's working on on <a href="https://twitter.com/DruRly">Twitter</a> or at <a href="https://join.trends.vc/">Trends.vc</a>.</p>]]>
      </content:encoded>
      <pubDate>Thu, 01 Apr 2021 13:41:05 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/5167e16b/bcf625be.mp3" length="55726775" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4582</itunes:duration>
      <itunes:summary>This is a special episode where Dru and Tyler "jam" on one of the topics for Dru's trends.vc reports.</itunes:summary>
      <itunes:subtitle>This is a special episode where Dru and Tyler "jam" on one of the topics for Dru's trends.vc reports.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Deep dive into an execution retreat</title>
      <itunes:episode>88</itunes:episode>
      <podcast:episode>88</podcast:episode>
      <itunes:title>Deep dive into an execution retreat</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ba472b4d-176b-4d86-a50c-96f9aed5f13c</guid>
      <link>https://share.transistor.fm/s/305e3fb2</link>
      <description>
        <![CDATA[Because Rick is taking some time off for parental leave, we recorded a special episode this week. Rick is about to do a week-long retreat to try to finish a major project before becoming a dad. We're going to spend this episode discussing how he can get the most out of the retreat.]]>
      </description>
      <content:encoded>
        <![CDATA[Because Rick is taking some time off for parental leave, we recorded a special episode this week. Rick is about to do a week-long retreat to try to finish a major project before becoming a dad. We're going to spend this episode discussing how he can get the most out of the retreat.]]>
      </content:encoded>
      <pubDate>Thu, 25 Mar 2021 17:16:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/305e3fb2/54ca1691.mp3" length="54835929" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3126</itunes:duration>
      <itunes:summary>Because Rick is taking some time off for parental leave, we recorded a special episode this week. Rick is about to do a week-long retreat to try to finish a major project before becoming a dad. We're going to spend this episode discussing how he can get the most out of the retreat.</itunes:summary>
      <itunes:subtitle>Because Rick is taking some time off for parental leave, we recorded a special episode this week. Rick is about to do a week-long retreat to try to finish a major project before becoming a dad. We're going to spend this episode discussing how he can get t</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Burnout</title>
      <itunes:episode>87</itunes:episode>
      <podcast:episode>87</podcast:episode>
      <itunes:title>Burnout</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e9059030-2cfe-4f1d-818e-f21bc3ff0e1d</guid>
      <link>https://share.transistor.fm/s/5e83db72</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick is feeling burnt out. We discuss how he noticed, and what he's doing to fix it.</li><li>Rick's baby is expected this next week, so the next two weeks of the podcast will be pre-recorded episodes.</li><li>Tyler is drowning in meetings.</li><li>Tyler gives an update on his new content site.</li><li>We talk a bit about SEO.</li><li>Rick is looking for two plugins to help with his Webflow site.</li><li>We have both received our first vaccine shots, and we discuss what it would look like to re-open an office.</li><li>Rick has realized how personal the information he needs from customers is, and how that impacts trust building.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick is feeling burnt out. We discuss how he noticed, and what he's doing to fix it.</li><li>Rick's baby is expected this next week, so the next two weeks of the podcast will be pre-recorded episodes.</li><li>Tyler is drowning in meetings.</li><li>Tyler gives an update on his new content site.</li><li>We talk a bit about SEO.</li><li>Rick is looking for two plugins to help with his Webflow site.</li><li>We have both received our first vaccine shots, and we discuss what it would look like to re-open an office.</li><li>Rick has realized how personal the information he needs from customers is, and how that impacts trust building.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 18 Mar 2021 17:15:04 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/5e83db72/9a267e3f.mp3" length="60190409" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3408</itunes:duration>
      <itunes:summary>This week, we talk about how to identify burnout, and what to do about it.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to identify burnout, and what to do about it.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Enterprise sales is just project management</title>
      <itunes:episode>86</itunes:episode>
      <podcast:episode>86</podcast:episode>
      <itunes:title>Enterprise sales is just project management</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ea417817-c265-48c9-8299-a1335ef0270c</guid>
      <link>https://share.transistor.fm/s/7da0f984</link>
      <description>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick breaks down how the new stimulus bill will impact health insurance and entrepreneurs.</li><li>Rick is putting his big project on hold until after paternity leave.</li><li>Tyler gives an update on Less Annoying Business.</li><li>We discuss enterprise sales, and how it's more about project management than convincing someone to buy.</li><li>We talk about Zapier's acquisition of Makerpad.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics this week:</p><ul><li>Rick breaks down how the new stimulus bill will impact health insurance and entrepreneurs.</li><li>Rick is putting his big project on hold until after paternity leave.</li><li>Tyler gives an update on Less Annoying Business.</li><li>We discuss enterprise sales, and how it's more about project management than convincing someone to buy.</li><li>We talk about Zapier's acquisition of Makerpad.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 11 Mar 2021 17:15:16 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7da0f984/dec61f20.mp3" length="61829498" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3551</itunes:duration>
      <itunes:summary>This week, we talk about what the new stimulus bill will mean for entrepreneurs, and we discuss some learnings from an ongoing enterprise sales project.</itunes:summary>
      <itunes:subtitle>This week, we talk about what the new stimulus bill will mean for entrepreneurs, and we discuss some learnings from an ongoing enterprise sales project.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What does Indie.vc's move mean for startup to last companies?</title>
      <itunes:episode>85</itunes:episode>
      <podcast:episode>85</podcast:episode>
      <itunes:title>What does Indie.vc's move mean for startup to last companies?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d16f57da-9a0e-4c6b-890e-78c57e8dba21</guid>
      <link>https://share.transistor.fm/s/d4acb202</link>
      <description>
        <![CDATA[<p>Topics discussed:</p><ul><li><a href="https://medium.com/@bryce/the-end-of-indie-6e1b92d90b09">Indie.vc is shutting down</a></li><li>Rick gives a revenue and churn update.</li><li>Rick is preparing for the birth of his first child, but has one more big project to finish first.</li><li>Tyler recaps the first week of results after launching <a href="https://www.lessannoyingbusiness.com/">Less Annoying Business</a> last week.</li><li>We discuss whether it makes sense to build an audience.</li><li>Tyler is trying to get help with Elasticsearch from his online community.</li><li>We discuss the long, slow SaaS ramp of death.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics discussed:</p><ul><li><a href="https://medium.com/@bryce/the-end-of-indie-6e1b92d90b09">Indie.vc is shutting down</a></li><li>Rick gives a revenue and churn update.</li><li>Rick is preparing for the birth of his first child, but has one more big project to finish first.</li><li>Tyler recaps the first week of results after launching <a href="https://www.lessannoyingbusiness.com/">Less Annoying Business</a> last week.</li><li>We discuss whether it makes sense to build an audience.</li><li>Tyler is trying to get help with Elasticsearch from his online community.</li><li>We discuss the long, slow SaaS ramp of death.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 04 Mar 2021 17:22:02 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/d4acb202/40d98bb2.mp3" length="61360306" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3354</itunes:duration>
      <itunes:summary>Earlier this week, Indie.VC, one of the main sources of financing for companies like the ones we run on this show, announced they're shutting down due to challenges finding financial backers. We discuss that, and much more on this episode.</itunes:summary>
      <itunes:subtitle>Earlier this week, Indie.VC, one of the main sources of financing for companies like the ones we run on this show, announced they're shutting down due to challenges finding financial backers. We discuss that, and much more on this episode.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Hardcore week building a content site</title>
      <itunes:episode>84</itunes:episode>
      <podcast:episode>84</podcast:episode>
      <itunes:title>Hardcore week building a content site</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">fa5ae54c-9cc7-4aaa-8929-51564ba1e9fb</guid>
      <link>https://share.transistor.fm/s/1bf5b77d</link>
      <description>
        <![CDATA[<p>Topics we covered today:</p><ul><li>Rick finished his goal for February of automating the monthly emails at Legup Health.</li><li>Tyler gives an update on his new <a href="https://www.lessannoyingbusiness.com/">small business advice</a> website. How do you like that link building I just did?</li><li>Tyler remembers how fast a project can move when you don't have legacy code slowing you down.</li><li>We discuss a variety of tools used to build a content site, especially Webflow and ConvertKit.</li><li>Tyler used Fiverr for the first time to hire a designer.</li><li>We discuss <a href="https://www.ricklindquist.com/blog/multitasking-for-motivation">multitasking for motivation</a>.</li><li>We both prefer creating content from our own personal voice rather than on behalf of the company.</li><li>We brainstorm what's next for Less Annoying Business/</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics we covered today:</p><ul><li>Rick finished his goal for February of automating the monthly emails at Legup Health.</li><li>Tyler gives an update on his new <a href="https://www.lessannoyingbusiness.com/">small business advice</a> website. How do you like that link building I just did?</li><li>Tyler remembers how fast a project can move when you don't have legacy code slowing you down.</li><li>We discuss a variety of tools used to build a content site, especially Webflow and ConvertKit.</li><li>Tyler used Fiverr for the first time to hire a designer.</li><li>We discuss <a href="https://www.ricklindquist.com/blog/multitasking-for-motivation">multitasking for motivation</a>.</li><li>We both prefer creating content from our own personal voice rather than on behalf of the company.</li><li>We brainstorm what's next for Less Annoying Business/</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 25 Feb 2021 17:19:58 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1bf5b77d/e12c9526.mp3" length="61722702" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3693</itunes:duration>
      <itunes:summary>This week, we talk about the strategy around Tyler's new content site</itunes:summary>
      <itunes:subtitle>This week, we talk about the strategy around Tyler's new content site</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Content marketing when you're not a domain expert</title>
      <itunes:episode>83</itunes:episode>
      <podcast:episode>83</podcast:episode>
      <itunes:title>Content marketing when you're not a domain expert</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">1bc31d26-7fbd-48a1-a7ef-8c7482c19ed9</guid>
      <link>https://share.transistor.fm/s/4d170a7a</link>
      <description>
        <![CDATA[<p>Topics discussed this week:</p><ul><li>Rick is learning more powerful no-code tricks with Zapier, and advancing his PHP knowledge.</li><li>We discuss the best way to learn how to write secure code.</li><li>Tyler is wrapping up a big project which involves setting deadlines. We discuss healthy vs. unhealthy deadlines.</li><li>Tyler is brainstorming content marketing approaches which is tough because he's not an expert on the topics his customers are most interested in.</li><li>We discuss Rick's learnings from Peter Drucker.</li><li>We talk about the idea of running an online competition</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics discussed this week:</p><ul><li>Rick is learning more powerful no-code tricks with Zapier, and advancing his PHP knowledge.</li><li>We discuss the best way to learn how to write secure code.</li><li>Tyler is wrapping up a big project which involves setting deadlines. We discuss healthy vs. unhealthy deadlines.</li><li>Tyler is brainstorming content marketing approaches which is tough because he's not an expert on the topics his customers are most interested in.</li><li>We discuss Rick's learnings from Peter Drucker.</li><li>We talk about the idea of running an online competition</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 18 Feb 2021 17:30:28 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/4d170a7a/16d13f3b.mp3" length="67416894" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3847</itunes:duration>
      <itunes:summary>This week, we talk about a the difficulties of content marketing when you're not a domain expert, healthy vs. unhealthy deadlines, and more.</itunes:summary>
      <itunes:subtitle>This week, we talk about a the difficulties of content marketing when you're not a domain expert, healthy vs. unhealthy deadlines, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Separating decision making from executing</title>
      <itunes:episode>82</itunes:episode>
      <podcast:episode>82</podcast:episode>
      <itunes:title>Separating decision making from executing</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">a2304700-7af8-4227-873f-38836b019acc</guid>
      <link>https://share.transistor.fm/s/2aba3632</link>
      <description>
        <![CDATA[<p>More topics:</p><ul><li>We discuss the <a href="https://microconf.com/sois-report-2021">state of independent SaaS</a> and what it means to have a very low payback period.</li><li>Rick has installed a development environment and is learning to code again.</li><li>Tyler is almost done getting ready to switch the LACRM marketing site to Webflow.</li><li>Tyler is considering trying out Mixpanel.</li><li>Salesforce is going more remote. What does that mean for San Francisco.</li><li>We discuss <a href="https://twitter.com/TylerMKing/status/1358553613287755780">Tyler's tweet thread</a> about his internal dashboards.</li><li>We talk about the <a href="https://twitter.com/trends_vc/status/1359555231051354117">Trends.vc report on competitor risk</a>.</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>More topics:</p><ul><li>We discuss the <a href="https://microconf.com/sois-report-2021">state of independent SaaS</a> and what it means to have a very low payback period.</li><li>Rick has installed a development environment and is learning to code again.</li><li>Tyler is almost done getting ready to switch the LACRM marketing site to Webflow.</li><li>Tyler is considering trying out Mixpanel.</li><li>Salesforce is going more remote. What does that mean for San Francisco.</li><li>We discuss <a href="https://twitter.com/TylerMKing/status/1358553613287755780">Tyler's tweet thread</a> about his internal dashboards.</li><li>We talk about the <a href="https://twitter.com/trends_vc/status/1359555231051354117">Trends.vc report on competitor risk</a>.</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 11 Feb 2021 17:28:49 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/2aba3632/2548486b.mp3" length="61965036" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3694</itunes:duration>
      <itunes:summary>This week we talk about the benefit of making decisions separately from executing on those decisions, whether or not it's risky to share internal metrics publicly, and more.</itunes:summary>
      <itunes:subtitle>This week we talk about the benefit of making decisions separately from executing on those decisions, whether or not it's risky to share internal metrics publicly, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Getting marketing ideas from Hubspot's acquisition of The Hustle</title>
      <itunes:episode>81</itunes:episode>
      <podcast:episode>81</podcast:episode>
      <itunes:title>Getting marketing ideas from Hubspot's acquisition of The Hustle</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">a388c744-9934-4542-9295-eb88232c27ec</guid>
      <link>https://share.transistor.fm/s/f8700d9b</link>
      <description>
        <![CDATA[<p>Other topics this week:</p><ul><li>Rick officially launched a "give back" program</li><li>Rick decided not to post internship openings until post-parental leave.</li><li>Rick wants to start a group focused on reaching local consumers.</li><li>Tyler is planning an at-home retreat.</li><li>Morale is a bit low as covid drags on.</li><li>We discuss a specific UI decision LACRM is facing.</li><li>We discuss aligning what you want to have happen with what will actually happen.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics this week:</p><ul><li>Rick officially launched a "give back" program</li><li>Rick decided not to post internship openings until post-parental leave.</li><li>Rick wants to start a group focused on reaching local consumers.</li><li>Tyler is planning an at-home retreat.</li><li>Morale is a bit low as covid drags on.</li><li>We discuss a specific UI decision LACRM is facing.</li><li>We discuss aligning what you want to have happen with what will actually happen.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 04 Feb 2021 17:23:29 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f8700d9b/a9eef98e.mp3" length="60514023" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3672</itunes:duration>
      <itunes:summary>This week, we talk about Hubspot's acquisition of The Hustle and how it gave us some new marketing ideas.</itunes:summary>
      <itunes:subtitle>This week, we talk about Hubspot's acquisition of The Hustle and how it gave us some new marketing ideas.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The paradox of success</title>
      <itunes:episode>80</itunes:episode>
      <podcast:episode>80</podcast:episode>
      <itunes:title>The paradox of success</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">4acc9077-945d-4668-95b6-e78b39e769a9</guid>
      <link>https://share.transistor.fm/s/933a6eb9</link>
      <description>
        <![CDATA[<p>Other topics this week:</p><ul><li>How Robinhood's recent controversy applies to Rick's business model.</li><li>Rick received his first cancelation.</li><li>Twitter acquired Revue.</li><li>Rick is working on a low-code solution to an automation issue.</li><li>Tyler is close to closing a deal with an enterprise client.</li><li>We discuss how to handle security audits (e.g. SOC 2 compliance) with enterprise customers.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics this week:</p><ul><li>How Robinhood's recent controversy applies to Rick's business model.</li><li>Rick received his first cancelation.</li><li>Twitter acquired Revue.</li><li>Rick is working on a low-code solution to an automation issue.</li><li>Tyler is close to closing a deal with an enterprise client.</li><li>We discuss how to handle security audits (e.g. SOC 2 compliance) with enterprise customers.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 28 Jan 2021 18:46:14 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/933a6eb9/0efd5165.mp3" length="57063466" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3442</itunes:duration>
      <itunes:summary>This week, we talk about a concept from a book Rick is reading.</itunes:summary>
      <itunes:subtitle>This week, we talk about a concept from a book Rick is reading.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Is building an audience worth it?</title>
      <itunes:episode>79</itunes:episode>
      <podcast:episode>79</podcast:episode>
      <itunes:title>Is building an audience worth it?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">97e1e951-4245-488a-874f-24ddf881fa45</guid>
      <link>https://share.transistor.fm/s/bb2bfbd4</link>
      <description>
        <![CDATA[<p>Other topics this week:</p><ul><li>Less Annoying CRM hit $3 million ARR, and the tweet about it got a lot of engagement.</li><li>Rick paid out referral rewards to his clients.</li><li>Rick explains his buyer journey exercise.</li><li>Rick reflects on the value of customer appreciation.</li><li>Tyler has been a guest on several other podcasts.</li><li>We discuss how to react when a competitor launches.</li><li>We discuss the idea of building buffer into everything we do, and how it relates to the startup to last philosophy.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics this week:</p><ul><li>Less Annoying CRM hit $3 million ARR, and the tweet about it got a lot of engagement.</li><li>Rick paid out referral rewards to his clients.</li><li>Rick explains his buyer journey exercise.</li><li>Rick reflects on the value of customer appreciation.</li><li>Tyler has been a guest on several other podcasts.</li><li>We discuss how to react when a competitor launches.</li><li>We discuss the idea of building buffer into everything we do, and how it relates to the startup to last philosophy.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 21 Jan 2021 17:23:06 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/bb2bfbd4/b5812367.mp3" length="63615528" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3822</itunes:duration>
      <itunes:summary>This week, we talk about whether or not building a personal audience is a good way to attract customers.</itunes:summary>
      <itunes:subtitle>This week, we talk about whether or not building a personal audience is a good way to attract customers.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The future of no-code</title>
      <itunes:episode>78</itunes:episode>
      <podcast:episode>78</podcast:episode>
      <itunes:title>The future of no-code</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0a502251-d5e1-4bd3-bf0b-21102b182b58</guid>
      <link>https://share.transistor.fm/s/09105902</link>
      <description>
        <![CDATA[<p>Other topics this week:</p><ul><li>Tyler reviews what he learned from last week's DDoS attack.</li><li>Rick has planned out the year and feels good about his ability to get it done.</li><li>Rick is allocating 50% of his time to promotion and 50% to automating his product.</li><li>Tyler is about to start teaching a design course.</li><li>LACRM is close to finishing a migration to Webflow.</li><li>We discuss Clubhouse.</li><li>Tyler is getting a Peloton.</li><li>Rick is experiencing anti-depressant withdrawal syndrome.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics this week:</p><ul><li>Tyler reviews what he learned from last week's DDoS attack.</li><li>Rick has planned out the year and feels good about his ability to get it done.</li><li>Rick is allocating 50% of his time to promotion and 50% to automating his product.</li><li>Tyler is about to start teaching a design course.</li><li>LACRM is close to finishing a migration to Webflow.</li><li>We discuss Clubhouse.</li><li>Tyler is getting a Peloton.</li><li>Rick is experiencing anti-depressant withdrawal syndrome.</li></ul>]]>
      </content:encoded>
      <pubDate>Fri, 15 Jan 2021 15:04:44 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/09105902/939f7226.mp3" length="56646636" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3453</itunes:duration>
      <itunes:summary>This week, we talk about what the world of no-code looks like now that Webflow has raised a massive round of funding.</itunes:summary>
      <itunes:subtitle>This week, we talk about what the world of no-code looks like now that Webflow has raised a massive round of funding.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What it's like to get DDoSed</title>
      <itunes:episode>77</itunes:episode>
      <podcast:episode>77</podcast:episode>
      <itunes:title>What it's like to get DDoSed</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">502368f7-95d9-4bf7-bdb2-3f0526174a96</guid>
      <link>https://share.transistor.fm/s/56180f66</link>
      <description>
        <![CDATA[<p>Other topics in this episode:</p><ul><li>Trump and his group of domestic terrorists are trying to overthrow the government and it sucks.</li><li>What a Democrat-controlled government means for healthcare</li><li>Rick's business is extremely seasonal.</li><li>We give financial updates from 2020.</li><li>Rick is working on some tooling changes: Twilio, Front, and knowledge bases.</li><li>Don't be envious of other people.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics in this episode:</p><ul><li>Trump and his group of domestic terrorists are trying to overthrow the government and it sucks.</li><li>What a Democrat-controlled government means for healthcare</li><li>Rick's business is extremely seasonal.</li><li>We give financial updates from 2020.</li><li>Rick is working on some tooling changes: Twilio, Front, and knowledge bases.</li><li>Don't be envious of other people.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 07 Jan 2021 17:35:06 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/56180f66/a003b814.mp3" length="55489414" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3448</itunes:duration>
      <itunes:summary>This week, we talk about a startup nightmare: What do you do when your website gets attacked?</itunes:summary>
      <itunes:subtitle>This week, we talk about a startup nightmare: What do you do when your website gets attacked?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>End of 2020 mega-episode</title>
      <itunes:episode>76</itunes:episode>
      <podcast:episode>76</podcast:episode>
      <itunes:title>End of 2020 mega-episode</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">895846e4-e31d-4888-8ce3-15547ebf4b91</guid>
      <link>https://share.transistor.fm/s/6b06d3a8</link>
      <description>
        <![CDATA[<p><strong>Looking back at 2020</strong></p><p>Note, many of the goals mentioned here were set in our <a href="https://www.startuptolast.com/episodes/looking-back-at-2019-and-forward-to-2020">2019 recap episode</a>.</p><ul><li>Personal accomplishments <ul><li>Rick <ul><li>2019 Goal: Get to a point where he and his wife feel comfortable having kids - ✅ Not only are they ready, Rick's wife is pregnant 🎉</li><li>2019 Goal: Increase level of play - ✅ He's been playing basketball, skiing, playing water sports, etc.</li><li>Had success writing his newsletter almost every week.</li></ul></li><li>Tyler <ul><li>2019 Goal: Get a dog - ✅ His name is jolo and he's an idiot.</li><li>2019 Goal: Exercise three times per week - ❌ Things were looking good until covid hit.</li><li>Got married and bought a house.</li></ul></li></ul></li><li>Business accomplishments <ul><li>Rick <ul><li>2019 Goal: Grow to $10k MRR - ❌ But did even better by focusing on one business and investing in the long term.</li><li>LegUp Health makes more money than it spends.</li><li>Built the LegUp Health product with no-code and low-code.</li><li>Shut down his old business, Group Current, while maintaining a strong relationship with his co-founder.</li></ul></li><li>Tyler <ul><li>2019 Goal: Continue product team's momentum - ✅ LACRM put out meaningful product improvements regularly throughout the year.</li><li>2019 Goal: Write code once per week - ❌ Didn't even come close.</li><li>2019 Goal: Average 50 paying users/month from the referral channel - ❌ Had the right input, but didn't get the results.</li><li>Launched a major redesign.</li><li>Made it through the pandemic despite a couple terrible months.</li><li>Raised prices.</li><li>Hired two new people.</li></ul></li></ul></li><li>Biggest disappointment <ul><li>Rick - Not spending enough time with customers, friends, and family.</li><li>Tyler - Had to fire an employee.</li></ul></li><li>Biggest learning <ul><li>Rick - The difference between earning 10% of a business vs 100%.</li><li>Tyler - The role of an entrepreneur vs. the role of a CEO.</li></ul></li></ul><p><strong>Discussing big picture goals</strong></p><ul><li>Why are we entrepreneurs? What drives us? <ul><li>Rick - He's good at it, he likes it. It's the best pathway to freedom.</li><li>Tyler - Trust, building things, creating a great place to work.</li></ul></li><li>What do we want to accomplish over 10+ years <ul><li>Rick - $10mm ARR, 20% profit. Become the one-stop shop for consumers finding healthcare. Build a full benefits platform for employers.</li><li>Tyler - Turn the one successful product into a suite of products for small businesses. Be more than a CRM.</li></ul></li><li>What do we our roles to be long-term? <ul><li>Rick - Build a management team. Stay involved in product marketing.</li><li>Tyler - Manage the product team and innovate on the product as an individual contributor. Be CEO, but mostly have non-product things delegated to a management team.</li></ul></li></ul><p><strong>Expectations for 2021</strong></p><ul><li>Personal themes/goals <ul><li>Rick - Get sleep under control. Adjust to being a dad.</li><li>Tyler - Spend more time with friends and family once the pandemic is under control (knock on wood)</li></ul></li><li>Professional themes/goals <ul><li>Rick <ul><li>Get to $10k MRR.</li><li>Automate/delegate so service can be scalable.</li></ul></li><li>Tyler <ul><li>Get marketing to the point that it can be delegated.</li><li>Design the new appointment scheduler product.</li></ul></li></ul></li><li>Biggest worry <ul><li>Rick - Being able to scale service.</li><li>Tyler - Growth leveling off after the benefit of the price increase wears off.</li></ul></li><li>What do we want to learn? <ul><li>Rick - Learn more coding, especially working with API data and generating dynamic emails.</li><li>Tyler - Re-learn how to iterate and move fast.</li></ul></li></ul><p><strong>Predictions</strong></p><ul><li>Our predictions from last year <ul><li>Rick - An all-in-one solution will emerge in the no-code space ❌</li><li>Tyler - Startups raising money from non-VCs will become more mainstream (sort of happened, but still in progress)</li></ul></li><li>Next year <ul><li>Rick - Asynchronous video will become big in professional settings.</li><li>Tyler - San Francisco will start a new era of opportunity for early-stage startups.</li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Looking back at 2020</strong></p><p>Note, many of the goals mentioned here were set in our <a href="https://www.startuptolast.com/episodes/looking-back-at-2019-and-forward-to-2020">2019 recap episode</a>.</p><ul><li>Personal accomplishments <ul><li>Rick <ul><li>2019 Goal: Get to a point where he and his wife feel comfortable having kids - ✅ Not only are they ready, Rick's wife is pregnant 🎉</li><li>2019 Goal: Increase level of play - ✅ He's been playing basketball, skiing, playing water sports, etc.</li><li>Had success writing his newsletter almost every week.</li></ul></li><li>Tyler <ul><li>2019 Goal: Get a dog - ✅ His name is jolo and he's an idiot.</li><li>2019 Goal: Exercise three times per week - ❌ Things were looking good until covid hit.</li><li>Got married and bought a house.</li></ul></li></ul></li><li>Business accomplishments <ul><li>Rick <ul><li>2019 Goal: Grow to $10k MRR - ❌ But did even better by focusing on one business and investing in the long term.</li><li>LegUp Health makes more money than it spends.</li><li>Built the LegUp Health product with no-code and low-code.</li><li>Shut down his old business, Group Current, while maintaining a strong relationship with his co-founder.</li></ul></li><li>Tyler <ul><li>2019 Goal: Continue product team's momentum - ✅ LACRM put out meaningful product improvements regularly throughout the year.</li><li>2019 Goal: Write code once per week - ❌ Didn't even come close.</li><li>2019 Goal: Average 50 paying users/month from the referral channel - ❌ Had the right input, but didn't get the results.</li><li>Launched a major redesign.</li><li>Made it through the pandemic despite a couple terrible months.</li><li>Raised prices.</li><li>Hired two new people.</li></ul></li></ul></li><li>Biggest disappointment <ul><li>Rick - Not spending enough time with customers, friends, and family.</li><li>Tyler - Had to fire an employee.</li></ul></li><li>Biggest learning <ul><li>Rick - The difference between earning 10% of a business vs 100%.</li><li>Tyler - The role of an entrepreneur vs. the role of a CEO.</li></ul></li></ul><p><strong>Discussing big picture goals</strong></p><ul><li>Why are we entrepreneurs? What drives us? <ul><li>Rick - He's good at it, he likes it. It's the best pathway to freedom.</li><li>Tyler - Trust, building things, creating a great place to work.</li></ul></li><li>What do we want to accomplish over 10+ years <ul><li>Rick - $10mm ARR, 20% profit. Become the one-stop shop for consumers finding healthcare. Build a full benefits platform for employers.</li><li>Tyler - Turn the one successful product into a suite of products for small businesses. Be more than a CRM.</li></ul></li><li>What do we our roles to be long-term? <ul><li>Rick - Build a management team. Stay involved in product marketing.</li><li>Tyler - Manage the product team and innovate on the product as an individual contributor. Be CEO, but mostly have non-product things delegated to a management team.</li></ul></li></ul><p><strong>Expectations for 2021</strong></p><ul><li>Personal themes/goals <ul><li>Rick - Get sleep under control. Adjust to being a dad.</li><li>Tyler - Spend more time with friends and family once the pandemic is under control (knock on wood)</li></ul></li><li>Professional themes/goals <ul><li>Rick <ul><li>Get to $10k MRR.</li><li>Automate/delegate so service can be scalable.</li></ul></li><li>Tyler <ul><li>Get marketing to the point that it can be delegated.</li><li>Design the new appointment scheduler product.</li></ul></li></ul></li><li>Biggest worry <ul><li>Rick - Being able to scale service.</li><li>Tyler - Growth leveling off after the benefit of the price increase wears off.</li></ul></li><li>What do we want to learn? <ul><li>Rick - Learn more coding, especially working with API data and generating dynamic emails.</li><li>Tyler - Re-learn how to iterate and move fast.</li></ul></li></ul><p><strong>Predictions</strong></p><ul><li>Our predictions from last year <ul><li>Rick - An all-in-one solution will emerge in the no-code space ❌</li><li>Tyler - Startups raising money from non-VCs will become more mainstream (sort of happened, but still in progress)</li></ul></li><li>Next year <ul><li>Rick - Asynchronous video will become big in professional settings.</li><li>Tyler - San Francisco will start a new era of opportunity for early-stage startups.</li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 31 Dec 2020 17:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/6b06d3a8/b2e9fa44.mp3" length="90990563" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>5539</itunes:duration>
      <itunes:summary>This week, we talk look back at 2020, look ahead to 2021, and make some predictions.</itunes:summary>
      <itunes:subtitle>This week, we talk look back at 2020, look ahead to 2021, and make some predictions.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Should your startup donate to charity?</title>
      <itunes:episode>75</itunes:episode>
      <podcast:episode>75</podcast:episode>
      <itunes:title>Should your startup donate to charity?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">122c428b-0ef5-4767-a852-d9ef5f06a6cf</guid>
      <link>https://share.transistor.fm/s/a3a7ae00</link>
      <description>
        <![CDATA[<p>Other topics:</p><ul><li>Tyler realized he might have more revenue growth next year than he originally thought.</li><li>Rick is learning that things don't die down immediately after open enrollment, and that's making it hard to do end-of-year planning.</li><li>Tyler has been thinking about what the approach might be when LACRM re-opens the office.</li><li>Rick is meeting his intern for the first time in-person.</li><li>Rick switched to Notion and is loving it.</li><li>Tyler has a marketing approach that he wants feedback on.</li><li>We discuss whether companies should donate money to charities.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics:</p><ul><li>Tyler realized he might have more revenue growth next year than he originally thought.</li><li>Rick is learning that things don't die down immediately after open enrollment, and that's making it hard to do end-of-year planning.</li><li>Tyler has been thinking about what the approach might be when LACRM re-opens the office.</li><li>Rick is meeting his intern for the first time in-person.</li><li>Rick switched to Notion and is loving it.</li><li>Tyler has a marketing approach that he wants feedback on.</li><li>We discuss whether companies should donate money to charities.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 24 Dec 2020 17:15:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/a3a7ae00/ae6d589c.mp3" length="64459013" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3889</itunes:duration>
      <itunes:summary>This week, we talk whether startups should donate a portion of their profits to charity.</itunes:summary>
      <itunes:subtitle>This week, we talk whether startups should donate a portion of their profits to charity.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Product Market Fit</title>
      <itunes:episode>74</itunes:episode>
      <podcast:episode>74</podcast:episode>
      <itunes:title>Product Market Fit</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">de0b73b4-7b04-4b33-a1df-0a152b854baa</guid>
      <link>https://share.transistor.fm/s/42e9e9e4</link>
      <description>
        <![CDATA[<p>Other topics from this episode:</p><ul><li>Rick is finished with open enrollment and walks through some metrics.</li><li>Rick is expecting his first churn from customers who signed up earlier this year.</li><li>Rick realizes that word of mouth happens at specific moments in time, such as when someone leaves their job, gets married, or has some other life event.</li><li>Tyler is learning more about his strengths and weaknesses.</li><li>Tyler is overwhelmed with interviews.</li><li>Tyler is preparing a presentation on recruiting and diversity.</li></ul><p>I would like to apologize for my lack of creativity in the sentence structure above. It's the middle of December and it's pitch black outside even though it's not even 6pm, so it just seems like writing up interesting show notes is not a great use of my time when I could instead be eating fast food and watching Netflix. Thanks for understanding.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics from this episode:</p><ul><li>Rick is finished with open enrollment and walks through some metrics.</li><li>Rick is expecting his first churn from customers who signed up earlier this year.</li><li>Rick realizes that word of mouth happens at specific moments in time, such as when someone leaves their job, gets married, or has some other life event.</li><li>Tyler is learning more about his strengths and weaknesses.</li><li>Tyler is overwhelmed with interviews.</li><li>Tyler is preparing a presentation on recruiting and diversity.</li></ul><p>I would like to apologize for my lack of creativity in the sentence structure above. It's the middle of December and it's pitch black outside even though it's not even 6pm, so it just seems like writing up interesting show notes is not a great use of my time when I could instead be eating fast food and watching Netflix. Thanks for understanding.</p>]]>
      </content:encoded>
      <pubDate>Thu, 17 Dec 2020 17:39:58 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/42e9e9e4/54cf1882.mp3" length="71589772" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4369</itunes:duration>
      <itunes:summary>This week, we answer a listener question about product market fit.</itunes:summary>
      <itunes:subtitle>This week, we answer a listener question about product market fit.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Celebrating wins in the early days</title>
      <itunes:episode>73</itunes:episode>
      <podcast:episode>73</podcast:episode>
      <itunes:title>Celebrating wins in the early days</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">29ab7060-135b-42f6-b4ad-e9069d9cef01</guid>
      <link>https://share.transistor.fm/s/497b5390</link>
      <description>
        <![CDATA[<p>Other topics we covered this week:</p><ul><li><a href="https://adventofcode.com/">Advent of code</a></li><li>The Less Annoying CRM design fellowship is finalized.</li><li>Rick has a few different channels that are showing traction including Instagram DMs and getting referrals from other insurance agents.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics we covered this week:</p><ul><li><a href="https://adventofcode.com/">Advent of code</a></li><li>The Less Annoying CRM design fellowship is finalized.</li><li>Rick has a few different channels that are showing traction including Instagram DMs and getting referrals from other insurance agents.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 10 Dec 2020 18:05:53 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/497b5390/097e0a27.mp3" length="54899513" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3262</itunes:duration>
      <itunes:summary>This week, we talk about building a culture of celebrating wins when you're first getting started.</itunes:summary>
      <itunes:subtitle>This week, we talk about building a culture of celebrating wins when you're first getting started.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Info products moving to a subscription model</title>
      <itunes:episode>72</itunes:episode>
      <podcast:episode>72</podcast:episode>
      <itunes:title>Info products moving to a subscription model</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">466420a5-7b76-444d-b534-dd0f71f24708</guid>
      <link>https://share.transistor.fm/s/10334374</link>
      <description>
        <![CDATA[<p>Here are some of the other topics we discuss:</p><ul><li>Slack was acquired by Salesforce for a bunch of money. Like, a whole lot.</li><li>Stripe launched a new "Treasury" product.</li><li>Tyler finished his end-of-year planning.</li><li>Rick has been bouncing between projects.</li><li>Google Search Console has been broken for Rick.</li><li><a href="https://www.myfirstmillionpodcast.com/My-First-Million-bf3eb1b80cda4ba1be53aa8babc3cfcb">My first million</a> is a good podcast.</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some of the other topics we discuss:</p><ul><li>Slack was acquired by Salesforce for a bunch of money. Like, a whole lot.</li><li>Stripe launched a new "Treasury" product.</li><li>Tyler finished his end-of-year planning.</li><li>Rick has been bouncing between projects.</li><li>Google Search Console has been broken for Rick.</li><li><a href="https://www.myfirstmillionpodcast.com/My-First-Million-bf3eb1b80cda4ba1be53aa8babc3cfcb">My first million</a> is a good podcast.</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 03 Dec 2020 17:24:46 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/10334374/8262ebef.mp3" length="63283179" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3885</itunes:duration>
      <itunes:summary>This week, we talk about the pros and cons of the recent trend of info products moving to a subscription model.</itunes:summary>
      <itunes:subtitle>This week, we talk about the pros and cons of the recent trend of info products moving to a subscription model.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Planning a marketing sprint</title>
      <itunes:episode>71</itunes:episode>
      <podcast:episode>71</podcast:episode>
      <itunes:title>Planning a marketing sprint</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">3fa752c2-0a3e-4d87-96f7-099b8a3a19bf</guid>
      <link>https://share.transistor.fm/s/ace27c9c</link>
      <description>
        <![CDATA[<p>Because this is a short week, we didn't have many updates. Instead we focused on two main topics:</p><ul><li>The trend of SaaS companies bundling multiple products into a single subscription.</li><li>Rick's marketing plan for the next few weeks.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Because this is a short week, we didn't have many updates. Instead we focused on two main topics:</p><ul><li>The trend of SaaS companies bundling multiple products into a single subscription.</li><li>Rick's marketing plan for the next few weeks.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 26 Nov 2020 17:16:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/ace27c9c/9f0aff9c.mp3" length="53714326" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3309</itunes:duration>
      <itunes:summary>Rick is facing a unique situation. He has about two weeks to put together a marketing campaign before the window of opportunity closes. In this episode, we workshop his marketing plan. Let's go.</itunes:summary>
      <itunes:subtitle>Rick is facing a unique situation. He has about two weeks to put together a marketing campaign before the window of opportunity closes. In this episode, we workshop his marketing plan. Let's go.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Traction vs distraction</title>
      <itunes:episode>70</itunes:episode>
      <podcast:episode>70</podcast:episode>
      <itunes:title>Traction vs distraction</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f466dc0e-093e-4e58-82e8-23bf0edea953</guid>
      <link>https://share.transistor.fm/s/6dbe5be3</link>
      <description>
        <![CDATA[<p>Some topics we cover:</p><ul><li>Rick has been reading two new books that teach about avoiding distraction and staying focused.</li><li>Tyler had a product strategy breakthrough after giving himself time to think through a bunch of bad ideas first.</li><li>Rick reflects on his failed startup from last year and we discuss the merits of having a portfolio of products vs a single product to focus on.</li><li>Rick has been marketing LegUp Health, including making an appearance on tv.</li><li>Tyler reports on the results of some help site changes Less Annoying CRM made a while back..</li><li>Tyler is planning a design fellowship.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Some topics we cover:</p><ul><li>Rick has been reading two new books that teach about avoiding distraction and staying focused.</li><li>Tyler had a product strategy breakthrough after giving himself time to think through a bunch of bad ideas first.</li><li>Rick reflects on his failed startup from last year and we discuss the merits of having a portfolio of products vs a single product to focus on.</li><li>Rick has been marketing LegUp Health, including making an appearance on tv.</li><li>Tyler reports on the results of some help site changes Less Annoying CRM made a while back..</li><li>Tyler is planning a design fellowship.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 19 Nov 2020 17:28:36 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/6dbe5be3/1a19e5b0.mp3" length="62740531" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3805</itunes:duration>
      <itunes:summary>This week, we talk about how to stay focused when starting and running a business.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to stay focused when starting and running a business.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Setting goals when you're just getting started</title>
      <itunes:episode>69</itunes:episode>
      <podcast:episode>69</podcast:episode>
      <itunes:title>Setting goals when you're just getting started</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">80a87977-78fa-4ed8-ad12-758f570e2295</guid>
      <link>https://share.transistor.fm/s/a3e9a6bd</link>
      <description>
        <![CDATA[<p>Other topics we discussed this week:</p><ul><li>Tyler has another lesson to share from the book he's reading.</li><li>Rick stopped marketing and he's struggling to get momentum back.</li><li>Tyler is trying to design team permissions for Less Annoying CRM and it's proving to be difficult.</li><li>We give a shoutout to <a href="https://www.jetboost.io/">Jetboost</a>.</li><li>Rick is frustrated that no-code tools aren't more transparent about their product priorities.</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics we discussed this week:</p><ul><li>Tyler has another lesson to share from the book he's reading.</li><li>Rick stopped marketing and he's struggling to get momentum back.</li><li>Tyler is trying to design team permissions for Less Annoying CRM and it's proving to be difficult.</li><li>We give a shoutout to <a href="https://www.jetboost.io/">Jetboost</a>.</li><li>Rick is frustrated that no-code tools aren't more transparent about their product priorities.</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 12 Nov 2020 17:43:34 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/a3e9a6bd/a91ebd87.mp3" length="63123009" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3919</itunes:duration>
      <itunes:summary>This week, we talk about how to set goals when your business is too young to be able to make accurate predictions about growth.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to set goals when your business is too young to be able to make accurate predictions about growth.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How big to go when moving upmarket</title>
      <itunes:episode>68</itunes:episode>
      <podcast:episode>68</podcast:episode>
      <itunes:title>How big to go when moving upmarket</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">35b90134-4085-40d1-8c0a-42b754774e13</guid>
      <link>https://share.transistor.fm/s/f56d8e6d</link>
      <description>
        <![CDATA[<p>Other topics this episode:</p><ul><li>Tyler is switching Less Annoying CRM to Notion.</li><li>Rick is finished with outreach to existing customers to prepare for open enrollment. Next up is marketing/sales.</li><li>Rick's employee Lena is doing a great job executing their content strategy.</li><li>Tyler gives an update on Less Annoying CRM's financial results in October.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Other topics this episode:</p><ul><li>Tyler is switching Less Annoying CRM to Notion.</li><li>Rick is finished with outreach to existing customers to prepare for open enrollment. Next up is marketing/sales.</li><li>Rick's employee Lena is doing a great job executing their content strategy.</li><li>Tyler gives an update on Less Annoying CRM's financial results in October.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 05 Nov 2020 17:44:36 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f56d8e6d/1b0b1147.mp3" length="68319554" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3979</itunes:duration>
      <itunes:summary>This week, we talk about the right size of customer to target when trying to increase ACV (annual contract value)</itunes:summary>
      <itunes:subtitle>This week, we talk about the right size of customer to target when trying to increase ACV (annual contract value)</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Startup community fatigue</title>
      <itunes:episode>67</itunes:episode>
      <podcast:episode>67</podcast:episode>
      <itunes:title>Startup community fatigue</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0e930316-6ed5-4917-b17b-e1906fe66e06</guid>
      <link>https://share.transistor.fm/s/14aba02f</link>
      <description>
        <![CDATA[<p>Some other topics from this week:</p><ul><li>Rick is getting ready for open enrollment, and he explains the history behind why health insurance is sold all at the same time in the U.S.</li><li>Tyler has been talking to customers a lot recently.</li><li>Tyler is using "revenue per employee" as a simple guide for whether or not LACRM can afford to hire employees.</li><li><a href="https://wildbit.com/">Wildbit</a> shows what it means to "startup to last" after celebrating their 20-year anniversary.</li><li>Rick is interested in <a href="https://grain.co/">grain.co</a>.</li><li>Instagram/Facebook are a cancer upon humanity and they should be destroyed. Or they should let Rick log into his account. Either way.</li><li>We discuss how Less Annoying CRM could package and position their product in a future where they have multiple sub-products all within the same app.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Some other topics from this week:</p><ul><li>Rick is getting ready for open enrollment, and he explains the history behind why health insurance is sold all at the same time in the U.S.</li><li>Tyler has been talking to customers a lot recently.</li><li>Tyler is using "revenue per employee" as a simple guide for whether or not LACRM can afford to hire employees.</li><li><a href="https://wildbit.com/">Wildbit</a> shows what it means to "startup to last" after celebrating their 20-year anniversary.</li><li>Rick is interested in <a href="https://grain.co/">grain.co</a>.</li><li>Instagram/Facebook are a cancer upon humanity and they should be destroyed. Or they should let Rick log into his account. Either way.</li><li>We discuss how Less Annoying CRM could package and position their product in a future where they have multiple sub-products all within the same app.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 29 Oct 2020 17:32:45 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/14aba02f/b5398b9e.mp3" length="65843786" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3975</itunes:duration>
      <itunes:summary>This week, we talk about being burnt out on all the startup communities out there and a bunch of other stuff.</itunes:summary>
      <itunes:subtitle>This week, we talk about being burnt out on all the startup communities out there and a bunch of other stuff.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Offering night and weekend support without burning out your team</title>
      <itunes:episode>66</itunes:episode>
      <podcast:episode>66</podcast:episode>
      <itunes:title>Offering night and weekend support without burning out your team</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">a91456f8-3cd9-41eb-b1d0-9cda31077cd7</guid>
      <link>https://share.transistor.fm/s/bc72171c</link>
      <description>
        <![CDATA[<p>Some other topics discussed this week:</p><ul><li>Rick separated his marketing site from his app and launched a site for his b2b product: <a href="https://www.legupbenefits.com/">www.legupbenefits.com</a></li><li>Less Annoying CRM launched a new help site and in-app help center.</li><li>We discuss what interns can do to get the most out of a remote internship.</li><li>Rick's ridiculous shoes arrived and they're meh. The lesson is: Don't buy shoes because a company put their logo on them.<ul><li>Rick will yell at me if I don't point out that he didn't get the ones with Slack's logo, he got the same type of shoe without the logo.</li></ul></li><li>We give a few shoutouts:<ul><li><a href="https://demodesk.com/">Demodesk</a> is a great tool for giving demos to customers.</li><li><a href="https://www.amazon.com/Turn-Ship-Around-Turning-Followers/dp/1591846404">Turn the ship around</a> is a helpful book on leadership.</li><li><a href="https://softwaresocial.dev/episodes/health-insurance-for-bootstrappers">This episode on health insurance for startup founders</a> is interesting and started a conversation about premium tax credits.</li></ul></li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Some other topics discussed this week:</p><ul><li>Rick separated his marketing site from his app and launched a site for his b2b product: <a href="https://www.legupbenefits.com/">www.legupbenefits.com</a></li><li>Less Annoying CRM launched a new help site and in-app help center.</li><li>We discuss what interns can do to get the most out of a remote internship.</li><li>Rick's ridiculous shoes arrived and they're meh. The lesson is: Don't buy shoes because a company put their logo on them.<ul><li>Rick will yell at me if I don't point out that he didn't get the ones with Slack's logo, he got the same type of shoe without the logo.</li></ul></li><li>We give a few shoutouts:<ul><li><a href="https://demodesk.com/">Demodesk</a> is a great tool for giving demos to customers.</li><li><a href="https://www.amazon.com/Turn-Ship-Around-Turning-Followers/dp/1591846404">Turn the ship around</a> is a helpful book on leadership.</li><li><a href="https://softwaresocial.dev/episodes/health-insurance-for-bootstrappers">This episode on health insurance for startup founders</a> is interesting and started a conversation about premium tax credits.</li></ul></li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 22 Oct 2020 17:45:43 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/bc72171c/82577a69.mp3" length="68176128" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4125</itunes:duration>
      <itunes:summary>This week, we talk about how you can hire talented support people to work nights and weekends without hating their jobs.</itunes:summary>
      <itunes:subtitle>This week, we talk about how you can hire talented support people to work nights and weekends without hating their jobs.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The perils of being dependent on a platform</title>
      <itunes:episode>65</itunes:episode>
      <podcast:episode>65</podcast:episode>
      <itunes:title>The perils of being dependent on a platform</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">15e32147-fb0f-4eac-b09e-6d617b6a8aec</guid>
      <link>https://share.transistor.fm/s/e55797bd</link>
      <description>
        <![CDATA[<p>Here are the topics we covered this week:</p><ul><li>Tyler has to decide between keeping his design consistent vs. optimizing each page's design for the content on that page.</li><li>Rick has moved into a new house</li><li>Tyler had his first meeting with the new mastermind group.</li><li>Tyler gives updates on his ongoing Webflow project.</li><li>We discuss the upsides and downsides of building a startup on tech platforms (e.g. no-code tools) as well as distribution platforms (e.g. the Shopify app store)</li><li>We talk about how Covid might impact things for the rest of the year.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are the topics we covered this week:</p><ul><li>Tyler has to decide between keeping his design consistent vs. optimizing each page's design for the content on that page.</li><li>Rick has moved into a new house</li><li>Tyler had his first meeting with the new mastermind group.</li><li>Tyler gives updates on his ongoing Webflow project.</li><li>We discuss the upsides and downsides of building a startup on tech platforms (e.g. no-code tools) as well as distribution platforms (e.g. the Shopify app store)</li><li>We talk about how Covid might impact things for the rest of the year.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 15 Oct 2020 19:00:43 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e55797bd/67d06021.mp3" length="61226952" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3593</itunes:duration>
      <itunes:summary>This week we discuss the upsides and downsides of building on a platform you don't control.</itunes:summary>
      <itunes:subtitle>This week we discuss the upsides and downsides of building on a platform you don't control.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Building a moat</title>
      <itunes:episode>64</itunes:episode>
      <podcast:episode>64</podcast:episode>
      <itunes:title>Building a moat</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">7702c0c4-87a6-4784-b335-25066bd0a171</guid>
      <link>https://share.transistor.fm/s/ed30983f</link>
      <description>
        <![CDATA[<p>Here's what we discussed this week:</p><ul><li>Tyler gives an update on the 1:1 meetings he's had with his whole team over the last week.</li><li>Rick launched a digital health tool marketplace</li><li>Rick is wrapping up his projects from earlier in the year and is ready to focus on a few important things going forward.</li><li>Less Annoying CRM is close to close two new accounts, each of which are significantly larger than any customer they've had before.</li><li>Rick complains about his CRM adding data automatically.</li><li>We give a shoutout to Rick's wife who helped launch <a href="https://lucidspark.com/">Lucidspark</a>.</li><li>We give a shoutout to <a href="https://twitter.com/DruRly">Dru Riley</a> and <a href="https://join.trends.vc/">Trends.vc</a>.</li><li>We give a shoutout (how many shoutouts are there?) to <a href="https://twitter.com/csallen">Courtland Allen</a> who's starting a podcast network which we're joining.</li><li>Tyler complains about restaurants that aren't trying to compete.</li><li>Rick likes some extremely stupid shoes that Cole Haan made in partnership with Slack.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here's what we discussed this week:</p><ul><li>Tyler gives an update on the 1:1 meetings he's had with his whole team over the last week.</li><li>Rick launched a digital health tool marketplace</li><li>Rick is wrapping up his projects from earlier in the year and is ready to focus on a few important things going forward.</li><li>Less Annoying CRM is close to close two new accounts, each of which are significantly larger than any customer they've had before.</li><li>Rick complains about his CRM adding data automatically.</li><li>We give a shoutout to Rick's wife who helped launch <a href="https://lucidspark.com/">Lucidspark</a>.</li><li>We give a shoutout to <a href="https://twitter.com/DruRly">Dru Riley</a> and <a href="https://join.trends.vc/">Trends.vc</a>.</li><li>We give a shoutout (how many shoutouts are there?) to <a href="https://twitter.com/csallen">Courtland Allen</a> who's starting a podcast network which we're joining.</li><li>Tyler complains about restaurants that aren't trying to compete.</li><li>Rick likes some extremely stupid shoes that Cole Haan made in partnership with Slack.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 08 Oct 2020 17:25:58 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/ed30983f/8876cb1a.mp3" length="63952015" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3864</itunes:duration>
      <itunes:summary>This week, we talk about how Less Annoying CRM uses customer service as a moat, and several other topics.</itunes:summary>
      <itunes:subtitle>This week, we talk about how Less Annoying CRM uses customer service as a moat, and several other topics.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Should multiple products share a single brand</title>
      <itunes:episode>63</itunes:episode>
      <podcast:episode>63</podcast:episode>
      <itunes:title>Should multiple products share a single brand</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c5ac188e-9f15-4f50-8b13-c49f4c02f202</guid>
      <link>https://share.transistor.fm/s/dfad2677</link>
      <description>
        <![CDATA[<p>Here are the topics we discuss this week:</p><ul><li>The difference between work and hobbies when hobbies involve work topics.</li><li>Rick is focusing more on outreach.</li><li>Tyler gave a 6-month presentation to his employees.</li><li>Rick is about to build his employer-facing product using <a href="https://www.glideapps.com/">Glide</a>.</li><li>Should startups with multiple products put them all under a single brand umbrella, or run separate marketing sites for each one?</li><li>Rick is switching from Google Meet to Zoom.</li><li>Should startups ask for a credit card when signing up for a trial, or after the trial has ended?</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are the topics we discuss this week:</p><ul><li>The difference between work and hobbies when hobbies involve work topics.</li><li>Rick is focusing more on outreach.</li><li>Tyler gave a 6-month presentation to his employees.</li><li>Rick is about to build his employer-facing product using <a href="https://www.glideapps.com/">Glide</a>.</li><li>Should startups with multiple products put them all under a single brand umbrella, or run separate marketing sites for each one?</li><li>Rick is switching from Google Meet to Zoom.</li><li>Should startups ask for a credit card when signing up for a trial, or after the trial has ended?</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 01 Oct 2020 17:30:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/dfad2677/19f1fe29.mp3" length="60471823" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3718</itunes:duration>
      <itunes:summary>This week, we discuss whether Rick should launch his b2b product under the same brand as his b2c product</itunes:summary>
      <itunes:subtitle>This week, we discuss whether Rick should launch his b2b product under the same brand as his b2c product</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>All-nighters</title>
      <itunes:episode>62</itunes:episode>
      <podcast:episode>62</podcast:episode>
      <itunes:title>All-nighters</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0bf845f1-da9f-40da-bcba-725bfb3a592c</guid>
      <link>https://share.transistor.fm/s/9efe4ab3</link>
      <description>
        <![CDATA[<p>Here are some topics we discussed this week:</p><ul><li>Rick was on an entrepreneurship panel at his former high school.</li><li>Rick has automated most of the onboarding process at LegUp health.</li><li>Tyler gives an update on his price increase.</li><li>Rick closed his first employer client and has lots of other opportunities coming up soon.</li><li>Rick gives shout-outs to <a href="https://simonsinek.com/the-infinite-game">The Infinite Game</a> and <a href="https://intro.me/">INTRO</a> (we also discuss <a href="https://earnestcapital.com/trailhead/">Trailhead</a>).</li><li>We commiserate about Webflow limitations.</li><li>We talk about smart home devices (what does this have to do with startups? Nothing).</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some topics we discussed this week:</p><ul><li>Rick was on an entrepreneurship panel at his former high school.</li><li>Rick has automated most of the onboarding process at LegUp health.</li><li>Tyler gives an update on his price increase.</li><li>Rick closed his first employer client and has lots of other opportunities coming up soon.</li><li>Rick gives shout-outs to <a href="https://simonsinek.com/the-infinite-game">The Infinite Game</a> and <a href="https://intro.me/">INTRO</a> (we also discuss <a href="https://earnestcapital.com/trailhead/">Trailhead</a>).</li><li>We commiserate about Webflow limitations.</li><li>We talk about smart home devices (what does this have to do with startups? Nothing).</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 24 Sep 2020 17:25:15 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/9efe4ab3/11ead1aa.mp3" length="57784018" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3561</itunes:duration>
      <itunes:summary>Rick is on a roll with LegUp Health, and he's burning the candle at both ends.</itunes:summary>
      <itunes:subtitle>Rick is on a roll with LegUp Health, and he's burning the candle at both ends.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Handling capacity at a seasonal business</title>
      <itunes:episode>61</itunes:episode>
      <podcast:episode>61</podcast:episode>
      <itunes:title>Handling capacity at a seasonal business</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">14310337-876e-425f-92cc-c6b3d26962e1</guid>
      <link>https://share.transistor.fm/s/1443407f</link>
      <description>
        <![CDATA[<p>Here are the topics this week:</p><ul><li>Rick is on a roll with his website build-out. Check it out at <a href="https://www.leguphealth.com/">leguphealth.com</a> and let him know what you think.</li><li>We talk about mistakes you can make when handing off ownership to employees.</li><li>Tyler is reconsidering the benefits philosophy at LACRM.</li><li>Rick is thinking about how to build out an employer-facing app.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are the topics this week:</p><ul><li>Rick is on a roll with his website build-out. Check it out at <a href="https://www.leguphealth.com/">leguphealth.com</a> and let him know what you think.</li><li>We talk about mistakes you can make when handing off ownership to employees.</li><li>Tyler is reconsidering the benefits philosophy at LACRM.</li><li>Rick is thinking about how to build out an employer-facing app.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 17 Sep 2020 18:19:57 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1443407f/19a32f50.mp3" length="65723444" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4091</itunes:duration>
      <itunes:summary>This week, we talk about how Rick is preparing for his busy season which starts in November</itunes:summary>
      <itunes:subtitle>This week, we talk about how Rick is preparing for his busy season which starts in November</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Pricing annual plans when users are added mid-year</title>
      <itunes:episode>60</itunes:episode>
      <podcast:episode>60</podcast:episode>
      <itunes:title>Pricing annual plans when users are added mid-year</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">68c50b7f-1646-4a01-92fc-cf7947c2876b</guid>
      <link>https://share.transistor.fm/s/14b19648</link>
      <description>
        <![CDATA[<p>Here are some of the topics we covered this week:</p><ul><li>Tyler is preparing for vacation.</li><li>Rick has his new CRM set up.</li><li>Rick is working on his website and isn't sure the right approach to take.</li><li>Less Annoying CRM hired a new developer.</li><li>Less Annoying CRM has a bunch of new features getting launched.</li><li>Tyler is considering how to get the rest of the team more involved in product prioritization.</li><li>Rick has been adding some new customers based on outreach he did months ago.</li><li>Deep dive: How should Rick build and price and MVP of a new b2b service?</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some of the topics we covered this week:</p><ul><li>Tyler is preparing for vacation.</li><li>Rick has his new CRM set up.</li><li>Rick is working on his website and isn't sure the right approach to take.</li><li>Less Annoying CRM hired a new developer.</li><li>Less Annoying CRM has a bunch of new features getting launched.</li><li>Tyler is considering how to get the rest of the team more involved in product prioritization.</li><li>Rick has been adding some new customers based on outreach he did months ago.</li><li>Deep dive: How should Rick build and price and MVP of a new b2b service?</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 10 Sep 2020 21:04:28 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/14b19648/770dcd75.mp3" length="63824001" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3949</itunes:duration>
      <itunes:summary>This week we dive into how Rick could price his b2b service.</itunes:summary>
      <itunes:subtitle>This week we dive into how Rick could price his b2b service.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Learning no-code</title>
      <itunes:episode>59</itunes:episode>
      <podcast:episode>59</podcast:episode>
      <itunes:title>Learning no-code</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d393b789-734d-4fc2-9270-955f664af8d1</guid>
      <link>https://share.transistor.fm/s/3ee46a84</link>
      <description>
        <![CDATA[<p>This week, we had a special guest: <a href="https://twitter.com/maliacodes">Malia Jones</a>. We discussed how to teach no-code to beginners.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This week, we had a special guest: <a href="https://twitter.com/maliacodes">Malia Jones</a>. We discussed how to teach no-code to beginners.</p>]]>
      </content:encoded>
      <pubDate>Thu, 03 Sep 2020 17:53:16 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/3ee46a84/0f538550.mp3" length="68016017" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4217</itunes:duration>
      <itunes:summary>This week, we talk all about no-code: What it is, what it can be used for, and how to learn it.</itunes:summary>
      <itunes:subtitle>This week, we talk all about no-code: What it is, what it can be used for, and how to learn it.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Networking without being annoying</title>
      <itunes:episode>58</itunes:episode>
      <podcast:episode>58</podcast:episode>
      <itunes:title>Networking without being annoying</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b7758dc0-f3fe-47ac-a96e-176523ae003a</guid>
      <link>https://share.transistor.fm/s/6a524607</link>
      <description>
        <![CDATA[<p>Here are some topics:</p><ul><li>Rick is taking a vacation which has him considering if his business should be remote-first so he can spend more time outside of Utah.</li><li>Tyler was on support last weekend and started testing out ways to limit wasteful uses of customer service time.</li><li>Tyler is prepping a presentation for his employees which he does every six months.</li><li>Tyler is formalizing the org chart at LACRM a bit.</li><li>We discuss how to network without annoying people.</li><li>Rick has people reaching out looking for opportunities to work at LegUp Health and wants to figure out how to respond.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some topics:</p><ul><li>Rick is taking a vacation which has him considering if his business should be remote-first so he can spend more time outside of Utah.</li><li>Tyler was on support last weekend and started testing out ways to limit wasteful uses of customer service time.</li><li>Tyler is prepping a presentation for his employees which he does every six months.</li><li>Tyler is formalizing the org chart at LACRM a bit.</li><li>We discuss how to network without annoying people.</li><li>Rick has people reaching out looking for opportunities to work at LegUp Health and wants to figure out how to respond.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 27 Aug 2020 17:48:53 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/6a524607/7902e9fd.mp3" length="55993679" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3552</itunes:duration>
      <itunes:summary>This week, we discuss networking (both online and in person) and how to use it in a non-annoying way to make sales. Spoiler alert: Maybe it's not possible.</itunes:summary>
      <itunes:subtitle>This week, we discuss networking (both online and in person) and how to use it in a non-annoying way to make sales. Spoiler alert: Maybe it's not possible.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What if you get hit by a bus?</title>
      <itunes:episode>57</itunes:episode>
      <podcast:episode>57</podcast:episode>
      <itunes:title>What if you get hit by a bus?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">1474d6b8-873d-41e4-a490-d88ec5756fe8</guid>
      <link>https://share.transistor.fm/s/c7cfbebf</link>
      <description>
        <![CDATA[<p>Here are some of the topics from this episode:</p><ul><li>University leadership handling covid this fall.</li><li>Rick is using Copper CRM.</li><li>Rick is done with positioning and moving on to making a website.</li><li>Tyler has pricing and growth updates.</li><li>Tyler has been learning about co-ops and thinking about succession plans.</li><li>We discuss whether ARR or MRR is the right metric to communicate to the team.</li><li>We discuss whether or not it's healthy/smart/necessary to work more than 40 hours per week as a founder.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some of the topics from this episode:</p><ul><li>University leadership handling covid this fall.</li><li>Rick is using Copper CRM.</li><li>Rick is done with positioning and moving on to making a website.</li><li>Tyler has pricing and growth updates.</li><li>Tyler has been learning about co-ops and thinking about succession plans.</li><li>We discuss whether ARR or MRR is the right metric to communicate to the team.</li><li>We discuss whether or not it's healthy/smart/necessary to work more than 40 hours per week as a founder.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 20 Aug 2020 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/c7cfbebf/67bfa343.mp3" length="62218284" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3704</itunes:duration>
      <itunes:summary>This week, we discuss when a startup should start putting together plans for losing a founder and much more.</itunes:summary>
      <itunes:subtitle>This week, we discuss when a startup should start putting together plans for losing a founder and much more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How college students can prepare for entrepreneurship</title>
      <itunes:episode>56</itunes:episode>
      <podcast:episode>56</podcast:episode>
      <itunes:title>How college students can prepare for entrepreneurship</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">828e1065-13ab-43c8-802f-295d266db85a</guid>
      <link>https://share.transistor.fm/s/d1ef2d81</link>
      <description>
        <![CDATA[<p>Here are some other topics we discussed:</p><ul><li>Tyler bought a house.</li><li>Tyler is starting to do some startup mentorship.</li><li>Rick's interns are gone.</li><li>Rick has made progress on his positioning work.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some other topics we discussed:</p><ul><li>Tyler bought a house.</li><li>Tyler is starting to do some startup mentorship.</li><li>Rick's interns are gone.</li><li>Rick has made progress on his positioning work.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 13 Aug 2020 17:28:40 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/d1ef2d81/ee6c3112.mp3" length="64029819" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3843</itunes:duration>
      <itunes:summary>This week, we answer a listener question about what college students can do to get ready for startup life.</itunes:summary>
      <itunes:subtitle>This week, we answer a listener question about what college students can do to get ready for startup life.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The Sims, but way more boring</title>
      <itunes:episode>55</itunes:episode>
      <podcast:episode>55</podcast:episode>
      <itunes:title>The Sims, but way more boring</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">98f49a04-d3a0-4931-bf5f-2405f48cc9de</guid>
      <link>https://share.transistor.fm/s/39f7b869</link>
      <description>
        <![CDATA[<p>Here are the topics we discussed:</p><ul><li>LACRM shipped a handful of small improvements the interns had been working on.</li><li>Tyler gives an update on the price increase.</li><li>Rick is applying the positioning framework we applied last week which involved competitor analysis.</li><li>Tyler officially decided to go with Sococo as a virtual office for the team while everyone is remote.</li><li>Rick decided what to do with this Slack community.</li><li>Rick's internship are wrapping up and he has a virtual get-together with all the interns next week.</li><li>Tyler is getting close to deploying the first stage of his Webflow project.</li><li>Rick wants to know how to maximize his experience with his first paid hire this fall.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are the topics we discussed:</p><ul><li>LACRM shipped a handful of small improvements the interns had been working on.</li><li>Tyler gives an update on the price increase.</li><li>Rick is applying the positioning framework we applied last week which involved competitor analysis.</li><li>Tyler officially decided to go with Sococo as a virtual office for the team while everyone is remote.</li><li>Rick decided what to do with this Slack community.</li><li>Rick's internship are wrapping up and he has a virtual get-together with all the interns next week.</li><li>Tyler is getting close to deploying the first stage of his Webflow project.</li><li>Rick wants to know how to maximize his experience with his first paid hire this fall.</li></ul>]]>
      </content:encoded>
      <pubDate>Fri, 07 Aug 2020 16:01:21 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/39f7b869/c6a1b8a2.mp3" length="63682338" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3824</itunes:duration>
      <itunes:summary>This week, we spend most of the hour giving updates on things we've been working on, including LACRM's decision to use Sococo.</itunes:summary>
      <itunes:subtitle>This week, we spend most of the hour giving updates on things we've been working on, including LACRM's decision to use Sococo.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Product positioning</title>
      <itunes:episode>54</itunes:episode>
      <podcast:episode>54</podcast:episode>
      <itunes:title>Product positioning</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e96ac480-8f4a-4aeb-b146-77f752f65a15</guid>
      <link>https://share.transistor.fm/s/5c0729dc</link>
      <description>
        <![CDATA[<p>Most of this week's discussion was about <a href="https://aprildunford.com/obviously-awesome/">Obviously Awesome</a> by April Dunford. We also gave some updates on the following topics:</p><ul><li>Now that Rick is fully committed to Legup Health, he's getting used to giving something his all again.</li><li>Tyler is considering tweaking the plan for the coding fellowship.</li><li>Tyler is evaluating Sococo to help with remote team culture.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Most of this week's discussion was about <a href="https://aprildunford.com/obviously-awesome/">Obviously Awesome</a> by April Dunford. We also gave some updates on the following topics:</p><ul><li>Now that Rick is fully committed to Legup Health, he's getting used to giving something his all again.</li><li>Tyler is considering tweaking the plan for the coding fellowship.</li><li>Tyler is evaluating Sococo to help with remote team culture.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 30 Jul 2020 17:33:23 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/5c0729dc/bd0b38ed.mp3" length="70875381" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4351</itunes:duration>
      <itunes:summary>This week, we discuss the book "Obviously Awesome" which provides a framework for how startups can figure out their positioning.</itunes:summary>
      <itunes:subtitle>This week, we discuss the book "Obviously Awesome" which provides a framework for how startups can figure out their positioning.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Asking for too much info during signup</title>
      <itunes:episode>53</itunes:episode>
      <podcast:episode>53</podcast:episode>
      <itunes:title>Asking for too much info during signup</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e6faa47a-608f-4f02-ab9f-305013430243</guid>
      <link>https://share.transistor.fm/s/4b4b08be</link>
      <description>
        <![CDATA[<p><em>Note from Tyler: I'm sorry that my dog is whining in the background throughout this episode. I'll banish him from my room in future episodes. He's such a wimp.<br></em><br>Here are some of the topics from this episode:</p><ul><li>Tyler's price increase went into effect, but it's too early to draw any conclusions.</li><li>Rick has gotten great feedback from sharing his slide deck.</li><li>Tyler has been tweaking how his team communicates remotely.</li><li>Rick has heard from his early customers that he's asking them for too much info, but it's necessary for him to provide them with service.</li><li>Tyler has reached a decision on what his mid-term product strategy will be.</li><li>Rick is reconsidering his ambitions to run a Slack community.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><em>Note from Tyler: I'm sorry that my dog is whining in the background throughout this episode. I'll banish him from my room in future episodes. He's such a wimp.<br></em><br>Here are some of the topics from this episode:</p><ul><li>Tyler's price increase went into effect, but it's too early to draw any conclusions.</li><li>Rick has gotten great feedback from sharing his slide deck.</li><li>Tyler has been tweaking how his team communicates remotely.</li><li>Rick has heard from his early customers that he's asking them for too much info, but it's necessary for him to provide them with service.</li><li>Tyler has reached a decision on what his mid-term product strategy will be.</li><li>Rick is reconsidering his ambitions to run a Slack community.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 23 Jul 2020 17:23:20 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/4b4b08be/779e382b.mp3" length="61476522" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3843</itunes:duration>
      <itunes:summary>Rick has heard feedback from his early customers that they're apprehensive about the amount of info he's asking from them during the signup process.</itunes:summary>
      <itunes:subtitle>Rick has heard feedback from his early customers that they're apprehensive about the amount of info he's asking from them during the signup process.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Building trust when you're an unproven business</title>
      <itunes:episode>52</itunes:episode>
      <podcast:episode>52</podcast:episode>
      <itunes:title>Building trust when you're an unproven business</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">15f8f580-0f06-43cb-a4a0-79dbea02b7da</guid>
      <link>https://share.transistor.fm/s/1312581a</link>
      <description>
        <![CDATA[<p>Topics discussed in this episode:</p><ul><li>Tyler's growth is still going strong.</li><li>Rick is going to write content to build trust with his early leads.</li><li>Rick created a slide deck to explain his business. <a href="https://docs.google.com/presentation/d/1sGf6OaROMHQlYrCMxu6kAu5OXQxCwtsCNxNvEk1hsm0/edit#slide=id.g8d7ec716b5_0_0">Check it out here</a> and let him know what you think.</li><li>Tyler is making long-term product decisions.</li><li>Tyler is thinking about making no-code a core part of the coding fellowship next year.</li><li>Rick recorded an interview with Memberstack which will be featured on their site.</li><li>Tyler is going to invest in Earnest Capital.</li><li>Rick had to give advice about how to come up with an idea.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics discussed in this episode:</p><ul><li>Tyler's growth is still going strong.</li><li>Rick is going to write content to build trust with his early leads.</li><li>Rick created a slide deck to explain his business. <a href="https://docs.google.com/presentation/d/1sGf6OaROMHQlYrCMxu6kAu5OXQxCwtsCNxNvEk1hsm0/edit#slide=id.g8d7ec716b5_0_0">Check it out here</a> and let him know what you think.</li><li>Tyler is making long-term product decisions.</li><li>Tyler is thinking about making no-code a core part of the coding fellowship next year.</li><li>Rick recorded an interview with Memberstack which will be featured on their site.</li><li>Tyler is going to invest in Earnest Capital.</li><li>Rick had to give advice about how to come up with an idea.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 16 Jul 2020 17:15:18 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1312581a/74a251c7.mp3" length="58226622" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3553</itunes:duration>
      <itunes:summary>This week, we talk about how Rick can convince his customers that he's trustworthy even though his business is so new that he doesn't have a proven track record yet.</itunes:summary>
      <itunes:subtitle>This week, we talk about how Rick can convince his customers that he's trustworthy even though his business is so new that he doesn't have a proven track record yet.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Winning awards</title>
      <itunes:episode>51</itunes:episode>
      <podcast:episode>51</podcast:episode>
      <itunes:title>Winning awards</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">450e26d8-a7d5-49f8-bf4d-13cdafbb5adb</guid>
      <link>https://share.transistor.fm/s/527fdf7d</link>
      <description>
        <![CDATA[<p>Here are some topics from this week:</p><ul><li>Less Annoying CRM was named the #1 CRM by U.S. News and World Report.</li><li>Tyler restarted employee raises after temporarily freezing them when the pandemic started.</li><li>Rick now has fully self-serve onboarding.</li><li>We discuss how to write a terms of service and privacy policy.</li><li>Rick is making trade offs between sales and product time.</li><li>Rick wants to retain some of his interns after the summer.</li><li>Rick has validated that real estate is a good customer segment and is planning next steps.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some topics from this week:</p><ul><li>Less Annoying CRM was named the #1 CRM by U.S. News and World Report.</li><li>Tyler restarted employee raises after temporarily freezing them when the pandemic started.</li><li>Rick now has fully self-serve onboarding.</li><li>We discuss how to write a terms of service and privacy policy.</li><li>Rick is making trade offs between sales and product time.</li><li>Rick wants to retain some of his interns after the summer.</li><li>Rick has validated that real estate is a good customer segment and is planning next steps.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 09 Jul 2020 17:35:47 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/527fdf7d/af2322a2.mp3" length="62577354" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3792</itunes:duration>
      <itunes:summary>This week is all about the updates. Less Annoying CRM won a big award, and as always, there's plenty of intern talk.</itunes:summary>
      <itunes:subtitle>This week is all about the updates. Less Annoying CRM won a big award, and as always, there's plenty of intern talk.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The dummy curve</title>
      <itunes:episode>50</itunes:episode>
      <podcast:episode>50</podcast:episode>
      <itunes:title>The dummy curve</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">79b559d2-9844-406d-bd9d-f30f3a0e16b9</guid>
      <link>https://share.transistor.fm/s/ed0d597d</link>
      <description>
        <![CDATA[<p>Here are some of the topics we discussed this week:</p><ul><li>All of Rick's interns are onboarding, and things are going well</li><li>Rick is building up a bit of sales momentum</li><li>We discuss whether or not it makes sense to create artificial scarcity by requiring a referral before signing up.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some of the topics we discussed this week:</p><ul><li>All of Rick's interns are onboarding, and things are going well</li><li>Rick is building up a bit of sales momentum</li><li>We discuss whether or not it makes sense to create artificial scarcity by requiring a referral before signing up.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 02 Jul 2020 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/ed0d597d/3ac050db.mp3" length="51523171" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3186</itunes:duration>
      <itunes:summary>This week Rick gives updates on his sales efforts and intern projects</itunes:summary>
      <itunes:subtitle>This week Rick gives updates on his sales efforts and intern projects</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>A price increase is coming</title>
      <itunes:episode>49</itunes:episode>
      <podcast:episode>49</podcast:episode>
      <itunes:title>A price increase is coming</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">56442c8d-c11c-4688-b1fe-4536afde2bdb</guid>
      <link>https://share.transistor.fm/s/e70bce01</link>
      <description>
        <![CDATA[<p>Topics from this week:</p><ul><li>Tyler talks about the reaction he got when telling his customers about an upcoming price increase.</li><li>Rick launched his referral program.</li><li>Tyler is working on a new API for LACRM.</li><li>Rick has finalized the interns he'll bring on this summer.</li><li>Rick wasted a bunch of time talking to the IRS about a notification that was sent in error.</li><li>We discuss HEY, the new email program from Basecamp.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Topics from this week:</p><ul><li>Tyler talks about the reaction he got when telling his customers about an upcoming price increase.</li><li>Rick launched his referral program.</li><li>Tyler is working on a new API for LACRM.</li><li>Rick has finalized the interns he'll bring on this summer.</li><li>Rick wasted a bunch of time talking to the IRS about a notification that was sent in error.</li><li>We discuss HEY, the new email program from Basecamp.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 25 Jun 2020 17:30:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e70bce01/05582796.mp3" length="56605632" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3541</itunes:duration>
      <itunes:summary>This week we talk about Tyler's pricing change and a bunch of other stuff</itunes:summary>
      <itunes:subtitle>This week we talk about Tyler's pricing change and a bunch of other stuff</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How should a self-serve SaaS handle inbound enterprise leads?</title>
      <itunes:episode>48</itunes:episode>
      <podcast:episode>48</podcast:episode>
      <itunes:title>How should a self-serve SaaS handle inbound enterprise leads?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b7852157-4e6c-4713-8478-03c3645bec2e</guid>
      <link>https://share.transistor.fm/s/1c9cd139</link>
      <description>
        <![CDATA[<p>Here are the topics we discussed this week:</p><ul><li>Rick's interns are acting as a forcing function to keep him more productive.</li><li>Tyler has decided on a plan for LACRM pricing changes.</li><li>Tyler has refined how he talks about project priorities with his team.</li><li>Akshay from UserBit (a boostrapped company that makes <a href="https://userbitapp.com/">software for UX teams</a>) wrote in to ask about how we should handle inbound enterprise leads.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are the topics we discussed this week:</p><ul><li>Rick's interns are acting as a forcing function to keep him more productive.</li><li>Tyler has decided on a plan for LACRM pricing changes.</li><li>Tyler has refined how he talks about project priorities with his team.</li><li>Akshay from UserBit (a boostrapped company that makes <a href="https://userbitapp.com/">software for UX teams</a>) wrote in to ask about how we should handle inbound enterprise leads.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 18 Jun 2020 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1c9cd139/12e184e8.mp3" length="63315163" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3880</itunes:duration>
      <itunes:summary>This week, we discuss a listener question about how to handle enterprise leads if you don't have sales experience.</itunes:summary>
      <itunes:subtitle>This week, we discuss a listener question about how to handle enterprise leads if you don't have sales experience.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Curiosity or conviction</title>
      <itunes:episode>47</itunes:episode>
      <podcast:episode>47</podcast:episode>
      <itunes:title>Curiosity or conviction</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">775370a4-761c-45bd-b781-7f4e967bac8d</guid>
      <link>https://share.transistor.fm/s/a47e63d4</link>
      <description>
        <![CDATA[<p>Here are the topics from this week:</p><ul><li>Tyler and Rick both have interns and need to figure out what projects they should be working on.</li><li>Rick has been working on a client referral program.</li><li>Tyler is wondering if there's anything for him to do to partner with customers who love LACRM.</li><li>Rick was considering an intrapreneurship opportunity (working as an entrepreneur within a larger company) and decided against it.</li><li>Tyler is struggling to prioritize product improvements.</li><li>Less Annoying CRM will need to raise prices at some point. Tyler is wondering if now is the right time.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are the topics from this week:</p><ul><li>Tyler and Rick both have interns and need to figure out what projects they should be working on.</li><li>Rick has been working on a client referral program.</li><li>Tyler is wondering if there's anything for him to do to partner with customers who love LACRM.</li><li>Rick was considering an intrapreneurship opportunity (working as an entrepreneur within a larger company) and decided against it.</li><li>Tyler is struggling to prioritize product improvements.</li><li>Less Annoying CRM will need to raise prices at some point. Tyler is wondering if now is the right time.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 11 Jun 2020 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/a47e63d4/b6ab07cc.mp3" length="60327623" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3685</itunes:duration>
      <itunes:summary>This we talk about intern projects, Rick's decision to stay focused on Legup Health, and more.</itunes:summary>
      <itunes:subtitle>This we talk about intern projects, Rick's decision to stay focused on Legup Health, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Racism</title>
      <itunes:episode>46</itunes:episode>
      <podcast:episode>46</podcast:episode>
      <itunes:title>Racism</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d793dedc-1c43-46f0-9715-889bb6f925a2</guid>
      <link>https://share.transistor.fm/s/b5b0d6bd</link>
      <description>
        <![CDATA[<p>Disclaimer: This is an awkward topic to discuss, but it needs to be discussed. We do not claim to be experts, but we believe that as privileged white men, it's our responsibility to try to learn, challenge ourselves, and evolve. This conversation is a part of our attempt to do so.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Disclaimer: This is an awkward topic to discuss, but it needs to be discussed. We do not claim to be experts, but we believe that as privileged white men, it's our responsibility to try to learn, challenge ourselves, and evolve. This conversation is a part of our attempt to do so.</p>]]>
      </content:encoded>
      <pubDate>Thu, 04 Jun 2020 18:30:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/b5b0d6bd/5ae77888.mp3" length="55392728" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3963</itunes:duration>
      <itunes:summary>Because of the murder of George Floyd and the protests in America right now, we're taking a break from our normal format</itunes:summary>
      <itunes:subtitle>Because of the murder of George Floyd and the protests in America right now, we're taking a break from our normal format</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Weighing options</title>
      <itunes:episode>45</itunes:episode>
      <podcast:episode>45</podcast:episode>
      <itunes:title>Weighing options</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">55333fe3-c2bf-4079-9588-9302ed07c50f</guid>
      <link>https://share.transistor.fm/s/302510da</link>
      <description>
        <![CDATA[<p>Here are some of the topics we covered this week:</p><ul><li>Tyler's interns started and they're keeping him busy.</li><li>Rick took a vacation over Memorial day weekend and feels refreshed.</li><li>Tyler has been brainstorming his product strategy more since last week.</li><li>Tyler gives an update on how May has been for Less Annoying CRM financially.</li><li>Rick has added his first non "beta" client.</li><li>Tyler used GDPR to get a company to delete some data.</li><li>Rick has a new professional opportunity that would come at the expense of LegUp Health.</li><li>We discuss the merits of masterminds and talk about the Microconf community.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some of the topics we covered this week:</p><ul><li>Tyler's interns started and they're keeping him busy.</li><li>Rick took a vacation over Memorial day weekend and feels refreshed.</li><li>Tyler has been brainstorming his product strategy more since last week.</li><li>Tyler gives an update on how May has been for Less Annoying CRM financially.</li><li>Rick has added his first non "beta" client.</li><li>Tyler used GDPR to get a company to delete some data.</li><li>Rick has a new professional opportunity that would come at the expense of LegUp Health.</li><li>We discuss the merits of masterminds and talk about the Microconf community.</li></ul>]]>
      </content:encoded>
      <pubDate>Fri, 29 May 2020 10:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/302510da/8125c41c.mp3" length="60236164" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3718</itunes:duration>
      <itunes:summary>This week, Tyler talks about the new interns and Rick discusses a potential new opportunity that fell into his lap</itunes:summary>
      <itunes:subtitle>This week, Tyler talks about the new interns and Rick discusses a potential new opportunity that fell into his lap</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>First revenue in the bank</title>
      <itunes:episode>44</itunes:episode>
      <podcast:episode>44</podcast:episode>
      <itunes:title>First revenue in the bank</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5448f659-319f-4d29-940f-df52a696ccd4</guid>
      <link>https://share.transistor.fm/s/cda6b33f</link>
      <description>
        <![CDATA[<p>Here are some of the topics we discussed this week:</p><ul><li>Rick made his first revenue with LegUp Health</li><li>Tyler pimped out his home office with a new chair</li><li>Rick is using Heap for product analytics</li><li>Less Annoying CRM had a "CRM Coach day of rest" where developers handled support for the day</li><li>Rick's intern has started and is already paying off</li><li>Tyler has a new framework for thinking about product improvements</li><li>We discuss how several tech companies are moving to a more permanent remote work model</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some of the topics we discussed this week:</p><ul><li>Rick made his first revenue with LegUp Health</li><li>Tyler pimped out his home office with a new chair</li><li>Rick is using Heap for product analytics</li><li>Less Annoying CRM had a "CRM Coach day of rest" where developers handled support for the day</li><li>Rick's intern has started and is already paying off</li><li>Tyler has a new framework for thinking about product improvements</li><li>We discuss how several tech companies are moving to a more permanent remote work model</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 21 May 2020 19:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/cda6b33f/65cc4986.mp3" length="62094751" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3608</itunes:duration>
      <itunes:summary>Rick sees his first revenue with LegUp Health, and Tyler has some new ideas about how to think about Less Annoying CRM's product roadmap</itunes:summary>
      <itunes:subtitle>Rick sees his first revenue with LegUp Health, and Tyler has some new ideas about how to think about Less Annoying CRM's product roadmap</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The interns are coming</title>
      <itunes:episode>43</itunes:episode>
      <podcast:episode>43</podcast:episode>
      <itunes:title>The interns are coming</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5ba66af7-5bcc-4e44-a6c8-33671320e82a</guid>
      <link>https://share.transistor.fm/s/7ad9c2fc</link>
      <description>
        <![CDATA[<p>Here are the topics we covered this week:</p><ul><li>Tyler got a new standing desk.</li><li>Rick hit a wall with his product.</li><li>Both Rick and Tyler have interns starting soon. There's a lot of work to do to prepare.</li><li>Less Annoying CRM had a breakthrough with their demo call workflow.</li><li>Rick learned from the wisdom of Charlie Munger.</li><li>Tyler is thinking about analytics because of a fan suggestion.</li><li>LegUp Health got their first user referral.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are the topics we covered this week:</p><ul><li>Tyler got a new standing desk.</li><li>Rick hit a wall with his product.</li><li>Both Rick and Tyler have interns starting soon. There's a lot of work to do to prepare.</li><li>Less Annoying CRM had a breakthrough with their demo call workflow.</li><li>Rick learned from the wisdom of Charlie Munger.</li><li>Tyler is thinking about analytics because of a fan suggestion.</li><li>LegUp Health got their first user referral.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 14 May 2020 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7ad9c2fc/e8f05429.mp3" length="49302122" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3045</itunes:duration>
      <itunes:summary>Tyler has an army of interns starting next week, and Rick just hired his company's first</itunes:summary>
      <itunes:subtitle>Tyler has an army of interns starting next week, and Rick just hired his company's first</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>It's all about the updates</title>
      <itunes:episode>42</itunes:episode>
      <podcast:episode>42</podcast:episode>
      <itunes:title>It's all about the updates</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c2b39dc7-7172-407f-83cd-27df2d7096b3</guid>
      <link>https://share.transistor.fm/s/82328624</link>
      <description>
        <![CDATA[<p>We tried out a new format in this episode. Instead of picking a deep dive topic and spending most of the time on that, we both had a lot of updates to give, so we spent the entire episode on that. Here are some of the topics we covered:</p><ul><li>Rick finished a project for a consulting client that probably won't get used. He talked about how deflating that feels, and how managers should be careful when doing this to employees.</li><li>Less Annoying CRM just received money through the PPP and we discuss what should be done with the extra cash that frees up.</li><li>Rick is dissolving one of his businesses as of July.</li><li>Tyler reached a better understanding of when optimizations are good (i.e. everyone benefits) vs. when they're bad (i.e. the company makes money but the customer experience becomes worse)</li><li>Rick's business taxes are done and we discussed the value of having an accountant who understands your unique needs.</li><li>Tyler is thinking about moving Less Annoying CRM's marketing site to Webflow. We discussed the merits of building web sites in-house vs. using a third-party platform.</li><li>Rick is looking into analytics tools to help understand user behavior.</li><li>College students have been reaching out to Rick asking about internships for Startup to Last.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>We tried out a new format in this episode. Instead of picking a deep dive topic and spending most of the time on that, we both had a lot of updates to give, so we spent the entire episode on that. Here are some of the topics we covered:</p><ul><li>Rick finished a project for a consulting client that probably won't get used. He talked about how deflating that feels, and how managers should be careful when doing this to employees.</li><li>Less Annoying CRM just received money through the PPP and we discuss what should be done with the extra cash that frees up.</li><li>Rick is dissolving one of his businesses as of July.</li><li>Tyler reached a better understanding of when optimizations are good (i.e. everyone benefits) vs. when they're bad (i.e. the company makes money but the customer experience becomes worse)</li><li>Rick's business taxes are done and we discussed the value of having an accountant who understands your unique needs.</li><li>Tyler is thinking about moving Less Annoying CRM's marketing site to Webflow. We discussed the merits of building web sites in-house vs. using a third-party platform.</li><li>Rick is looking into analytics tools to help understand user behavior.</li><li>College students have been reaching out to Rick asking about internships for Startup to Last.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 07 May 2020 17:15:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/82328624/1b1ca3cb.mp3" length="54480357" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3350</itunes:duration>
      <itunes:summary>In this episode, we discuss PPP, taxes, winding down an old company, what types of optimizations are good for the customer, and more.</itunes:summary>
      <itunes:subtitle>In this episode, we discuss PPP, taxes, winding down an old company, what types of optimizations are good for the customer, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The first 100 customers for a B2C company</title>
      <itunes:episode>41</itunes:episode>
      <podcast:episode>41</podcast:episode>
      <itunes:title>The first 100 customers for a B2C company</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">4e4bee48-e675-4bd3-9001-19330c34be93</guid>
      <link>https://share.transistor.fm/s/b3901c88</link>
      <description>
        <![CDATA[<p>The main question we addressed this week was whether Rick should spend his time selling within his personal network (which would be sure to work, but isn't really repeatable or scalable) or start building out a repeatable marketing channel. The main takeaway is that the repeatable channel would be more effective if he had more budget to spend on it, and the way to get there is by getting his revenue up as quickly as possible (which means using non-repeatable methods for now).</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>The main question we addressed this week was whether Rick should spend his time selling within his personal network (which would be sure to work, but isn't really repeatable or scalable) or start building out a repeatable marketing channel. The main takeaway is that the repeatable channel would be more effective if he had more budget to spend on it, and the way to get there is by getting his revenue up as quickly as possible (which means using non-repeatable methods for now).</p>]]>
      </content:encoded>
      <pubDate>Thu, 30 Apr 2020 05:25:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/b3901c88/2a8cf12a.mp3" length="53435194" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3244</itunes:duration>
      <itunes:summary>This week, we talk about how a B2C company should go about acquiring its first 100 customers. Rick is shifting his focus towards growth, and he needs to decide how to spend his time.</itunes:summary>
      <itunes:subtitle>This week, we talk about how a B2C company should go about acquiring its first 100 customers. Rick is shifting his focus towards growth, and he needs to decide how to spend his time.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Marketing during a recession</title>
      <itunes:episode>40</itunes:episode>
      <podcast:episode>40</podcast:episode>
      <itunes:title>Marketing during a recession</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ed55c563-0d78-42a0-a02b-d9c03753a239</guid>
      <link>https://share.transistor.fm/s/e378ca50</link>
      <description>
        <![CDATA[<p>Takeaways from this episode:</p><ul><li>It's important to separate marketing tactics from strategy. It's possible that specific tactics make sense, but you need to understand why you're doing those things? What's the goal?</li><li>It's important to focus on a segment or niche, but not all niches are created equal. The goal is to find a niche where the people within it share with each other so that your work can have a multiplicative effect.</li></ul><p><br></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Takeaways from this episode:</p><ul><li>It's important to separate marketing tactics from strategy. It's possible that specific tactics make sense, but you need to understand why you're doing those things? What's the goal?</li><li>It's important to focus on a segment or niche, but not all niches are created equal. The goal is to find a niche where the people within it share with each other so that your work can have a multiplicative effect.</li></ul><p><br></p>]]>
      </content:encoded>
      <pubDate>Thu, 23 Apr 2020 17:30:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e378ca50/1fc154d4.mp3" length="64119646" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3845</itunes:duration>
      <itunes:summary>This week, we talk about how to market during a recession. When people aren't buying new things, what can you do to get yourself in front of the right people so that they'll be ready to buy when things get back to normal.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to market during a recession. When people aren't buying new things, what can you do to get yourself in front of the right people so that they'll be ready to buy when things get back to normal.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Attracting and compensating operating partners</title>
      <itunes:episode>39</itunes:episode>
      <podcast:episode>39</podcast:episode>
      <itunes:title>Attracting and compensating operating partners</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c6ddee29-1e57-42f9-8dc9-df52a0f14564</guid>
      <link>https://share.transistor.fm/s/7d2a768c</link>
      <description>
        <![CDATA[<p>Takeaways from this episode:</p><ul><li>Rick isn't at a point where he needs to figure this out right now. He thought he might need to know this so he could start courting potential employees for the future, but he can do that without knowing the details of compensation.</li><li>Compensation is a combination of salary, benefits, equity, and other perks. One way or another, you need to put a package together that is competitive. One reason a lot of startups give stock options is because they can't afford to pay a high salary.</li><li>Companies that aren't planning on exiting might not want to give equity because it's not worth much without an exit.</li><li>If you want to share upside with employees without giving equity, you can offer a profit share. There are different models, and you can structure yours to align with the goals and incentives you want to provide to employees.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Takeaways from this episode:</p><ul><li>Rick isn't at a point where he needs to figure this out right now. He thought he might need to know this so he could start courting potential employees for the future, but he can do that without knowing the details of compensation.</li><li>Compensation is a combination of salary, benefits, equity, and other perks. One way or another, you need to put a package together that is competitive. One reason a lot of startups give stock options is because they can't afford to pay a high salary.</li><li>Companies that aren't planning on exiting might not want to give equity because it's not worth much without an exit.</li><li>If you want to share upside with employees without giving equity, you can offer a profit share. There are different models, and you can structure yours to align with the goals and incentives you want to provide to employees.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 16 Apr 2020 17:45:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7d2a768c/95a5d978.mp3" length="62939520" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3758</itunes:duration>
      <itunes:summary>This week, we discuss what Rick can do to give his early employees a share of the upside without giving away equity</itunes:summary>
      <itunes:subtitle>This week, we discuss what Rick can do to give his early employees a share of the upside without giving away equity</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Building remote culture</title>
      <itunes:episode>38</itunes:episode>
      <podcast:episode>38</podcast:episode>
      <itunes:title>Building remote culture</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">2c49bd1e-92e7-4642-8083-d827044df70f</guid>
      <link>https://share.transistor.fm/s/cc0a3497</link>
      <description>
        <![CDATA[<p>There were a variety of different ideas thrown around in this episode. Here are some of the takeaways:</p><ul><li>Ideally, a healthy remote culture won't just mimic an in-person culture, it will actually take advantage of the unique characteristics remote has to offer.</li><li>After companies start going back to in-person work, we shouldn't just go back to business as usual. We should try to maintain the things that are better about remote.</li><li>There are a number of subtle elements of in-person conversations that break down over video chat because of the lag and worse audio quality. This makes it difficult to have more than 5-6 people in the same conversation remotely.<ul><li>One solution to this is to break into smaller groups.</li><li>Another solution is to add structure to the conversation (e.g. everyone goes in a circle taking turns at doing something) so that people know who's turn it is to talk.</li></ul></li><li>Many relationship-building moments are based around sharing experiences. Consider what experiences can be shared online (playing games, watching the same video, etc.)</li><li>There's not currently a tool for high-fidelity, asynchronous communication at a business. This is an opportunity to explore.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>There were a variety of different ideas thrown around in this episode. Here are some of the takeaways:</p><ul><li>Ideally, a healthy remote culture won't just mimic an in-person culture, it will actually take advantage of the unique characteristics remote has to offer.</li><li>After companies start going back to in-person work, we shouldn't just go back to business as usual. We should try to maintain the things that are better about remote.</li><li>There are a number of subtle elements of in-person conversations that break down over video chat because of the lag and worse audio quality. This makes it difficult to have more than 5-6 people in the same conversation remotely.<ul><li>One solution to this is to break into smaller groups.</li><li>Another solution is to add structure to the conversation (e.g. everyone goes in a circle taking turns at doing something) so that people know who's turn it is to talk.</li></ul></li><li>Many relationship-building moments are based around sharing experiences. Consider what experiences can be shared online (playing games, watching the same video, etc.)</li><li>There's not currently a tool for high-fidelity, asynchronous communication at a business. This is an opportunity to explore.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 09 Apr 2020 17:30:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/cc0a3497/fcd823e0.mp3" length="62721063" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3792</itunes:duration>
      <itunes:summary>This week, we talk about how to facilitate building and strengthening relationships between coworkers at a remote company</itunes:summary>
      <itunes:subtitle>This week, we talk about how to facilitate building and strengthening relationships between coworkers at a remote company</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Dealing with impatience as a founder</title>
      <itunes:episode>37</itunes:episode>
      <podcast:episode>37</podcast:episode>
      <itunes:title>Dealing with impatience as a founder</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">75fbce68-9483-4b42-9dfc-9a0d475b64c9</guid>
      <link>https://share.transistor.fm/s/6dc57689</link>
      <description>
        <![CDATA[<p>Here are some takeaways from this week's episode:</p><ul><li>There are two common reasons for a manager to feel impatient: someone isn't motivated to work hard, or they're working hard but not getting enough done.<ul><li>The first type is best to avoid entirely by hiring people who are intrinsically motivated. If you can trust that they aren't intentionally slacking off, it takes a lot of pressure off your plate as a manager.</li><li>The second type is frustrating, but it's not the employee's fault. If they're working hard but not getting the results you want, either your expectations are off, or you're not putting them in a position to succeed.</li></ul></li><li>Deadlines can be a major cause of impatience and can cause stress for the manager and the employee. Avoid deadlines when possible. Instead, break projects into small chunks and set targets, but don't put pressure on anyone to hit those targets exactly.</li><li>If someone misses a target, have a discussion about why. Was it poor planning? Did something unexpected come up? Try to learn from that, but don't let it cause you to become impatient.</li><li>Trust is a huge element in terms of working with urgency without being impatience. Building trust with your team is more about the process than the result. Let employees in on decisions you're making and make sure they feel heard.</li><li>Founders need to manage their own mental state. Design the company to be able to handle slower than anticipated progress because things rarely go according to plan.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some takeaways from this week's episode:</p><ul><li>There are two common reasons for a manager to feel impatient: someone isn't motivated to work hard, or they're working hard but not getting enough done.<ul><li>The first type is best to avoid entirely by hiring people who are intrinsically motivated. If you can trust that they aren't intentionally slacking off, it takes a lot of pressure off your plate as a manager.</li><li>The second type is frustrating, but it's not the employee's fault. If they're working hard but not getting the results you want, either your expectations are off, or you're not putting them in a position to succeed.</li></ul></li><li>Deadlines can be a major cause of impatience and can cause stress for the manager and the employee. Avoid deadlines when possible. Instead, break projects into small chunks and set targets, but don't put pressure on anyone to hit those targets exactly.</li><li>If someone misses a target, have a discussion about why. Was it poor planning? Did something unexpected come up? Try to learn from that, but don't let it cause you to become impatient.</li><li>Trust is a huge element in terms of working with urgency without being impatience. Building trust with your team is more about the process than the result. Let employees in on decisions you're making and make sure they feel heard.</li><li>Founders need to manage their own mental state. Design the company to be able to handle slower than anticipated progress because things rarely go according to plan.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 02 Apr 2020 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/6dc57689/4f901854.mp3" length="70292907" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4134</itunes:duration>
      <itunes:summary>This week, we talk about how a founder or manager can deal with impatience. When you have a vision and it's taking longer than you'd like for it to turn into reality, that can cause problems with the company culture.</itunes:summary>
      <itunes:subtitle>This week, we talk about how a founder or manager can deal with impatience. When you have a vision and it's taking longer than you'd like for it to turn into reality, that can cause problems with the company culture.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Optimizing a customer service team</title>
      <itunes:episode>36</itunes:episode>
      <podcast:episode>36</podcast:episode>
      <itunes:title>Optimizing a customer service team</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">48d72dc2-2cdf-4d09-ac05-2819ff55c447</guid>
      <link>https://share.transistor.fm/s/e9056172</link>
      <description>
        <![CDATA[<p>Here are some takeaways from this week's conversation:</p><ul><li>It's easier to optimize interactions with existing customers rather than new customers who are onboarding because with new customers, every change is more likely to mess up your onboarding funnel. Existing customers have more isolated support events.</li><li>Start by collecting data from the support team on what they're spending their time on. Iterate on that to find insights about why support interactions can be low value.</li><li>Identify the types of customers who aren't going to be a good fit in a self-service way (e.g. a form when they schedule a phone call) so you don't waste both sides' time with a call that doesn't need to happen.</li><li>Put more information on your marketing site to let people disqualify themselves before signing up for a trial.</li><li>This is a big topic. All you can do is collect information, form a hypothesis, and test it. Do that over and over forever.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some takeaways from this week's conversation:</p><ul><li>It's easier to optimize interactions with existing customers rather than new customers who are onboarding because with new customers, every change is more likely to mess up your onboarding funnel. Existing customers have more isolated support events.</li><li>Start by collecting data from the support team on what they're spending their time on. Iterate on that to find insights about why support interactions can be low value.</li><li>Identify the types of customers who aren't going to be a good fit in a self-service way (e.g. a form when they schedule a phone call) so you don't waste both sides' time with a call that doesn't need to happen.</li><li>Put more information on your marketing site to let people disqualify themselves before signing up for a trial.</li><li>This is a big topic. All you can do is collect information, form a hypothesis, and test it. Do that over and over forever.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 26 Mar 2020 17:40:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e9056172/8564deec.mp3" length="56754684" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3428</itunes:duration>
      <itunes:summary>This week, we talk about how to enable a customer service team to spend as much of their time on high-value conversations that really help customers, and less time on conversations that provide no value.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to enable a customer service team to spend as much of their time on high-value conversations that really help customers, and less time on conversations that provide no value.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Writing a startup manifesto</title>
      <itunes:episode>35</itunes:episode>
      <podcast:episode>35</podcast:episode>
      <itunes:title>Writing a startup manifesto</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">3bdaa108-2f57-4290-8818-8d2b5fbd7ed4</guid>
      <link>https://share.transistor.fm/s/8e1aae0b</link>
      <description>
        <![CDATA[<p>First off, sorry about the terrible audio this week. This is probably related to the fact that Tyler is recording from his apartment instead of his office due to COVID-19. We'll get this figured out before next week.</p><p>Here are some takeaways from this episode:</p><ul><li>There are three possible audiences for a startup manifesto: customers, founders, and employees</li><li>The customer-facing version is very different from the founder/employee version because it should focus more on the problem that your company is trying to solve. Write that type of manifesto can be a great way to get people interested in your company before you have a product. It's mostly a marketing play.</li><li>The founder version is mostly useful as a way of keeping you focused on your core values which makes it easier to make decisions. It is especially helpful for knowing what not to do.</li><li>When you hire your first employee, that's probably a good time to take an informal founder version and write it up in more detail so that you can share your vision with employees.</li><li>Because Rick isn't primarily focused on marketing or internal culture right now, he's going to wait to spend time on a manifesto. Instead, he's going to write a press release about what his product might look like in a few months. This will help unblock his product work, but it's not really the same as writing a manifesto.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>First off, sorry about the terrible audio this week. This is probably related to the fact that Tyler is recording from his apartment instead of his office due to COVID-19. We'll get this figured out before next week.</p><p>Here are some takeaways from this episode:</p><ul><li>There are three possible audiences for a startup manifesto: customers, founders, and employees</li><li>The customer-facing version is very different from the founder/employee version because it should focus more on the problem that your company is trying to solve. Write that type of manifesto can be a great way to get people interested in your company before you have a product. It's mostly a marketing play.</li><li>The founder version is mostly useful as a way of keeping you focused on your core values which makes it easier to make decisions. It is especially helpful for knowing what not to do.</li><li>When you hire your first employee, that's probably a good time to take an informal founder version and write it up in more detail so that you can share your vision with employees.</li><li>Because Rick isn't primarily focused on marketing or internal culture right now, he's going to wait to spend time on a manifesto. Instead, he's going to write a press release about what his product might look like in a few months. This will help unblock his product work, but it's not really the same as writing a manifesto.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 19 Mar 2020 06:10:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/8e1aae0b/96de186c.mp3" length="48013559" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3020</itunes:duration>
      <itunes:summary>This week, we discuss how and when to write a manifesto for your startup. What are the reasons to write one, who should the audience be, and what can you do with a manifesto once it's written?</itunes:summary>
      <itunes:subtitle>This week, we discuss how and when to write a manifesto for your startup. What are the reasons to write one, who should the audience be, and what can you do with a manifesto once it's written?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Coronavirus and the stock market crash</title>
      <itunes:episode>34</itunes:episode>
      <podcast:episode>34</podcast:episode>
      <itunes:title>Coronavirus and the stock market crash</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d277c266-f7d7-4781-8bbe-5d6910dc518d</guid>
      <link>https://share.transistor.fm/s/a88d5824</link>
      <description>
        <![CDATA[This week we take a break from our normal deep dive topics to talk about current events. Between the coronavirus and the stock market volatility, a lot has been happening that could potentially impact our businesses and lives.]]>
      </description>
      <content:encoded>
        <![CDATA[This week we take a break from our normal deep dive topics to talk about current events. Between the coronavirus and the stock market volatility, a lot has been happening that could potentially impact our businesses and lives.]]>
      </content:encoded>
      <pubDate>Fri, 13 Mar 2020 11:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/a88d5824/2887eb4e.mp3" length="52214199" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3475</itunes:duration>
      <itunes:summary>This week we take a break from our normal deep dive topics to talk about current events. Between the coronavirus and the stock market volatility, a lot has been happening that could potentially impact our businesses and lives.</itunes:summary>
      <itunes:subtitle>This week we take a break from our normal deep dive topics to talk about current events. Between the coronavirus and the stock market volatility, a lot has been happening that could potentially impact our businesses and lives.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Industry-specific marketing</title>
      <itunes:episode>33</itunes:episode>
      <podcast:episode>33</podcast:episode>
      <itunes:title>Industry-specific marketing</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b15e34ca-e27f-49c4-b04b-d1fd8197f461</guid>
      <link>https://share.transistor.fm/s/20fafd94</link>
      <description>
        <![CDATA[<p>Here are some of the takeaways from this episode:</p><ul><li>Even if your product is good for a large group of people (all small businesses in this case) it can be helpful to focus on a specific segment rather than "boiling the ocean" because it gets easier to acquire new customers as you become more dominant within the segment.</li><li>There are different ways to segment your customers (industry, job title, age, location, etc.). The specific segment you should choose depends on your company, but it's helpful to pick one that can easily be targeted. It might be easier to reach a specific industry (trade shows, etc.) than a specific age group.</li><li>Once you pick an industry, the key is to commit as many resources to dominating that industry as you can, for as long as you can. You won't see results overnight.</li><li>Do everything you can to be known in the industry. Nothing is off the table. Go to trade shows, run ads, sponsor podcasts, write blog posts, build a referral network, etc. The more touch-points you can get with each person in that industry, the easier it will be to acquire them.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some of the takeaways from this episode:</p><ul><li>Even if your product is good for a large group of people (all small businesses in this case) it can be helpful to focus on a specific segment rather than "boiling the ocean" because it gets easier to acquire new customers as you become more dominant within the segment.</li><li>There are different ways to segment your customers (industry, job title, age, location, etc.). The specific segment you should choose depends on your company, but it's helpful to pick one that can easily be targeted. It might be easier to reach a specific industry (trade shows, etc.) than a specific age group.</li><li>Once you pick an industry, the key is to commit as many resources to dominating that industry as you can, for as long as you can. You won't see results overnight.</li><li>Do everything you can to be known in the industry. Nothing is off the table. Go to trade shows, run ads, sponsor podcasts, write blog posts, build a referral network, etc. The more touch-points you can get with each person in that industry, the easier it will be to acquire them.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 27 Feb 2020 17:40:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/20fafd94/8c2ba662.mp3" length="64956462" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3936</itunes:duration>
      <itunes:summary>This week, we talk about how to segment your total audience and design a marketing campaign for a specific industry</itunes:summary>
      <itunes:subtitle>This week, we talk about how to segment your total audience and design a marketing campaign for a specific industry</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Raising non-dilutive funding for your startup</title>
      <itunes:episode>32</itunes:episode>
      <podcast:episode>32</podcast:episode>
      <itunes:title>Raising non-dilutive funding for your startup</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">62be2444-ab88-49df-8e37-8b74ffa2339f</guid>
      <link>https://share.transistor.fm/s/5d672144</link>
      <description>
        <![CDATA[<p>Rick's new business is ramping up, and he's starting to think about how he's going to fund it until it's profitable. He definitely doesn't want to give up any equity at this early stage, so he needs to consider non-dilutive options. Here are some things we cover:</p><ul><li>There are a few main ways to fund a new business without giving up equity:<ul><li>Consult or work a normal job to make money and funnel that into your business</li><li>Enter pitch contests and apply for grants</li><li>Take on debt</li><li>Make enough revenue directly from your customers to pay your expenses (this is ultimately what every bootstrapped company needs to do, it's just a matter of how long it takes to get there)</li></ul></li><li>It's helpful to understand the different capital needs for different parts of your business. Some things might be risky and uncertain. Others might be proven. Rather than thinking "I need $x to run the whole business", break it down by expense type because some might be a better fit for debt (e.g. scaling proven customer acquisition channels) whereas others might need other types of funding (e.g. paying employee salaries).</li><li>For each type of funding, consider how much you'll get out of it relative to the time it takes to get the money. The most obvious thing you get out is the funding, but there might be other benefits that are harder to measure. For example:<ul><li>Winning a startup pitch could help you earn credibility for things like raising money from investors or finding early employees.</li><li>Making money directly from customers might be harder at first, but the effort you're putting in is moving you in the right direction vs. something like consulting which is probably unrelated to your startup's business model.</li></ul></li><li><a href="https://podcasts.apple.com/us/podcast/the-lending-wave/id1470198478?i=1000465356333">This episode</a> of the Out of Beta Podcast discusses ways to think about raising debt</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Rick's new business is ramping up, and he's starting to think about how he's going to fund it until it's profitable. He definitely doesn't want to give up any equity at this early stage, so he needs to consider non-dilutive options. Here are some things we cover:</p><ul><li>There are a few main ways to fund a new business without giving up equity:<ul><li>Consult or work a normal job to make money and funnel that into your business</li><li>Enter pitch contests and apply for grants</li><li>Take on debt</li><li>Make enough revenue directly from your customers to pay your expenses (this is ultimately what every bootstrapped company needs to do, it's just a matter of how long it takes to get there)</li></ul></li><li>It's helpful to understand the different capital needs for different parts of your business. Some things might be risky and uncertain. Others might be proven. Rather than thinking "I need $x to run the whole business", break it down by expense type because some might be a better fit for debt (e.g. scaling proven customer acquisition channels) whereas others might need other types of funding (e.g. paying employee salaries).</li><li>For each type of funding, consider how much you'll get out of it relative to the time it takes to get the money. The most obvious thing you get out is the funding, but there might be other benefits that are harder to measure. For example:<ul><li>Winning a startup pitch could help you earn credibility for things like raising money from investors or finding early employees.</li><li>Making money directly from customers might be harder at first, but the effort you're putting in is moving you in the right direction vs. something like consulting which is probably unrelated to your startup's business model.</li></ul></li><li><a href="https://podcasts.apple.com/us/podcast/the-lending-wave/id1470198478?i=1000465356333">This episode</a> of the Out of Beta Podcast discusses ways to think about raising debt</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 20 Feb 2020 21:30:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/5d672144/567bcd6f.mp3" length="58432064" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3425</itunes:duration>
      <itunes:summary>This week, we discuss options for funding a business without dilution (i.e. giving up equity). From pitch contests and grants to consulting on the side, we walk through all the different options and weight their pros and cons.</itunes:summary>
      <itunes:subtitle>This week, we discuss options for funding a business without dilution (i.e. giving up equity). From pitch contests and grants to consulting on the side, we walk through all the different options and weight their pros and cons.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Running one-on-one meetings with employees</title>
      <itunes:episode>31</itunes:episode>
      <podcast:episode>31</podcast:episode>
      <itunes:title>Running one-on-one meetings with employees</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">69faa56c-f14f-4545-9980-d9eb44189375</guid>
      <link>https://share.transistor.fm/s/f5076090</link>
      <description>
        <![CDATA[<p>The main theme of our discussion was that it's important to understand the objectives of any meeting. Rick helped Tyler narrow the list of objectives down, and now Tyler needs to (1) consider which objectives are most important to him, (2) consider if some of the objectives are being met in other ways so they can be left out of the meeting, and (3) communicate the objectives to employees prior to each meeting so that they can understand what's expected of them.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>The main theme of our discussion was that it's important to understand the objectives of any meeting. Rick helped Tyler narrow the list of objectives down, and now Tyler needs to (1) consider which objectives are most important to him, (2) consider if some of the objectives are being met in other ways so they can be left out of the meeting, and (3) communicate the objectives to employees prior to each meeting so that they can understand what's expected of them.</p>]]>
      </content:encoded>
      <pubDate>Thu, 13 Feb 2020 17:30:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/f5076090/65787a98.mp3" length="58558051" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3490</itunes:duration>
      <itunes:summary>This week, we talk about how to structure periodic meetings with employees. How often should they be, what format should you use, and what are the objectives?</itunes:summary>
      <itunes:subtitle>This week, we talk about how to structure periodic meetings with employees. How often should they be, what format should you use, and what are the objectives?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Structuring your time to maximize productivity</title>
      <itunes:episode>30</itunes:episode>
      <podcast:episode>30</podcast:episode>
      <itunes:title>Structuring your time to maximize productivity</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">54633a7a-be49-4ebc-8076-8850601d49c4</guid>
      <link>https://share.transistor.fm/s/e6963ded</link>
      <description>
        <![CDATA[<p>Here are a few takeaways from this week:</p><ul><li>Identify what your most important work is, and devote most of your time to that. Rick was spending some of his most productive hours on reading and blogging, neither of which are priorities for his business.</li><li>If you have things you have to get done (e.g. client work), try to knock that out early in the week so you can focus on your other work without distractions hanging over you.</li><li>There are two types of work: transactional (meetings, phone calls, routine maintenance, etc.) and creative work (writing, strategy, programming, etc.). Transactional work can be done effectively even when you're not at your most productive, but creative work can't. So try to devote your most productive hours to creative work.</li><li>"Flow state" is when you're in the zone and getting a lot of work done. When working on creative work, one hour in flow state can be more productive than a day of normal productivity. But it's hard to get into flow state, so the key is to protect it once you're in it. To do this, try to structure your days to allow max flexibility to stay focused if you do enter flow state.</li><li>The downside to giving yourself unstructured time for creative work is that it can be hard to manage your mental health. It can lead to stress and burnout because it doesn't follow the "hours worked = productivity" equation of more structured work. Combat this by expecting to go hours or even days without being very productive, and give yourself time to recover if you do end up having a productive streak.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are a few takeaways from this week:</p><ul><li>Identify what your most important work is, and devote most of your time to that. Rick was spending some of his most productive hours on reading and blogging, neither of which are priorities for his business.</li><li>If you have things you have to get done (e.g. client work), try to knock that out early in the week so you can focus on your other work without distractions hanging over you.</li><li>There are two types of work: transactional (meetings, phone calls, routine maintenance, etc.) and creative work (writing, strategy, programming, etc.). Transactional work can be done effectively even when you're not at your most productive, but creative work can't. So try to devote your most productive hours to creative work.</li><li>"Flow state" is when you're in the zone and getting a lot of work done. When working on creative work, one hour in flow state can be more productive than a day of normal productivity. But it's hard to get into flow state, so the key is to protect it once you're in it. To do this, try to structure your days to allow max flexibility to stay focused if you do enter flow state.</li><li>The downside to giving yourself unstructured time for creative work is that it can be hard to manage your mental health. It can lead to stress and burnout because it doesn't follow the "hours worked = productivity" equation of more structured work. Combat this by expecting to go hours or even days without being very productive, and give yourself time to recover if you do end up having a productive streak.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 06 Feb 2020 18:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/e6963ded/84050314.mp3" length="53541673" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3171</itunes:duration>
      <itunes:summary>This week, we're going to talk about how to structure a week in a way that allows you to spend your most productive time on your most important work.</itunes:summary>
      <itunes:subtitle>This week, we're going to talk about how to structure a week in a way that allows you to spend your most productive time on your most important work.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What programmers can do to help with marketing</title>
      <itunes:episode>29</itunes:episode>
      <podcast:episode>29</podcast:episode>
      <itunes:title>What programmers can do to help with marketing</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b10c79ac-c873-4b0a-8027-6e6e043f753b</guid>
      <link>https://share.transistor.fm/s/a72aebf2</link>
      <description>
        <![CDATA[<p>Here are some takeaways from this week's episode:</p><ul><li>Marketing can be broken down into two categories: (1) bringing new people into the top of your funnel and (2) optimizing the conversion rates within your funnel. A lot of technical marketing projects are more about the second than the first. This can be helpful, but there's a ceiling to how effective marketing can be within increasing the top of the funnel.</li><li>Increasing the top of the funnel is all about figuring out where your potential customers are, meeting them there, and telling your story. This can be done via inbound marketing (content creation, SEO, etc.) and outbound marketing (advertising, trade shows, participating in online communities, etc.)</li><li>In order to know where to target your outreach, it's important to understand your existing customers. Where did they come from? What was their buying journey. This can be done by having one-on-one conversations with them, but it can also be automated by having analytics on your website, asking questions when someone signs up, etc.</li><li>Because Tyler is interested in technical projects that help with marketing, a good approach is to build technology to help collect the right information about existing leads/customers so that the non-technical members of his team can understand where to focus their efforts to drive more people into the top of the funnel.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here are some takeaways from this week's episode:</p><ul><li>Marketing can be broken down into two categories: (1) bringing new people into the top of your funnel and (2) optimizing the conversion rates within your funnel. A lot of technical marketing projects are more about the second than the first. This can be helpful, but there's a ceiling to how effective marketing can be within increasing the top of the funnel.</li><li>Increasing the top of the funnel is all about figuring out where your potential customers are, meeting them there, and telling your story. This can be done via inbound marketing (content creation, SEO, etc.) and outbound marketing (advertising, trade shows, participating in online communities, etc.)</li><li>In order to know where to target your outreach, it's important to understand your existing customers. Where did they come from? What was their buying journey. This can be done by having one-on-one conversations with them, but it can also be automated by having analytics on your website, asking questions when someone signs up, etc.</li><li>Because Tyler is interested in technical projects that help with marketing, a good approach is to build technology to help collect the right information about existing leads/customers so that the non-technical members of his team can understand where to focus their efforts to drive more people into the top of the funnel.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 30 Jan 2020 17:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/a72aebf2/31712991.mp3" length="57089884" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3460</itunes:duration>
      <itunes:summary>This week, Rick gives Tyler some advice on how to make the most of his work retreat. Specifically, Tyler is a programmer who wants to build tools to help the marketing efforts at Less Annoying CRM, and Rick will suggest how those tools can fit into a broader marketing strategy.</itunes:summary>
      <itunes:subtitle>This week, Rick gives Tyler some advice on how to make the most of his work retreat. Specifically, Tyler is a programmer who wants to build tools to help the marketing efforts at Less Annoying CRM, and Rick will suggest how those tools can fit into a broa</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to acquire customers in the early days</title>
      <itunes:episode>28</itunes:episode>
      <podcast:episode>28</podcast:episode>
      <itunes:title>How to acquire customers in the early days</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">235850db-5a60-4949-b119-f7ff703f2575</guid>
      <link>https://share.transistor.fm/s/1b6f0185</link>
      <description>
        <![CDATA[<p>Acquiring customers will be different for every business, but there are a few themes we discussed that should apply to almost any business:</p><ul><li>There are two goals when acquiring early customers: 1) Growing your business, and 2) Learning what works and what doesn't. Some growth channels might work for one or the other, but the best approach is to do both at the same time.</li><li>Identify what type of person you want to sell to. You can use intuition for this, but if you already have a few customers, it's helpful to start by looking at what they have in common and trying to find more people like that.</li><li>Conversations are key to learning. Even if you don't plan on selling your product one-on-one forever, you need to talk to customers (in person, over the phone, over email, whatever) so you can learn from them.</li><li>If you don't already have access to the right people to have conversations, you can try advertising or cold outreach. Every business will be different, but the key is to identify the right people and go where they are.</li><li>It's very difficult to change someone's behavior, so try to find people who are already doing whatever your product is meant for.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Acquiring customers will be different for every business, but there are a few themes we discussed that should apply to almost any business:</p><ul><li>There are two goals when acquiring early customers: 1) Growing your business, and 2) Learning what works and what doesn't. Some growth channels might work for one or the other, but the best approach is to do both at the same time.</li><li>Identify what type of person you want to sell to. You can use intuition for this, but if you already have a few customers, it's helpful to start by looking at what they have in common and trying to find more people like that.</li><li>Conversations are key to learning. Even if you don't plan on selling your product one-on-one forever, you need to talk to customers (in person, over the phone, over email, whatever) so you can learn from them.</li><li>If you don't already have access to the right people to have conversations, you can try advertising or cold outreach. Every business will be different, but the key is to identify the right people and go where they are.</li><li>It's very difficult to change someone's behavior, so try to find people who are already doing whatever your product is meant for.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 23 Jan 2020 17:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1b6f0185/2fd68fd3.mp3" length="68848670" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>4104</itunes:duration>
      <itunes:summary>This week, we talk about one of the most fundamental issues that every startup faces: how to acquire customers in the early days. Rick has validated his idea for Legup Health and now it’s time to go out and bootstrap his way to profitability</itunes:summary>
      <itunes:subtitle>This week, we talk about one of the most fundamental issues that every startup faces: how to acquire customers in the early days. Rick has validated his idea for Legup Health and now it’s time to go out and bootstrap his way to profitability</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Building a simple financial model</title>
      <itunes:episode>27</itunes:episode>
      <podcast:episode>27</podcast:episode>
      <itunes:title>Building a simple financial model</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">6892ca03-6764-4b40-99f0-201b161c1c72</guid>
      <link>https://share.transistor.fm/s/609385ee</link>
      <description>
        <![CDATA[<p>It's impossible to cover the entirety of this topic in one episode, but there were some key takeaways that should apply to pretty much any startup:</p><ul><li>A financial model is something that takes inputs (e.g. historic data and assumptions about the future) and gives outputs (e.g. how much money might you make this year). It can be as simple as some notes on a piece of paper, or it can be much more complicated.</li><li>There's no standard model that everyone should follow. The key is to figure out what questions you have, and build a model that will answer them.</li><li>In some cases you'll want more than one model. For example, you might make a specific model to help predict what your customer acquisition could look like in the future, and then use the output of that as an input of a higher-level model predicting what your overall profit might be.</li><li>The complexity of your model probably depends on the complexity of your business. Don't compare yourself with other companies.</li><li>Having said that, you might find the process of building a model helpful as a way to force you to think through your business.</li><li>If you're trying to raise money, your model needs to communicate information to them which you might not otherwise be interested in. Things can get more complicated at that point.</li><li>Understanding all of the above, building a model is just a matter of opening up Excel, entering the inputs, and doing your best to generate reasonable estimates for the outputs. Each model is different, so it's hard to be more specific than that.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>It's impossible to cover the entirety of this topic in one episode, but there were some key takeaways that should apply to pretty much any startup:</p><ul><li>A financial model is something that takes inputs (e.g. historic data and assumptions about the future) and gives outputs (e.g. how much money might you make this year). It can be as simple as some notes on a piece of paper, or it can be much more complicated.</li><li>There's no standard model that everyone should follow. The key is to figure out what questions you have, and build a model that will answer them.</li><li>In some cases you'll want more than one model. For example, you might make a specific model to help predict what your customer acquisition could look like in the future, and then use the output of that as an input of a higher-level model predicting what your overall profit might be.</li><li>The complexity of your model probably depends on the complexity of your business. Don't compare yourself with other companies.</li><li>Having said that, you might find the process of building a model helpful as a way to force you to think through your business.</li><li>If you're trying to raise money, your model needs to communicate information to them which you might not otherwise be interested in. Things can get more complicated at that point.</li><li>Understanding all of the above, building a model is just a matter of opening up Excel, entering the inputs, and doing your best to generate reasonable estimates for the outputs. Each model is different, so it's hard to be more specific than that.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 16 Jan 2020 19:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/609385ee/858a01c4.mp3" length="57269178" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3594</itunes:duration>
      <itunes:summary>This week, we discuss financial models. What are they for, what should be included in them, and how sophisticated to they need to be for different types of businesses?</itunes:summary>
      <itunes:subtitle>This week, we discuss financial models. What are they for, what should be included in them, and how sophisticated to they need to be for different types of businesses?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>What it means to startup to last</title>
      <itunes:episode>26</itunes:episode>
      <podcast:episode>26</podcast:episode>
      <itunes:title>What it means to startup to last</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">a61e4fe1-3cc5-41f8-8468-1400d374ef42</guid>
      <link>https://share.transistor.fm/s/1419fa53</link>
      <description>
        <![CDATA[<p>We considered having this conversation privately, but since almost every business should have a conversation like this, we decided to record it in the hopes that the discussion is helpful for others. As expected, this ended up being a bigger topic than we could cover in a single episode, but we did start narrowing down on some ideas and constraints around the idea of starting up to last:</p><ul><li>Traditional entrepreneurship is already set up well if your goal is to become as rich as possible. Startup to last companies should probably have some other motivation such as enjoying the work, feeling fulfilled by the impact the company has, etc.</li><li>Despite needing to be motivated by something other than money, sustainability is key to survival, and that means that every business needs to at least make enough money to make it worthwhile for the founders. That's the first priority, and then once that "enough" number has been reached, it's time to start focusing on non-monetary goals.</li><li>It's only possible to run a company this way if all shareholders are on board. It's not hard to get founders, employees, and customers aligned. It's harder, but maybe not impossible, to get investors on the same page (venture capitalists specifically are unlikely to want this approach). This is why bootstrapping is common among these types of companies.</li><li>Because the goals of startup to last companies are different so are the rules. We didn't get too deep into how this might impact how you operate the business, but there's a lot to discuss there.</li><li>It's helpful to think about the company as a place you'll work for the rest of your professional life (even if that's not true). That will help you prioritize sustainability, enjoyment and fulfillment. Companies that expect to exit soon can justify burnout-level work environments because they know it doesn't have to last.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>We considered having this conversation privately, but since almost every business should have a conversation like this, we decided to record it in the hopes that the discussion is helpful for others. As expected, this ended up being a bigger topic than we could cover in a single episode, but we did start narrowing down on some ideas and constraints around the idea of starting up to last:</p><ul><li>Traditional entrepreneurship is already set up well if your goal is to become as rich as possible. Startup to last companies should probably have some other motivation such as enjoying the work, feeling fulfilled by the impact the company has, etc.</li><li>Despite needing to be motivated by something other than money, sustainability is key to survival, and that means that every business needs to at least make enough money to make it worthwhile for the founders. That's the first priority, and then once that "enough" number has been reached, it's time to start focusing on non-monetary goals.</li><li>It's only possible to run a company this way if all shareholders are on board. It's not hard to get founders, employees, and customers aligned. It's harder, but maybe not impossible, to get investors on the same page (venture capitalists specifically are unlikely to want this approach). This is why bootstrapping is common among these types of companies.</li><li>Because the goals of startup to last companies are different so are the rules. We didn't get too deep into how this might impact how you operate the business, but there's a lot to discuss there.</li><li>It's helpful to think about the company as a place you'll work for the rest of your professional life (even if that's not true). That will help you prioritize sustainability, enjoyment and fulfillment. Companies that expect to exit soon can justify burnout-level work environments because they know it doesn't have to last.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 09 Jan 2020 17:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1419fa53/d10d915b.mp3" length="60266224" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3771</itunes:duration>
      <itunes:summary>This week, we go all meta and discuss what "startup to last" actually means. Why did we name the podcast this, and what characteristics do "startup to last" companies have in common?</itunes:summary>
      <itunes:subtitle>This week, we go all meta and discuss what "startup to last" actually means. Why did we name the podcast this, and what characteristics do "startup to last" companies have in common?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Onboarding a new hire</title>
      <itunes:episode>25</itunes:episode>
      <podcast:episode>25</podcast:episode>
      <itunes:title>Onboarding a new hire</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">6156ea50-e96c-482b-b27a-4ce2e09eb023</guid>
      <link>https://share.transistor.fm/s/eb41a797</link>
      <description>
        <![CDATA[<p>Takeaways from our conversation:</p><ul><li>Starting a new job is stressful, and one of the main goals should be to make the new employee feel safe. One way to do this is to set expectations are that (a) small enough to be achieved over a short time period and (b) not related to actual job performance at first.<ul><li>In the case of LACRM, expectations will be set around trust. The goal of the first month is for the new hire to feel safe and trust the rest of the team and the company. This way they know they don't need to worry about their job performance during training.</li></ul></li><li>It's valuable to give new hires a lot of context about the business (e.g. the history, who you serve, why, etc.) but this can be hard for employees to retain because they're learning so much at once. One way to help with this is to build everything into the same narrative.<ul><li>In the case of LACRM, because "trust" is the theme of onboarding, it might make sense to center all the other company lessons around that same concept. Instead of teaching new hires about 20 random concepts, explain how each of those concepts leads to trust.</li></ul></li><li>Most importantly: explain to the new hire why you're doing things the way you are. Just giving them info won't be helpful (and might actually be hurtful) if you don't contextualize it. This should be a topic for the first day, or maybe even before the first day.<ul><li>In the case of LACRM, focusing on trust might actually give new hires a reason to distrust the company if it's not explained why trust is so important (they might wonder what happened in the past to cause trust to be such an emphasis).</li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Takeaways from our conversation:</p><ul><li>Starting a new job is stressful, and one of the main goals should be to make the new employee feel safe. One way to do this is to set expectations are that (a) small enough to be achieved over a short time period and (b) not related to actual job performance at first.<ul><li>In the case of LACRM, expectations will be set around trust. The goal of the first month is for the new hire to feel safe and trust the rest of the team and the company. This way they know they don't need to worry about their job performance during training.</li></ul></li><li>It's valuable to give new hires a lot of context about the business (e.g. the history, who you serve, why, etc.) but this can be hard for employees to retain because they're learning so much at once. One way to help with this is to build everything into the same narrative.<ul><li>In the case of LACRM, because "trust" is the theme of onboarding, it might make sense to center all the other company lessons around that same concept. Instead of teaching new hires about 20 random concepts, explain how each of those concepts leads to trust.</li></ul></li><li>Most importantly: explain to the new hire why you're doing things the way you are. Just giving them info won't be helpful (and might actually be hurtful) if you don't contextualize it. This should be a topic for the first day, or maybe even before the first day.<ul><li>In the case of LACRM, focusing on trust might actually give new hires a reason to distrust the company if it's not explained why trust is so important (they might wonder what happened in the past to cause trust to be such an emphasis).</li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 02 Jan 2020 18:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/eb41a797/d1b03e91.mp3" length="54105797" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3285</itunes:duration>
      <itunes:summary>This week, we talk about how to offer a great experience during a new hire's first few weeks. Tyler is about to have a new employee start, and he's looking for ideas on what he can do better.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to offer a great experience during a new hire's first few weeks. Tyler is about to have a new employee start, and he's looking for ideas on what he can do better.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Looking back at 2019 and forward to 2020</title>
      <itunes:episode>24</itunes:episode>
      <podcast:episode>24</podcast:episode>
      <itunes:title>Looking back at 2019 and forward to 2020</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5ccba7c6-03e5-4454-abda-e212efe6f362</guid>
      <link>https://share.transistor.fm/s/031c252e</link>
      <description>
        <![CDATA[<p>This week, we wanted to take some time to reflect on what happened in 2019 and set goals for 2020. We created a series of questions that Rick and Tyler both had to answer. Here are the answers...</p><ul><li>What happened in 2019?<ul><li>In our personal lives<ul><li>Rick: Took 7-8 months of to figure out who he is and what his goals are, especially with his new marriage.</li><li>Tyler: Figured out a sustainable diet</li></ul></li><li>In our professional lives<ul><li>Rick<ul><li>Figured out what he wants to do after leaving his previous job of 11+ years</li><li>Started <a href="https://www.legupventures.com/">LegUp Ventures</a> which is a holding company for his various ventures:<ul><li><a href="https://www.groupcurrent.com/">GroupCurrent</a> - Outsourced member management</li><li>Startup to Last - This podcast</li><li><a href="https://www.ricklindquist.com/">RickLinquist.com</a> - Rick's personal writing</li><li><a href="https://health.legupventures.com/">LegUp Health</a> - Reducing healthcare-related anxiety for people without job-based insurance</li></ul></li></ul></li><li>Tyler<ul><li>Started the year working on a new project called Sparse which was abandoned in February</li><li>The rest of the year was spent on a major redesign of <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a> which included two major new features: Custom fields and Outlook Calendar Sync</li><li>This was the best year for the LACRM product team</li></ul></li></ul></li><li>Biggest accomplishment<ul><li>Tyler: Finally built a real product team at LACRM</li><li>Rick: GroupCurrent turned around the business model of their first client and got it to sustainability</li></ul></li><li>Biggest disappointment<ul><li>Tyler: Sales in the second half of the year were below expectations</li><li>Rick: Wasn't thoughtful enough about getting his wife's buy-in when starting his new ventures</li></ul></li></ul></li><li>Looking forward to 2020<ul><li>Personal goals<ul><li>Rick: Get to a point where he and his wife feel comfortable having kids</li><li>Tyler: Get a dog</li></ul></li><li>High-level professional goals / the theme of 2020<ul><li>Tyler: Continue the product teams momentum and establish a rhythm of regularly shipping updates to LACRM</li><li>Rick: Calm growth. His life is calm right now, and as his ventures pick up, he doesn't want that to change.</li></ul></li><li>Biggest worries / what's keeping you up at night?<ul><li>Rick: Making enough personal income to be able to sustain his ventures</li><li>Tyler: Growth at LACRM needs to pick up eventually</li></ul></li><li>Three specific goals for 2020<ul><li>Tyler<ul><li>Exercise moderately three times per week</li><li>Write code once per week</li><li>By the end of the year, average 50 paying users per month joining LACRM through the referral channel</li></ul></li><li>Rick<ul><li>Play more sports. He has an exercise routine, but it's boring and doesn't involve games or play</li><li>Be ready to start trying to having kids</li><li>Get distribution revenue from LegUp Ventures to $10k/month</li></ul></li><li>Shared goal: Get this podcast to 250 subscribers</li></ul></li><li>Make a prediction for 2020<ul><li>Tyler: Starting a software business without venture capital will become much more mainstream over the next year</li><li>Rick: An all-in-one leader will emerge in the no-code industry</li></ul></li><li>What do you want to read in 2020?<ul><li>Rick: Too many to name, but wants to read a lot about emotions.</li><li>Tyler: <a href="https://www.amazon.com/Unicorn-Project-Developers-Disruption-Thriving-ebook/dp/B07QT9QR41">The unicorn project</a> and <a href="https://www.amazon.com/Obviously-Awesome-Product-Positioning-Customers-ebook/dp/B07PPW5V9C/">Obviously Awesome</a></li></ul></li></ul></li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This week, we wanted to take some time to reflect on what happened in 2019 and set goals for 2020. We created a series of questions that Rick and Tyler both had to answer. Here are the answers...</p><ul><li>What happened in 2019?<ul><li>In our personal lives<ul><li>Rick: Took 7-8 months of to figure out who he is and what his goals are, especially with his new marriage.</li><li>Tyler: Figured out a sustainable diet</li></ul></li><li>In our professional lives<ul><li>Rick<ul><li>Figured out what he wants to do after leaving his previous job of 11+ years</li><li>Started <a href="https://www.legupventures.com/">LegUp Ventures</a> which is a holding company for his various ventures:<ul><li><a href="https://www.groupcurrent.com/">GroupCurrent</a> - Outsourced member management</li><li>Startup to Last - This podcast</li><li><a href="https://www.ricklindquist.com/">RickLinquist.com</a> - Rick's personal writing</li><li><a href="https://health.legupventures.com/">LegUp Health</a> - Reducing healthcare-related anxiety for people without job-based insurance</li></ul></li></ul></li><li>Tyler<ul><li>Started the year working on a new project called Sparse which was abandoned in February</li><li>The rest of the year was spent on a major redesign of <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a> which included two major new features: Custom fields and Outlook Calendar Sync</li><li>This was the best year for the LACRM product team</li></ul></li></ul></li><li>Biggest accomplishment<ul><li>Tyler: Finally built a real product team at LACRM</li><li>Rick: GroupCurrent turned around the business model of their first client and got it to sustainability</li></ul></li><li>Biggest disappointment<ul><li>Tyler: Sales in the second half of the year were below expectations</li><li>Rick: Wasn't thoughtful enough about getting his wife's buy-in when starting his new ventures</li></ul></li></ul></li><li>Looking forward to 2020<ul><li>Personal goals<ul><li>Rick: Get to a point where he and his wife feel comfortable having kids</li><li>Tyler: Get a dog</li></ul></li><li>High-level professional goals / the theme of 2020<ul><li>Tyler: Continue the product teams momentum and establish a rhythm of regularly shipping updates to LACRM</li><li>Rick: Calm growth. His life is calm right now, and as his ventures pick up, he doesn't want that to change.</li></ul></li><li>Biggest worries / what's keeping you up at night?<ul><li>Rick: Making enough personal income to be able to sustain his ventures</li><li>Tyler: Growth at LACRM needs to pick up eventually</li></ul></li><li>Three specific goals for 2020<ul><li>Tyler<ul><li>Exercise moderately three times per week</li><li>Write code once per week</li><li>By the end of the year, average 50 paying users per month joining LACRM through the referral channel</li></ul></li><li>Rick<ul><li>Play more sports. He has an exercise routine, but it's boring and doesn't involve games or play</li><li>Be ready to start trying to having kids</li><li>Get distribution revenue from LegUp Ventures to $10k/month</li></ul></li><li>Shared goal: Get this podcast to 250 subscribers</li></ul></li><li>Make a prediction for 2020<ul><li>Tyler: Starting a software business without venture capital will become much more mainstream over the next year</li><li>Rick: An all-in-one leader will emerge in the no-code industry</li></ul></li><li>What do you want to read in 2020?<ul><li>Rick: Too many to name, but wants to read a lot about emotions.</li><li>Tyler: <a href="https://www.amazon.com/Unicorn-Project-Developers-Disruption-Thriving-ebook/dp/B07QT9QR41">The unicorn project</a> and <a href="https://www.amazon.com/Obviously-Awesome-Product-Positioning-Customers-ebook/dp/B07PPW5V9C/">Obviously Awesome</a></li></ul></li></ul></li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 26 Dec 2019 07:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/031c252e/28d11fe2.mp3" length="58340936" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3543</itunes:duration>
      <itunes:summary>Because this is the last week of the year, we're going to summarize what happened in 2019 and set goals for 2020.</itunes:summary>
      <itunes:subtitle>Because this is the last week of the year, we're going to summarize what happened in 2019 and set goals for 2020.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Delivering awesome customer service for a low ARPU product</title>
      <itunes:episode>23</itunes:episode>
      <podcast:episode>23</podcast:episode>
      <itunes:title>Delivering awesome customer service for a low ARPU product</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">848993d8-6261-4140-a658-0d93c6865f9c</guid>
      <link>https://share.transistor.fm/s/9bd42f98</link>
      <description>
        <![CDATA[<p>Takeaways from our conversation:</p><ul><li>In the early days, a founder can easily offer great customer service just because they're an expert on the topic and are empowered to solve every problem. Rick doesn't need to worry about this at first.</li><li>For a low ARPU (average revenue per user) product, it's best to think of support reps as "coaches" so they can be more proactive and replace other functions such as sales and customer success. It's not viable to have separate teams for each function at a low price point, nor is it desirable.</li><li>Rick's first move should be to do all the coaching himself until he has it systematized. Some of it can be automated with things like tutorial videos, but some of it will need to be manual.</li><li>Once he knows exactly how to manually provide the best coaching and he has enough customers that he can't handle any more, it will be time to start building a team.</li><li>Offering great customer service for a low ARPU product will hurt margins. This might mean that certain investors aren't interested in the business, but it's still possible to be profitable enough to bootstrap.</li></ul>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Takeaways from our conversation:</p><ul><li>In the early days, a founder can easily offer great customer service just because they're an expert on the topic and are empowered to solve every problem. Rick doesn't need to worry about this at first.</li><li>For a low ARPU (average revenue per user) product, it's best to think of support reps as "coaches" so they can be more proactive and replace other functions such as sales and customer success. It's not viable to have separate teams for each function at a low price point, nor is it desirable.</li><li>Rick's first move should be to do all the coaching himself until he has it systematized. Some of it can be automated with things like tutorial videos, but some of it will need to be manual.</li><li>Once he knows exactly how to manually provide the best coaching and he has enough customers that he can't handle any more, it will be time to start building a team.</li><li>Offering great customer service for a low ARPU product will hurt margins. This might mean that certain investors aren't interested in the business, but it's still possible to be profitable enough to bootstrap.</li></ul>]]>
      </content:encoded>
      <pubDate>Thu, 19 Dec 2019 17:30:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/9bd42f98/a2f7fadb.mp3" length="56711055" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3404</itunes:duration>
      <itunes:summary>This week, we talk about how Rick can use customer service as a differentiator for his new company despite the fact that he won't be making much money per customer</itunes:summary>
      <itunes:subtitle>This week, we talk about how Rick can use customer service as a differentiator for his new company despite the fact that he won't be making much money per customer</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Planning a marketing site redesign</title>
      <itunes:episode>22</itunes:episode>
      <podcast:episode>22</podcast:episode>
      <itunes:title>Planning a marketing site redesign</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">14e86662-c1b6-4ce9-be92-06845c3ffec2</guid>
      <link>https://share.transistor.fm/s/caa0fefd</link>
      <description>
        <![CDATA[<p>In this episode, Tyler gets Rick’s advice on how to think about redesigning the <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a> marketing website. Here are some of the takeaways:</p><ul><li><strong>There are different types of website redesigns, including:</strong><ul><li>AB testing (iterating pages on the site based on performance).</li><li>Style update (updating the CSS, or look and feel based on a new brand style guide).</li><li>Restructuring the site (changing the site navigation and pages to better accomplish objectives).</li><li>Rebranding the site (changing the brand name and/or positioning of the site).</li></ul></li><li><strong>You want to do the minimum necessary when you're redesigning a website. </strong><ul><li>Figure out the smallest thing that you know you need and just go do it.</li><li>If you can get away with basic iterative AB testing, that's awesome. It means you're in a really good place. </li><li>If you need a whole rebrand, figure out how to do it as quickly as possible because when you're going through wholesale changes, it's messing with reporting.</li></ul></li><li><strong>When doing a redesign consider the following questions:</strong><ul><li>Is my brand name or positioning changing?<ul><li>If your brand name is changing, you may need to consider transitioning a new domain. (Note: This comes with significant search engine optimization challenges.)  </li><li>If your positioning is changing, you may need to review copy on all of your pages. (Note: This might impact SEO if the copy changes are significant.)</li></ul></li><li>What are the main functions of the site and are they changing?<ul><li>Is it for users to login?</li><li>Is it to generate leads?</li><li>Is it to convert free trials?</li><li>If the functions are changing, you may need to restructure the site (Note: This can impact SEO in a big way if you are onsite links or removing pages).  </li></ul></li><li>How complex is the site?<ul><li>How many unique pages and designs are there on the site?</li><li>Can you get away with designing a few templates and applying them across multiple pages?</li><li>Or, is every page unique?</li><li>More complex sites taking longer to redesign.</li></ul></li><li>Does look and feel (style) need to change?<ul><li>Do colors need to change?</li><li>Do fonts need to change?</li><li>Do page layouts need to change?</li><li>Do UI components need to change?</li></ul></li></ul></li><li><strong>It’s OK to prioritize a redesign based on a standards without data proof.</strong><ul><li>At the end of the day, if brand is important to you, it's important to you. </li><li>If you're failing on your brand promise or standard, that's going to keep you up at night and that's not healthy. </li><li>Just go fix it and don’t waste time trying to justify your brand standards.<p></p></li></ul></li></ul><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Tyler: </strong>So what we're going to talk about is ... I'm actually interested, I'm not entirely sure where this is going to go, but Less Annoying CRM, my company, just did this big redesign that I keep talking about, but that was just the app. So when a customer logs in, the experience they have in the logged in part of it has been redesigned. The other stuff, what I'll call the marketing site here, still looks like it did four or five years ago. And so there's this big mismatch between the, first, impression a customer gets when going to our marketing site versus the actual polished and good design that they get once they log in. So we're basically trying to think about some kind of a redesign of the marketing site. This could be really, really small. It could literally just be like go in and make some CSS tweaks, but leave everything else the same. It could be completely, from the ground up, rethink what this website should even be, think about SEO, switch to a content management system like WordPress or something. It could be as big as we want it to be. So that's basically what we're talking about here. I have a little more context, but maybe what I should say is just what I'm hoping is we can talk through, A, how big of a project should this be and then, B, we're not going to plan the whole thing out in this next 40 minutes or whatever, but where should I start? What should some actions be that I can take to really get moving on this project?</p><p><br></p><p><strong>Rick: </strong>Yeah. So I'm interested in what problems you need to solve by doing this. It sounds like you're mostly concerned about more of a brand consistency or user experience consistency more so than anything else. I'm not hearing, "Hey, we need to get more leads," or, "Man, people are complaining about the website." It seems like it's more of a personal, "Hey, this website is no longer up to my standard," type thing.</p><p><strong>Tyler: </strong>Mm-hmm (affirmative). There's definitely part of that. And, yeah. I'll say, I'm really skeptical about a lot of marketing. I think 20% of marketing is super valuable and critical to a company and I think a lot of it is just a bunch of overpaid people in suits being like, "Oh, your font doesn't communicate the trust that you're ..." Nobody cares about the font. Shut up. So, yeah. I don't want it to be what a marketing agency would turn this project into. The way I look at it is, it's kind of like if you're single and you're dating and you go to a bar to meet somebody, you know that the things that matter are personality and trust and all this, but all you can see is their physical appearance when you walk into the bar. And so people naturally tend to overemphasize that when it comes to first impressions. The same thing is true with a company. Just the other day, actually, for my wedding, I had to get insurance for the wedding and our wedding planner sent us two websites. I went to both of them. One of them had not been redesigned in a decade and one of them looked nice and I was just like, "I have no information here. I can't tell which insurance is better, so I'm just going to go with the one that looks like a more professional company." So that's really what I'm going for is, once someone uses our product, they like it, we treat them well, everything goes well, the personality stuff in the dating analogy is good, but we need to put on a little makeup and actually try at the bar if we're going to get these customers in the first place.</p><p><strong>Rick: </strong>So it sounds like your main concern is what's the first impression people have of Less Annoying CRM when they come to your website.</p><p><strong>Tyler: </strong>Absolutely.</p><p><br></p><p><strong>Why is this a priority right now?<br></strong><br></p><p><strong>Rick: </strong>Okay. So flying up a little higher, just for context, why are we talking about this right now over some other priority? Why do you feel like now is the right time to worry about the first impression?</p><p><strong>Tyler: </strong>That's a fair question. It's possible that it's not. I would say that, probably two years ago was the right time, but the reality was that the app would've let down that first impression either way. So I think it's just, now that the app looks good, I don't think ... Redesigning the app was a nine-month project. I think redesigning the website could be as little as a one-week project. And so I just feel like it's kind of low-hanging fruit because we've done the hard part already.</p><p><strong>Rick: </strong>Interesting.</p><p><strong>Tyler: </strong>But, yeah. If it didn't happen for the next six months, I don't think there would be any real consequences.</p><p><strong>Rick: </strong>Have you talked to any new users who've gone through the existing marketing site experience with the new interface?</p><p>...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Tyler gets Rick’s advice on how to think about redesigning the <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a> marketing website. Here are some of the takeaways:</p><ul><li><strong>There are different types of website redesigns, including:</strong><ul><li>AB testing (iterating pages on the site based on performance).</li><li>Style update (updating the CSS, or look and feel based on a new brand style guide).</li><li>Restructuring the site (changing the site navigation and pages to better accomplish objectives).</li><li>Rebranding the site (changing the brand name and/or positioning of the site).</li></ul></li><li><strong>You want to do the minimum necessary when you're redesigning a website. </strong><ul><li>Figure out the smallest thing that you know you need and just go do it.</li><li>If you can get away with basic iterative AB testing, that's awesome. It means you're in a really good place. </li><li>If you need a whole rebrand, figure out how to do it as quickly as possible because when you're going through wholesale changes, it's messing with reporting.</li></ul></li><li><strong>When doing a redesign consider the following questions:</strong><ul><li>Is my brand name or positioning changing?<ul><li>If your brand name is changing, you may need to consider transitioning a new domain. (Note: This comes with significant search engine optimization challenges.)  </li><li>If your positioning is changing, you may need to review copy on all of your pages. (Note: This might impact SEO if the copy changes are significant.)</li></ul></li><li>What are the main functions of the site and are they changing?<ul><li>Is it for users to login?</li><li>Is it to generate leads?</li><li>Is it to convert free trials?</li><li>If the functions are changing, you may need to restructure the site (Note: This can impact SEO in a big way if you are onsite links or removing pages).  </li></ul></li><li>How complex is the site?<ul><li>How many unique pages and designs are there on the site?</li><li>Can you get away with designing a few templates and applying them across multiple pages?</li><li>Or, is every page unique?</li><li>More complex sites taking longer to redesign.</li></ul></li><li>Does look and feel (style) need to change?<ul><li>Do colors need to change?</li><li>Do fonts need to change?</li><li>Do page layouts need to change?</li><li>Do UI components need to change?</li></ul></li></ul></li><li><strong>It’s OK to prioritize a redesign based on a standards without data proof.</strong><ul><li>At the end of the day, if brand is important to you, it's important to you. </li><li>If you're failing on your brand promise or standard, that's going to keep you up at night and that's not healthy. </li><li>Just go fix it and don’t waste time trying to justify your brand standards.<p></p></li></ul></li></ul><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Tyler: </strong>So what we're going to talk about is ... I'm actually interested, I'm not entirely sure where this is going to go, but Less Annoying CRM, my company, just did this big redesign that I keep talking about, but that was just the app. So when a customer logs in, the experience they have in the logged in part of it has been redesigned. The other stuff, what I'll call the marketing site here, still looks like it did four or five years ago. And so there's this big mismatch between the, first, impression a customer gets when going to our marketing site versus the actual polished and good design that they get once they log in. So we're basically trying to think about some kind of a redesign of the marketing site. This could be really, really small. It could literally just be like go in and make some CSS tweaks, but leave everything else the same. It could be completely, from the ground up, rethink what this website should even be, think about SEO, switch to a content management system like WordPress or something. It could be as big as we want it to be. So that's basically what we're talking about here. I have a little more context, but maybe what I should say is just what I'm hoping is we can talk through, A, how big of a project should this be and then, B, we're not going to plan the whole thing out in this next 40 minutes or whatever, but where should I start? What should some actions be that I can take to really get moving on this project?</p><p><br></p><p><strong>Rick: </strong>Yeah. So I'm interested in what problems you need to solve by doing this. It sounds like you're mostly concerned about more of a brand consistency or user experience consistency more so than anything else. I'm not hearing, "Hey, we need to get more leads," or, "Man, people are complaining about the website." It seems like it's more of a personal, "Hey, this website is no longer up to my standard," type thing.</p><p><strong>Tyler: </strong>Mm-hmm (affirmative). There's definitely part of that. And, yeah. I'll say, I'm really skeptical about a lot of marketing. I think 20% of marketing is super valuable and critical to a company and I think a lot of it is just a bunch of overpaid people in suits being like, "Oh, your font doesn't communicate the trust that you're ..." Nobody cares about the font. Shut up. So, yeah. I don't want it to be what a marketing agency would turn this project into. The way I look at it is, it's kind of like if you're single and you're dating and you go to a bar to meet somebody, you know that the things that matter are personality and trust and all this, but all you can see is their physical appearance when you walk into the bar. And so people naturally tend to overemphasize that when it comes to first impressions. The same thing is true with a company. Just the other day, actually, for my wedding, I had to get insurance for the wedding and our wedding planner sent us two websites. I went to both of them. One of them had not been redesigned in a decade and one of them looked nice and I was just like, "I have no information here. I can't tell which insurance is better, so I'm just going to go with the one that looks like a more professional company." So that's really what I'm going for is, once someone uses our product, they like it, we treat them well, everything goes well, the personality stuff in the dating analogy is good, but we need to put on a little makeup and actually try at the bar if we're going to get these customers in the first place.</p><p><strong>Rick: </strong>So it sounds like your main concern is what's the first impression people have of Less Annoying CRM when they come to your website.</p><p><strong>Tyler: </strong>Absolutely.</p><p><br></p><p><strong>Why is this a priority right now?<br></strong><br></p><p><strong>Rick: </strong>Okay. So flying up a little higher, just for context, why are we talking about this right now over some other priority? Why do you feel like now is the right time to worry about the first impression?</p><p><strong>Tyler: </strong>That's a fair question. It's possible that it's not. I would say that, probably two years ago was the right time, but the reality was that the app would've let down that first impression either way. So I think it's just, now that the app looks good, I don't think ... Redesigning the app was a nine-month project. I think redesigning the website could be as little as a one-week project. And so I just feel like it's kind of low-hanging fruit because we've done the hard part already.</p><p><strong>Rick: </strong>Interesting.</p><p><strong>Tyler: </strong>But, yeah. If it didn't happen for the next six months, I don't think there would be any real consequences.</p><p><strong>Rick: </strong>Have you talked to any new users who've gone through the existing marketing site experience with the new interface?</p><p>...</p>]]>
      </content:encoded>
      <pubDate>Thu, 12 Dec 2019 18:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/caa0fefd/6e14c0d7.mp3" length="55999026" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3356</itunes:duration>
      <itunes:summary>This week, we talk about redesigning Less Annoying CRM’s marketing site. Tyler's company just finished a major redesign of the app, and now the marketing site doesn’t do it justice. Rick gives advice on how to approach the project.</itunes:summary>
      <itunes:subtitle>This week, we talk about redesigning Less Annoying CRM’s marketing site. Tyler's company just finished a major redesign of the app, and now the marketing site doesn’t do it justice. Rick gives advice on how to approach the project.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The role of emotions in business</title>
      <itunes:episode>21</itunes:episode>
      <podcast:episode>21</podcast:episode>
      <itunes:title>The role of emotions in business</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f4eb57ee-5ddb-47e1-bf6e-88384cf64066</guid>
      <link>https://share.transistor.fm/s/10f5abd7</link>
      <description>
        <![CDATA[<p>In this episode as part of some research for his next book, Rick interviews Tyler about his experience with emotions in the <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a> workplace. Here are some of the takeaways:</p><ul><li><strong>There are frameworks out there for emotional intelligence, self-regulation, but there isn’t much stuff out there about how emotions impact company culture, team performance, and leadership.</strong><ul><li>There aren’t a ton of CEOs talking about their own experiences.</li><li>Most of the stories out there are from therapists about their anonymous clients.</li></ul></li><li><strong>There isn't agreement on the definition of emotion.</strong><ul><li>One model is <a href="https://en.wikipedia.org/wiki/Robert_Plutchik">Robert Plutchik’s</a> wheel of emotions (see image below) that defines 8 primary emotions: <ul><li>joy and sadness</li><li>anger and fear</li><li>trust and disgust</li><li>surprise and anticipation</li></ul></li></ul></li><li><strong>A leader who priorities trust may be more likely to create a safer culture where people are free to express their emotions.</strong><ul><li>This makes it so that the emotions that you and other people experience happen in a way that is healthy, and has a mostly positive impact on other people (and  team performance / culture).</li><li>It also makes it safe for everyone to inquire about clarifying the meaning of each others’ emotions (instead of making assumptions).</li><li>When you're in a distrusting situation, emotions are probably more violent in a negative way.</li></ul></li><li><strong>Trust relies on character and authenticity.</strong><ul><li>You might experience trust when you see someone do something that's not in their own best interest, but they do it because they think it's right or some set of values.</li><li>Competence may also play a part.</li></ul></li><li><strong>Distrust leads to distrust</strong><ul><li>If you hire and keep people who you don’t trust, it can lead to a negative cycle of distrust.</li></ul></li><li><strong>One source of potentially negative emotion for leaders is the time between becoming aware of a problem and figuring out what to do about it</strong><ul><li>If you have don’t have a high-trust environment, this can be a risky time period when emotions might be misinterpreted</li><li>Another source of potentially negative emotion is when an employee leaves<p></p></li></ul></li></ul><p>What else would you add to this list?</p><p><br></p><p></p><p>Source: <a href="https://en.wikipedia.org/wiki/Robert_Plutchik#/media/File:Plutchik-wheel.svg">Wikipedia</a></p><p><br></p><p><strong>Context</strong></p><p><br></p><p><strong>Rick:</strong> It's my week for the topic. I don't really have a critical problem per se to bring you that I want to brainstorm with you, at least not more important than what I'm bringing to you today. So taking a slightly different approach with the topic I'm bringing, and it could be a total bust, so I'm prepared for bad feedback from this from the audience. But maybe this works. I guess listeners out there, if you listen to this and you don't get value, please tell us so that we don't repeat this. But if you do like it, please tell us because we'll have more confidence covering topics like this in the future. Now that I've got my writing cadence going at <a href="https://www.ricklindquist.com/">RickLindquist.com</a>, I spend two to three hours every morning before 9:00 AM researching and writing about a topic of my choice. My goal is not to just throw out content, it's primarily learning through the process of writing. And so I want <a href="https://www.ricklindquist.com/projects">to write a book about emotions, leadership, and teams</a>, and I'm starting to outline that book in terms of what would the table of contents be so it can drive my research. Because I'm going to be learning a lot as I go because I'm not an expert on emotions by any means, I know that the specific angle I'm going to take and the specific outline is going to change over time, but I hope that by constantly revising the outline based on what I'm learning, it can drive my short-term and short-form writing on a weekly so that I'm killing two birds with one stone. I'm writing and fulfilling what I want to do at RickLindquist.com in terms of outputting content, but I'm also learning the things necessary as part of research for this larger book. It may take me a whole year to write this thing. It's just a question of putting a couple of hours in a day most days. I started this week researching emotions and building the outline. I'm stunned at how little agreement there is on how emotions work and how they impact people. Most of what I'm reading is research and academic papers. I have not been able to find a ton of CEOs talking publicly about the role of emotions in leadership and in teams. Kind of coming back to listeners out there, I personally think that this is a topic that we all need to talk about more because I hypothesize that we can become better leaders if we're more in touch with our own emotions and others' emotions because it's the basis for how we form trust with our strong relationships. And trust is the ultimate success factor for a highly functioning team. But I'm trying to do research. I'm having trouble finding like layman's explanations of the stuff with consensus. I was hoping today that I could, I don't want to say interrogate, but I kind of have a feeling that I need to ask you some tough questions. I want to ask you some tough questions about your experience with emotions, both from how they happen in your head and within your body, as a leader and CEO. Then also, how you react and observe and handle emotions of team members in the day-to-day stuff. We've talked offline I know you've, we've talked offline and made sure that was okay, but is there anything that's off limits in terms of asking you questions?</p><p><br></p><p><strong>Tyler:</strong> No, I mean there might be ... I'm happy to share my own experiences and I might be a little more secretive if I feel like I'm exposing something about someone else who hasn't necessarily given permission. But for myself, now I think I'm an open book. We'll see.</p><p><strong>Rick:</strong> Yeah. Cool. Listeners, I think that the other thing that we want to do here is I want to model talking about this openly, so I'll also jump in with my own insights on emotions. I'm a pretty, in terms of like emotional spectrum, I wear my emotions on my sleeve much more than Tyler does. Not to say that we're both not emotional people, it's just we may have very different experiences with emotions because of our personalities. I'll jump in when I can add a personal take. Would you add any anything?</p><p><strong>Tyler:</strong> I'm curious here, so I don't hear people maybe using the word emotions a lot, but I hear people talking about m...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode as part of some research for his next book, Rick interviews Tyler about his experience with emotions in the <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a> workplace. Here are some of the takeaways:</p><ul><li><strong>There are frameworks out there for emotional intelligence, self-regulation, but there isn’t much stuff out there about how emotions impact company culture, team performance, and leadership.</strong><ul><li>There aren’t a ton of CEOs talking about their own experiences.</li><li>Most of the stories out there are from therapists about their anonymous clients.</li></ul></li><li><strong>There isn't agreement on the definition of emotion.</strong><ul><li>One model is <a href="https://en.wikipedia.org/wiki/Robert_Plutchik">Robert Plutchik’s</a> wheel of emotions (see image below) that defines 8 primary emotions: <ul><li>joy and sadness</li><li>anger and fear</li><li>trust and disgust</li><li>surprise and anticipation</li></ul></li></ul></li><li><strong>A leader who priorities trust may be more likely to create a safer culture where people are free to express their emotions.</strong><ul><li>This makes it so that the emotions that you and other people experience happen in a way that is healthy, and has a mostly positive impact on other people (and  team performance / culture).</li><li>It also makes it safe for everyone to inquire about clarifying the meaning of each others’ emotions (instead of making assumptions).</li><li>When you're in a distrusting situation, emotions are probably more violent in a negative way.</li></ul></li><li><strong>Trust relies on character and authenticity.</strong><ul><li>You might experience trust when you see someone do something that's not in their own best interest, but they do it because they think it's right or some set of values.</li><li>Competence may also play a part.</li></ul></li><li><strong>Distrust leads to distrust</strong><ul><li>If you hire and keep people who you don’t trust, it can lead to a negative cycle of distrust.</li></ul></li><li><strong>One source of potentially negative emotion for leaders is the time between becoming aware of a problem and figuring out what to do about it</strong><ul><li>If you have don’t have a high-trust environment, this can be a risky time period when emotions might be misinterpreted</li><li>Another source of potentially negative emotion is when an employee leaves<p></p></li></ul></li></ul><p>What else would you add to this list?</p><p><br></p><p></p><p>Source: <a href="https://en.wikipedia.org/wiki/Robert_Plutchik#/media/File:Plutchik-wheel.svg">Wikipedia</a></p><p><br></p><p><strong>Context</strong></p><p><br></p><p><strong>Rick:</strong> It's my week for the topic. I don't really have a critical problem per se to bring you that I want to brainstorm with you, at least not more important than what I'm bringing to you today. So taking a slightly different approach with the topic I'm bringing, and it could be a total bust, so I'm prepared for bad feedback from this from the audience. But maybe this works. I guess listeners out there, if you listen to this and you don't get value, please tell us so that we don't repeat this. But if you do like it, please tell us because we'll have more confidence covering topics like this in the future. Now that I've got my writing cadence going at <a href="https://www.ricklindquist.com/">RickLindquist.com</a>, I spend two to three hours every morning before 9:00 AM researching and writing about a topic of my choice. My goal is not to just throw out content, it's primarily learning through the process of writing. And so I want <a href="https://www.ricklindquist.com/projects">to write a book about emotions, leadership, and teams</a>, and I'm starting to outline that book in terms of what would the table of contents be so it can drive my research. Because I'm going to be learning a lot as I go because I'm not an expert on emotions by any means, I know that the specific angle I'm going to take and the specific outline is going to change over time, but I hope that by constantly revising the outline based on what I'm learning, it can drive my short-term and short-form writing on a weekly so that I'm killing two birds with one stone. I'm writing and fulfilling what I want to do at RickLindquist.com in terms of outputting content, but I'm also learning the things necessary as part of research for this larger book. It may take me a whole year to write this thing. It's just a question of putting a couple of hours in a day most days. I started this week researching emotions and building the outline. I'm stunned at how little agreement there is on how emotions work and how they impact people. Most of what I'm reading is research and academic papers. I have not been able to find a ton of CEOs talking publicly about the role of emotions in leadership and in teams. Kind of coming back to listeners out there, I personally think that this is a topic that we all need to talk about more because I hypothesize that we can become better leaders if we're more in touch with our own emotions and others' emotions because it's the basis for how we form trust with our strong relationships. And trust is the ultimate success factor for a highly functioning team. But I'm trying to do research. I'm having trouble finding like layman's explanations of the stuff with consensus. I was hoping today that I could, I don't want to say interrogate, but I kind of have a feeling that I need to ask you some tough questions. I want to ask you some tough questions about your experience with emotions, both from how they happen in your head and within your body, as a leader and CEO. Then also, how you react and observe and handle emotions of team members in the day-to-day stuff. We've talked offline I know you've, we've talked offline and made sure that was okay, but is there anything that's off limits in terms of asking you questions?</p><p><br></p><p><strong>Tyler:</strong> No, I mean there might be ... I'm happy to share my own experiences and I might be a little more secretive if I feel like I'm exposing something about someone else who hasn't necessarily given permission. But for myself, now I think I'm an open book. We'll see.</p><p><strong>Rick:</strong> Yeah. Cool. Listeners, I think that the other thing that we want to do here is I want to model talking about this openly, so I'll also jump in with my own insights on emotions. I'm a pretty, in terms of like emotional spectrum, I wear my emotions on my sleeve much more than Tyler does. Not to say that we're both not emotional people, it's just we may have very different experiences with emotions because of our personalities. I'll jump in when I can add a personal take. Would you add any anything?</p><p><strong>Tyler:</strong> I'm curious here, so I don't hear people maybe using the word emotions a lot, but I hear people talking about m...</p>]]>
      </content:encoded>
      <pubDate>Fri, 06 Dec 2019 06:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/10f5abd7/c91657cc.mp3" length="59701904" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3587</itunes:duration>
      <itunes:summary>This week, we talk about a topic that Rick is researching for his book: how can emotions help and hurt business leaders?</itunes:summary>
      <itunes:subtitle>This week, we talk about a topic that Rick is researching for his book: how can emotions help and hurt business leaders?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to balance building new features vs. maintaining existing ones</title>
      <itunes:episode>20</itunes:episode>
      <podcast:episode>20</podcast:episode>
      <itunes:title>How to balance building new features vs. maintaining existing ones</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">9a13d1e6-6bc9-46ec-b5c2-c19f97686379</guid>
      <link>https://share.transistor.fm/s/20c8816e</link>
      <description>
        <![CDATA[<p>In this episode, Tyler seeks Rick’s advice on how to plan the <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a> product roadmap for the upcoming year. Here are some of the takeaways:</p><ul><li><strong>Product roadmap planning is easier when you are able to align to clear company goals and constraints. In this context:</strong><ul><li>Goals = what you really want to accomplish during a time frame. E.g.:<ul><li>“Increase signups from word of mouth”</li></ul></li><li>Constraints = the things you aren’t willing to ignore / don’t want to drop while you’re pursuing your goals. E.g.:<ul><li>“Spend 10% of development hours paying down technical debt”</li></ul></li></ul></li><li><strong>Take time to make sure employees are bought in to the company goals and constraints prior to planning the product roadmap. </strong><ul><li>One way to do this is to include employees in the prioritization and trade-off process.<ul><li>Company leaders often go through a number of change cycles and trade-off decisions when setting company goals. </li><li>If you can allow employees to have a voice in these trade off decisions, they are much more likely to buy in to your prioritization decisions</li></ul></li></ul></li><li><strong>When you get to product roadmap planning, allocate resources based on your company goals and constraints.</strong> <ul><li>Once you’ve addressed your constraints, ideally you can put all of your remaining resources toward the company goal(s). </li><li>Common (non-outcome-based) allocation buckets include:<ul><li>New feature development</li><li>Improvement to existing features</li><li>Bug fixes</li><li>Paying down technical debt</li></ul></li><li>(Note: if you can logically bucket roadmap items into specific business outcomes tied to your company goals and constraints, do it)</li></ul></li><li><strong>It's nice to think, "What's our top priority? We're only going to work on that.</strong>" But, even at a one-person company, this is likely unrealistic. <ul><li>You lose momentum if you ignore parts of the business and this could get you in trouble.</li><li>Setting constraints on goals is one way to address this problem.<p></p></li></ul></li></ul><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Tyler:</strong> What we're going to talk about is basically the... Like any company, there's a lot of different things I want to work on next. We're finally at the point where we have multiple developers so we can do multiple things at once, which is not really something I've been faced with much in the past, and I'm trying to figure out how to prioritize different categories of things. One category is building totally new features. That's the sexy, fun-to-announce type of thing, like, "Here's something the software can do that it couldn't do before," versus improving existing features in a way that customers care about versus improving features in a way that customers won't even notice, but the idea of paying off technical debt or something like that, so, a bit of context here, we're finishing up this redesign, and, in a couple months, we're going to have all four developers plus myself moving on to other things, and basically, while we've been doing this redesign, which took almost all year, we've cut a lot of corners. The goal is to get it done as quickly as possible. There's a lot of stuff we want to go back and fix. This is normally referred to as technical debt. We have a lot of ideas for just minor tweaks to our current products that our customers would love, little one-week, two-week things, but we could do it for a year and not run out of ideas there, and they're just slam dunks, makes the product better, and then there's the go-out-and-really-do-something-new that our product doesn't currently do and maybe have a bigger splash, but it's a little more risky, so, yeah, I'm interested in basically just, A, figuring out what should I be doing, but, B, coming up with a framework for how I should think about this in the future.</p><p><strong>Rick:</strong> Yeah. What timeframe are you thinking about? Is it over the full course of 2020 starting in January? Is it next month for a couple of months? What are you thinking?</p><p><strong>Tyler: </strong>Probably, I think, the next six months. January through June, July would probably be a good... planning the most immediate next things, and then I'd like that the framework I was talking about can inform once... In April or May, when we start planning the next six months, I'd like to be able to apply that framework again.</p><p><strong>Rick:</strong> Makes sense. How have you gone about this in the past?</p><p><strong>Tyler:</strong> I just haven't. Partially, I've been very undisciplined about it. It's gone fine. It hasn't been a problem exactly, but, normally, there's just an obvious next thing. Having said that, it's not clear that the obvious next thing is actually the right next thing, but, in the moment, it's like what piece of software, what piece of our product is clearly the worst thing, that's normally what's going to get the most attention.</p><p><br></p><p><strong>Rick:</strong> It sounds like you want to add some discipline to your planning process and then you also, it sounds like, have some capacity to do more than one thing and in terms of you have more developers that are fully up to speed and capable that you can put on different things and get more done.</p><p><strong>Tyler:</strong> Yeah, absolutely, and so one of the reasons I say I've never had a system for this, we haven't launched a totally new, little features, but like a new major thing in maybe since 2014 or something like that. The last several big projects we've done, we're just redoing things we already had, so we redid the calendar, we redid custom fields, we did a redesign, so, yeah, it's weird having the resources and say, "Should we actually start adding to the functionality?"</p><p><strong><br>What are the company goals?<br></strong><br></p><p><strong>Rick: </strong>This was a big challenge for me. I went through a similar transition from Zane Benefits to <a href="https://www.peoplekeep.com/">PeopleKeep</a>. At Zane Benefits, it was very much a... I was the dictator of what got done on a monthly to quarterly basis, and there wasn't this engaged planning process that we thought about things over a long period of time. When I got money to fund PeopleKeep and hired a new CTO for that, he brought a whole nother mentality around roadmap planning and thinking through, and the... one thing that was really hard for him to do a good roadmap on... the situation that made it very hard for him to do a roadmap on was a situation in which I hadn't clarified the company goals for the year, so, I guess, what the... where I would start with this is what are the... If we look at the timeframe for a year from a company perspective, at the end of 2020, when you're looking back, what are the things you want to have accomplished and how will you have measured that? That should drive the first six months of the product roadmap.</p><p><strong>Tyler:</strong> Yeah, so, if I only get to answer one goal, I want 2020 to be the year of the referral. I want it to be word of mouth. We talked about this in a podcast, I don't know, a month ago about how I was thinking, and I had some questions around referrals and word of mouth. From a business standpoint, I want to make that better, but I also think products can have a big role in there. Now, having said that, I've been making a fair number of implicit or explicit promises to the dev team about it's okay to cut this corner, we'll come back and clean that up later, so I have other concerns beyond just this one big goal, but that's the biggest thing.</p><p><strong>Rick:</strong> Yeah, and are...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Tyler seeks Rick’s advice on how to plan the <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a> product roadmap for the upcoming year. Here are some of the takeaways:</p><ul><li><strong>Product roadmap planning is easier when you are able to align to clear company goals and constraints. In this context:</strong><ul><li>Goals = what you really want to accomplish during a time frame. E.g.:<ul><li>“Increase signups from word of mouth”</li></ul></li><li>Constraints = the things you aren’t willing to ignore / don’t want to drop while you’re pursuing your goals. E.g.:<ul><li>“Spend 10% of development hours paying down technical debt”</li></ul></li></ul></li><li><strong>Take time to make sure employees are bought in to the company goals and constraints prior to planning the product roadmap. </strong><ul><li>One way to do this is to include employees in the prioritization and trade-off process.<ul><li>Company leaders often go through a number of change cycles and trade-off decisions when setting company goals. </li><li>If you can allow employees to have a voice in these trade off decisions, they are much more likely to buy in to your prioritization decisions</li></ul></li></ul></li><li><strong>When you get to product roadmap planning, allocate resources based on your company goals and constraints.</strong> <ul><li>Once you’ve addressed your constraints, ideally you can put all of your remaining resources toward the company goal(s). </li><li>Common (non-outcome-based) allocation buckets include:<ul><li>New feature development</li><li>Improvement to existing features</li><li>Bug fixes</li><li>Paying down technical debt</li></ul></li><li>(Note: if you can logically bucket roadmap items into specific business outcomes tied to your company goals and constraints, do it)</li></ul></li><li><strong>It's nice to think, "What's our top priority? We're only going to work on that.</strong>" But, even at a one-person company, this is likely unrealistic. <ul><li>You lose momentum if you ignore parts of the business and this could get you in trouble.</li><li>Setting constraints on goals is one way to address this problem.<p></p></li></ul></li></ul><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Tyler:</strong> What we're going to talk about is basically the... Like any company, there's a lot of different things I want to work on next. We're finally at the point where we have multiple developers so we can do multiple things at once, which is not really something I've been faced with much in the past, and I'm trying to figure out how to prioritize different categories of things. One category is building totally new features. That's the sexy, fun-to-announce type of thing, like, "Here's something the software can do that it couldn't do before," versus improving existing features in a way that customers care about versus improving features in a way that customers won't even notice, but the idea of paying off technical debt or something like that, so, a bit of context here, we're finishing up this redesign, and, in a couple months, we're going to have all four developers plus myself moving on to other things, and basically, while we've been doing this redesign, which took almost all year, we've cut a lot of corners. The goal is to get it done as quickly as possible. There's a lot of stuff we want to go back and fix. This is normally referred to as technical debt. We have a lot of ideas for just minor tweaks to our current products that our customers would love, little one-week, two-week things, but we could do it for a year and not run out of ideas there, and they're just slam dunks, makes the product better, and then there's the go-out-and-really-do-something-new that our product doesn't currently do and maybe have a bigger splash, but it's a little more risky, so, yeah, I'm interested in basically just, A, figuring out what should I be doing, but, B, coming up with a framework for how I should think about this in the future.</p><p><strong>Rick:</strong> Yeah. What timeframe are you thinking about? Is it over the full course of 2020 starting in January? Is it next month for a couple of months? What are you thinking?</p><p><strong>Tyler: </strong>Probably, I think, the next six months. January through June, July would probably be a good... planning the most immediate next things, and then I'd like that the framework I was talking about can inform once... In April or May, when we start planning the next six months, I'd like to be able to apply that framework again.</p><p><strong>Rick:</strong> Makes sense. How have you gone about this in the past?</p><p><strong>Tyler:</strong> I just haven't. Partially, I've been very undisciplined about it. It's gone fine. It hasn't been a problem exactly, but, normally, there's just an obvious next thing. Having said that, it's not clear that the obvious next thing is actually the right next thing, but, in the moment, it's like what piece of software, what piece of our product is clearly the worst thing, that's normally what's going to get the most attention.</p><p><br></p><p><strong>Rick:</strong> It sounds like you want to add some discipline to your planning process and then you also, it sounds like, have some capacity to do more than one thing and in terms of you have more developers that are fully up to speed and capable that you can put on different things and get more done.</p><p><strong>Tyler:</strong> Yeah, absolutely, and so one of the reasons I say I've never had a system for this, we haven't launched a totally new, little features, but like a new major thing in maybe since 2014 or something like that. The last several big projects we've done, we're just redoing things we already had, so we redid the calendar, we redid custom fields, we did a redesign, so, yeah, it's weird having the resources and say, "Should we actually start adding to the functionality?"</p><p><strong><br>What are the company goals?<br></strong><br></p><p><strong>Rick: </strong>This was a big challenge for me. I went through a similar transition from Zane Benefits to <a href="https://www.peoplekeep.com/">PeopleKeep</a>. At Zane Benefits, it was very much a... I was the dictator of what got done on a monthly to quarterly basis, and there wasn't this engaged planning process that we thought about things over a long period of time. When I got money to fund PeopleKeep and hired a new CTO for that, he brought a whole nother mentality around roadmap planning and thinking through, and the... one thing that was really hard for him to do a good roadmap on... the situation that made it very hard for him to do a roadmap on was a situation in which I hadn't clarified the company goals for the year, so, I guess, what the... where I would start with this is what are the... If we look at the timeframe for a year from a company perspective, at the end of 2020, when you're looking back, what are the things you want to have accomplished and how will you have measured that? That should drive the first six months of the product roadmap.</p><p><strong>Tyler:</strong> Yeah, so, if I only get to answer one goal, I want 2020 to be the year of the referral. I want it to be word of mouth. We talked about this in a podcast, I don't know, a month ago about how I was thinking, and I had some questions around referrals and word of mouth. From a business standpoint, I want to make that better, but I also think products can have a big role in there. Now, having said that, I've been making a fair number of implicit or explicit promises to the dev team about it's okay to cut this corner, we'll come back and clean that up later, so I have other concerns beyond just this one big goal, but that's the biggest thing.</p><p><strong>Rick:</strong> Yeah, and are...</p>]]>
      </content:encoded>
      <pubDate>Wed, 27 Nov 2019 07:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/20c8816e/7f659f5f.mp3" length="53694411" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3126</itunes:duration>
      <itunes:summary>This week, we talk about how to balance competing goals when it comes to product development: how much time should you spend building new features vs maintaining old ones? Tyler's company is wrapping up a major project and he's trying to figure out how to prioritize what to do next.</itunes:summary>
      <itunes:subtitle>This week, we talk about how to balance competing goals when it comes to product development: how much time should you spend building new features vs maintaining old ones? Tyler's company is wrapping up a major project and he's trying to figure out how to</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Should you consult on the side while launching a startup?</title>
      <itunes:episode>19</itunes:episode>
      <podcast:episode>19</podcast:episode>
      <itunes:title>Should you consult on the side while launching a startup?</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ed27f774-ea1b-4b91-abf8-9b6637cf3829</guid>
      <link>https://share.transistor.fm/s/1dde74a0</link>
      <description>
        <![CDATA[<p>In this episode, Rick seeks Tyler’s advice on how to approach consulting on the side to fund <a href="http://legupventures.com/">LegUp Ventures</a>. Here are some of the takeaways:</p><ul><li><strong>If you need the money, you’ve got to consult or get a job</strong><ul><li><em>Ain’t no way around it</em></li></ul></li><li><strong>Consulting can be preferable as you have way more flexibility</strong><ul><li>It's way easier to bootstrap with consulting as your source of money versus a full time job</li><li>You hourly rate as a consultant might be higher also</li></ul></li><li><strong>Be proactive about consulting.(Don’t want until you need the money)</strong><ul><li>View consulting as protection for your business —&gt; it will help you sustain your startup while you’re searching for a repeatable business model</li><li>Consulting helps avoid putting negative pressure on your startup to generate cash when you should be focused on learning</li></ul></li><li><strong>Figure out how much you need to make consulting for the year so you can focus on a specific number</strong><ul><li>This number is totally dependent on your personal goals and constraints</li></ul></li><li><strong>Then, decide how to approach projects </strong><ul><li>There are two core approaches: <ul><li>1) big project chunks, and </li><li>2) smaller, consistent retainer work</li></ul></li></ul></li><li><strong>Consider getting a job or consulting project in an area that will help you learn or hone stuff related to your startup(e.g. skills, know-how, etc.) </strong><ul><li>I.e. Get paid to learn</li><li>Note that there's probably an inverse correlation between how much you get paid and how much you're learning<ul><li>If you're learning, it means you're not already an expert at it and they're probably not going to be willing to pay you as much</li></ul></li></ul></li></ul><p><br></p><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Rick:</strong> Yeah. So, I think this is a question that a lot of people probably face when they're trying to bootstrap. Obviously, if you're ... maybe not obviously, but if you're trying to build a venture backed business, this may not be an issue because you're going to go raise money so that you have runway to deal with things, but when you set a constraint on, hey, I'm not going to raise money or I'm not going to raise ... I'm not going to raise money ever or I'm not going to raise money until a certain milestone is hit, like I've set, which is, I don't want to raise money until after product-market fit is reached, which I consider to be a pretty high revenue base, hundreds of thousands of recurring dollars per month.</p><p><strong>Tyler:</strong> Per month?</p><p><strong>Rick:</strong> Per month, yeah. It's a very high bar for me.</p><p><strong>Tyler</strong>: So, you're saying like where <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a> is right now, you want to bootstrap to that point?</p><p><strong>Rick</strong>: Yeah. I think you have product market fit.</p><p><strong>Tyler:</strong> We've had product market fit for like nine years.</p><p><strong>Rick:</strong> Not by my definition.</p><p><strong>Tyler:</strong> Okay, I got you.</p><p><strong>Rick: </strong>Yeah. But, maybe like you've had it for a couple of years, maybe not nine years, somewhere in between there. There was some level where you hit it probably and you've been slowly increasing on top of that. You and I are different, I would probably say, somewhere in the last four or five years I probably would've said, hey, let's go raise some money.</p><p><strong>Tyler:</strong> What's the reason to wait that long? Well, sorry, why don't you intro it and then I'll get to my questions.</p><p><br></p><p><strong>Rick:</strong> Yeah. This is a whole mentality. So, this is my weirdness. I'll hold off on why that's the case. So, one constraint is, I'm not going to let myself raise money until I reach a pretty high proof of real business threshold. So, that means that in order to fund things, I've got to have cash available. I also have a constraint on my own personal life where I'm not going cash flow negative on this. So, that's a big thing where it's like, I have a pretty nice life style, I'm not going to let that life ... I'm not going to downgrade the lifestyle and I'm not going to allow that lifestyle to be a negative cash flow, personally. Okay? So, this means a couple of things. One, it means LegUp has to pay me money, right? From the get go. Two, it means that leg up has to make money in order for me to pay that. So, it's not like I can go raise money and then start paying myself money. LegUp's actually got to produce revenue. The quickest way for me to produce money is to sell my time. I have some expertise that allows me to sell time at a pretty high ... the metric I talk about in this case is return on time. I have a pretty good return on time invested, but it comes at a cost to me working on some of the early stage ventures I have going on in terms of focus and energy that I have to go after them. So, when I do take on a consulting project, it's generally a larger project and it takes a good bit of my focus and energy which means a lot of my other initiatives slow down. But, they're very lucrative and they give me a lot of runway when they happen. So, context, when I started Leg Up this year in June, May or June, I actually started it for a couple of consulting clients I had and then added a third and basically those consulting clients have been enough to pay my salary that I've been paying myself from Leg Up for this year and I haven't consulted in a few months and it's allowed me to have pure focus on the ventures that I've created. Now, I've gotten spoiled. Okay? So, I've really enjoyed having basically being able to set my week every week on what I want to focus on, but as I plan ahead, I'm realizing every time I put pressure on a venture to make money faster than it will just naturally happening by just continuous improvement processes, it gets less fun and it also leads to, I think, bad long term decision making. So, while I want to focus on these things and maybe move faster, if I do my constraints, it's going to put pressure on these ventures producing cash faster than maybe that is good for them and could lead to worse longer term outcomes and then on the other side, if I go consult, it takes all the pressure off of cash, but slows down progress and if I had to make a decision today just to give you an idea of where I am, I know I should go probably plan on consulting and then it becomes a question of like, okay, I'm going to go consult, how much do I need to consult? Do I front load it for the year and just work my, pardon me, ass off for like three or four months?</p><p><strong>Tyler:</strong> How offensive.</p><p><strong>Rick:</strong> Well, I just wrote a pretty sensitive<a href="https://www.ricklindquist.com/blog/how-non-mormons-and-mormons-can-build-stronger-relationships"> article on the Church of Jesus Christ of Latter-day Saints</a>, ie Mormons.</p><p><strong>Tyler: </strong>You're trying not to use naughty words? Okay.</p><p><strong><br>Should I consult?<br></strong><br></p><p><strong>Rick:</strong> Yeah. Bad words. So, anyway, summarizing, should I consult? If not, tell me why. I would love to hear your perspective. If so, how much. I'd love to brainstorm I guess. If we decide yes, I should consult, I'd like to just go into how best to structure that, is it small projects that kind of continue throughout the year? Is it a couple big projects front loaded at the beginning? Like I did this year. I'm interested in your thoughts.</p><p><br></p><p><strong>Tyler: </strong>Yeah. Okay. So, I'll start...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Rick seeks Tyler’s advice on how to approach consulting on the side to fund <a href="http://legupventures.com/">LegUp Ventures</a>. Here are some of the takeaways:</p><ul><li><strong>If you need the money, you’ve got to consult or get a job</strong><ul><li><em>Ain’t no way around it</em></li></ul></li><li><strong>Consulting can be preferable as you have way more flexibility</strong><ul><li>It's way easier to bootstrap with consulting as your source of money versus a full time job</li><li>You hourly rate as a consultant might be higher also</li></ul></li><li><strong>Be proactive about consulting.(Don’t want until you need the money)</strong><ul><li>View consulting as protection for your business —&gt; it will help you sustain your startup while you’re searching for a repeatable business model</li><li>Consulting helps avoid putting negative pressure on your startup to generate cash when you should be focused on learning</li></ul></li><li><strong>Figure out how much you need to make consulting for the year so you can focus on a specific number</strong><ul><li>This number is totally dependent on your personal goals and constraints</li></ul></li><li><strong>Then, decide how to approach projects </strong><ul><li>There are two core approaches: <ul><li>1) big project chunks, and </li><li>2) smaller, consistent retainer work</li></ul></li></ul></li><li><strong>Consider getting a job or consulting project in an area that will help you learn or hone stuff related to your startup(e.g. skills, know-how, etc.) </strong><ul><li>I.e. Get paid to learn</li><li>Note that there's probably an inverse correlation between how much you get paid and how much you're learning<ul><li>If you're learning, it means you're not already an expert at it and they're probably not going to be willing to pay you as much</li></ul></li></ul></li></ul><p><br></p><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Rick:</strong> Yeah. So, I think this is a question that a lot of people probably face when they're trying to bootstrap. Obviously, if you're ... maybe not obviously, but if you're trying to build a venture backed business, this may not be an issue because you're going to go raise money so that you have runway to deal with things, but when you set a constraint on, hey, I'm not going to raise money or I'm not going to raise ... I'm not going to raise money ever or I'm not going to raise money until a certain milestone is hit, like I've set, which is, I don't want to raise money until after product-market fit is reached, which I consider to be a pretty high revenue base, hundreds of thousands of recurring dollars per month.</p><p><strong>Tyler:</strong> Per month?</p><p><strong>Rick:</strong> Per month, yeah. It's a very high bar for me.</p><p><strong>Tyler</strong>: So, you're saying like where <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a> is right now, you want to bootstrap to that point?</p><p><strong>Rick</strong>: Yeah. I think you have product market fit.</p><p><strong>Tyler:</strong> We've had product market fit for like nine years.</p><p><strong>Rick:</strong> Not by my definition.</p><p><strong>Tyler:</strong> Okay, I got you.</p><p><strong>Rick: </strong>Yeah. But, maybe like you've had it for a couple of years, maybe not nine years, somewhere in between there. There was some level where you hit it probably and you've been slowly increasing on top of that. You and I are different, I would probably say, somewhere in the last four or five years I probably would've said, hey, let's go raise some money.</p><p><strong>Tyler:</strong> What's the reason to wait that long? Well, sorry, why don't you intro it and then I'll get to my questions.</p><p><br></p><p><strong>Rick:</strong> Yeah. This is a whole mentality. So, this is my weirdness. I'll hold off on why that's the case. So, one constraint is, I'm not going to let myself raise money until I reach a pretty high proof of real business threshold. So, that means that in order to fund things, I've got to have cash available. I also have a constraint on my own personal life where I'm not going cash flow negative on this. So, that's a big thing where it's like, I have a pretty nice life style, I'm not going to let that life ... I'm not going to downgrade the lifestyle and I'm not going to allow that lifestyle to be a negative cash flow, personally. Okay? So, this means a couple of things. One, it means LegUp has to pay me money, right? From the get go. Two, it means that leg up has to make money in order for me to pay that. So, it's not like I can go raise money and then start paying myself money. LegUp's actually got to produce revenue. The quickest way for me to produce money is to sell my time. I have some expertise that allows me to sell time at a pretty high ... the metric I talk about in this case is return on time. I have a pretty good return on time invested, but it comes at a cost to me working on some of the early stage ventures I have going on in terms of focus and energy that I have to go after them. So, when I do take on a consulting project, it's generally a larger project and it takes a good bit of my focus and energy which means a lot of my other initiatives slow down. But, they're very lucrative and they give me a lot of runway when they happen. So, context, when I started Leg Up this year in June, May or June, I actually started it for a couple of consulting clients I had and then added a third and basically those consulting clients have been enough to pay my salary that I've been paying myself from Leg Up for this year and I haven't consulted in a few months and it's allowed me to have pure focus on the ventures that I've created. Now, I've gotten spoiled. Okay? So, I've really enjoyed having basically being able to set my week every week on what I want to focus on, but as I plan ahead, I'm realizing every time I put pressure on a venture to make money faster than it will just naturally happening by just continuous improvement processes, it gets less fun and it also leads to, I think, bad long term decision making. So, while I want to focus on these things and maybe move faster, if I do my constraints, it's going to put pressure on these ventures producing cash faster than maybe that is good for them and could lead to worse longer term outcomes and then on the other side, if I go consult, it takes all the pressure off of cash, but slows down progress and if I had to make a decision today just to give you an idea of where I am, I know I should go probably plan on consulting and then it becomes a question of like, okay, I'm going to go consult, how much do I need to consult? Do I front load it for the year and just work my, pardon me, ass off for like three or four months?</p><p><strong>Tyler:</strong> How offensive.</p><p><strong>Rick:</strong> Well, I just wrote a pretty sensitive<a href="https://www.ricklindquist.com/blog/how-non-mormons-and-mormons-can-build-stronger-relationships"> article on the Church of Jesus Christ of Latter-day Saints</a>, ie Mormons.</p><p><strong>Tyler: </strong>You're trying not to use naughty words? Okay.</p><p><strong><br>Should I consult?<br></strong><br></p><p><strong>Rick:</strong> Yeah. Bad words. So, anyway, summarizing, should I consult? If not, tell me why. I would love to hear your perspective. If so, how much. I'd love to brainstorm I guess. If we decide yes, I should consult, I'd like to just go into how best to structure that, is it small projects that kind of continue throughout the year? Is it a couple big projects front loaded at the beginning? Like I did this year. I'm interested in your thoughts.</p><p><br></p><p><strong>Tyler: </strong>Yeah. Okay. So, I'll start...</p>]]>
      </content:encoded>
      <pubDate>Thu, 21 Nov 2019 17:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/1dde74a0/88e3e932.mp3" length="59353097" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3355</itunes:duration>
      <itunes:summary>This week, we talk about whether or not it makes sense to use consulting revenue to bootstrap a business. If so, what's the right way to split time between consulting and your startup?</itunes:summary>
      <itunes:subtitle>This week, we talk about whether or not it makes sense to use consulting revenue to bootstrap a business. If so, what's the right way to split time between consulting and your startup?</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to price and position your second product</title>
      <itunes:episode>18</itunes:episode>
      <podcast:episode>18</podcast:episode>
      <itunes:title>How to price and position your second product</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">bd02a6a8-cc0f-4c54-a6e9-5bc9b6c1f2b4</guid>
      <link>https://share.transistor.fm/s/a169510a</link>
      <description>
        <![CDATA[<p><b>In this episode, we discuss how to think about positioning, packaging, and pricing a second product when you have an existing customer base. Here are some of the takeaways:</b></p><ul><li><strong>Be clear about the primary reason you want to add a second product.</strong><ul><li>This will impact how you package and price the product. </li><li>Is this the right thing for the business and for your customers?</li><li>Or is this about you and what makes you happy? </li></ul></li><li><strong>Is your goal to expand customer acquisition?</strong><ul><li>It might make sense to package the product on a stand-alone basis.<ul><li>If you take a stand-alone product approach, recognize that it may be more work.</li><li>Positioning will be harder.</li><li>You may have to build additional infrastructure.</li></ul></li><li>It also might make sense to give it away for free.</li></ul></li><li><strong>Is your goal is to retain more customers?</strong><ul><li>It might make sense to include the second product with current pricing.</li></ul></li><li><strong>Is you goal is to increase revenue per customer?</strong><ul><li>It might make sense to offer the second product as an add-on.<ul><li>If you decide to take an add-on approach, recognize that it may be harder to maximize the price. <ul><li><strong>An add-on probably shouldn’t be 100%+ of the base price.</strong></li><li>You’re probably looking more like a 50% up-sell opportunity.</li></ul></li></ul></li><li>Or it might make sense to package the second product as part of a second, higher tier of pricing.</li></ul></li><li><strong>Are you just bored and wanting to build something to satisfy a personal craving?</strong><ul><li>It might make more sense to do the product as a side thing.</li></ul></li></ul><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Tyler:</strong> To the deep dive topic here. So this is an issue I'm thinking about right now and it's basically pricing a second product. I have a first product... Let me get a little context on what we've got right now. So like I said, we're 10 years old about. Our product has always been $10 per user per month. I know a lot of people would say that's too low or whatever, but we're pretty entrenched in the lower tier of the market at this point. And we've grown to 22 thousand paying users. So we've got a pretty big customer base, at least relative to what we used to. The plan from day one was build a suite of products. Our name is actually Less Annoying Software, not <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a>. That's just the first thing. But we expected probably a year or two in launch that second thing and a year turns into 10.</p><p><strong>Ben:</strong> Turns out every 10 years you get a new something.</p><p><strong>Tyler:</strong> Yeah, exactly.</p><p><strong>Ben: </strong>Something less annoying.</p><p><strong>Tyler:</strong> By the time I retire we'll have four products.</p><p><strong>Ben:</strong> Okay.</p><p><strong>Tyler:</strong> But yeah, I think we're finally at a point where our dev team's big enough. We can peel a few people, maybe two people off and launch something new. When I say a new product, I think the idea is it would be within the same app. So one login, one billing system. But it's like, do you want the CRM or do you want both of these things? Or maybe the other thing standalone, depending. Most likely, we surveyed our customers, did a little customer research. I think the thing that's low hanging fruit to get our current customers to buy something else is an appointment scheduler. So a <a href="https://calendly.com/">Calendly</a> type of thing. And then we could grow... We have a lot of ideas beyond just appointment scheduling, but kind of starting there and building it out. So what I'm interested in talking about is A, general structures for, it's one thing to price one product, but when you have this idea that I want to sell two things to the same group of people, the right structure for that. I'm less interested in the number but more the, is it a bundle thing, is it a la carte? What if we had a third product? Kind of general structure stuff to this. And then a few things that have kind of been on my mind to consider here is should we be prioritizing getting our current customer base to upgrade versus treating this as a channel for getting new customers? Should people be able to buy this new product on its own? Obviously all else being equal, it'd be nice, but is it worth the effort versus just upselling our current people? And then should we be thinking about a third product or should we basically just say, it took us 10 years to get to our second one, it would be stupid to base any decisions we make right now around the idea of a third one coming out. So, that's a lot. But those are some different things to chew on here.</p><p><br></p><p><strong>Ben:</strong> Is this product done, like you're already committed to this decision? This is a thing that's happening?</p><p><strong>Tyler:</strong> No it's not. We've done a fair amount of validating it with customers. We have not built anything yet. I should say, one thing, that not all CRMs have this, we have a fully functional calendar with all of the functionality you get from Google or Outlook or something. So we're in a good position to build calendar related tools, but we haven't actually started this second product, no.</p><p><strong>Ben:</strong> What's the motivation behind adding another product?</p><p><strong><br>Why are you building a second product?<br></strong><br></p><p><strong>Tyler:</strong> A couple. One is the unit economics of the business could get better. You could say just raise the price on the existing product. That would certainly work from a... If a private equity firm bought us, that's what they would do and it would work. We have certain other interests and I take a lot of pride in serving the low tier of the market that a lot of other SaaS companies don't care about. So I want to be able to improve our margins without raising prices and that's one way to do it I think. Another thing is I do think that our customers... I don't know, I feel like software goes in cycles between everything being bundled together and then everything unbundling and being a bunch of different tools that integrate together. And we're in a very unbundled phase right now and I think a lot of value could be provided by going back to bundling here for our customers who are not tech savvy and really just want one clean experience. But that's a fair question. Do you think that maybe we should back up even more?</p><p><br></p><p><strong>Ben:</strong> Oh, I mean, I don't know. Maybe. You did say you don't want to raise the prices, but if you roll out a new feature and say this new feature costs extra money, you haven't exactly raised the price, but you kind of have. You're... Yeah.</p><p><strong>Tyler:</strong> Yeah. The standard I was hoping to hold myself to here is basically, if there are standalone products that sell just this thing, I can call it a different product, but if it's like this is clearly dependent on the CRM, that would be included in what we already offer. So for example, if we add our... Yeah, go ahead. Sorry.</p><p><strong>Rick:</strong> Oh sorry. I interrupted you.</p><p><strong>Tyler: </strong>I was just going to say if we add a little more reporting to how our pipeline reports work, I wouldn't charge more for that. But if we say, "Well, now there's an email client built in," I think it's pretty justifiable to say that's a different thing.</p><p><strong>Rick:</strong> Do you have a way you're leaning right now in terms of, without us talking about today. If you had to make a decision today, what would you roll ou...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><b>In this episode, we discuss how to think about positioning, packaging, and pricing a second product when you have an existing customer base. Here are some of the takeaways:</b></p><ul><li><strong>Be clear about the primary reason you want to add a second product.</strong><ul><li>This will impact how you package and price the product. </li><li>Is this the right thing for the business and for your customers?</li><li>Or is this about you and what makes you happy? </li></ul></li><li><strong>Is your goal to expand customer acquisition?</strong><ul><li>It might make sense to package the product on a stand-alone basis.<ul><li>If you take a stand-alone product approach, recognize that it may be more work.</li><li>Positioning will be harder.</li><li>You may have to build additional infrastructure.</li></ul></li><li>It also might make sense to give it away for free.</li></ul></li><li><strong>Is your goal is to retain more customers?</strong><ul><li>It might make sense to include the second product with current pricing.</li></ul></li><li><strong>Is you goal is to increase revenue per customer?</strong><ul><li>It might make sense to offer the second product as an add-on.<ul><li>If you decide to take an add-on approach, recognize that it may be harder to maximize the price. <ul><li><strong>An add-on probably shouldn’t be 100%+ of the base price.</strong></li><li>You’re probably looking more like a 50% up-sell opportunity.</li></ul></li></ul></li><li>Or it might make sense to package the second product as part of a second, higher tier of pricing.</li></ul></li><li><strong>Are you just bored and wanting to build something to satisfy a personal craving?</strong><ul><li>It might make more sense to do the product as a side thing.</li></ul></li></ul><p>What else would you add to this list?</p><p><strong><br>Context<br></strong><br></p><p><strong>Tyler:</strong> To the deep dive topic here. So this is an issue I'm thinking about right now and it's basically pricing a second product. I have a first product... Let me get a little context on what we've got right now. So like I said, we're 10 years old about. Our product has always been $10 per user per month. I know a lot of people would say that's too low or whatever, but we're pretty entrenched in the lower tier of the market at this point. And we've grown to 22 thousand paying users. So we've got a pretty big customer base, at least relative to what we used to. The plan from day one was build a suite of products. Our name is actually Less Annoying Software, not <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a>. That's just the first thing. But we expected probably a year or two in launch that second thing and a year turns into 10.</p><p><strong>Ben:</strong> Turns out every 10 years you get a new something.</p><p><strong>Tyler:</strong> Yeah, exactly.</p><p><strong>Ben: </strong>Something less annoying.</p><p><strong>Tyler:</strong> By the time I retire we'll have four products.</p><p><strong>Ben:</strong> Okay.</p><p><strong>Tyler:</strong> But yeah, I think we're finally at a point where our dev team's big enough. We can peel a few people, maybe two people off and launch something new. When I say a new product, I think the idea is it would be within the same app. So one login, one billing system. But it's like, do you want the CRM or do you want both of these things? Or maybe the other thing standalone, depending. Most likely, we surveyed our customers, did a little customer research. I think the thing that's low hanging fruit to get our current customers to buy something else is an appointment scheduler. So a <a href="https://calendly.com/">Calendly</a> type of thing. And then we could grow... We have a lot of ideas beyond just appointment scheduling, but kind of starting there and building it out. So what I'm interested in talking about is A, general structures for, it's one thing to price one product, but when you have this idea that I want to sell two things to the same group of people, the right structure for that. I'm less interested in the number but more the, is it a bundle thing, is it a la carte? What if we had a third product? Kind of general structure stuff to this. And then a few things that have kind of been on my mind to consider here is should we be prioritizing getting our current customer base to upgrade versus treating this as a channel for getting new customers? Should people be able to buy this new product on its own? Obviously all else being equal, it'd be nice, but is it worth the effort versus just upselling our current people? And then should we be thinking about a third product or should we basically just say, it took us 10 years to get to our second one, it would be stupid to base any decisions we make right now around the idea of a third one coming out. So, that's a lot. But those are some different things to chew on here.</p><p><br></p><p><strong>Ben:</strong> Is this product done, like you're already committed to this decision? This is a thing that's happening?</p><p><strong>Tyler:</strong> No it's not. We've done a fair amount of validating it with customers. We have not built anything yet. I should say, one thing, that not all CRMs have this, we have a fully functional calendar with all of the functionality you get from Google or Outlook or something. So we're in a good position to build calendar related tools, but we haven't actually started this second product, no.</p><p><strong>Ben:</strong> What's the motivation behind adding another product?</p><p><strong><br>Why are you building a second product?<br></strong><br></p><p><strong>Tyler:</strong> A couple. One is the unit economics of the business could get better. You could say just raise the price on the existing product. That would certainly work from a... If a private equity firm bought us, that's what they would do and it would work. We have certain other interests and I take a lot of pride in serving the low tier of the market that a lot of other SaaS companies don't care about. So I want to be able to improve our margins without raising prices and that's one way to do it I think. Another thing is I do think that our customers... I don't know, I feel like software goes in cycles between everything being bundled together and then everything unbundling and being a bunch of different tools that integrate together. And we're in a very unbundled phase right now and I think a lot of value could be provided by going back to bundling here for our customers who are not tech savvy and really just want one clean experience. But that's a fair question. Do you think that maybe we should back up even more?</p><p><br></p><p><strong>Ben:</strong> Oh, I mean, I don't know. Maybe. You did say you don't want to raise the prices, but if you roll out a new feature and say this new feature costs extra money, you haven't exactly raised the price, but you kind of have. You're... Yeah.</p><p><strong>Tyler:</strong> Yeah. The standard I was hoping to hold myself to here is basically, if there are standalone products that sell just this thing, I can call it a different product, but if it's like this is clearly dependent on the CRM, that would be included in what we already offer. So for example, if we add our... Yeah, go ahead. Sorry.</p><p><strong>Rick:</strong> Oh sorry. I interrupted you.</p><p><strong>Tyler: </strong>I was just going to say if we add a little more reporting to how our pipeline reports work, I wouldn't charge more for that. But if we say, "Well, now there's an email client built in," I think it's pretty justifiable to say that's a different thing.</p><p><strong>Rick:</strong> Do you have a way you're leaning right now in terms of, without us talking about today. If you had to make a decision today, what would you roll ou...</p>]]>
      </content:encoded>
      <pubDate>Thu, 14 Nov 2019 17:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/a169510a/414194af.mp3" length="58780064" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3453</itunes:duration>
      <itunes:summary>This week, we’re joined by Ben Orenstein, co-founder of Tuple.app and co-host of The Art of Product Podcast. We discuss how to think about offering a second product to an existing customer base. From pricing, to positioning, to whether or not a second product is even a good idea in the first, place, there’s a lot to consider.</itunes:summary>
      <itunes:subtitle>This week, we’re joined by Ben Orenstein, co-founder of Tuple.app and co-host of The Art of Product Podcast. We discuss how to think about offering a second product to an existing customer base. From pricing, to positioning, to whether or not a second pro</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Getting beta testers to use your product</title>
      <itunes:episode>17</itunes:episode>
      <podcast:episode>17</podcast:episode>
      <itunes:title>Getting beta testers to use your product</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">2b44ca16-e284-4fba-8c83-0bd665161f82</guid>
      <link>https://share.transistor.fm/s/52f17acf</link>
      <description>
        <![CDATA[<p>In this episode, we discuss how to identify, invite and recruit beta users for your product. Rick uses one of his ventures as an example, and Tyler helps him work through structuring a beta program for his software-enabled service idea. While we worked through a specific situation, the general concept applies often. Here’s the framework that emerged:</p><ul><li><strong>Decide if you are ready for a beta program. </strong><ul><li>Here’s how you’ll know:<ul><li>The minute you feel you can offer users something of value, you’re ready. </li><li>If you aren’t there, you may need to do more customer interviews to validate your idea(s).</li></ul></li></ul></li><li><strong>Design your beta program. </strong><ul><li>Ask yourself the following questions:<ul><li>What are you trying to learn / test?</li><li>Is a closed or open beta more appropriate?</li><li>What the profile of your ideal beta user?</li><li>How can you position the program to these beta users?<ul><li>What is your differentiating theme?</li><li>What is your offer / value proposition?</li></ul></li><li>Should you / do you need to incentivize participation?</li></ul></li></ul></li><li><strong>Launch the program and recruit beta users.</strong><ul><li>Ask yourself the following questions:<ul><li>Where do the ideal beta users hang out?</li><li>Can I find enough ideal beta users via my network?</li><li>If not, how can I leverage other marketing channels?</li></ul></li></ul></li><li><strong>Execute the program.</strong><ul><li>Ask yourself the following questions:<ul><li>How can I make my beta users feel like they are part of the journey?</li><li>What incentives can I offer to reward users?</li><li>How can I build a one-to-one relationship with each beta user? </li><li>How can I improve the offering?</li></ul></li></ul></li></ul><p><strong>Takeaways:</strong></p><ul><li>Don’t add too much structure to start. <ul><li>Start out with as little structure as possible and then iterate your way to more structure when it adds value or scalability based on learnings.</li></ul></li><li>Launch a beta as soon as you can add value. <ul><li>As soon as you can offer anything to anybody, get it out there and start testing it with real users.</li><li>The productized service approach to MVPs allows a lot more room for error in the software because you can lean on the service component for immediate value.</li></ul></li><li>When looking for beta users, tap your network first.<ul><li>If you can't do it with networking, you're probably not networking enough or you’re not good at it. <ul><li>Alternatively, you can go out and use traditional marketing channels to find people who might be beta testers, but you have to go into it expecting a high investment, whether it's in time, or money, or whatever, because your pitch isn't refined yet, your product isn't refined yet, you don't even know who to target. </li><li>Traditional marketing works, it's just you have to bring in a ton of people at the top of the funnel to get one good early adopter.</li></ul></li></ul></li><li>How to get the most out of beta users<ul><li>Invite your beta users to be part of the journey. <ul><li>The people who do beta tests, a lot of times they do it because they see some big potential. </li><li>Start with the why, and really get people on board with the mission and the reason you're doing it. </li><li>The more you can let them in and not just tell them why you're doing it, but make them feel like they're contributing to it, the more engaged they'll be.</li></ul></li><li>Offer unexpected incentives like swag and gift cards.</li><li>Spend time one-on-one with your early users to build real trust-based relationships.<ul><li>Do it in person if you can.</li></ul></li><li>Avoid offering incentives that could become the primary motivator for a user joining your beta program.</li></ul></li></ul><p><strong>Context<br></strong><br></p><p><strong>Rick:</strong> So specifically with my health insurance app, I actually didn't expect to be where I am today, I'm ahead of schedule. I now have everything I need to actually launch a beta product. So I was anticipating having this be more of a hypothetical conversation, but I will actually have ... I can guarantee a product in the next couple of weeks that people can sign up for as beta users. So what I want to get out of this conversation is I want to brainstorm some ways to gain beta users for this product. I don't just want anyone on the internet to sign up. Because this is a health insurance thing, they need to be in Utah, because that's where I'm licensed. They need to be consumers of individual health insurance. So it's a very narrow focus. So anyway, it's not like I can just go post this on Google Ads or go invite all my best friends, because most of my best friends don't live in Utah. So it's difficult. So I want to brainstorm some ways to identify, invite, and recruit them. Recruit would mean them actually agreeing to the beta program. The second is once they've agreed to participate in the beta program, keeping them active and engaged, whether that's with incentives or with just guilt. That's what I want to talk about. I can add some context ... I guess any clarifying questions about what I want to get out of this?</p><p><br></p><p><strong>Tyler:</strong> Yeah, well, it sounds ... I mean, getting a beta user, a beta tester is probably not radically different from getting a customer, but the goals are a little different. The goal is to learn instead of to make money, and the type of person you're looking for is someone on the very, very cutting edge of the adoption curve. But like a lot of concepts, this is going to be a specific type of marketing we're talking about here, I guess.</p><p><strong>Rick: </strong>Exactly. I envision these people ... I want these people to be evangelists of the community. I want them to care about the problem I'm solving as much as I do. And they will get free access. I don't know exactly what the value of that is yet, but hopefully they'll help me figure it out. But I think that the right beta user for this particular product, which I'll go into, is someone who cares deeply about the problem that exists today that the app promises to solve eventually.</p><p><strong>Tyler: </strong>Cool. So let's dive into ... we can talk generally about how to get beta users, but I think it's helpful to know what product we're actually trying to get. You said earlier there's three things you're doing. One is a thing with Sable, your wife. One is a <a href="http://groupcurrent.com/">GroupCurrent</a> thing. But that's not what we're talking about here. You have a specific healthcare, health insurance type of product. Can you talk about what that is?</p><p><strong>Rick:</strong> Yeah. So on the last episode, I was a little bit hesitant to talk about it because it is in the same realm of health insurance as my previous company, <a href="https://www.peoplekeep.com/">PeopleKeep</a>. I do have a restriction on where I can play. I was kind of put on the spot on the podcast and I didn't feel comfortable talking about it without thinking about it more. So having thought about it, there is no issue. This is non-competitive. Not even close. I feel comfortable talking about it. So I'll kind of give you the general premise. Maybe I can work from the problem that I'm focused on and then work down to how I think the MVP will attempt to solve that. Does that work?</p><p><strong>Tyler:</strong> Yeah, yeah.</p><p><strong><br>The problem to solve<br></strong><br></p><p><strong>Rick:</strong> Okay, so there's a huge problem out there in that people who buy individual health insurance largely don't get any service in exchange for the commission that they get taken out of their premium. So every time you pay a health insurance premium, whether it's a group policy through y...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss how to identify, invite and recruit beta users for your product. Rick uses one of his ventures as an example, and Tyler helps him work through structuring a beta program for his software-enabled service idea. While we worked through a specific situation, the general concept applies often. Here’s the framework that emerged:</p><ul><li><strong>Decide if you are ready for a beta program. </strong><ul><li>Here’s how you’ll know:<ul><li>The minute you feel you can offer users something of value, you’re ready. </li><li>If you aren’t there, you may need to do more customer interviews to validate your idea(s).</li></ul></li></ul></li><li><strong>Design your beta program. </strong><ul><li>Ask yourself the following questions:<ul><li>What are you trying to learn / test?</li><li>Is a closed or open beta more appropriate?</li><li>What the profile of your ideal beta user?</li><li>How can you position the program to these beta users?<ul><li>What is your differentiating theme?</li><li>What is your offer / value proposition?</li></ul></li><li>Should you / do you need to incentivize participation?</li></ul></li></ul></li><li><strong>Launch the program and recruit beta users.</strong><ul><li>Ask yourself the following questions:<ul><li>Where do the ideal beta users hang out?</li><li>Can I find enough ideal beta users via my network?</li><li>If not, how can I leverage other marketing channels?</li></ul></li></ul></li><li><strong>Execute the program.</strong><ul><li>Ask yourself the following questions:<ul><li>How can I make my beta users feel like they are part of the journey?</li><li>What incentives can I offer to reward users?</li><li>How can I build a one-to-one relationship with each beta user? </li><li>How can I improve the offering?</li></ul></li></ul></li></ul><p><strong>Takeaways:</strong></p><ul><li>Don’t add too much structure to start. <ul><li>Start out with as little structure as possible and then iterate your way to more structure when it adds value or scalability based on learnings.</li></ul></li><li>Launch a beta as soon as you can add value. <ul><li>As soon as you can offer anything to anybody, get it out there and start testing it with real users.</li><li>The productized service approach to MVPs allows a lot more room for error in the software because you can lean on the service component for immediate value.</li></ul></li><li>When looking for beta users, tap your network first.<ul><li>If you can't do it with networking, you're probably not networking enough or you’re not good at it. <ul><li>Alternatively, you can go out and use traditional marketing channels to find people who might be beta testers, but you have to go into it expecting a high investment, whether it's in time, or money, or whatever, because your pitch isn't refined yet, your product isn't refined yet, you don't even know who to target. </li><li>Traditional marketing works, it's just you have to bring in a ton of people at the top of the funnel to get one good early adopter.</li></ul></li></ul></li><li>How to get the most out of beta users<ul><li>Invite your beta users to be part of the journey. <ul><li>The people who do beta tests, a lot of times they do it because they see some big potential. </li><li>Start with the why, and really get people on board with the mission and the reason you're doing it. </li><li>The more you can let them in and not just tell them why you're doing it, but make them feel like they're contributing to it, the more engaged they'll be.</li></ul></li><li>Offer unexpected incentives like swag and gift cards.</li><li>Spend time one-on-one with your early users to build real trust-based relationships.<ul><li>Do it in person if you can.</li></ul></li><li>Avoid offering incentives that could become the primary motivator for a user joining your beta program.</li></ul></li></ul><p><strong>Context<br></strong><br></p><p><strong>Rick:</strong> So specifically with my health insurance app, I actually didn't expect to be where I am today, I'm ahead of schedule. I now have everything I need to actually launch a beta product. So I was anticipating having this be more of a hypothetical conversation, but I will actually have ... I can guarantee a product in the next couple of weeks that people can sign up for as beta users. So what I want to get out of this conversation is I want to brainstorm some ways to gain beta users for this product. I don't just want anyone on the internet to sign up. Because this is a health insurance thing, they need to be in Utah, because that's where I'm licensed. They need to be consumers of individual health insurance. So it's a very narrow focus. So anyway, it's not like I can just go post this on Google Ads or go invite all my best friends, because most of my best friends don't live in Utah. So it's difficult. So I want to brainstorm some ways to identify, invite, and recruit them. Recruit would mean them actually agreeing to the beta program. The second is once they've agreed to participate in the beta program, keeping them active and engaged, whether that's with incentives or with just guilt. That's what I want to talk about. I can add some context ... I guess any clarifying questions about what I want to get out of this?</p><p><br></p><p><strong>Tyler:</strong> Yeah, well, it sounds ... I mean, getting a beta user, a beta tester is probably not radically different from getting a customer, but the goals are a little different. The goal is to learn instead of to make money, and the type of person you're looking for is someone on the very, very cutting edge of the adoption curve. But like a lot of concepts, this is going to be a specific type of marketing we're talking about here, I guess.</p><p><strong>Rick: </strong>Exactly. I envision these people ... I want these people to be evangelists of the community. I want them to care about the problem I'm solving as much as I do. And they will get free access. I don't know exactly what the value of that is yet, but hopefully they'll help me figure it out. But I think that the right beta user for this particular product, which I'll go into, is someone who cares deeply about the problem that exists today that the app promises to solve eventually.</p><p><strong>Tyler: </strong>Cool. So let's dive into ... we can talk generally about how to get beta users, but I think it's helpful to know what product we're actually trying to get. You said earlier there's three things you're doing. One is a thing with Sable, your wife. One is a <a href="http://groupcurrent.com/">GroupCurrent</a> thing. But that's not what we're talking about here. You have a specific healthcare, health insurance type of product. Can you talk about what that is?</p><p><strong>Rick:</strong> Yeah. So on the last episode, I was a little bit hesitant to talk about it because it is in the same realm of health insurance as my previous company, <a href="https://www.peoplekeep.com/">PeopleKeep</a>. I do have a restriction on where I can play. I was kind of put on the spot on the podcast and I didn't feel comfortable talking about it without thinking about it more. So having thought about it, there is no issue. This is non-competitive. Not even close. I feel comfortable talking about it. So I'll kind of give you the general premise. Maybe I can work from the problem that I'm focused on and then work down to how I think the MVP will attempt to solve that. Does that work?</p><p><strong>Tyler:</strong> Yeah, yeah.</p><p><strong><br>The problem to solve<br></strong><br></p><p><strong>Rick:</strong> Okay, so there's a huge problem out there in that people who buy individual health insurance largely don't get any service in exchange for the commission that they get taken out of their premium. So every time you pay a health insurance premium, whether it's a group policy through y...</p>]]>
      </content:encoded>
      <pubDate>Thu, 07 Nov 2019 17:00:00 -0600</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/52f17acf/65b2baa3.mp3" length="58181948" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3413</itunes:duration>
      <itunes:summary>Rick is almost done with the prototype of one of his new product ideas, and now it's time for him to get people to start using it. This week, we talk about getting users, motivating them to participate in the beta test, and learning based on their feedback.</itunes:summary>
      <itunes:subtitle>Rick is almost done with the prototype of one of his new product ideas, and now it's time for him to get people to start using it. This week, we talk about getting users, motivating them to participate in the beta test, and learning based on their feedbac</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to get job candidates to accept an offer</title>
      <itunes:episode>16</itunes:episode>
      <podcast:episode>16</podcast:episode>
      <itunes:title>How to get job candidates to accept an offer</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">5f707a1b-06e5-4eda-afca-6ed56e79db25</guid>
      <link>https://share.transistor.fm/s/7f6ed695</link>
      <description>
        <![CDATA[<p>This episode ended up being a brainstorming exercise on how Tyler can increase the acceptance rate of his job offers at <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>. </p><p><br><strong>Takeaways include:</strong></p><ul><li>Survey candidates after they either accept or reject to learn more<ul><li>When someone says no, ask why they're saying no. </li><li>That might lead to some really quick problems you could solve.</li><li>Look at this from two lenses:<ul><li>Controllable rejections - there’s a way you could’ve changed this outcome. </li><li>Uncontrollable rejections - there's no way you could've changed it. </li></ul></li><li>Even if it's uncontrollable, that doesn't mean there's no action you could've taken.<ul><li>You probably could have figured this out earlier in the interview process, and just stopped interviewing them because they were never going to accept anyway. </li></ul></li></ul></li><li>Understand why people accept your offer<ul><li>This can lead to some of the best insights on the value propositions that you need to focus on more with future candidates.</li></ul></li><li>Highlight your differentiation throughout the interview process<ul><li>Make sure your candidates understand why your workplace is unique and special</li><li>You can do this at every touchpoint</li></ul></li><li>When you make an offer, show them your excited<ul><li>Make a personal call or send a personal note</li><li>Have other people at the company reach out after we give an offer to encourage them to accept</li><li>Don’t be afraid to share your excitement with emotion</li></ul></li><li>Try making the offer in-person<ul><li>You could have them come into the office for a final meeting</li><li>Or you could go to them</li></ul></li><li>Invite questions and concerns before a final decision<ul><li>Offer to go out and meet them and talk about stuff after the offer.</li></ul></li><li>Consider whether your acceptance rate is good enough<ul><li>Maybe it would be better to focus on more applicants instead of increase the conversion rate</li></ul></li><li>Make the written offer special <ul><li>Make the offer letter personal</li><li>Sell the role and company instead of just explaining what the offer is. </li><li>Answer the key questions about total compensation and benefits</li></ul></li><li>Before you make an offer, find out where the candidates stands<ul><li>Before you stop the final interview and move to offer mode, spend some time with the candidate and try to pull concerns out, pull anxieties out, pull out what might make them say no. Then address the issues before you make an offer.</li><li>Question examples:<ul><li>“If you're not working here five years from now, what's the most likely reason why?”</li><li>“If you were to decline our offer, what would be the most likely reason</li></ul></li></ul></li><li>When you are the employer, there’s a power imbalance<ul><li>Keep this power imbalance in mind to avoid false signals and to make sure your candidate is comfortable</li></ul></li></ul><p><strong>Introduction<br></strong><br></p><p><strong>Tyler:</strong> The topic for today is basically flipping interview advice on its head, and saying normally it's assuming that the company is in the driver's seat and has all the power. What I want to talk about today is after you get to the point where you know you want someone, well or before that point, but what can you do to really maximize the odds of someone actually accepting one of these offers. We have a coding fellow, which is where we teach people to code, we have two different internships, and we have a full time position we're recruiting for right now. It really, really sucks when you find the perfect person, you give them the offer, and they decline. I just want to avoid that if I can.</p><p><strong>Rick:</strong> Yeah. Well, before the show I asked you I think what your acceptance rate was currently, can you share that?</p><p><br></p><p><strong>Tyler</strong>: Yeah, this is kind of back of the napkin because we don't have a real applicant tracking system for this, but I would guess it's about 75% probably say yes, and 25% decline, would be my guess. More people decline earlier, but I'd say if we give an offer, some people bow out of the process before this, but if we give an offer, I'd say we have about 75%.</p><p><strong>Rick:</strong> Cool. It sounds like what you want to focus on is how to increase that 75% up to a higher rate.</p><p><strong>Tyler:</strong> Yeah. Absolutely. And I think there's other benefits to this too. It's sort of like the way a good sales process for a company is going to lead to better customer retention also. This is the first impression for a recruit, and we want to build momentum that carries all the way through to after they start.</p><p><strong>Rick: </strong>Okay. All right. Well, I guess, what would be success for this conversation?</p><p><strong>Tyler: </strong>Yeah, I mean, what I'm looking for, I think, I mean ultimately the vague version of this is I just want to get people to actually say yes when I give them job offers. Specifically, I think I'd love a couple tangible takeaways or, not even... just ideas. I feel this is like a brainstorming thing where it's like maybe we can come up with five or ten things I can try, and maybe I'll actually actually try three of them, and one of them will work. But things I can actually do to just do more than whatever I'm doing now, which might be, in some ways, the bare minimum to get people to say yes.</p><p><br></p><p><strong>How the interview and offer process works currently<br></strong><br></p><p><strong>Rick: </strong>Well can you talk about what you're doing now?</p><p><strong>Tyler:</strong> Yeah. I'm inclined to break this into two categories. One is what's the whole interview process? Because that's leaving an impression on the person, and then there's the actual offer itself. I'm probably really bad at the offer itself. That's probably like the low hanging fruit here. But I'm happy to start at the beginning if you think that'd be helpful.</p><p><strong>Rick:</strong> Totally up to you. We can dive in right to the offer, how you're positioning that, or you could add context about how you're going about this.</p><p><strong>Tyler:</strong> Okay. Let me add a little context, but let's start by talking about the offer just because I think there's the most opportunity to improve there. We go and recruit mostly at schools, but sometimes through LinkedIn, or whatever other channel. The general process, it depends on the job, but it's something like a phone screen followed by, well sorry, they apply with a writing sample and a resume, we do a phone screen, then we bring them in for an in-person. The in-person interview is pretty long. And one of the reasons for that is it's like half us interviewing them, but half us trying to show them they would like it here. Which is easy for college students. With an adult, it's a little harder. Everyone wants different things. College students don't have a very refined idea of what they want. We play a board game with them, and give them free food, and they're like, "Oh great." But it's about a four-ish hour in-person with about half of that being us trying to make them think it's a cool place to work. Normally there's maybe let's say a week, or two, or three where we're finishing all those in-person interviews and we give the offer. What we do for that right now is I call them up. One thing I'm interested in your thoughts on is should it be me, should it be the person's direct manager calling them, but I call them up. No one ever picks up their phone, so the options are leave a voicemail, a vague voicemail that's like call me back or just give them the offer in the voicemail. I've dabbled with both. Right now I'm of the opinio...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This episode ended up being a brainstorming exercise on how Tyler can increase the acceptance rate of his job offers at <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>. </p><p><br><strong>Takeaways include:</strong></p><ul><li>Survey candidates after they either accept or reject to learn more<ul><li>When someone says no, ask why they're saying no. </li><li>That might lead to some really quick problems you could solve.</li><li>Look at this from two lenses:<ul><li>Controllable rejections - there’s a way you could’ve changed this outcome. </li><li>Uncontrollable rejections - there's no way you could've changed it. </li></ul></li><li>Even if it's uncontrollable, that doesn't mean there's no action you could've taken.<ul><li>You probably could have figured this out earlier in the interview process, and just stopped interviewing them because they were never going to accept anyway. </li></ul></li></ul></li><li>Understand why people accept your offer<ul><li>This can lead to some of the best insights on the value propositions that you need to focus on more with future candidates.</li></ul></li><li>Highlight your differentiation throughout the interview process<ul><li>Make sure your candidates understand why your workplace is unique and special</li><li>You can do this at every touchpoint</li></ul></li><li>When you make an offer, show them your excited<ul><li>Make a personal call or send a personal note</li><li>Have other people at the company reach out after we give an offer to encourage them to accept</li><li>Don’t be afraid to share your excitement with emotion</li></ul></li><li>Try making the offer in-person<ul><li>You could have them come into the office for a final meeting</li><li>Or you could go to them</li></ul></li><li>Invite questions and concerns before a final decision<ul><li>Offer to go out and meet them and talk about stuff after the offer.</li></ul></li><li>Consider whether your acceptance rate is good enough<ul><li>Maybe it would be better to focus on more applicants instead of increase the conversion rate</li></ul></li><li>Make the written offer special <ul><li>Make the offer letter personal</li><li>Sell the role and company instead of just explaining what the offer is. </li><li>Answer the key questions about total compensation and benefits</li></ul></li><li>Before you make an offer, find out where the candidates stands<ul><li>Before you stop the final interview and move to offer mode, spend some time with the candidate and try to pull concerns out, pull anxieties out, pull out what might make them say no. Then address the issues before you make an offer.</li><li>Question examples:<ul><li>“If you're not working here five years from now, what's the most likely reason why?”</li><li>“If you were to decline our offer, what would be the most likely reason</li></ul></li></ul></li><li>When you are the employer, there’s a power imbalance<ul><li>Keep this power imbalance in mind to avoid false signals and to make sure your candidate is comfortable</li></ul></li></ul><p><strong>Introduction<br></strong><br></p><p><strong>Tyler:</strong> The topic for today is basically flipping interview advice on its head, and saying normally it's assuming that the company is in the driver's seat and has all the power. What I want to talk about today is after you get to the point where you know you want someone, well or before that point, but what can you do to really maximize the odds of someone actually accepting one of these offers. We have a coding fellow, which is where we teach people to code, we have two different internships, and we have a full time position we're recruiting for right now. It really, really sucks when you find the perfect person, you give them the offer, and they decline. I just want to avoid that if I can.</p><p><strong>Rick:</strong> Yeah. Well, before the show I asked you I think what your acceptance rate was currently, can you share that?</p><p><br></p><p><strong>Tyler</strong>: Yeah, this is kind of back of the napkin because we don't have a real applicant tracking system for this, but I would guess it's about 75% probably say yes, and 25% decline, would be my guess. More people decline earlier, but I'd say if we give an offer, some people bow out of the process before this, but if we give an offer, I'd say we have about 75%.</p><p><strong>Rick:</strong> Cool. It sounds like what you want to focus on is how to increase that 75% up to a higher rate.</p><p><strong>Tyler:</strong> Yeah. Absolutely. And I think there's other benefits to this too. It's sort of like the way a good sales process for a company is going to lead to better customer retention also. This is the first impression for a recruit, and we want to build momentum that carries all the way through to after they start.</p><p><strong>Rick: </strong>Okay. All right. Well, I guess, what would be success for this conversation?</p><p><strong>Tyler: </strong>Yeah, I mean, what I'm looking for, I think, I mean ultimately the vague version of this is I just want to get people to actually say yes when I give them job offers. Specifically, I think I'd love a couple tangible takeaways or, not even... just ideas. I feel this is like a brainstorming thing where it's like maybe we can come up with five or ten things I can try, and maybe I'll actually actually try three of them, and one of them will work. But things I can actually do to just do more than whatever I'm doing now, which might be, in some ways, the bare minimum to get people to say yes.</p><p><br></p><p><strong>How the interview and offer process works currently<br></strong><br></p><p><strong>Rick: </strong>Well can you talk about what you're doing now?</p><p><strong>Tyler:</strong> Yeah. I'm inclined to break this into two categories. One is what's the whole interview process? Because that's leaving an impression on the person, and then there's the actual offer itself. I'm probably really bad at the offer itself. That's probably like the low hanging fruit here. But I'm happy to start at the beginning if you think that'd be helpful.</p><p><strong>Rick:</strong> Totally up to you. We can dive in right to the offer, how you're positioning that, or you could add context about how you're going about this.</p><p><strong>Tyler:</strong> Okay. Let me add a little context, but let's start by talking about the offer just because I think there's the most opportunity to improve there. We go and recruit mostly at schools, but sometimes through LinkedIn, or whatever other channel. The general process, it depends on the job, but it's something like a phone screen followed by, well sorry, they apply with a writing sample and a resume, we do a phone screen, then we bring them in for an in-person. The in-person interview is pretty long. And one of the reasons for that is it's like half us interviewing them, but half us trying to show them they would like it here. Which is easy for college students. With an adult, it's a little harder. Everyone wants different things. College students don't have a very refined idea of what they want. We play a board game with them, and give them free food, and they're like, "Oh great." But it's about a four-ish hour in-person with about half of that being us trying to make them think it's a cool place to work. Normally there's maybe let's say a week, or two, or three where we're finishing all those in-person interviews and we give the offer. What we do for that right now is I call them up. One thing I'm interested in your thoughts on is should it be me, should it be the person's direct manager calling them, but I call them up. No one ever picks up their phone, so the options are leave a voicemail, a vague voicemail that's like call me back or just give them the offer in the voicemail. I've dabbled with both. Right now I'm of the opinio...</p>]]>
      </content:encoded>
      <pubDate>Thu, 31 Oct 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7f6ed695/44fe76d1.mp3" length="45094503" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2704</itunes:duration>
      <itunes:summary>Tyler is in the middle of a recruiting cycle and he'll start giving job offers soon. This week, we talk about what he can do to to increase the odds of candidates accepting those offers.</itunes:summary>
      <itunes:subtitle>Tyler is in the middle of a recruiting cycle and he'll start giving job offers soon. This week, we talk about what he can do to to increase the odds of candidates accepting those offers.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to know when a product is minimally viable</title>
      <itunes:episode>15</itunes:episode>
      <podcast:episode>15</podcast:episode>
      <itunes:title>How to know when a product is minimally viable</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b5e963ef-8f43-4d61-88cc-8a1274dcd6c4</guid>
      <link>https://share.transistor.fm/s/edb10145</link>
      <description>
        <![CDATA[<p>This episode ended up being a brainstorming exercise on how Rick can set high-confidence MVP requirements for his <a href="https://www.legupventures.com/ventures">ventures at LegUp</a>. We identified several approaches to scoping an initial MVP:</p><ul><li><strong>The productized service approach. </strong>This is where you start with a service business and iterate your service into a product with automation tools and software. </li><li><strong>The skateboard approach.</strong> This is where you start with a simple product that solves a very tiny piece of your big problem (e.g. the skateboard solves the big transportation in much simpler way than a car).</li><li><strong>The learning approach</strong>. This is where you scope MVPs to test specific, prioritized hypotheses about your business.</li></ul><p><strong>Takeaways include:</strong></p><ul><li>MVPs are a tool designed to help validate ideas and learn.<ul><li>It's up to each person to figure out how to apply it in a way that works for them.</li><li>Don’t lose sight of this and overcomplicate it.</li></ul></li><li>Consider a minimum viable product verses minimum sellable product.<ul><li>Viable could mean learning in exchange for delivering value.</li><li>Sellable means receiving cash in exchange for delivering value.</li></ul></li><li>Don’t worry so much about having the perfect industry-accepted definition for what you're trying to do.<ul><li>When you're new to entrepreneurship, you hear these terms, and sometimes you just need to talk to someone about what you're trying to accomplish and just validate it, and make sure that you just check your sanity on these things. </li></ul></li><li>The situation drives everything.<ul><li>There are also constraints that are brought by the situation, such as whether you fund yourself or raise capital, whether you have partners, what skill sets you have around the table, those kinds of things.</li></ul></li><li>Consider whether you're building a process problem solver or a productivity tool. <ul><li>The type of problem you are solving drives a lot of difference in how you approach building MVPs.</li></ul></li><li>First time founders should consider identifying problems that can be started as a service business and productized later. <ul><li>It's much, much easier to support yourself and generate some revenue with services, consulting, contracting, than it is with a product. Start with the easy money and then evolve towards that product.</li></ul></li><li>Don't be afraid to build a product that's, to the user, providing a lot of value. But behind the scenes it's cobbled together with spreadsheets. <ul><li>What matters is that you're delivering value.</li></ul></li></ul><p><strong><br>Introduction<br></strong><br></p><p><strong>Tyler: </strong>Okay, let's dive into the topic here. We're going to talk about, basically, out of an MVP, a minimum viable product, how do you know when you're at a V, the viable part? Do you want to intro this a little bit?</p><p><strong>Rick: </strong>Yeah, I thought about some context right before this, so I want to share this with you. I don't know exactly how this topic conversation's going to go. I'm perfectly fine with just having some confidence to move forward with what I'm thinking already, that would be a great outcome. But I feel a lack of confidence with my plan moving forward, and I'm hoping that, whether it changes or not, whenever we do takeaways, I'm moving forward after this. Additional context is that, I can't remember exactly what you said in a previous episode, but one contributing factor to this is, I'm new to coding. Outside of computer science classes, I've actually never built by myself a product and released it to the world. I've always had a partner or coworkers working with me on that. This is new to me. Here's what you said, I think I just remembered it. You said that, compared with where we were when we worked together at <a href="http://zanebenefits.com/">Zane Benefits</a> back 2007, 2008, 2009, it's 2019 going into 2020 now, and you said that the minimally viable product threshold for an internet-based software business has increased significantly over the last 10 years. I guess that's one thing that is holding me back is, how do I know when I've met that threshold is a question. But, what I'd like to do is add some more context. Does that make sense?</p><p><br></p><p><strong>Tyler:</strong> Yeah. I mean, I think anyone who ever starts a business has this question of, "How good does it have to be?" Like everyone says, you want to go out and validate and test stuff, so you make something, you go sell it. But what if it's so crappy? It would have worked if it was better, but it doesn't work at its current version. How do you know when it's actually ready to go sell it? Right?</p><p><strong>Rick: </strong>Yup. Yup. Exactly. I'm starting to scope a few no-code minimally viable products to work on for the rest of the year. Just to give you some specifics around the industries, they're all software businesses, internet-based. One is in the financial services space, specifically I would say health insurance, one is <a href="http://groupcurrent.com/">GroupCurrent's</a> member management software, so a community management platform. Arguably we already have an MVP there, we're just interesting to talk about. Then the third is... One problem I have, this is a personal problem, when you taught me, you said, "Teach yourself how to code." You said, "Find a personal problem to solve and learn to code around that." I'm actually probably going to do that coding-wise versus no-code. But I read a lot of books and I listen to a lot of podcasts. I consume a lot of content, and I want to talk to Sable about those things, Sable's my wife. I can't oftentimes get her to... she doesn't have time to read the books that I read, nor does she really want to. I want to build a Sable notes app, which allows me to basically summarize the takeaways and the topics and give enough context to her from these books and these podcasts I'm listening to so that we can talk about it.</p><p><br></p><p><strong>Tyler: </strong>But that's a personal project to learn to code. That's not an MVP type of thing, right?</p><p><strong>Rick: </strong>Well, I guess in this case if Sable uses it, that would be the measure of success. But, I could apply the principles to this, but the threshold is much lower. Anyway, those are some of the things I'm thinking about. One thing I need to do that's actually probably unique to no-code in this space is, I need to identify the right stack of tools. Stack meaning, what different tools do I need to stack on top of each other to make this work with no-code, make the product work. In order to identify the right stack I need to be pretty clear about the minimum viability requirements because with no-code there are some pretty specific use cases for each stack. Getting the right stack setup, you may have to change all the tools if you get the minimally viable requirements wrong.</p><p><strong>Tyler: </strong>Yeah. Do you want to... I mean we could have this conversation like, "Yes, you're going to build it with no-code, but maybe that's a separate thing. How do you take what we say, or do you want to say, let's frame this around the constraints of what no-code tools give you.</p><p><strong><br>What is an MVP and where does it fit?<br></strong><br></p><p><strong>Rick:</strong> I'd rather fly above no-code because I think that that's just a way to get it done. At the end of the day, I need a framework to give myself confidence that I can move to the next step in the entrepreneurial journey. What I would like to start with is, I'd like to tell you how I'm thinking about it, and my definition of MVP, and then I have no doubt that you're going to have a different philosophy than me. Here's how I think abou...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This episode ended up being a brainstorming exercise on how Rick can set high-confidence MVP requirements for his <a href="https://www.legupventures.com/ventures">ventures at LegUp</a>. We identified several approaches to scoping an initial MVP:</p><ul><li><strong>The productized service approach. </strong>This is where you start with a service business and iterate your service into a product with automation tools and software. </li><li><strong>The skateboard approach.</strong> This is where you start with a simple product that solves a very tiny piece of your big problem (e.g. the skateboard solves the big transportation in much simpler way than a car).</li><li><strong>The learning approach</strong>. This is where you scope MVPs to test specific, prioritized hypotheses about your business.</li></ul><p><strong>Takeaways include:</strong></p><ul><li>MVPs are a tool designed to help validate ideas and learn.<ul><li>It's up to each person to figure out how to apply it in a way that works for them.</li><li>Don’t lose sight of this and overcomplicate it.</li></ul></li><li>Consider a minimum viable product verses minimum sellable product.<ul><li>Viable could mean learning in exchange for delivering value.</li><li>Sellable means receiving cash in exchange for delivering value.</li></ul></li><li>Don’t worry so much about having the perfect industry-accepted definition for what you're trying to do.<ul><li>When you're new to entrepreneurship, you hear these terms, and sometimes you just need to talk to someone about what you're trying to accomplish and just validate it, and make sure that you just check your sanity on these things. </li></ul></li><li>The situation drives everything.<ul><li>There are also constraints that are brought by the situation, such as whether you fund yourself or raise capital, whether you have partners, what skill sets you have around the table, those kinds of things.</li></ul></li><li>Consider whether you're building a process problem solver or a productivity tool. <ul><li>The type of problem you are solving drives a lot of difference in how you approach building MVPs.</li></ul></li><li>First time founders should consider identifying problems that can be started as a service business and productized later. <ul><li>It's much, much easier to support yourself and generate some revenue with services, consulting, contracting, than it is with a product. Start with the easy money and then evolve towards that product.</li></ul></li><li>Don't be afraid to build a product that's, to the user, providing a lot of value. But behind the scenes it's cobbled together with spreadsheets. <ul><li>What matters is that you're delivering value.</li></ul></li></ul><p><strong><br>Introduction<br></strong><br></p><p><strong>Tyler: </strong>Okay, let's dive into the topic here. We're going to talk about, basically, out of an MVP, a minimum viable product, how do you know when you're at a V, the viable part? Do you want to intro this a little bit?</p><p><strong>Rick: </strong>Yeah, I thought about some context right before this, so I want to share this with you. I don't know exactly how this topic conversation's going to go. I'm perfectly fine with just having some confidence to move forward with what I'm thinking already, that would be a great outcome. But I feel a lack of confidence with my plan moving forward, and I'm hoping that, whether it changes or not, whenever we do takeaways, I'm moving forward after this. Additional context is that, I can't remember exactly what you said in a previous episode, but one contributing factor to this is, I'm new to coding. Outside of computer science classes, I've actually never built by myself a product and released it to the world. I've always had a partner or coworkers working with me on that. This is new to me. Here's what you said, I think I just remembered it. You said that, compared with where we were when we worked together at <a href="http://zanebenefits.com/">Zane Benefits</a> back 2007, 2008, 2009, it's 2019 going into 2020 now, and you said that the minimally viable product threshold for an internet-based software business has increased significantly over the last 10 years. I guess that's one thing that is holding me back is, how do I know when I've met that threshold is a question. But, what I'd like to do is add some more context. Does that make sense?</p><p><br></p><p><strong>Tyler:</strong> Yeah. I mean, I think anyone who ever starts a business has this question of, "How good does it have to be?" Like everyone says, you want to go out and validate and test stuff, so you make something, you go sell it. But what if it's so crappy? It would have worked if it was better, but it doesn't work at its current version. How do you know when it's actually ready to go sell it? Right?</p><p><strong>Rick: </strong>Yup. Yup. Exactly. I'm starting to scope a few no-code minimally viable products to work on for the rest of the year. Just to give you some specifics around the industries, they're all software businesses, internet-based. One is in the financial services space, specifically I would say health insurance, one is <a href="http://groupcurrent.com/">GroupCurrent's</a> member management software, so a community management platform. Arguably we already have an MVP there, we're just interesting to talk about. Then the third is... One problem I have, this is a personal problem, when you taught me, you said, "Teach yourself how to code." You said, "Find a personal problem to solve and learn to code around that." I'm actually probably going to do that coding-wise versus no-code. But I read a lot of books and I listen to a lot of podcasts. I consume a lot of content, and I want to talk to Sable about those things, Sable's my wife. I can't oftentimes get her to... she doesn't have time to read the books that I read, nor does she really want to. I want to build a Sable notes app, which allows me to basically summarize the takeaways and the topics and give enough context to her from these books and these podcasts I'm listening to so that we can talk about it.</p><p><br></p><p><strong>Tyler: </strong>But that's a personal project to learn to code. That's not an MVP type of thing, right?</p><p><strong>Rick: </strong>Well, I guess in this case if Sable uses it, that would be the measure of success. But, I could apply the principles to this, but the threshold is much lower. Anyway, those are some of the things I'm thinking about. One thing I need to do that's actually probably unique to no-code in this space is, I need to identify the right stack of tools. Stack meaning, what different tools do I need to stack on top of each other to make this work with no-code, make the product work. In order to identify the right stack I need to be pretty clear about the minimum viability requirements because with no-code there are some pretty specific use cases for each stack. Getting the right stack setup, you may have to change all the tools if you get the minimally viable requirements wrong.</p><p><strong>Tyler: </strong>Yeah. Do you want to... I mean we could have this conversation like, "Yes, you're going to build it with no-code, but maybe that's a separate thing. How do you take what we say, or do you want to say, let's frame this around the constraints of what no-code tools give you.</p><p><strong><br>What is an MVP and where does it fit?<br></strong><br></p><p><strong>Rick:</strong> I'd rather fly above no-code because I think that that's just a way to get it done. At the end of the day, I need a framework to give myself confidence that I can move to the next step in the entrepreneurial journey. What I would like to start with is, I'd like to tell you how I'm thinking about it, and my definition of MVP, and then I have no doubt that you're going to have a different philosophy than me. Here's how I think abou...</p>]]>
      </content:encoded>
      <pubDate>Thu, 24 Oct 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/edb10145/de1a4179.mp3" length="51508134" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3075</itunes:duration>
      <itunes:summary>This week, we talk about how "viable" an MVP actually needs to be before you can stop building, and start selling.</itunes:summary>
      <itunes:subtitle>This week, we talk about how "viable" an MVP actually needs to be before you can stop building, and start selling.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to improve a customer referral program</title>
      <itunes:episode>14</itunes:episode>
      <podcast:episode>14</podcast:episode>
      <itunes:title>How to improve a customer referral program</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">efe79ad3-2645-45c1-991c-e07c39e63de8</guid>
      <link>https://share.transistor.fm/s/bd045e66</link>
      <description>
        <![CDATA[<p>This episode ended up being a brainstorming exercise on how Tyler can increase usage of  <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>’s customer referral program. Tyler may focus in the following areas: </p><ol><li>Trying to increase usage of the existing referral program by driving more awareness</li><li>Trying to capture more information from signups to determine if they were referred</li><li>Trying to repackage the referral program to make it more transactional.</li></ol><p>Takeaways include:</p><ul><li>It’s important to have a remarkable product experience (that people want to talk about) before you focus on referrals</li><li>Decide what the objective of your customer referral program is upfront<ul><li>For example, is it to create leads or paid signups?</li></ul></li><li>It’s hard to create a customer referral program for products with long sales cycles<ul><li>If you have a long sales cycle, consider creating or packaging a mini-product that is more transactional in nature to make it easier for your customers to refer (e.g. <a href="https://website.grader.com/">Hubspot’s website grader</a>)</li></ul></li><li>It’s hard to incentivize referrals on a low-ACV product<ul><li>This is especially hard if there is also a long sales cycle</li><li>Considering gamifying and /or tieing referrals into product features</li></ul></li><li>Think of your customers referral program as a product that requires its own product / market fit.<ul><li>Consider the size of your market (customers and their potential referrals) and how to build the right product for both parties</li></ul></li><li>Once you think you have a solid referral program product, make sure your customers are aware of it<ul><li>Be careful, you don’t want to be annoying or spammy</li><li>Considering marketing it passively as part of larger “join the movement” community building<ul><li>With thoughtful design, you can do this in passive sections of your newsletters, emails, website pages and app pages. (But, don’t be too annoying)</li></ul></li></ul></li><li><a href="https://www.morningbrew.com/daily/r/?kid=fd820f">Morning Brew</a>, a daily newsletter, provides a good example of an awesome referral program.<ul><li>They've actually written <a href="https://medium.com/the-mission/how-morning-brews-referral-program-built-an-audience-of-1-5-million-subscribers-3315482c1aa5">a blog post about it</a>.</li></ul></li></ul><p><strong>Introduction<br></strong><br></p><p><strong>Tyler: </strong>We're framing it as, how to structure a referral program. But let me dive into why I'm thinking about this.Less Annoying CRM, my business, is currently at about two and a half million dollars in annual recurring revenue. We're growing about 20% per year. I'm happy with both of those numbers, but every company obviously wants to grow, at the very least continue growing and maybe even increase growth. We have not had a lot of success with a lot of marketing things we've tried. One of the reasons for this is totally my fault that I refuse to do certain things. I don't want to do retargeting advertising because I think it's a privacy violation. Anything that's not permission marketing, I'm pretty much opposed to. Also, it's just not one of our core competencies, and because our price point is so low, we don't have the type of budget to compete with other companies on marketing. As a result of that, the way we grow is almost entirely through word of mouth, which is awesome because it's free, it aligns what we're doing with customers. I really like word of mouth growth, but the downside is we have no control over it. I think that's... Would you agree that's true with most companies, that you just cross your fingers and hope word of mouth happens?</p><p><strong>Rick:</strong> Yeah, I would say so. It's definitely one of those voodoo marketing tricks versus a systematic levered sales approach.</p><p><strong>Tyler:</strong> Right? Word of mouth is a big topic. Making the product better, for example, maybe is one way to help with it. That's not what I want to talk about today. What I want to specifically do is say, in as much as we can control word of mouth growth, well, A, we have to be able to track it in order to do anything with it, and B, a referral program is one of potentially many ways to increase word of mouth growth. That's what I want to talk about. Historically, what we've done as a company is, we've offered a deal. It's basically the Dropbox deal, which is, anyone of our customers who refers someone else, that other person gets an extra free month of their free trial, and the person who did the referring gets a $10 credit. A free month themselves.</p><p><br></p><p><strong>Rick:</strong> Give one get one.</p><p><strong>Tyler:</strong> Give one get one. A pretty classic approach, it's worked plenty of times before. Unfortunately, not many people actually use this. Anecdotally, we have quite a bit of reason to believe that lots of people... almost all our growth comes from word of mouth, but the vast majority of that, I would estimate it at about five to 10%, actually uses the referral program. Which is not great because it means we can't track it, we can't tell what's working, we can't experiment very easily. Basically what I would like to talk about today is, how do we offer some kind of referral program that gets our users, when they refer someone, when they do the word of mouth thing, the person who's signing up actually uses a link that tracks back to... Or maybe that's not even the way to do it, but that one way or another we can track it back to the person who did the referral. This might involve giving incentives, it might be restructuring how the technology for the link tracking works. I don't know, but that's the basic problem I'm interested in talking about.</p><p><strong>Rick:</strong> Yeah. Recapping, I want to make sure I got this. You've got a couple of challenges. Well, you've got a great product that people want to talk about, that's the good thing.</p><p><br></p><p><strong>Tyler:</strong> Yeah, that's the good thing.</p><p><strong><br>The challenge of low ACVs<br></strong><br></p><p><strong>Rick</strong>: You know that that's happening, you just don't have control over it. One constraint you have is that you have a low ACV, which means you can't spend a whole lot of money on this. I think the bigger constraint though is your philosophical constraints that you're placing on yourself that don't allow you to engage in some of the marketing activities that actually do give you control over this in terms of data collection.</p><p><br></p><p><strong>Tyler:</strong> Fair. Maybe we should talk about this because it's a case by case basis I guess.</p><p><strong>Rick</strong>: Yeah. I think it's hard enough to control marketing on a low ACV by itself. Then when you add, "Oh I'm not going to do that-"</p><p><strong>Tyler:</strong> Sorry, ACV is annual contract value, right?</p><p><strong>Rick</strong>: Correct. Thank you. Annual contract value, which is... Let's just talk in, it's $10 per user per month. With that amount of money, you don't have a whole lot of money to spend on advertising or anything like that. Then on top of that you're saying, but I wouldn't even be willing to do that if I did have the money because I don't believe in it.</p><p><strong>Tyler:</strong> That's one of the reasons I'm trying to constrain to say, there is a whole range of topics about marketing that we could be talking about. But just to keep this constrained I'm saying, people are already doing word of mouth like referrals. I want to be able to track it and consider ways to specifically enable them. One of the things I love about word of mouth is that the customer wants to refer people to us. Everyone is aligned here. I just want to empower them to do it and...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This episode ended up being a brainstorming exercise on how Tyler can increase usage of  <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>’s customer referral program. Tyler may focus in the following areas: </p><ol><li>Trying to increase usage of the existing referral program by driving more awareness</li><li>Trying to capture more information from signups to determine if they were referred</li><li>Trying to repackage the referral program to make it more transactional.</li></ol><p>Takeaways include:</p><ul><li>It’s important to have a remarkable product experience (that people want to talk about) before you focus on referrals</li><li>Decide what the objective of your customer referral program is upfront<ul><li>For example, is it to create leads or paid signups?</li></ul></li><li>It’s hard to create a customer referral program for products with long sales cycles<ul><li>If you have a long sales cycle, consider creating or packaging a mini-product that is more transactional in nature to make it easier for your customers to refer (e.g. <a href="https://website.grader.com/">Hubspot’s website grader</a>)</li></ul></li><li>It’s hard to incentivize referrals on a low-ACV product<ul><li>This is especially hard if there is also a long sales cycle</li><li>Considering gamifying and /or tieing referrals into product features</li></ul></li><li>Think of your customers referral program as a product that requires its own product / market fit.<ul><li>Consider the size of your market (customers and their potential referrals) and how to build the right product for both parties</li></ul></li><li>Once you think you have a solid referral program product, make sure your customers are aware of it<ul><li>Be careful, you don’t want to be annoying or spammy</li><li>Considering marketing it passively as part of larger “join the movement” community building<ul><li>With thoughtful design, you can do this in passive sections of your newsletters, emails, website pages and app pages. (But, don’t be too annoying)</li></ul></li></ul></li><li><a href="https://www.morningbrew.com/daily/r/?kid=fd820f">Morning Brew</a>, a daily newsletter, provides a good example of an awesome referral program.<ul><li>They've actually written <a href="https://medium.com/the-mission/how-morning-brews-referral-program-built-an-audience-of-1-5-million-subscribers-3315482c1aa5">a blog post about it</a>.</li></ul></li></ul><p><strong>Introduction<br></strong><br></p><p><strong>Tyler: </strong>We're framing it as, how to structure a referral program. But let me dive into why I'm thinking about this.Less Annoying CRM, my business, is currently at about two and a half million dollars in annual recurring revenue. We're growing about 20% per year. I'm happy with both of those numbers, but every company obviously wants to grow, at the very least continue growing and maybe even increase growth. We have not had a lot of success with a lot of marketing things we've tried. One of the reasons for this is totally my fault that I refuse to do certain things. I don't want to do retargeting advertising because I think it's a privacy violation. Anything that's not permission marketing, I'm pretty much opposed to. Also, it's just not one of our core competencies, and because our price point is so low, we don't have the type of budget to compete with other companies on marketing. As a result of that, the way we grow is almost entirely through word of mouth, which is awesome because it's free, it aligns what we're doing with customers. I really like word of mouth growth, but the downside is we have no control over it. I think that's... Would you agree that's true with most companies, that you just cross your fingers and hope word of mouth happens?</p><p><strong>Rick:</strong> Yeah, I would say so. It's definitely one of those voodoo marketing tricks versus a systematic levered sales approach.</p><p><strong>Tyler:</strong> Right? Word of mouth is a big topic. Making the product better, for example, maybe is one way to help with it. That's not what I want to talk about today. What I want to specifically do is say, in as much as we can control word of mouth growth, well, A, we have to be able to track it in order to do anything with it, and B, a referral program is one of potentially many ways to increase word of mouth growth. That's what I want to talk about. Historically, what we've done as a company is, we've offered a deal. It's basically the Dropbox deal, which is, anyone of our customers who refers someone else, that other person gets an extra free month of their free trial, and the person who did the referring gets a $10 credit. A free month themselves.</p><p><br></p><p><strong>Rick:</strong> Give one get one.</p><p><strong>Tyler:</strong> Give one get one. A pretty classic approach, it's worked plenty of times before. Unfortunately, not many people actually use this. Anecdotally, we have quite a bit of reason to believe that lots of people... almost all our growth comes from word of mouth, but the vast majority of that, I would estimate it at about five to 10%, actually uses the referral program. Which is not great because it means we can't track it, we can't tell what's working, we can't experiment very easily. Basically what I would like to talk about today is, how do we offer some kind of referral program that gets our users, when they refer someone, when they do the word of mouth thing, the person who's signing up actually uses a link that tracks back to... Or maybe that's not even the way to do it, but that one way or another we can track it back to the person who did the referral. This might involve giving incentives, it might be restructuring how the technology for the link tracking works. I don't know, but that's the basic problem I'm interested in talking about.</p><p><strong>Rick:</strong> Yeah. Recapping, I want to make sure I got this. You've got a couple of challenges. Well, you've got a great product that people want to talk about, that's the good thing.</p><p><br></p><p><strong>Tyler:</strong> Yeah, that's the good thing.</p><p><strong><br>The challenge of low ACVs<br></strong><br></p><p><strong>Rick</strong>: You know that that's happening, you just don't have control over it. One constraint you have is that you have a low ACV, which means you can't spend a whole lot of money on this. I think the bigger constraint though is your philosophical constraints that you're placing on yourself that don't allow you to engage in some of the marketing activities that actually do give you control over this in terms of data collection.</p><p><br></p><p><strong>Tyler:</strong> Fair. Maybe we should talk about this because it's a case by case basis I guess.</p><p><strong>Rick</strong>: Yeah. I think it's hard enough to control marketing on a low ACV by itself. Then when you add, "Oh I'm not going to do that-"</p><p><strong>Tyler:</strong> Sorry, ACV is annual contract value, right?</p><p><strong>Rick</strong>: Correct. Thank you. Annual contract value, which is... Let's just talk in, it's $10 per user per month. With that amount of money, you don't have a whole lot of money to spend on advertising or anything like that. Then on top of that you're saying, but I wouldn't even be willing to do that if I did have the money because I don't believe in it.</p><p><strong>Tyler:</strong> That's one of the reasons I'm trying to constrain to say, there is a whole range of topics about marketing that we could be talking about. But just to keep this constrained I'm saying, people are already doing word of mouth like referrals. I want to be able to track it and consider ways to specifically enable them. One of the things I love about word of mouth is that the customer wants to refer people to us. Everyone is aligned here. I just want to empower them to do it and...</p>]]>
      </content:encoded>
      <pubDate>Thu, 17 Oct 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/bd045e66/f8fd08d5.mp3" length="52637155" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3098</itunes:duration>
      <itunes:summary>This week, we talk about how Tyler can get his customers to use his company's referral program so that it's easier to track word of mouth growth. </itunes:summary>
      <itunes:subtitle>This week, we talk about how Tyler can get his customers to use his company's referral program so that it's easier to track word of mouth growth. </itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Resetting stakeholder expectations when things change at your business</title>
      <itunes:episode>13</itunes:episode>
      <podcast:episode>13</podcast:episode>
      <itunes:title>Resetting stakeholder expectations when things change at your business</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">2d48f2cf-d845-4884-ab36-1cfc31bb4042</guid>
      <link>https://share.transistor.fm/s/d295e2ce</link>
      <description>
        <![CDATA[<p>In this episode, we discuss how to reset expectations with stakeholders when things change. Rick shares a challenge he is facing at one of his companies. While we worked through a specific situation, the general concept applies often. Here’s the general framework that emerged:</p><ul><li>Clarify what needs to change and why<ul><li>Frame the problem(s) thoughtfully</li></ul></li><li>Identify the stakeholders and where do they stand<ul><li>Identify who has decision-making authority and who can be an ally</li></ul></li><li>Decide who to talk to first and iterate from there as a team<ul><li>Be open to feedback</li></ul></li><li>Get everyone aligned and move forward together<ul><li>Be aware of fundamental differences; these may require you or someone else to leave</li></ul></li></ul><p>Takeaways include: </p><ul><li>Change happens all the time and resetting expectations is critical when it happens</li><li>Some companies die because they never change their expectations</li><li>When you're going through change, the minimum time investment isn't enough. You have to talk a lot more</li><li>Start with the problems, but be thoughtful about how you frame them so that they're generalized problems that don't cause defensiveness</li><li>As a leader, people don't see the world like you do. Your job is to get them to see it like you do, and that takes communication and it takes patience</li><li>It is critical to get everyone to see the problems and talk about the problems</li><li>When you can talk about the problems because they're emotional, you can't talk about the solutions and get on the same page</li><li>When there is a fundamental disagreement you can’t get over, someone has to go (and it may be you). Get aligned on fundamental values and expectations before forming new partnerships</li></ul><p><strong><br>The problem<br></strong><br></p><p><strong>Rick</strong>: In life, change happens all the time. That's especially true in the workplace. Once you've been in business for more than a couple of years... even in the first year... lots of things that you thought were true are no longer true, and you have to change your mindset around what the truth is and what's going to happen next as a result of that. When you're on your own as a solo entrepreneur or you're an early founder, you just have a couple people that are all working pretty well together. It can be pretty easy to make those changes happen because the people in charge are able to make the decisions necessary to change their expectations. When you grow and you have multiple hands in the pot at different levels and it's been a longer period of time investment, you get to this place where resetting expectations is critical when a change happens, but it gets a lot harder. It gets a lot more emotionally complex. It gets a lot more complex just from sheer volume.</p><p><br></p><p><strong>Tyler:</strong> Different stakeholders who all want different things and they think they know what you're doing and things change.</p><p><strong>Rick:</strong> Multidimensional complexity increases over time. This applies to employees, partners, board members, investors. Even at home, when I was thinking about how to frame this problem I was thinking, "Well, this a Sable and Rick..." Sable is my wife. We deal with this constantly, especially in our first year of marriage where we're trying to talk about when do we have kids, what's our budget for certain things? I got fired a week before our marriage from my CEO job. It's one of those things that's like that had to go through a lot of expectation changes. Mostly, what I want to talk to you about is dealing with this at work with the stakeholders that you deal with, specifically at a nonprofit. At <a href="http://groupcurrent.com/">GroupCurrent</a>, we focus on helping member-based groups reach sustainability. Most of these groups are nonprofits. By design, most of our customers or nonprofit customers come to us because they've not been successful sustaining themselves. I don't want to say it's a shit show, but it's not a good situation.</p><p><br></p><p><strong>Tyler:</strong> To clarify sustaining themselves, you're saying they start out where they're getting donations from various places but it's a one-time donation. They can operate for a while, but what they want is an actual business model that they can count on, and that's where they come to you to help with.</p><p><strong>Rick: </strong>Yeah, and donations can be sustainable if you have a way of predicting them and continuing to receive them. When we starting GroupCurrent and deciding whether or not we wanted to be in this business, the thing that got me really excited is I discovered this problem that nonprofits often face, and it's not too different from a lot of founders... serial entrepreneurs, in my opinion. The situation is called the organizational starvation cycle. Some people call it the nonprofit starvation cycle, but I like organizational because I think it applies to more than just nonprofits. It starts with some unrealistic expectations from founders. In the nonprofit world, founders are called funders because generally the founders just provide the money and some guidance at the board level. They don't do the work. A lot of times, what they do is they hire a managing director or bring on some fellow board members to help run it, and they have super high expectations, unrealistic expectations. Those people that they hired feel a significant amount of pressure to conform to those expectations, which leads to either overworking, which leads to burnout, or it leads to fudging certain accuracy of things, whether it's maybe omitting when it should be said or rounding up when it should be rounded down. I speak to this stuff sensitively, because it is sensitive, but it leads to bad behavior to meet those expectations, which in turn leads to more unrealistic expectations because you're not dealing with the problem, which is unrealistic expectations. This cycle typically continues from the early days until it reaches a breaking point, which one of two things happen. Either there's no money and management gets fired and the nonprofit gets into this zombie land of, "What do we do next?" Maybe they shut down. Most of them just kind of live without doing much. Or the management goes, "Screw you guys. I can't do this anymore. I quit." There's some actual good things going on, but no one there to do the things anymore. To be successful at GroupCurrent, our clients are going to come to us because they've been in this situation, which is extremely complex emotionally. You've got founders who put a lot of money into it. You've got former people who have worked at the company who probably didn't feel like they were treated the right way. It's extremely complex. In order for us to be successful, we've got to be really good at coming in and resetting those expectations and getting all the stakeholders... the founders, the board members, and the employees that are currently working there, any current donors or community partners, any customers... on the same page with what to expect going forward. Those expectations could be mission, vision, values. It could be business model. It could be, "Hey, board members, you've got to start doing work now. You can't just sit." Roles are changing. We're dealing with this with one of our clients. We're very happy with our customer. This isn't a talk about how much the situation sucks, it's just there's a reality of the situation where the organization has gone through different renditions and it hasn't gotten yet to that place of sustainability. And it's not there yet, even with the work that we've done so far. I guess... go ahead.</p><p><br></p><p><strong>Tyler:</strong> I was just going to say I like this topic because we're going to talk about it specifically in your case. But this applies very much to the topic of...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discuss how to reset expectations with stakeholders when things change. Rick shares a challenge he is facing at one of his companies. While we worked through a specific situation, the general concept applies often. Here’s the general framework that emerged:</p><ul><li>Clarify what needs to change and why<ul><li>Frame the problem(s) thoughtfully</li></ul></li><li>Identify the stakeholders and where do they stand<ul><li>Identify who has decision-making authority and who can be an ally</li></ul></li><li>Decide who to talk to first and iterate from there as a team<ul><li>Be open to feedback</li></ul></li><li>Get everyone aligned and move forward together<ul><li>Be aware of fundamental differences; these may require you or someone else to leave</li></ul></li></ul><p>Takeaways include: </p><ul><li>Change happens all the time and resetting expectations is critical when it happens</li><li>Some companies die because they never change their expectations</li><li>When you're going through change, the minimum time investment isn't enough. You have to talk a lot more</li><li>Start with the problems, but be thoughtful about how you frame them so that they're generalized problems that don't cause defensiveness</li><li>As a leader, people don't see the world like you do. Your job is to get them to see it like you do, and that takes communication and it takes patience</li><li>It is critical to get everyone to see the problems and talk about the problems</li><li>When you can talk about the problems because they're emotional, you can't talk about the solutions and get on the same page</li><li>When there is a fundamental disagreement you can’t get over, someone has to go (and it may be you). Get aligned on fundamental values and expectations before forming new partnerships</li></ul><p><strong><br>The problem<br></strong><br></p><p><strong>Rick</strong>: In life, change happens all the time. That's especially true in the workplace. Once you've been in business for more than a couple of years... even in the first year... lots of things that you thought were true are no longer true, and you have to change your mindset around what the truth is and what's going to happen next as a result of that. When you're on your own as a solo entrepreneur or you're an early founder, you just have a couple people that are all working pretty well together. It can be pretty easy to make those changes happen because the people in charge are able to make the decisions necessary to change their expectations. When you grow and you have multiple hands in the pot at different levels and it's been a longer period of time investment, you get to this place where resetting expectations is critical when a change happens, but it gets a lot harder. It gets a lot more emotionally complex. It gets a lot more complex just from sheer volume.</p><p><br></p><p><strong>Tyler:</strong> Different stakeholders who all want different things and they think they know what you're doing and things change.</p><p><strong>Rick:</strong> Multidimensional complexity increases over time. This applies to employees, partners, board members, investors. Even at home, when I was thinking about how to frame this problem I was thinking, "Well, this a Sable and Rick..." Sable is my wife. We deal with this constantly, especially in our first year of marriage where we're trying to talk about when do we have kids, what's our budget for certain things? I got fired a week before our marriage from my CEO job. It's one of those things that's like that had to go through a lot of expectation changes. Mostly, what I want to talk to you about is dealing with this at work with the stakeholders that you deal with, specifically at a nonprofit. At <a href="http://groupcurrent.com/">GroupCurrent</a>, we focus on helping member-based groups reach sustainability. Most of these groups are nonprofits. By design, most of our customers or nonprofit customers come to us because they've not been successful sustaining themselves. I don't want to say it's a shit show, but it's not a good situation.</p><p><br></p><p><strong>Tyler:</strong> To clarify sustaining themselves, you're saying they start out where they're getting donations from various places but it's a one-time donation. They can operate for a while, but what they want is an actual business model that they can count on, and that's where they come to you to help with.</p><p><strong>Rick: </strong>Yeah, and donations can be sustainable if you have a way of predicting them and continuing to receive them. When we starting GroupCurrent and deciding whether or not we wanted to be in this business, the thing that got me really excited is I discovered this problem that nonprofits often face, and it's not too different from a lot of founders... serial entrepreneurs, in my opinion. The situation is called the organizational starvation cycle. Some people call it the nonprofit starvation cycle, but I like organizational because I think it applies to more than just nonprofits. It starts with some unrealistic expectations from founders. In the nonprofit world, founders are called funders because generally the founders just provide the money and some guidance at the board level. They don't do the work. A lot of times, what they do is they hire a managing director or bring on some fellow board members to help run it, and they have super high expectations, unrealistic expectations. Those people that they hired feel a significant amount of pressure to conform to those expectations, which leads to either overworking, which leads to burnout, or it leads to fudging certain accuracy of things, whether it's maybe omitting when it should be said or rounding up when it should be rounded down. I speak to this stuff sensitively, because it is sensitive, but it leads to bad behavior to meet those expectations, which in turn leads to more unrealistic expectations because you're not dealing with the problem, which is unrealistic expectations. This cycle typically continues from the early days until it reaches a breaking point, which one of two things happen. Either there's no money and management gets fired and the nonprofit gets into this zombie land of, "What do we do next?" Maybe they shut down. Most of them just kind of live without doing much. Or the management goes, "Screw you guys. I can't do this anymore. I quit." There's some actual good things going on, but no one there to do the things anymore. To be successful at GroupCurrent, our clients are going to come to us because they've been in this situation, which is extremely complex emotionally. You've got founders who put a lot of money into it. You've got former people who have worked at the company who probably didn't feel like they were treated the right way. It's extremely complex. In order for us to be successful, we've got to be really good at coming in and resetting those expectations and getting all the stakeholders... the founders, the board members, and the employees that are currently working there, any current donors or community partners, any customers... on the same page with what to expect going forward. Those expectations could be mission, vision, values. It could be business model. It could be, "Hey, board members, you've got to start doing work now. You can't just sit." Roles are changing. We're dealing with this with one of our clients. We're very happy with our customer. This isn't a talk about how much the situation sucks, it's just there's a reality of the situation where the organization has gone through different renditions and it hasn't gotten yet to that place of sustainability. And it's not there yet, even with the work that we've done so far. I guess... go ahead.</p><p><br></p><p><strong>Tyler:</strong> I was just going to say I like this topic because we're going to talk about it specifically in your case. But this applies very much to the topic of...</p>]]>
      </content:encoded>
      <pubDate>Thu, 10 Oct 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/d295e2ce/4d9d0cd7.mp3" length="59181831" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3538</itunes:duration>
      <itunes:summary>Change is a given at every business and organization. This week, we discuss how you can get all the stakeholders on board when circumstances have changed, and expectations need to change with them.</itunes:summary>
      <itunes:subtitle>Change is a given at every business and organization. This week, we discuss how you can get all the stakeholders on board when circumstances have changed, and expectations need to change with them.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Interview with Rick Lindquist, founder of LegUp Ventures</title>
      <itunes:episode>12</itunes:episode>
      <podcast:episode>12</podcast:episode>
      <itunes:title>Interview with Rick Lindquist, founder of LegUp Ventures</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d99fe187-38b0-45db-a24a-bd8249861a84</guid>
      <link>https://share.transistor.fm/s/0a561c95</link>
      <description>
        <![CDATA[<p>Here’s what you should know about Rick:</p><ul><li>Born in Raleigh, NC and grew up in Morganton and Charlotte, NC</li><li>Went to college at Duke University</li><li>Majored in Economics and Computer Science</li><li>Wrestled at Duke</li><li>Moved to Park City to Ski bum in after graduation</li><li>Met Tyler at a startup called Zane Benefits (which is now part of <a href="http://www.peoplekeep.com/">PeopleKeep</a>) in 2007</li><li>Became the President of Zane Benefits after a mass layoff in 2008</li><li>Bootstrapped Zane Benefits to $4+ million in annual revenue in 2013/2014</li><li>After a regulatory threat in 2013, launched a new business called PeopleKeep<ul><li>Raised ~$3M in venture capital to finance this</li></ul></li><li><a href="https://www.ricklindquist.com/books">Wrote a book</a> in 2014 which was published by Wiley</li><li>Merged Zane Benefits with PeopleKeep after confirming the legality of PeopleKeep’s approach and reaching product market fit in 2018. Milestones included:<ul><li>$120K in monthly recurring revenue (MRR)</li><li>Profitable unit economics</li><li>50+ user NPS</li><li>Low churn for very small business segment</li><li>Numerous customer growth and product expansion opportunities</li></ul></li><li>Was <a href="https://www.ricklindquist.com/blog/im-no-longer-the-ceo-of-peoplekeep">fired by the board in October 2018</a> when unable to align on long term compensation</li><li>Founded <a href="http://legupventures.com/">LegUp Ventures</a> in May 2019, which owns and operates companies that empower underdogs. Current ventures include:<ul><li><a href="http://groupcurrent.com/">GroupCurrent</a>, which helps member-based groups reach sustainability</li><li><a href="https://www.ricklindquist.com/">RickLindquist.com</a>, where Rick writes and consults on various topics</li><li>Startup to Last, this podcast</li></ul></li><li>Likes:<ul><li>Physical fitness</li><li>Continuous improvement</li><li>Sustainability (i.e. balance)</li></ul></li><li>Dislikes:<ul><li>Bullies</li><li>Victim playing</li><li>Intellectual laziness</li></ul></li></ul><p><strong><br>Entrepreneurial beginnings<br></strong><br></p><p><strong>Tyler:</strong> Can you just kind of give a little background on how you got into the startup space, entrepreneurship in general?</p><p><strong>Rick:</strong> Well, I guess I do kind of have that story of always being a little entrepreneurial. I had lemonade stands.</p><p><br></p><p><strong>Tyler:</strong> You did? At what age was your very first venture?</p><p><strong>Rick:</strong> Four or five. Yeah, I did the lemonade stands. I took it very seriously. I mowed grass. I tried a lot of different things. I always thought about it. I read business books when I was in high school, entrepreneurial books. I always knew that was what I wanted to do, but I didn't know what my path was. I thought it was something that ... The story I like to tell is, my dad is a lawyer, which is kind of a sole proprietorship in a way. You're a partner in a law firm and you do actually have to produce for yourself. And then my grandfather owned an ACE Hardware store, True Value Hardware store. So I witnessed a lot of entrepreneurship growing up, but my dad always hated his job. He's a litigator and he always had to fight with people for a living. So I was really scared to go to start working because I thought I'd hate my life. I thought that's what everyone did. So I was born in North Carolina. My parents got a divorce at a young age. So I moved all around North Carolina. I think I lived in, like, 17 different houses. I never had that one house. In fact, living in Utah, the Park City area, that's the longest time I've ever lived anywhere. </p><p><strong><br>College and major<br></strong><br></p><p><strong>Rick: </strong>And so anyway, I ended up going to Duke for college. I graduated in 2007 and had no idea what I wanted to do.</p><p><strong>Tyler: </strong>Well, let me stop you for a second. So what did you major in?</p><p><strong>Rick:</strong> Economics and computer science.</p><p><strong>Tyler:</strong> So you had an entrepreneurial spirit before college. Did that inform what you majored in or anything like that?</p><p><strong>Rick:</strong> Yeah. One thing that I think you'll learn about me is, I'm generally open to anything but, once I form an opinion about it, I form a pretty strong opinion about it. So I actually did not declare a major until the end of sophomore year. I took just about every 101 course at Duke, including political science and I dropped that class midway through and had a really big blowup with the professor. I hate political science classes. They're too political.</p><p><strong>Tyler:</strong> Who would've thought?</p><p><strong>Rick:</strong> Yeah. Who would've thought? So I knew that I was interested in economics. I knew that I was interested in computer science. So those were my first two if I had declared freshman year, but I wanted to see what was out there. And then they were the most practical. One was learning about how money works and the other ... and people work and markets work, and the other was how to build things, I thought. And then I realized, computer science is actually a bunch of theory and bullshit. And I think I had two programming classes and they were my favorite classes at Duke.</p><p><strong>Tyler:</strong> Yeah. I mean, all college professors are theorists, right? So in a sense, every major is theory.</p><p><strong>Rick:</strong> Yeah.</p><p><strong>Tyler:</strong> Anyway.</p><p><strong>Rick:</strong> Yeah. So I did a lot in college. I wrestled. I was in a frat. It was an atypical frat, but still a frat. I did student government. I did a lot of different stuff. By the time I graduated, I was pretty burnt out and so I remember everyone just doing investment banking interviews and I went through a couple of those and I was like, "I cannot do this. I could not move to New York and work with these guys. I need a break." So I decided to move out to Park City to ski bum. Called my dad. He basically said, "That's cool, as long as you're off the payroll." I think he gave me until July to move out and I basically just came out here expecting to ski bum. Unlike you, who came for a job.</p><p><br></p><p><strong>Ski bumming to startup<br></strong><br></p><p><strong>Tyler:</strong> A job. I never heard of Park City, nor had I ever skied before. But you knew what you wanted to do here.</p><p><strong>Rick: </strong>Yeah. So my grandfather bought a condo out of bankruptcy in the '80s with an ownership group. So we always came out here for a week to ski. So I was very familiar with the area and I always heard my dad and my grandfather and people talking, like, "I wish I had taken a year off to go ski bumming." So I called them out on that and I took advantage of it. But I got out here, I'd carpet clean in the mornings for a carpet cleaning company locally and then I was a bellman at a hotel called Park City Hotel. And then sometime in November ... I got here in July, and sometime maybe in November that year, I met a headhunter who was recruiting for this startup called Zane Benefits. They had just raised a $3 million series A. And I was driving this person around or it was something like, "What are you doing? You have a Duke degree and you're carpet cleaning and driving people around?" I said, "Yeah. I'm serious about ski bumming." So anyway, I ended up taking a job there because I got really interested in the problem. And I came on as an entry level sales rep and that was my first professional, what I would call my first professional job.</p><p><strong>Tyler: </strong>Because you didn't do internships or anything like that, right?</p><p><strong>Rick:</strong> My internship ... So one summer,...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here’s what you should know about Rick:</p><ul><li>Born in Raleigh, NC and grew up in Morganton and Charlotte, NC</li><li>Went to college at Duke University</li><li>Majored in Economics and Computer Science</li><li>Wrestled at Duke</li><li>Moved to Park City to Ski bum in after graduation</li><li>Met Tyler at a startup called Zane Benefits (which is now part of <a href="http://www.peoplekeep.com/">PeopleKeep</a>) in 2007</li><li>Became the President of Zane Benefits after a mass layoff in 2008</li><li>Bootstrapped Zane Benefits to $4+ million in annual revenue in 2013/2014</li><li>After a regulatory threat in 2013, launched a new business called PeopleKeep<ul><li>Raised ~$3M in venture capital to finance this</li></ul></li><li><a href="https://www.ricklindquist.com/books">Wrote a book</a> in 2014 which was published by Wiley</li><li>Merged Zane Benefits with PeopleKeep after confirming the legality of PeopleKeep’s approach and reaching product market fit in 2018. Milestones included:<ul><li>$120K in monthly recurring revenue (MRR)</li><li>Profitable unit economics</li><li>50+ user NPS</li><li>Low churn for very small business segment</li><li>Numerous customer growth and product expansion opportunities</li></ul></li><li>Was <a href="https://www.ricklindquist.com/blog/im-no-longer-the-ceo-of-peoplekeep">fired by the board in October 2018</a> when unable to align on long term compensation</li><li>Founded <a href="http://legupventures.com/">LegUp Ventures</a> in May 2019, which owns and operates companies that empower underdogs. Current ventures include:<ul><li><a href="http://groupcurrent.com/">GroupCurrent</a>, which helps member-based groups reach sustainability</li><li><a href="https://www.ricklindquist.com/">RickLindquist.com</a>, where Rick writes and consults on various topics</li><li>Startup to Last, this podcast</li></ul></li><li>Likes:<ul><li>Physical fitness</li><li>Continuous improvement</li><li>Sustainability (i.e. balance)</li></ul></li><li>Dislikes:<ul><li>Bullies</li><li>Victim playing</li><li>Intellectual laziness</li></ul></li></ul><p><strong><br>Entrepreneurial beginnings<br></strong><br></p><p><strong>Tyler:</strong> Can you just kind of give a little background on how you got into the startup space, entrepreneurship in general?</p><p><strong>Rick:</strong> Well, I guess I do kind of have that story of always being a little entrepreneurial. I had lemonade stands.</p><p><br></p><p><strong>Tyler:</strong> You did? At what age was your very first venture?</p><p><strong>Rick:</strong> Four or five. Yeah, I did the lemonade stands. I took it very seriously. I mowed grass. I tried a lot of different things. I always thought about it. I read business books when I was in high school, entrepreneurial books. I always knew that was what I wanted to do, but I didn't know what my path was. I thought it was something that ... The story I like to tell is, my dad is a lawyer, which is kind of a sole proprietorship in a way. You're a partner in a law firm and you do actually have to produce for yourself. And then my grandfather owned an ACE Hardware store, True Value Hardware store. So I witnessed a lot of entrepreneurship growing up, but my dad always hated his job. He's a litigator and he always had to fight with people for a living. So I was really scared to go to start working because I thought I'd hate my life. I thought that's what everyone did. So I was born in North Carolina. My parents got a divorce at a young age. So I moved all around North Carolina. I think I lived in, like, 17 different houses. I never had that one house. In fact, living in Utah, the Park City area, that's the longest time I've ever lived anywhere. </p><p><strong><br>College and major<br></strong><br></p><p><strong>Rick: </strong>And so anyway, I ended up going to Duke for college. I graduated in 2007 and had no idea what I wanted to do.</p><p><strong>Tyler: </strong>Well, let me stop you for a second. So what did you major in?</p><p><strong>Rick:</strong> Economics and computer science.</p><p><strong>Tyler:</strong> So you had an entrepreneurial spirit before college. Did that inform what you majored in or anything like that?</p><p><strong>Rick:</strong> Yeah. One thing that I think you'll learn about me is, I'm generally open to anything but, once I form an opinion about it, I form a pretty strong opinion about it. So I actually did not declare a major until the end of sophomore year. I took just about every 101 course at Duke, including political science and I dropped that class midway through and had a really big blowup with the professor. I hate political science classes. They're too political.</p><p><strong>Tyler:</strong> Who would've thought?</p><p><strong>Rick:</strong> Yeah. Who would've thought? So I knew that I was interested in economics. I knew that I was interested in computer science. So those were my first two if I had declared freshman year, but I wanted to see what was out there. And then they were the most practical. One was learning about how money works and the other ... and people work and markets work, and the other was how to build things, I thought. And then I realized, computer science is actually a bunch of theory and bullshit. And I think I had two programming classes and they were my favorite classes at Duke.</p><p><strong>Tyler:</strong> Yeah. I mean, all college professors are theorists, right? So in a sense, every major is theory.</p><p><strong>Rick:</strong> Yeah.</p><p><strong>Tyler:</strong> Anyway.</p><p><strong>Rick:</strong> Yeah. So I did a lot in college. I wrestled. I was in a frat. It was an atypical frat, but still a frat. I did student government. I did a lot of different stuff. By the time I graduated, I was pretty burnt out and so I remember everyone just doing investment banking interviews and I went through a couple of those and I was like, "I cannot do this. I could not move to New York and work with these guys. I need a break." So I decided to move out to Park City to ski bum. Called my dad. He basically said, "That's cool, as long as you're off the payroll." I think he gave me until July to move out and I basically just came out here expecting to ski bum. Unlike you, who came for a job.</p><p><br></p><p><strong>Ski bumming to startup<br></strong><br></p><p><strong>Tyler:</strong> A job. I never heard of Park City, nor had I ever skied before. But you knew what you wanted to do here.</p><p><strong>Rick: </strong>Yeah. So my grandfather bought a condo out of bankruptcy in the '80s with an ownership group. So we always came out here for a week to ski. So I was very familiar with the area and I always heard my dad and my grandfather and people talking, like, "I wish I had taken a year off to go ski bumming." So I called them out on that and I took advantage of it. But I got out here, I'd carpet clean in the mornings for a carpet cleaning company locally and then I was a bellman at a hotel called Park City Hotel. And then sometime in November ... I got here in July, and sometime maybe in November that year, I met a headhunter who was recruiting for this startup called Zane Benefits. They had just raised a $3 million series A. And I was driving this person around or it was something like, "What are you doing? You have a Duke degree and you're carpet cleaning and driving people around?" I said, "Yeah. I'm serious about ski bumming." So anyway, I ended up taking a job there because I got really interested in the problem. And I came on as an entry level sales rep and that was my first professional, what I would call my first professional job.</p><p><strong>Tyler: </strong>Because you didn't do internships or anything like that, right?</p><p><strong>Rick:</strong> My internship ... So one summer,...</p>]]>
      </content:encoded>
      <pubDate>Thu, 03 Oct 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/0a561c95/c2123cf5.mp3" length="33803441" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2079</itunes:duration>
      <itunes:summary>This week we're mixing the format up a bit. Instead of doing a deep dive on a specific topic, Tyler interviews Rick to learn about how he went from an entry level salesperson to the CEO of a startup that grew to over 50 employees, and what he's doing now to start his next venture.</itunes:summary>
      <itunes:subtitle>This week we're mixing the format up a bit. Instead of doing a deep dive on a specific topic, Tyler interviews Rick to learn about how he went from an entry level salesperson to the CEO of a startup that grew to over 50 employees, and what he's doing now </itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Why we started this podcast</title>
      <itunes:title>Why we started this podcast</itunes:title>
      <itunes:episodeType>bonus</itunes:episodeType>
      <guid isPermaLink="false">50a7f8df-3ff1-47e6-ad5f-60b8a4819101</guid>
      <link>https://share.transistor.fm/s/2572fa01</link>
      <description>
        <![CDATA[In this short bonus episode, we talk a bit about why we started this podcast and what we hope our listeners can get out of it]]>
      </description>
      <content:encoded>
        <![CDATA[In this short bonus episode, we talk a bit about why we started this podcast and what we hope our listeners can get out of it]]>
      </content:encoded>
      <pubDate>Sun, 29 Sep 2019 12:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/2572fa01/2011910d.mp3" length="6860258" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>410</itunes:duration>
      <itunes:summary>In this short bonus episode, we talk a bit about why we started this podcast and what we hope our listeners can get out of it</itunes:summary>
      <itunes:subtitle>In this short bonus episode, we talk a bit about why we started this podcast and what we hope our listeners can get out of it</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>How to recruit interns</title>
      <itunes:episode>11</itunes:episode>
      <podcast:episode>11</podcast:episode>
      <itunes:title>How to recruit interns</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f8c5140a-0512-47e1-a34e-3b7a9743790c</guid>
      <link>https://share.transistor.fm/s/ff6c12c0</link>
      <description>
        <![CDATA[<p>This episode ended up being much more about how to increase workforce diversity than how to hire interns. Here’s a quick rundown: </p><ul><li>Tyler and his team at Less Annoying CRM want to increase diversity</li><li>They primarily source candidates via their summer internship program</li><li>Tyler and his team have had great success at WashU with this model</li><li>However, this has led to a lack of diversity across his 17 employees (~50% went to WashU)</li><li>Tyler wants more internships to come from schools other than WashU</li><li>Despite effort, Tyler has not been able to replicate the internship funnel at other schools in Missouri<ul><li>E.g. He’s tried recruiting via career fairs, by connecting with professors, and by partnering with student groups</li></ul></li><li>Tyler pointed out that WashU is successful is due to the numerous former WashU graduate success stories that currently work or formerly worked at Less Annoying CRM<ul><li>I.e. They have product-market fit at WashU for their internship offering</li></ul></li><li>However, at other schools, they can’t even get students to apply<ul><li>I.e. They don’t know if they have the right internship offering yet</li></ul></li><li>Rick recommended Tyler focus on customer development to learn more about what the students at these other colleges are looking for</li><li>Tyler realized that creating diversity is really hard, and focusing on small wins initially is key</li></ul><p>Takeaways include: </p><ul><li>Internships provide a safe way to hire because they allow you to work with someone temporarily before you extend a full-time offer</li><li>Summer internships, by their nature, discriminate in favor of privilege</li><li>Private schools have a culture that encourages summer internships; Public schools don’t seem to have this same focus.</li><li>One challenge is that college students, privileged or not, are not very responsive</li><li>When working to increase diversity, focusing on small wins up front is key. Once you get your foot in the door with a new segment, it gets much easier from there.</li></ul><p><strong><br>The problem<br></strong><br></p><p><strong>Tyler: </strong>All right, let's dive into the topic for today. So this one is mine. So basically we're going to talk about how to recruit interns. And I can give a little background on where I'm coming from with this topic. Basically at <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>, so we have 17 employees, but we've hired significantly more than that in total because every summer we have about 10-ish interns, or coding fellows, which coding fellows and interns are about the same thing here. </p><p><br></p><p><strong>Tyler: </strong>Basically college students who come for the summer. We've had a lot of success with this. It makes hiring really easy because you get to take risks on people kind of and bring in a bunch of people. And then if someone's really a perfect fit, give them a full-time offer to work here after they graduate. So have had a lot of success with that. Really enjoy it. And I kind of have a system worked out, which maybe one thing we should talk about today is just what's currently working. Like Rick, you went to Duke, I went to WashU. That type of place has an intern culture. Students are planning on applying for these, it's expected. Other universities in the area don't have that culture. And we've struggled to get students interested in it, which is kind of counter intuitive because they're schools where the fact that they're paid internships and it's a really great opportunity. You'd think it'd be even more appealing to someone who's not going to as top tier of a school. But the reality is we really struggle to get anyone from those other schools even to apply. So the results-</p><p><br></p><p><strong>Rick: </strong>Sorry, what are they doing instead?</p><p><strong>Tyler: </strong>Yeah, it's a combination of things. Part of it is a lot of these schools, people aren't full-time students as much and so they're not off for the summer in the same way. So that's one challenge. And then the other thing is, I think if you're going to a $60,000 a year private university, probably you come from wealth and probably you kind of have options. And you're like, "I'm going to dabble and try different things and see where my life takes me." If you're going to, for example, the local public university, UMSL, University of Missouri-St. Louis, still a good school. But if you go there probably you're like, "I need a job out of this." And you're majoring in whatever you're majoring in and you're not looking for random other opportunities that aren't specifically in your field.</p><p><strong>Rick: </strong>Sorry, I interrupted you when you were describing the problem. I'll let you finish that.</p><p><strong><br>A lack of diversity, starting with interns<br></strong><br></p><p><strong>Tyler: </strong>Yeah. Okay. Sorry, I'm rambling here. I'm basically done. But basically we have a model that works for hiring interns at WashU. We don't have a model that works elsewhere and the result of this is our employee base lacks diversity in any number of ways. First of all, there's kind of socioeconomic diversity of only rich kids go to WashU. And then also WashU has its own diversity problems in terms of race, in terms of gender, at least on the technical side. So we're not getting a very diverse applicant pool because of the way we're recruiting interns. So I'm interested in discussing how can we go out and attract interns from other universities that maybe don't have that strong of an intern culture.</p><p><strong>Rick: </strong>Got it. So diversify your interns?</p><p><strong>Tyler: </strong>Yes. Exactly.</p><p><strong>Rick: </strong>The problem is you lack diversity with your interns, you've been trying to increase that, you haven't been able to for a number of different reasons, which we'll probably go into later. I'm very interested in what you're... I think you're right. I think it should start with how you do interns. What the intern period is, what you're paying, what you're offering and what's going well so far with those.</p><p><strong><br>How Less Annoying CRM does internships<br></strong><br></p><p><strong>Tyler: </strong>Cool. Okay. So the history here, so a lot of people probably haven't heard of WashU, but in terms of price and difficulty to get into, it's kind of like a top 15 top 20 university. Lots of rich kids, people with high test scores, right?</p><p><strong>Rick:</strong> It's the best school that no one knows about.</p><p><strong>Tyler:</strong> Yeah, it's probably there. It's on par with the Northwestern. Except you've heard of Northwestern and you haven't heard it WashU.</p><p><strong>Rick: </strong>Exactly. I remember when one of my buddies in high school got into WashU and he was so excited. He was running around. This is a Charlotte private high school. He's running running around the halls going, "I got into WashU, I got in WashU." Everybody's like, "What is WashU? The University of Washington? You're going to go the West Coast?"</p><p><strong>Tyler: </strong>Or George Washington.</p><p><strong>Rick:</strong> "What are you talking about?"</p><p><strong>Tyler:</strong> Yeah, so no one's heard of it, but it's a pretty good school, which comes with all the downsides of good schools. So I did what every first time entrepreneur does, which is the first time I had to hire people, I was like, "I don't know. I'm going to go back to the school I went to. And I already know people there and I'm going to start recruiting." And it was pretty easy. Basically we posted on there, every university has a free job board and any employer can sign up and post there. We went to the career fair. People walk by, we g...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>This episode ended up being much more about how to increase workforce diversity than how to hire interns. Here’s a quick rundown: </p><ul><li>Tyler and his team at Less Annoying CRM want to increase diversity</li><li>They primarily source candidates via their summer internship program</li><li>Tyler and his team have had great success at WashU with this model</li><li>However, this has led to a lack of diversity across his 17 employees (~50% went to WashU)</li><li>Tyler wants more internships to come from schools other than WashU</li><li>Despite effort, Tyler has not been able to replicate the internship funnel at other schools in Missouri<ul><li>E.g. He’s tried recruiting via career fairs, by connecting with professors, and by partnering with student groups</li></ul></li><li>Tyler pointed out that WashU is successful is due to the numerous former WashU graduate success stories that currently work or formerly worked at Less Annoying CRM<ul><li>I.e. They have product-market fit at WashU for their internship offering</li></ul></li><li>However, at other schools, they can’t even get students to apply<ul><li>I.e. They don’t know if they have the right internship offering yet</li></ul></li><li>Rick recommended Tyler focus on customer development to learn more about what the students at these other colleges are looking for</li><li>Tyler realized that creating diversity is really hard, and focusing on small wins initially is key</li></ul><p>Takeaways include: </p><ul><li>Internships provide a safe way to hire because they allow you to work with someone temporarily before you extend a full-time offer</li><li>Summer internships, by their nature, discriminate in favor of privilege</li><li>Private schools have a culture that encourages summer internships; Public schools don’t seem to have this same focus.</li><li>One challenge is that college students, privileged or not, are not very responsive</li><li>When working to increase diversity, focusing on small wins up front is key. Once you get your foot in the door with a new segment, it gets much easier from there.</li></ul><p><strong><br>The problem<br></strong><br></p><p><strong>Tyler: </strong>All right, let's dive into the topic for today. So this one is mine. So basically we're going to talk about how to recruit interns. And I can give a little background on where I'm coming from with this topic. Basically at <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>, so we have 17 employees, but we've hired significantly more than that in total because every summer we have about 10-ish interns, or coding fellows, which coding fellows and interns are about the same thing here. </p><p><br></p><p><strong>Tyler: </strong>Basically college students who come for the summer. We've had a lot of success with this. It makes hiring really easy because you get to take risks on people kind of and bring in a bunch of people. And then if someone's really a perfect fit, give them a full-time offer to work here after they graduate. So have had a lot of success with that. Really enjoy it. And I kind of have a system worked out, which maybe one thing we should talk about today is just what's currently working. Like Rick, you went to Duke, I went to WashU. That type of place has an intern culture. Students are planning on applying for these, it's expected. Other universities in the area don't have that culture. And we've struggled to get students interested in it, which is kind of counter intuitive because they're schools where the fact that they're paid internships and it's a really great opportunity. You'd think it'd be even more appealing to someone who's not going to as top tier of a school. But the reality is we really struggle to get anyone from those other schools even to apply. So the results-</p><p><br></p><p><strong>Rick: </strong>Sorry, what are they doing instead?</p><p><strong>Tyler: </strong>Yeah, it's a combination of things. Part of it is a lot of these schools, people aren't full-time students as much and so they're not off for the summer in the same way. So that's one challenge. And then the other thing is, I think if you're going to a $60,000 a year private university, probably you come from wealth and probably you kind of have options. And you're like, "I'm going to dabble and try different things and see where my life takes me." If you're going to, for example, the local public university, UMSL, University of Missouri-St. Louis, still a good school. But if you go there probably you're like, "I need a job out of this." And you're majoring in whatever you're majoring in and you're not looking for random other opportunities that aren't specifically in your field.</p><p><strong>Rick: </strong>Sorry, I interrupted you when you were describing the problem. I'll let you finish that.</p><p><strong><br>A lack of diversity, starting with interns<br></strong><br></p><p><strong>Tyler: </strong>Yeah. Okay. Sorry, I'm rambling here. I'm basically done. But basically we have a model that works for hiring interns at WashU. We don't have a model that works elsewhere and the result of this is our employee base lacks diversity in any number of ways. First of all, there's kind of socioeconomic diversity of only rich kids go to WashU. And then also WashU has its own diversity problems in terms of race, in terms of gender, at least on the technical side. So we're not getting a very diverse applicant pool because of the way we're recruiting interns. So I'm interested in discussing how can we go out and attract interns from other universities that maybe don't have that strong of an intern culture.</p><p><strong>Rick: </strong>Got it. So diversify your interns?</p><p><strong>Tyler: </strong>Yes. Exactly.</p><p><strong>Rick: </strong>The problem is you lack diversity with your interns, you've been trying to increase that, you haven't been able to for a number of different reasons, which we'll probably go into later. I'm very interested in what you're... I think you're right. I think it should start with how you do interns. What the intern period is, what you're paying, what you're offering and what's going well so far with those.</p><p><strong><br>How Less Annoying CRM does internships<br></strong><br></p><p><strong>Tyler: </strong>Cool. Okay. So the history here, so a lot of people probably haven't heard of WashU, but in terms of price and difficulty to get into, it's kind of like a top 15 top 20 university. Lots of rich kids, people with high test scores, right?</p><p><strong>Rick:</strong> It's the best school that no one knows about.</p><p><strong>Tyler:</strong> Yeah, it's probably there. It's on par with the Northwestern. Except you've heard of Northwestern and you haven't heard it WashU.</p><p><strong>Rick: </strong>Exactly. I remember when one of my buddies in high school got into WashU and he was so excited. He was running around. This is a Charlotte private high school. He's running running around the halls going, "I got into WashU, I got in WashU." Everybody's like, "What is WashU? The University of Washington? You're going to go the West Coast?"</p><p><strong>Tyler: </strong>Or George Washington.</p><p><strong>Rick:</strong> "What are you talking about?"</p><p><strong>Tyler:</strong> Yeah, so no one's heard of it, but it's a pretty good school, which comes with all the downsides of good schools. So I did what every first time entrepreneur does, which is the first time I had to hire people, I was like, "I don't know. I'm going to go back to the school I went to. And I already know people there and I'm going to start recruiting." And it was pretty easy. Basically we posted on there, every university has a free job board and any employer can sign up and post there. We went to the career fair. People walk by, we g...</p>]]>
      </content:encoded>
      <pubDate>Thu, 26 Sep 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/ff6c12c0/00ee02de.mp3" length="51616695" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3036</itunes:duration>
      <itunes:summary>This week, we discuss how to recruit interns, especially from non-traditional backgrounds.</itunes:summary>
      <itunes:subtitle>This week, we discuss how to recruit interns, especially from non-traditional backgrounds.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Interview with Tyler King, co-founder and CEO of Less Annoying CRM</title>
      <itunes:episode>10</itunes:episode>
      <podcast:episode>10</podcast:episode>
      <itunes:title>Interview with Tyler King, co-founder and CEO of Less Annoying CRM</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">edd0c670-bdeb-42cd-afcf-bc0ba9326d0d</guid>
      <link>https://share.transistor.fm/s/faa1aeb4</link>
      <description>
        <![CDATA[<p>Here’s what you should know about Tyler:</p><ul><li>Grew up in St. Louis, Missouri</li><li>Went to college at Washington University in St. Louis (“Wash U.”)</li><li>Majored in Computer Science</li><li>Became a web developer through side projects and internships</li><li>Played guitar in a heavy metal band called Embers Rise (<a href="https://www.startuptolast.com/topics/interview-with-tyler-king-co-founder-and-ceo-of-less-annoying-crm#Embers">listen here</a>)</li><li>Left his Masters program early to join a startup called Zane Benefits (which is now part of <a href="https://peoplekeep.com/">PeopleKeep</a>) in Park City, Utah  </li><li>Met Rick at Zane Benefits in 2007</li><li>Survived a lay-off with Rick in October 2008 and became head of product</li><li>Worked with Rick to pivot the business model to get to cash flow positive<ul><li>Zane Benefits provided a software-enabled service to small businesses that allowed a company to reimburse its employees for individual health insurance tax-free</li></ul></li><li>Had no interest at all in entrepreneurship prior to Zane Benefits</li><li>Got frustrated having the responsibility to lead Zane Benefits without the power to make key decisions (i.e. “board decisions”)</li><li>Founded what is now <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a> in 2009 with his brother <a href="https://www.linkedin.com/in/brackenking/">Bracken King</a></li><li>Less Annoying CRM is a simple customer relationship (CRM) tool for small business people</li><li>Got the idea from working with insurance agents and Salesforce at Zane Benefits</li><li>Less Annoying CRM is 100% self-funded and bootstrapped<ul><li>Launched the product at the beginning of 2010</li><li>At the beginning of 2011, hit  50 users / $6,000 in annual recurring revenue (ARR)</li><li>At the beginning of 2012, hit 500 users / $60,000 in ARR</li><li>As of the recording of this episode, at 22,000 users /  $2.6 million ARR growing at ~20% per year. </li></ul></li><li>Wants to run Less Annoying CRM for the rest of his life</li><li>Unique perspectives<ul><li>Fan of bootstrapping</li><li>Thinks raising venture capital is limiting for a company</li><li>Thinks more founders should look to run companies for life versus selling</li></ul></li></ul><p><strong><br>Where were you born?<br></strong><br></p><p><strong>Tyler: </strong>Cool. So, Rick, you are interviewing me today. Where would you like to start?</p><p><strong>Rick: </strong>I'd like to start at your birth.</p><p><strong>Tyler:</strong> Ah. Tucson, Arizona is a hot, dry-</p><p><strong>Rick: </strong>Were you really?</p><p><br></p><p><strong>Tyler:</strong> Yes.</p><p><strong>Rick: </strong>Oh, I didn't know that.</p><p><strong>Tyler: </strong>Yeah. I was there for like a year.</p><p><strong>Rick: </strong>Yeah. Tell me your personal story.</p><p><strong>Tyler:</strong> My personal story. So yeah. I grew up in St. Louis, moved there when I was one, and basically, I'll focus specifically on how I got to the startup world, right?</p><p><strong>Rick: </strong>Mm-hmm (affirmative).</p><p><strong><br>College and major</strong></p><p><br></p><p><strong>Tyler: </strong>I had no interest in it at all. I think everyone wants to have that, "Oh, I was selling lemonade when I was a kid. I was a hustler." I didn't have anything like that. </p><p><strong>Rick: </strong>What year?</p><p><strong>Tyler: </strong>Well, they forced me to take a computer science class my freshman year just to meet the requirements for electrical engineering. I went to my advisor and I was like, "I promise you I will never code. I hate computers. Don't make me take this class. It's a complete waste of time." My advisor was like, "No, you have to take it." I took it and I just loved it. So I didn't switch freshman year, but that was really the start right away. And then I worked as a student web developer for the business school that summer and then did internships and stuff. I didn't particularly love classes, but I loved the process outside of school, like building personal websites. I was in bands and I made a message board for a heavy metal band, Embers Rise, just fun projects.</p><p><br></p><p><strong>Rick:</strong> Where can I find a copy or a streaming song of Embers Rise?</p><p><strong>Tyler: </strong>Embers Rise. I think there's another band called Embers Rise now, so if you Google it, you'll find a band. But it's not mine. My Dropbox is the only place to find recordings.</p><p><strong>Rick: </strong>I'm going to have to find one of those and publish it on StartupToLast.com.</p><p><br></p><p><br></p><p><strong>Tyler: </strong>We'll see if that happens or not. But yeah. So I was more of a hobbyist. Even though I was majoring in computer science, I was never good at the academic side of it. But I was kind of a hobbyist, and that's where I really developed a passion for building software.</p><p><br></p><p><strong>Working at Startup in 2007<br></strong><br></p><p><strong>Rick: </strong>So what happened after college?</p><p><strong>Tyler: </strong>This is when I met you, as you know. So I was actually supposed to do a fifth year. I was in a bachelor's/master's program, and during the fifth year, a friend from high school, <a href="https://www.linkedin.com/in/tomelgin/">Tom Elgin</a>, reached out to me and was like, "Hey, I live in this place called Park City, Utah," which I'd never heard of before. It's a ski town in Utah. "And there's this startup here that's like about to go... It's about to explode. It's about to be hugely successful." I actually at the time, because I wasn't good at school... I mean, I wasn't terrible, but I was a B-minus student. I didn't have a lot of confidence in my professional capabilities, and I thought, "This might be the only chance I have in my whole life to just ride other people's coattails success." So I wouldn't say exactly dropped out. I ended up getting my bachelor's because I had finished the requirements for it, but I left school in the middle of the semester, drove to Utah, and started working at this tech startup called Zane Benefits.</p><p><br></p><p><strong>Rick: </strong>What year is this?</p><p><strong>Tyler: </strong>This was 2007, which, for people who were around back then, was an interesting year to enter the workforce because for that first year things were pretty normal. You joined at the same time. For the first year at this company, it was a normal venture-backed startup. They just raised... What is it? A series A or a seed or something.</p><p><strong>Rick:</strong> They call it a series A. Three million dollars.</p><p><strong><br>Leading a startup from 2008 to 2009<br></strong><br></p><p><strong>Tyler: </strong>Yeah. So I was just like an entry-level programmer. I had bosses, and I was just learning the normal corporate world. And then I assume we'll talk about this when I interview you as well, but 2008 hit and global recession and all that. I don't know the whole... You know the whole story a lot better than I do, but basically, 20 out of 25 people or something like that got laid off at the company. Both of us were lucky enough to be survivors of those layoffs. I tell every person we hire, everyone who wants to really know my story on entrepreneurship, this was the defining moment because we showed up the next day to work and there was... Our bosses had been fired, right? The CEO fired himself. So we just showed up and we're like, "Well, I guess we're in charge of the company now." I don't know if... Did we realize that at the time?</p><p><strong>Rick: </strong>Oh yeah.</p><p><strong>Tyler:</strong> Yeah. We were just like, "Nobody else here is going to care enough t...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Here’s what you should know about Tyler:</p><ul><li>Grew up in St. Louis, Missouri</li><li>Went to college at Washington University in St. Louis (“Wash U.”)</li><li>Majored in Computer Science</li><li>Became a web developer through side projects and internships</li><li>Played guitar in a heavy metal band called Embers Rise (<a href="https://www.startuptolast.com/topics/interview-with-tyler-king-co-founder-and-ceo-of-less-annoying-crm#Embers">listen here</a>)</li><li>Left his Masters program early to join a startup called Zane Benefits (which is now part of <a href="https://peoplekeep.com/">PeopleKeep</a>) in Park City, Utah  </li><li>Met Rick at Zane Benefits in 2007</li><li>Survived a lay-off with Rick in October 2008 and became head of product</li><li>Worked with Rick to pivot the business model to get to cash flow positive<ul><li>Zane Benefits provided a software-enabled service to small businesses that allowed a company to reimburse its employees for individual health insurance tax-free</li></ul></li><li>Had no interest at all in entrepreneurship prior to Zane Benefits</li><li>Got frustrated having the responsibility to lead Zane Benefits without the power to make key decisions (i.e. “board decisions”)</li><li>Founded what is now <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a> in 2009 with his brother <a href="https://www.linkedin.com/in/brackenking/">Bracken King</a></li><li>Less Annoying CRM is a simple customer relationship (CRM) tool for small business people</li><li>Got the idea from working with insurance agents and Salesforce at Zane Benefits</li><li>Less Annoying CRM is 100% self-funded and bootstrapped<ul><li>Launched the product at the beginning of 2010</li><li>At the beginning of 2011, hit  50 users / $6,000 in annual recurring revenue (ARR)</li><li>At the beginning of 2012, hit 500 users / $60,000 in ARR</li><li>As of the recording of this episode, at 22,000 users /  $2.6 million ARR growing at ~20% per year. </li></ul></li><li>Wants to run Less Annoying CRM for the rest of his life</li><li>Unique perspectives<ul><li>Fan of bootstrapping</li><li>Thinks raising venture capital is limiting for a company</li><li>Thinks more founders should look to run companies for life versus selling</li></ul></li></ul><p><strong><br>Where were you born?<br></strong><br></p><p><strong>Tyler: </strong>Cool. So, Rick, you are interviewing me today. Where would you like to start?</p><p><strong>Rick: </strong>I'd like to start at your birth.</p><p><strong>Tyler:</strong> Ah. Tucson, Arizona is a hot, dry-</p><p><strong>Rick: </strong>Were you really?</p><p><br></p><p><strong>Tyler:</strong> Yes.</p><p><strong>Rick: </strong>Oh, I didn't know that.</p><p><strong>Tyler: </strong>Yeah. I was there for like a year.</p><p><strong>Rick: </strong>Yeah. Tell me your personal story.</p><p><strong>Tyler:</strong> My personal story. So yeah. I grew up in St. Louis, moved there when I was one, and basically, I'll focus specifically on how I got to the startup world, right?</p><p><strong>Rick: </strong>Mm-hmm (affirmative).</p><p><strong><br>College and major</strong></p><p><br></p><p><strong>Tyler: </strong>I had no interest in it at all. I think everyone wants to have that, "Oh, I was selling lemonade when I was a kid. I was a hustler." I didn't have anything like that. </p><p><strong>Rick: </strong>What year?</p><p><strong>Tyler: </strong>Well, they forced me to take a computer science class my freshman year just to meet the requirements for electrical engineering. I went to my advisor and I was like, "I promise you I will never code. I hate computers. Don't make me take this class. It's a complete waste of time." My advisor was like, "No, you have to take it." I took it and I just loved it. So I didn't switch freshman year, but that was really the start right away. And then I worked as a student web developer for the business school that summer and then did internships and stuff. I didn't particularly love classes, but I loved the process outside of school, like building personal websites. I was in bands and I made a message board for a heavy metal band, Embers Rise, just fun projects.</p><p><br></p><p><strong>Rick:</strong> Where can I find a copy or a streaming song of Embers Rise?</p><p><strong>Tyler: </strong>Embers Rise. I think there's another band called Embers Rise now, so if you Google it, you'll find a band. But it's not mine. My Dropbox is the only place to find recordings.</p><p><strong>Rick: </strong>I'm going to have to find one of those and publish it on StartupToLast.com.</p><p><br></p><p><br></p><p><strong>Tyler: </strong>We'll see if that happens or not. But yeah. So I was more of a hobbyist. Even though I was majoring in computer science, I was never good at the academic side of it. But I was kind of a hobbyist, and that's where I really developed a passion for building software.</p><p><br></p><p><strong>Working at Startup in 2007<br></strong><br></p><p><strong>Rick: </strong>So what happened after college?</p><p><strong>Tyler: </strong>This is when I met you, as you know. So I was actually supposed to do a fifth year. I was in a bachelor's/master's program, and during the fifth year, a friend from high school, <a href="https://www.linkedin.com/in/tomelgin/">Tom Elgin</a>, reached out to me and was like, "Hey, I live in this place called Park City, Utah," which I'd never heard of before. It's a ski town in Utah. "And there's this startup here that's like about to go... It's about to explode. It's about to be hugely successful." I actually at the time, because I wasn't good at school... I mean, I wasn't terrible, but I was a B-minus student. I didn't have a lot of confidence in my professional capabilities, and I thought, "This might be the only chance I have in my whole life to just ride other people's coattails success." So I wouldn't say exactly dropped out. I ended up getting my bachelor's because I had finished the requirements for it, but I left school in the middle of the semester, drove to Utah, and started working at this tech startup called Zane Benefits.</p><p><br></p><p><strong>Rick: </strong>What year is this?</p><p><strong>Tyler: </strong>This was 2007, which, for people who were around back then, was an interesting year to enter the workforce because for that first year things were pretty normal. You joined at the same time. For the first year at this company, it was a normal venture-backed startup. They just raised... What is it? A series A or a seed or something.</p><p><strong>Rick:</strong> They call it a series A. Three million dollars.</p><p><strong><br>Leading a startup from 2008 to 2009<br></strong><br></p><p><strong>Tyler: </strong>Yeah. So I was just like an entry-level programmer. I had bosses, and I was just learning the normal corporate world. And then I assume we'll talk about this when I interview you as well, but 2008 hit and global recession and all that. I don't know the whole... You know the whole story a lot better than I do, but basically, 20 out of 25 people or something like that got laid off at the company. Both of us were lucky enough to be survivors of those layoffs. I tell every person we hire, everyone who wants to really know my story on entrepreneurship, this was the defining moment because we showed up the next day to work and there was... Our bosses had been fired, right? The CEO fired himself. So we just showed up and we're like, "Well, I guess we're in charge of the company now." I don't know if... Did we realize that at the time?</p><p><strong>Rick: </strong>Oh yeah.</p><p><strong>Tyler:</strong> Yeah. We were just like, "Nobody else here is going to care enough t...</p>]]>
      </content:encoded>
      <pubDate>Fri, 20 Sep 2019 09:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/faa1aeb4/926466a1.mp3" length="35137956" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2220</itunes:duration>
      <itunes:summary>This week we're mixing the format up a bit. Instead of doing a deep dive on a specific topic, Rick interviews Tyler to learn about how he bootstrapped a business to over $2.5 million in revenue, what the future holds, and how he approaches business in general. We hope this provides some helpful context when listening to our opinions in other episodes.</itunes:summary>
      <itunes:subtitle>This week we're mixing the format up a bit. Instead of doing a deep dive on a specific topic, Rick interviews Tyler to learn about how he bootstrapped a business to over $2.5 million in revenue, what the future holds, and how he approaches business in gen</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to market a podcast</title>
      <itunes:episode>9</itunes:episode>
      <podcast:episode>9</podcast:episode>
      <itunes:title>How to market a podcast</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">380beb9b-9590-4901-90e9-0b46d3939d15</guid>
      <link>https://share.transistor.fm/s/7e7bd966</link>
      <description>
        <![CDATA[<p>In this episode, we talk about why we started the podcast, who we think our ideal listener is, and how we plan to grow our audience.</p><p>After going back and forth, the following framework emerged for marketing a podcast</p><ul><li>Why did we start the podcast?</li><li>Who is our audience and ideal listener?</li><li>What problem are we solving for our audience?</li><li>What makes our podcast unique?</li><li>How will we measure success?</li><li>How will we achieve success?</li></ul><p><strong>Takeaways include: </strong></p><ul><li>Our ideal listener is someone who:<ul><li>Wants to achieve freedom through entrepreneurship</li><li>Wants to build something sustainable that will last for many years</li><li>Does things the way they see is the right way to do them</li><li>Doesn't feel like they have a sufficient peer group for the hard conversations</li></ul></li><li>Control, freedom, flexibility, and doing things the right way (as we define “right”) are important to our ideal listener<ul><li>Our hosts (Tyler and Rick) share these values</li></ul></li><li>There is a hole between the venture capital communities and serial entrepreneurs who are flipping companies<ul><li>And that hole is build startups to last with sustainable impact and value creation for customers, employees, and owners</li></ul></li><li>We think the Startup to Last podcast is unique in the following ways:<ul><li>We have a deep-dive topic each week</li><li>We do not follow the guest-interview framework</li><li>Our hosts (Tyler and Rick) have skill sets that cover the whole spectrum in a way that most other podcast hosts don’t</li><li>We cover the spectrum in terms of company size and maturity<ul><li>Tyler is 10 years into his company while Rick is in the very early stages of his company</li></ul></li><li>We are both comfortable with the essence of entrepreneurship: not knowing the answer and being OK with talking about it until we find it</li></ul></li><li>Startup to Last has achieved basic traction since launching in June 2019:<ul><li>200+ downloads across multiple platforms:<ul><li>33% are on Apple</li><li>22% are on a web browser</li><li>12% are on Spotify</li><li>The rest are on various other platforms.</li></ul></li><li>11+ subscribers (Thank you)</li><li>95% of our downloads and subscribers are from the U.S<ul><li>We've got a couple in Mexico, and then some in Europe</li></ul></li><li>From July to August, we doubled the number of downloads month-over-month</li></ul></li><li>We will measure success going forward by making the following metrics go up:<ul><li>Subscribers</li><li>Downloads per most recent episode</li></ul></li><li>We will achieve success by:<ul><li>Talking to our existing listeners</li><li>Doing customer development with potential listeners</li><li>Experimenting with various growth channels and tactics</li></ul></li><li>We think our ideal listeners hang out in the following places:<ul><li>Online bootstrapper communities (e.g. people engaging at <a href="https://www.indiehackers.com/">Indie Hackers</a> and attendees at <a href="https://microconf.com/">MicroConf</a> )</li><li>Social media sites (e.g. people who follow similar podcasts on <a href="https://twitter.com/">Twitter</a>)</li><li>Q&amp;A sites (e.g. people who are asking / answering related questions on <a href="http://quora.com/">Quora</a>)</li></ul></li></ul><p><strong>Why did we start the podcast?<br></strong><br></p><p><strong>Tyler: </strong>For anyone listening, you haven't been listening for long because this is our ninth episode ever. When we started this podcast, we were planning on just focusing on how do we make the content, so recording it, having a schedule, picking topics, editing, producing, publishing it. All that stuff, and at this point, we feel like we've kind of got it down. I mean, I'm sure we'll get better over time, but we've got a system where we can get podcasts published pretty regularly, so now the next question is, how do we get anyone to actually listen to this, and so we're going to talk about that today. </p><p><br></p><p><strong>Tyler: </strong>Keep in mind that neither of us have ever done a podcast before, so this is going to be very speculative and maybe every idea we have here is going to fail, but basically, we need to have this conversation anyway, so let's record it, and maybe people will find it interesting, what we're planning here. So with that said, you're more of a marketing person than me certainly, Rick, but I was thinking one thing we could potentially do is go over some ideas we already have or maybe you could start high-level and just talk about how you think we should even approach getting listeners to a podcast like this?</p><p><br></p><p><strong>Rick: </strong>I think one challenge that we have, Tyler, is that the reason we created a podcast was pretty selfish. It wasn't with a customer in mind or an audience in mind. For background, we started this podcast because we want to spend more time together. Right? You live in St. Louis. I live in Utah. Well, you came out every other quarter or every few quarters or so. I recently made a trip out to St. Louis. We had a great time, and we both said, "We'd like to spend more time together. How do we do that?" I think both of us were thinking podcast when we said that. Two reasons. One, we want to spend more time together. Two, it's kind of interesting to see if a podcast would work. Neither of us have ever done that. Let's try it. And so we did that, and now it's been, you said, nine episodes, I think?</p><p><strong>Tyler: </strong>Yeah. We did two or three that we kind of threw out before we started actually publishing them.</p><p><strong>Rick: </strong>Yup, yup, and so now, what is kind of weird here is we have content that is valuable to us. I'm getting value out of this every week when I talk to you. I think you're getting value out of it. But the content that we've created was made for us. It wasn't made for some market out there of potential listeners that we have a high confidence that will get value out of this.</p><p><strong>Tyler: </strong>Yes. Although, I listen to a lot of podcasts that are, if anything, even less for an audience than this. I listen to maybe five podcasts where it's two founders talking, and some of them don't even have deep-dive topics like we do. Some of them are just, "Hey, what did you work on this week? What did you work on this week? Okay. Bye," and I think they all have thousands or tens of thousands of listeners.</p><p><strong>Rick: </strong>In marketing, that's luck. Right?</p><p><strong>Tyler: </strong>Yes, but there's an audience that wants to listen to founders talking to each other I guess is my point.</p><p><br></p><p><strong>Rick: </strong>I can't disagree with that. We're coming at this from a product-first standpoint or not even a product-first. We're coming at it from a, "Hey, we want to spend more time together, and then see what happens," which is a little different than, "Hey, there's a problem out there," like a normal business venture or something that you're designing to actually be sustainable and make money. You go, "Hey, there's a problem out here that I know about, or that I heard about, or I've witnessed, or I've felt myself, and there's a market for people who had this problem. I've talked to them, and they're... They don't tell me what the solution is, but based on their symptoms, what's out there currently from a current solution standpoint, what they are looking to achieve, what their ultimate outcome or job-to-be-done is. You go, "Okay. Well, this person is trying to get from A to B. There's a problem getting in the way. I'm going to solve that problem, and then we're going to create a solution for that." We really didn't go through that process. So, we're in our ninth episode. We've got some traction, and we could talk about that, but I don...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we talk about why we started the podcast, who we think our ideal listener is, and how we plan to grow our audience.</p><p>After going back and forth, the following framework emerged for marketing a podcast</p><ul><li>Why did we start the podcast?</li><li>Who is our audience and ideal listener?</li><li>What problem are we solving for our audience?</li><li>What makes our podcast unique?</li><li>How will we measure success?</li><li>How will we achieve success?</li></ul><p><strong>Takeaways include: </strong></p><ul><li>Our ideal listener is someone who:<ul><li>Wants to achieve freedom through entrepreneurship</li><li>Wants to build something sustainable that will last for many years</li><li>Does things the way they see is the right way to do them</li><li>Doesn't feel like they have a sufficient peer group for the hard conversations</li></ul></li><li>Control, freedom, flexibility, and doing things the right way (as we define “right”) are important to our ideal listener<ul><li>Our hosts (Tyler and Rick) share these values</li></ul></li><li>There is a hole between the venture capital communities and serial entrepreneurs who are flipping companies<ul><li>And that hole is build startups to last with sustainable impact and value creation for customers, employees, and owners</li></ul></li><li>We think the Startup to Last podcast is unique in the following ways:<ul><li>We have a deep-dive topic each week</li><li>We do not follow the guest-interview framework</li><li>Our hosts (Tyler and Rick) have skill sets that cover the whole spectrum in a way that most other podcast hosts don’t</li><li>We cover the spectrum in terms of company size and maturity<ul><li>Tyler is 10 years into his company while Rick is in the very early stages of his company</li></ul></li><li>We are both comfortable with the essence of entrepreneurship: not knowing the answer and being OK with talking about it until we find it</li></ul></li><li>Startup to Last has achieved basic traction since launching in June 2019:<ul><li>200+ downloads across multiple platforms:<ul><li>33% are on Apple</li><li>22% are on a web browser</li><li>12% are on Spotify</li><li>The rest are on various other platforms.</li></ul></li><li>11+ subscribers (Thank you)</li><li>95% of our downloads and subscribers are from the U.S<ul><li>We've got a couple in Mexico, and then some in Europe</li></ul></li><li>From July to August, we doubled the number of downloads month-over-month</li></ul></li><li>We will measure success going forward by making the following metrics go up:<ul><li>Subscribers</li><li>Downloads per most recent episode</li></ul></li><li>We will achieve success by:<ul><li>Talking to our existing listeners</li><li>Doing customer development with potential listeners</li><li>Experimenting with various growth channels and tactics</li></ul></li><li>We think our ideal listeners hang out in the following places:<ul><li>Online bootstrapper communities (e.g. people engaging at <a href="https://www.indiehackers.com/">Indie Hackers</a> and attendees at <a href="https://microconf.com/">MicroConf</a> )</li><li>Social media sites (e.g. people who follow similar podcasts on <a href="https://twitter.com/">Twitter</a>)</li><li>Q&amp;A sites (e.g. people who are asking / answering related questions on <a href="http://quora.com/">Quora</a>)</li></ul></li></ul><p><strong>Why did we start the podcast?<br></strong><br></p><p><strong>Tyler: </strong>For anyone listening, you haven't been listening for long because this is our ninth episode ever. When we started this podcast, we were planning on just focusing on how do we make the content, so recording it, having a schedule, picking topics, editing, producing, publishing it. All that stuff, and at this point, we feel like we've kind of got it down. I mean, I'm sure we'll get better over time, but we've got a system where we can get podcasts published pretty regularly, so now the next question is, how do we get anyone to actually listen to this, and so we're going to talk about that today. </p><p><br></p><p><strong>Tyler: </strong>Keep in mind that neither of us have ever done a podcast before, so this is going to be very speculative and maybe every idea we have here is going to fail, but basically, we need to have this conversation anyway, so let's record it, and maybe people will find it interesting, what we're planning here. So with that said, you're more of a marketing person than me certainly, Rick, but I was thinking one thing we could potentially do is go over some ideas we already have or maybe you could start high-level and just talk about how you think we should even approach getting listeners to a podcast like this?</p><p><br></p><p><strong>Rick: </strong>I think one challenge that we have, Tyler, is that the reason we created a podcast was pretty selfish. It wasn't with a customer in mind or an audience in mind. For background, we started this podcast because we want to spend more time together. Right? You live in St. Louis. I live in Utah. Well, you came out every other quarter or every few quarters or so. I recently made a trip out to St. Louis. We had a great time, and we both said, "We'd like to spend more time together. How do we do that?" I think both of us were thinking podcast when we said that. Two reasons. One, we want to spend more time together. Two, it's kind of interesting to see if a podcast would work. Neither of us have ever done that. Let's try it. And so we did that, and now it's been, you said, nine episodes, I think?</p><p><strong>Tyler: </strong>Yeah. We did two or three that we kind of threw out before we started actually publishing them.</p><p><strong>Rick: </strong>Yup, yup, and so now, what is kind of weird here is we have content that is valuable to us. I'm getting value out of this every week when I talk to you. I think you're getting value out of it. But the content that we've created was made for us. It wasn't made for some market out there of potential listeners that we have a high confidence that will get value out of this.</p><p><strong>Tyler: </strong>Yes. Although, I listen to a lot of podcasts that are, if anything, even less for an audience than this. I listen to maybe five podcasts where it's two founders talking, and some of them don't even have deep-dive topics like we do. Some of them are just, "Hey, what did you work on this week? What did you work on this week? Okay. Bye," and I think they all have thousands or tens of thousands of listeners.</p><p><strong>Rick: </strong>In marketing, that's luck. Right?</p><p><strong>Tyler: </strong>Yes, but there's an audience that wants to listen to founders talking to each other I guess is my point.</p><p><br></p><p><strong>Rick: </strong>I can't disagree with that. We're coming at this from a product-first standpoint or not even a product-first. We're coming at it from a, "Hey, we want to spend more time together, and then see what happens," which is a little different than, "Hey, there's a problem out there," like a normal business venture or something that you're designing to actually be sustainable and make money. You go, "Hey, there's a problem out here that I know about, or that I heard about, or I've witnessed, or I've felt myself, and there's a market for people who had this problem. I've talked to them, and they're... They don't tell me what the solution is, but based on their symptoms, what's out there currently from a current solution standpoint, what they are looking to achieve, what their ultimate outcome or job-to-be-done is. You go, "Okay. Well, this person is trying to get from A to B. There's a problem getting in the way. I'm going to solve that problem, and then we're going to create a solution for that." We really didn't go through that process. So, we're in our ninth episode. We've got some traction, and we could talk about that, but I don...</p>]]>
      </content:encoded>
      <pubDate>Thu, 05 Sep 2019 18:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/7e7bd966/fb9596d5.mp3" length="54210180" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3351</itunes:duration>
      <itunes:summary>This week, we take a look inward and discuss what we can do to get more listeners for this podcast. We discuss how to identify an ideal audience, customer development, and more.</itunes:summary>
      <itunes:subtitle>This week, we take a look inward and discuss what we can do to get more listeners for this podcast. We discuss how to identify an ideal audience, customer development, and more.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, bootstrapping, founders, technology, software</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to teach yourself to code a web-based application</title>
      <itunes:episode>8</itunes:episode>
      <podcast:episode>8</podcast:episode>
      <itunes:title>How to teach yourself to code a web-based application</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">38c91e3f-2e33-4d69-bb2a-86f107391a82</guid>
      <link>https://share.transistor.fm/s/0cea910d</link>
      <description>
        <![CDATA[<p>In this episode, Tyler helps Rick create a plan to teach himself how to code a web-based application. Rick isn’t sure where to start and asks Tyler for help. Tyler shares best practices he’s learned from teaching more than 15 people how to code from scratch. </p><p>After going back and forth, the following framework emerged for teaching yourself how to code a web-based application:</p><ul><li>Clarify why you want to learn how to code.</li><li>Get a macro understanding of the skills, languages, and technologies you need to know in order to build an application. </li><li>Pick a simple CRUD (Create Read Update Delete) application to build from scratch (e.g. a blog).</li><li>Set up some basic infrastructure and pick a server-side (or back-end) language (e.g. PHP, Python, Ruby, etc.)</li><li>Start by building a static version of your web application with HTML and CSS</li><li>Then work through the C-R-U-D of CRUD. Create, read, update, delete one at a time.</li><li>Add Javascript to freshen up the UI or UX.</li><li>And add APIs to add third party functionality (e.g. Stripe for billing). </li></ul><p>Takeaways include: </p><ul><li>Start macro. There's a bird’s-eye view that requires some generalist research to help you visualize the macro components required to build a CRUD app. </li><li>Picking your server-side technology and languages are going to be one of the hardest things to do. What is your server-side language going to be? How are you going to set up your database? Where will you host your servers? Take some time to get this right.</li><li>Set up a local server on your computer to start. This simplifies the initial infrastructure setup.</li><li>Use GitHub. When you're writing code, get in the habit of checking all your code into GitHub so that it's backed up. This helps with version control and code review.</li><li>Find a mentor. Find someone who will do regular code reviews with you and give you feedback.</li><li>Keep the front-end simple to start.</li></ul><p><strong><br>Why learn to code?<br></strong><br></p><p><strong>Rick:</strong> Now that we've got <a href="http://pandolabs.org/">PandoLabs</a> steady and <a href="https://groupcurrent.com/">GroupCurrent</a> on a good trajectory, I'm starting to turn my attention to how I can finance the development of a minimally viable product, specifically in the business-to-business software application space. One of my constraints at <a href="https://www.legupventures.com/">LegUp Ventures</a> is I don't want to give up control of the company as I scale it, so I have to be very cautious about giving up equity early in the company because I need to be able to give up equity later without losing control. In our <a href="https://www.startuptolast.com/topics/how-a-non-technical-founder-can-make-their-first-technical-hire">episode about technical co-founders</a>, I realized the person I need is a full stack developer, and basically that's a unicorn that is going to cost me an arm and a leg in terms of cash and/or equity. So I reflected on that. I talked to some people. I talked to you offline. What I came to was I was a computer science major at Duke, so I'm not some person who doesn't know anything about how a web application works. But from what I learned, the Duke computer science program when I was there, we were doing assembly classes. My eyes were glazed over. The best classes were the programming classes where we actually built something that resulted in something that worked. Facebook was just getting started at the time. The whole idea of building a web application and building a business around it was no part of the curriculum.</p><p><strong>Tyler:</strong> Well, if I can interject for a second, I think a lot of people who didn't major in computer science don't appreciate the fact that most computer science classes, you don't code at all. You write your answers down on a piece of paper and turn it in. You really don't learn much about software engineering, which is a whole different discipline from computer science.</p><p><strong>Rick:</strong> Exactly. And the reason I majored in computer science was to learn how to code, but I ended up not learning much about how to code. But I learned a lot of theory and I learned the history of the internet, and some valuable things. And plus I can say I majored in computer science and people think that's cool. But I did learn some things about coding through that major. But there's been 12 years, 13 years since I've coded past HTML and CSS. So there's a huge gap between how I think in my head based on what I learned about how building a web application works, and what the truth is today. There's been significant evolution in the no-code space for example, which allows people who have no ability to code to logically and visually design applications. There are also significant infrastructure automation tools that massively reduce the knowledge you have to have about setting up and running servers, and worrying about security, and all these things that you really had to know back in our day, my day, 2007. So I've decided that I need to learn these things and I don't know where to start. So I think there are a couple of approaches. So why do I want to do this? I want to start there. I am terrified of making a mistake hiring someone to do this and wasting a ton of money. I'm also terrified of bringing the wrong co-founder on because I don't know enough about what I truly need. When you say I need to hire a full stack developer, that's good. That's like a unicorn to me and I feel that's very risky. So through this effort, my main goal is to reduce risk. I don't actually expect my myself to actually learn how to code a full application. I do expect to de-risk bringing on support to build the application.</p><p><br></p><p><strong>Tyler:</strong> If I can add one other reason to do this, I think it'll make you a better executive overseeing future technical hiring. There's no business in the world that doesn't have some technical component to it anymore. And if you want to run businesses, knowing how to code will help you even if you never write a line of code ever again.</p><p><strong>Rick:</strong> Totally agree.</p><p><strong>Tyler:</strong> Cool.</p><p><strong>Rick:</strong> My problem is not necessarily to learn how to build an application. It's to address my fear of really wasting money in early stage product development. Where do I start?</p><p><strong>Tyler: </strong>Yeah. Well I think it's good that you have that constraint here because for anyone listening to this episode, it's like how to learn how to code is such a broad topic. We need a constraint. And the constraint here is you're not trying to go get a job as a professional developer. If you were, I'd say you'd probably need a much better theoretical background first of all. And second of all, the technology you use would need to be really focused on what's sexy and trendy right now because that's how you get hired. You don't care about any of that. So it's really how do you build an MVP as quickly as possible, ignoring your learning, and the sustainability of the software long term because someone else is going to come along and rebuild it probably.</p><p><br></p><p><strong>Rick: </strong>Yup, exactly.</p><p><strong><br>Where to start?<br></strong><br></p><p><strong>Tyler:</strong> Okay, so my background here, I majored in computer science at the exact same time you did and got sounds like the exact same education you did. But then became a professional software engineer after that. And I don't code a ton anymore. I probably maybe put in 10 hours a week at this point, but I think I'm relatively up to speed on how things go. My attitude is that it was much, much easier to ship a working software product 10 years ago than it is now. Let me clarify. You can s...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Tyler helps Rick create a plan to teach himself how to code a web-based application. Rick isn’t sure where to start and asks Tyler for help. Tyler shares best practices he’s learned from teaching more than 15 people how to code from scratch. </p><p>After going back and forth, the following framework emerged for teaching yourself how to code a web-based application:</p><ul><li>Clarify why you want to learn how to code.</li><li>Get a macro understanding of the skills, languages, and technologies you need to know in order to build an application. </li><li>Pick a simple CRUD (Create Read Update Delete) application to build from scratch (e.g. a blog).</li><li>Set up some basic infrastructure and pick a server-side (or back-end) language (e.g. PHP, Python, Ruby, etc.)</li><li>Start by building a static version of your web application with HTML and CSS</li><li>Then work through the C-R-U-D of CRUD. Create, read, update, delete one at a time.</li><li>Add Javascript to freshen up the UI or UX.</li><li>And add APIs to add third party functionality (e.g. Stripe for billing). </li></ul><p>Takeaways include: </p><ul><li>Start macro. There's a bird’s-eye view that requires some generalist research to help you visualize the macro components required to build a CRUD app. </li><li>Picking your server-side technology and languages are going to be one of the hardest things to do. What is your server-side language going to be? How are you going to set up your database? Where will you host your servers? Take some time to get this right.</li><li>Set up a local server on your computer to start. This simplifies the initial infrastructure setup.</li><li>Use GitHub. When you're writing code, get in the habit of checking all your code into GitHub so that it's backed up. This helps with version control and code review.</li><li>Find a mentor. Find someone who will do regular code reviews with you and give you feedback.</li><li>Keep the front-end simple to start.</li></ul><p><strong><br>Why learn to code?<br></strong><br></p><p><strong>Rick:</strong> Now that we've got <a href="http://pandolabs.org/">PandoLabs</a> steady and <a href="https://groupcurrent.com/">GroupCurrent</a> on a good trajectory, I'm starting to turn my attention to how I can finance the development of a minimally viable product, specifically in the business-to-business software application space. One of my constraints at <a href="https://www.legupventures.com/">LegUp Ventures</a> is I don't want to give up control of the company as I scale it, so I have to be very cautious about giving up equity early in the company because I need to be able to give up equity later without losing control. In our <a href="https://www.startuptolast.com/topics/how-a-non-technical-founder-can-make-their-first-technical-hire">episode about technical co-founders</a>, I realized the person I need is a full stack developer, and basically that's a unicorn that is going to cost me an arm and a leg in terms of cash and/or equity. So I reflected on that. I talked to some people. I talked to you offline. What I came to was I was a computer science major at Duke, so I'm not some person who doesn't know anything about how a web application works. But from what I learned, the Duke computer science program when I was there, we were doing assembly classes. My eyes were glazed over. The best classes were the programming classes where we actually built something that resulted in something that worked. Facebook was just getting started at the time. The whole idea of building a web application and building a business around it was no part of the curriculum.</p><p><strong>Tyler:</strong> Well, if I can interject for a second, I think a lot of people who didn't major in computer science don't appreciate the fact that most computer science classes, you don't code at all. You write your answers down on a piece of paper and turn it in. You really don't learn much about software engineering, which is a whole different discipline from computer science.</p><p><strong>Rick:</strong> Exactly. And the reason I majored in computer science was to learn how to code, but I ended up not learning much about how to code. But I learned a lot of theory and I learned the history of the internet, and some valuable things. And plus I can say I majored in computer science and people think that's cool. But I did learn some things about coding through that major. But there's been 12 years, 13 years since I've coded past HTML and CSS. So there's a huge gap between how I think in my head based on what I learned about how building a web application works, and what the truth is today. There's been significant evolution in the no-code space for example, which allows people who have no ability to code to logically and visually design applications. There are also significant infrastructure automation tools that massively reduce the knowledge you have to have about setting up and running servers, and worrying about security, and all these things that you really had to know back in our day, my day, 2007. So I've decided that I need to learn these things and I don't know where to start. So I think there are a couple of approaches. So why do I want to do this? I want to start there. I am terrified of making a mistake hiring someone to do this and wasting a ton of money. I'm also terrified of bringing the wrong co-founder on because I don't know enough about what I truly need. When you say I need to hire a full stack developer, that's good. That's like a unicorn to me and I feel that's very risky. So through this effort, my main goal is to reduce risk. I don't actually expect my myself to actually learn how to code a full application. I do expect to de-risk bringing on support to build the application.</p><p><br></p><p><strong>Tyler:</strong> If I can add one other reason to do this, I think it'll make you a better executive overseeing future technical hiring. There's no business in the world that doesn't have some technical component to it anymore. And if you want to run businesses, knowing how to code will help you even if you never write a line of code ever again.</p><p><strong>Rick:</strong> Totally agree.</p><p><strong>Tyler:</strong> Cool.</p><p><strong>Rick:</strong> My problem is not necessarily to learn how to build an application. It's to address my fear of really wasting money in early stage product development. Where do I start?</p><p><strong>Tyler: </strong>Yeah. Well I think it's good that you have that constraint here because for anyone listening to this episode, it's like how to learn how to code is such a broad topic. We need a constraint. And the constraint here is you're not trying to go get a job as a professional developer. If you were, I'd say you'd probably need a much better theoretical background first of all. And second of all, the technology you use would need to be really focused on what's sexy and trendy right now because that's how you get hired. You don't care about any of that. So it's really how do you build an MVP as quickly as possible, ignoring your learning, and the sustainability of the software long term because someone else is going to come along and rebuild it probably.</p><p><br></p><p><strong>Rick: </strong>Yup, exactly.</p><p><strong><br>Where to start?<br></strong><br></p><p><strong>Tyler:</strong> Okay, so my background here, I majored in computer science at the exact same time you did and got sounds like the exact same education you did. But then became a professional software engineer after that. And I don't code a ton anymore. I probably maybe put in 10 hours a week at this point, but I think I'm relatively up to speed on how things go. My attitude is that it was much, much easier to ship a working software product 10 years ago than it is now. Let me clarify. You can s...</p>]]>
      </content:encoded>
      <pubDate>Fri, 30 Aug 2019 12:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/0cea910d/ecf64ed1.mp3" length="50276344" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3050</itunes:duration>
      <itunes:summary>This week, we talk about how an entrepreneur without a technical background could teach themselves to code well enough to build an MVP (minimum viable product) for a web-based SaaS app.</itunes:summary>
      <itunes:subtitle>This week, we talk about how an entrepreneur without a technical background could teach themselves to code well enough to build an MVP (minimum viable product) for a web-based SaaS app.</itunes:subtitle>
      <itunes:keywords>SaaS, programming, web</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How to communicate major product changes to your users</title>
      <itunes:episode>7</itunes:episode>
      <podcast:episode>7</podcast:episode>
      <itunes:title>How to communicate major product changes to your users</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">673695f1-ff53-43d9-9af8-f24f9b406e93</guid>
      <link>https://share.transistor.fm/s/64c6f7d6</link>
      <description>
        <![CDATA[<p>In this episode, Rick helps Tyler think through how to roll out a major product redesign for his 20,000 users. Tyler has a plan, but he’s concerned about losing customers through the transition. His biggest roadblock is figuring out how to roll this out without causing his customers to get angry and leave.</p><p>After going back and forth, the following framework emerged for communicating major product changes to existing users:</p><ul><li>Why you are making the product changes in the first place?</li><li>How will you measure success (i.e. the desired outcome)? </li><li>What are the key messages you need users to understand?</li><li>What proof points (e.g. screenshots, quotes, stats, etc.) can you provide that your key messages are true?</li><li>How can you segment users and prioritize them?</li><li>What mediums should you use to communicate?</li><li>How often and over what time period can you communicate these key messages and proof points to each segment?</li></ul><p>Takeaways include: </p><ul><li>Start with why. Identify why you are doing this. Is it for customer acquisition, customer retention, or something else?</li><li>Recognize that some users will go through <a href="https://changecycle.com/change-cycle/">change cycles</a>, and help them through it. This starts with clear messaging.</li><li>Don’t surprise your users. Give them plenty of notice and time to get through the change cycle.</li><li>Treat this like a marketing funnel or sales pipeline. It’s a conversion.</li><li>Segment customers by risk and value so you can prioritize outreach. This might be based on revenue, net promoter score (NPS), product usage or a new survey.</li><li>Choose mediums and frequencies that support your annual contract value (ACV). If you are a low-ACV product, you probably can’t afford 1:1 phone calls for every customer. </li></ul><p><br>The change cycle concept</p><p></p><p>Source: <a href="https://changecycle.com/change-cycle/">changecycle.com</a></p><p><strong>What’s the product change?<br></strong><br></p><p><strong>Tyler:</strong> The topic for this week is how to communicate major product changes to your users. This could go any number of directions, but the reason I'm bringing this up is, I've referenced the last few episodes where we're working on this big redesign of <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>. It's both a redesign and two major new features. It’s the biggest update we've had in at least five plus years, if not ever.</p><p><br></p><p><strong>Rick:</strong> Did you say two new features?</p><p><strong>Tyler:</strong> Two new features. Yeah, outlook, calendar sync. And we're completely redoing custom fields. Pretty big features, but the thing people will notice most is the redesign. And so I've been kind of thinking, "how do we communicate this to people?" The traditional way to think of this is, "how do you build hype and use it as a marketing event?", which we can talk about. But the theme of the podcast is "how do you build a business to last?" And I think a lot of companies change and eventually it leads to their downfall if they do this wrong. They forget their core audience and all that. They get too excited about the upside. Our audience is not one that loves change. And so most of the communication side that I'm thinking of is not, "how do we market this?", but instead, "how do we reveal this to people in a way that will minimize their likelihood of flipping out and leaving." Basically.</p><p><strong>Rick:</strong> In other words, a lot of companies might see this as an opportunity to wow users. You don't see that. You see this as a threat to users.</p><p><strong><br>Why you are making the product changes in the first place?<br></strong><br></p><p><strong>Tyler: </strong>I think it's good for them, but if I'm being totally honest, the reason we have to do this, is to keep getting new users. The two new features will be helpful to our existing users. The redesign won't. They already know how it works. It'll look nicer, but that doesn't provide any value to them and they're not going to be excited about the fact that we redesigned.</p><p><strong>Rick:</strong> Is this true in most cases? When companies do redesigns, is it always usually for new users?</p><p><strong>Tyler:</strong> Yeah, I think so. I was just kind of thinking of this case, but if your audience is really into design or something like that, maybe they get excited about it. But for the most part, if you think of software as a tool, which CRM software certainly is. I think most B2B software is a tool. Once you know how the tool works, I can't imagine much benefit to saying, "okay, now you have to learn a new way for it to work."</p><p><strong>Rick</strong>: If it works currently?</p><p><strong>Tyler</strong>: Yeah. Yeah, true.</p><p><strong>Rick: </strong>Got it. Yeah. Okay. Man, I guess, if the redesign is valuable to new users, there's got to be some benefit to switching to the new design for old users.</p><p><strong>Tyler: </strong>Yes. And so a couple things on that. First of all, this is one reason why we're bundling it with two new features. We've done this throughout our history. You know how anytime Facebook changes anything? Everyone on Facebook's like, "oh, I hate it, I'm quitting." And then they forget about it a couple of weeks later. One way we try to minimize that reaction is saying, "there's an actual new feature for you here that you care about." And probably it doesn't have to come with the redesign, but to a user, it seems like they're a package deal.</p><p><strong>Rick</strong>: Yeah. I'm also realizing that your users are probably highly sensitive to this because this is a CRM product. They use it every minute of every hour of every workday.</p><p><strong>Tyler: </strong>And there's also a history here, which is a lot of our users are older, 40 plus years old and they've been through multiple cycles of CRM companies screwing them over. And so part of this is a lot of them, their natural reaction is, "oh, you're getting ready for an acquisition. You're getting ready to raise prices." They see the writing on the wall anytime anything changes. So I have to kind of reassure them like, "no, no, no. We hadn't redesigned the software in seven years. We need a new design here."</p><p><strong>Rick:</strong> I think we should dive into why you're doing this. Just because you need to do it for seven years doesn't resonate with me. It probably won't resonate with your users. So why do a redesign? Let's actually exclude the two new features from this conversation.</p><p><br></p><p><strong>Tyler: </strong>Yeah, I agree.</p><p><strong>Rick: </strong>Why are you prioritizing a redesign and what does it mean for the company?</p><p><strong>Tyler: </strong>Okay. Let's break this into two categorie...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Rick helps Tyler think through how to roll out a major product redesign for his 20,000 users. Tyler has a plan, but he’s concerned about losing customers through the transition. His biggest roadblock is figuring out how to roll this out without causing his customers to get angry and leave.</p><p>After going back and forth, the following framework emerged for communicating major product changes to existing users:</p><ul><li>Why you are making the product changes in the first place?</li><li>How will you measure success (i.e. the desired outcome)? </li><li>What are the key messages you need users to understand?</li><li>What proof points (e.g. screenshots, quotes, stats, etc.) can you provide that your key messages are true?</li><li>How can you segment users and prioritize them?</li><li>What mediums should you use to communicate?</li><li>How often and over what time period can you communicate these key messages and proof points to each segment?</li></ul><p>Takeaways include: </p><ul><li>Start with why. Identify why you are doing this. Is it for customer acquisition, customer retention, or something else?</li><li>Recognize that some users will go through <a href="https://changecycle.com/change-cycle/">change cycles</a>, and help them through it. This starts with clear messaging.</li><li>Don’t surprise your users. Give them plenty of notice and time to get through the change cycle.</li><li>Treat this like a marketing funnel or sales pipeline. It’s a conversion.</li><li>Segment customers by risk and value so you can prioritize outreach. This might be based on revenue, net promoter score (NPS), product usage or a new survey.</li><li>Choose mediums and frequencies that support your annual contract value (ACV). If you are a low-ACV product, you probably can’t afford 1:1 phone calls for every customer. </li></ul><p><br>The change cycle concept</p><p></p><p>Source: <a href="https://changecycle.com/change-cycle/">changecycle.com</a></p><p><strong>What’s the product change?<br></strong><br></p><p><strong>Tyler:</strong> The topic for this week is how to communicate major product changes to your users. This could go any number of directions, but the reason I'm bringing this up is, I've referenced the last few episodes where we're working on this big redesign of <a href="http://lessannoyingcrm.com/">Less Annoying CRM</a>. It's both a redesign and two major new features. It’s the biggest update we've had in at least five plus years, if not ever.</p><p><br></p><p><strong>Rick:</strong> Did you say two new features?</p><p><strong>Tyler:</strong> Two new features. Yeah, outlook, calendar sync. And we're completely redoing custom fields. Pretty big features, but the thing people will notice most is the redesign. And so I've been kind of thinking, "how do we communicate this to people?" The traditional way to think of this is, "how do you build hype and use it as a marketing event?", which we can talk about. But the theme of the podcast is "how do you build a business to last?" And I think a lot of companies change and eventually it leads to their downfall if they do this wrong. They forget their core audience and all that. They get too excited about the upside. Our audience is not one that loves change. And so most of the communication side that I'm thinking of is not, "how do we market this?", but instead, "how do we reveal this to people in a way that will minimize their likelihood of flipping out and leaving." Basically.</p><p><strong>Rick:</strong> In other words, a lot of companies might see this as an opportunity to wow users. You don't see that. You see this as a threat to users.</p><p><strong><br>Why you are making the product changes in the first place?<br></strong><br></p><p><strong>Tyler: </strong>I think it's good for them, but if I'm being totally honest, the reason we have to do this, is to keep getting new users. The two new features will be helpful to our existing users. The redesign won't. They already know how it works. It'll look nicer, but that doesn't provide any value to them and they're not going to be excited about the fact that we redesigned.</p><p><strong>Rick:</strong> Is this true in most cases? When companies do redesigns, is it always usually for new users?</p><p><strong>Tyler:</strong> Yeah, I think so. I was just kind of thinking of this case, but if your audience is really into design or something like that, maybe they get excited about it. But for the most part, if you think of software as a tool, which CRM software certainly is. I think most B2B software is a tool. Once you know how the tool works, I can't imagine much benefit to saying, "okay, now you have to learn a new way for it to work."</p><p><strong>Rick</strong>: If it works currently?</p><p><strong>Tyler</strong>: Yeah. Yeah, true.</p><p><strong>Rick: </strong>Got it. Yeah. Okay. Man, I guess, if the redesign is valuable to new users, there's got to be some benefit to switching to the new design for old users.</p><p><strong>Tyler: </strong>Yes. And so a couple things on that. First of all, this is one reason why we're bundling it with two new features. We've done this throughout our history. You know how anytime Facebook changes anything? Everyone on Facebook's like, "oh, I hate it, I'm quitting." And then they forget about it a couple of weeks later. One way we try to minimize that reaction is saying, "there's an actual new feature for you here that you care about." And probably it doesn't have to come with the redesign, but to a user, it seems like they're a package deal.</p><p><strong>Rick</strong>: Yeah. I'm also realizing that your users are probably highly sensitive to this because this is a CRM product. They use it every minute of every hour of every workday.</p><p><strong>Tyler: </strong>And there's also a history here, which is a lot of our users are older, 40 plus years old and they've been through multiple cycles of CRM companies screwing them over. And so part of this is a lot of them, their natural reaction is, "oh, you're getting ready for an acquisition. You're getting ready to raise prices." They see the writing on the wall anytime anything changes. So I have to kind of reassure them like, "no, no, no. We hadn't redesigned the software in seven years. We need a new design here."</p><p><strong>Rick:</strong> I think we should dive into why you're doing this. Just because you need to do it for seven years doesn't resonate with me. It probably won't resonate with your users. So why do a redesign? Let's actually exclude the two new features from this conversation.</p><p><br></p><p><strong>Tyler: </strong>Yeah, I agree.</p><p><strong>Rick: </strong>Why are you prioritizing a redesign and what does it mean for the company?</p><p><strong>Tyler: </strong>Okay. Let's break this into two categorie...</p>]]>
      </content:encoded>
      <pubDate>Thu, 22 Aug 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/64c6f7d6/278d2707.mp3" length="47828177" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3011</itunes:duration>
      <itunes:summary>This week, we talk about two of the main things to consider when communicating upcoming product changes to your users: how tell a story to generate excitement, and how to make sure that your change-averse users don't get angry and leave.</itunes:summary>
      <itunes:subtitle>This week, we talk about two of the main things to consider when communicating upcoming product changes to your users: how tell a story to generate excitement, and how to make sure that your change-averse users don't get angry and leave.</itunes:subtitle>
      <itunes:keywords>SaaS, startups, communication, product announcements</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How a non-technical founder can make their first technical hire</title>
      <itunes:episode>6</itunes:episode>
      <podcast:episode>6</podcast:episode>
      <itunes:title>How a non-technical founder can make their first technical hire</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">bf40193e-ae38-41cc-8ea6-d89a33051b2f</guid>
      <link>https://share.transistor.fm/s/0247aac0</link>
      <description>
        <![CDATA[<p>In this episode, Tyler helps Rick evaluate how to build a new software application from scratch. Since Rick is a nontechnical founder, his biggest roadblock is figuring out how to build the application without raising money.</p><p>After going back and forth, the following framework emerged for nontechnical founders trying to hire a first employee:</p><ul><li>What is the idea (i.e. problem and solution)?</li><li>What type of application needs to be built to deliver on the idea (i.e. requirements)?</li><li>What technical skills are required to build the application?</li><li>How much are these skills going to cost?</li><li>How are you going to finance these costs?</li></ul><p>Some of the takeaways include: </p><ul><li>If you're a non-technical founder, it’s very hard to bootstrap early product development without giving up equity. </li><li>CRUD (Create. Read. Update. Delete) software applications require a generalist “full stack” developer while more sophisticated software applications may require a specific specialty.</li><li>There are two big buckets of skills for product development: design and technical. </li><li>The design bucket is made up of two categories: 1) user interface (UI) design and/or user experience (UX) design; and 2) graphic and/or visual design.</li><li>The technical bucket is made up of three categories: front-end development, back-end development, and infrastructure.</li><li>There are a number of ways to staff these skills ranging from finding an experienced generalist co-founder, which is most expensive, to outsourcing, to hiring entry level talent at the low-end. Each approach comes with it’s pros and cons.</li><li>One downside of going with less experienced talent is “technical debt”, which can increase costs down the road. Another downside is slower progress due to the learning curve.</li><li>To attract top talent, you either have to: a) have a compelling idea and be willing to give up significant equity, or 2) already have some traction and be able to pay a competitive salary and bonus. </li></ul><p><strong>What is the idea?<br></strong><br></p><p><strong>Tyler: </strong>In this episode, we’re going to talk about the ideal technical co-founder or first employee for a software company, and how to find them.</p><p><strong>Rick: </strong>I’m excited about the topic today because I’m not technical. For purposes of this conversation, let's assume it's a software application in the business-to-business (B2B) realm. Obviously, [what type of software you want to build] is going to be a determining factor. But for the purposes of this conversation, let's condense it to, “what's the right technical co-founder for a B2B software company.” This is on my mind because I just ran into a [technical] problem with <a href="https://www.groupcurrent.com/">Group Current</a>. But, it's also on my mind because as I think about <a href="https://www.legupventures.com/">LegUp Ventures</a>, which is my parent company that owns and operates [my startups], I'm starting to think about other types of software applications that I might want to build. For example, I'm still very interested in the employee benefits space outside of health insurance. I have an idea about education benefits where a company could give money to employees, tax-free, and let them go into a marketplace similar to the health insurance marketplace and peruse courses from all types of vendors [ranging] from <a href="https://www.coursera.org/">Coursera</a> to <a href="https://www.saastr.com/pro/">SaaStr</a> to, even in-person events or books on <a href="https://www.amazon.com/">Amazon</a>, buy them, and then get reimbursed tax-free by their company. I've thrown this around with a lot of people, especially millennials who are interested in going to take advantage of these new tools, and there seems to be a solid demand for it. I cannot find anyone who's delivering on this. I know exactly how this is going to work and all the technical specs. The big roadblock for me is knowing how to go about building the application in a way that I can prove [product market fit] before I raise money.</p><p><strong>Tyler:</strong> Yeah. So it seems like there's at least two parts of this. One is what skills would the ideal technical co-founder have and all that? The other one is how do you find that person?</p><p><strong>Rick:</strong> Yeah, and I would say there's a third element. So one is, yes, skillset. Two is how do you find them, and then the third is what do you call them and how do you pay them? Is it a co-founder? Is it a contractor? Is it an [outsourced] shop? Is it an employee? And what's their title? Is it engineer? Is it co-founder? Is it CTO?</p><p><strong>Tyler:</strong> Right. Okay, so where do you want to start here?</p><p><strong>Rick:</strong> Skills.</p><p><strong><br>What type of software application are you building?<br></strong><br></p><p><strong>Tyler:</strong> So you're talking about a web-based application, right? And this is something that absolutely doesn't require genius-level technical knowledge to build. Do you know the term CRUD? This is a CRUD app.</p><p><strong>Rick:</strong> CRUD sounds bad. Is CRUD bad?</p><p><strong>Tyler:</strong> No. It's Create, Read, Update, Delete. It's basically the four main database functions, and a lot of software out there is nothing more than putting stuff into a database, taking stuff out of a database, and then putting a [user interface] (UI) on top of it.</p><p><strong>Rick:</strong> Yes, and I would say that the UI for this is critical, because it's going to be a low ACV (or annual contract value) product and self service is really key.</p><p><strong>Tyler:</strong> Yeah, so the UI design might be more important than the actual technical implementation here because, with most CRUD apps, and I consider a CRM to be one as well, you don't need a <a href="https://careers.google.com/how-we-hire/">Google</a>-level genius computer science PHD to build it. Maybe you need someone who has more empathy for customers and stuff like that. Do you think the person you're talking about is going to design it, or do you think someone else is going to?</p><p><strong><br>What skills do you need to build the application?<br></strong><br></p><p><strong>Rick:</strong> So, maybe I could talk about what my skills are. It sounds like this is going to be variable based on what compliments I need. I am a terrible designer from a “look and feel” standpoint. I can wireframe a usable product. I can wireframe a vision for something, but in terms of making it an exciting experience for a user, from colors to a style, to even specific placement of elements, that's not me. But in terms of writing requirements, describing the high level technical requirements, describing the user persona, the strategy around marketing this, that's all I'm really strong at. I would love someone that is as passionate about the user experience as me, but I can't do the design, I can't code the design.</p><p><strong>Tyler:</strong> So you either need a designer and a programmer, or a jack-of-all-trades who's going to be able to do both of those? A lot of companies would have two different people for these two different roles.</p><p><strong>Rick:</strong> Well, let's assume for this conversation that I'm looking for one person to fill this void, and I'm open to calling them a co-founder. I'm also open to calling them whatever is appropriate to call them. Employee. Contractor. Outsource shop. If this is going to be one person, what are all the skills that they would need to be able to design, code, and, I guess, launch?</p><p><strong>Tyler:</strong> Yeah. So where you leave off is basically a requirement doc. Maybe you could do the wireframe, but it sounds like where does stuff...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, Tyler helps Rick evaluate how to build a new software application from scratch. Since Rick is a nontechnical founder, his biggest roadblock is figuring out how to build the application without raising money.</p><p>After going back and forth, the following framework emerged for nontechnical founders trying to hire a first employee:</p><ul><li>What is the idea (i.e. problem and solution)?</li><li>What type of application needs to be built to deliver on the idea (i.e. requirements)?</li><li>What technical skills are required to build the application?</li><li>How much are these skills going to cost?</li><li>How are you going to finance these costs?</li></ul><p>Some of the takeaways include: </p><ul><li>If you're a non-technical founder, it’s very hard to bootstrap early product development without giving up equity. </li><li>CRUD (Create. Read. Update. Delete) software applications require a generalist “full stack” developer while more sophisticated software applications may require a specific specialty.</li><li>There are two big buckets of skills for product development: design and technical. </li><li>The design bucket is made up of two categories: 1) user interface (UI) design and/or user experience (UX) design; and 2) graphic and/or visual design.</li><li>The technical bucket is made up of three categories: front-end development, back-end development, and infrastructure.</li><li>There are a number of ways to staff these skills ranging from finding an experienced generalist co-founder, which is most expensive, to outsourcing, to hiring entry level talent at the low-end. Each approach comes with it’s pros and cons.</li><li>One downside of going with less experienced talent is “technical debt”, which can increase costs down the road. Another downside is slower progress due to the learning curve.</li><li>To attract top talent, you either have to: a) have a compelling idea and be willing to give up significant equity, or 2) already have some traction and be able to pay a competitive salary and bonus. </li></ul><p><strong>What is the idea?<br></strong><br></p><p><strong>Tyler: </strong>In this episode, we’re going to talk about the ideal technical co-founder or first employee for a software company, and how to find them.</p><p><strong>Rick: </strong>I’m excited about the topic today because I’m not technical. For purposes of this conversation, let's assume it's a software application in the business-to-business (B2B) realm. Obviously, [what type of software you want to build] is going to be a determining factor. But for the purposes of this conversation, let's condense it to, “what's the right technical co-founder for a B2B software company.” This is on my mind because I just ran into a [technical] problem with <a href="https://www.groupcurrent.com/">Group Current</a>. But, it's also on my mind because as I think about <a href="https://www.legupventures.com/">LegUp Ventures</a>, which is my parent company that owns and operates [my startups], I'm starting to think about other types of software applications that I might want to build. For example, I'm still very interested in the employee benefits space outside of health insurance. I have an idea about education benefits where a company could give money to employees, tax-free, and let them go into a marketplace similar to the health insurance marketplace and peruse courses from all types of vendors [ranging] from <a href="https://www.coursera.org/">Coursera</a> to <a href="https://www.saastr.com/pro/">SaaStr</a> to, even in-person events or books on <a href="https://www.amazon.com/">Amazon</a>, buy them, and then get reimbursed tax-free by their company. I've thrown this around with a lot of people, especially millennials who are interested in going to take advantage of these new tools, and there seems to be a solid demand for it. I cannot find anyone who's delivering on this. I know exactly how this is going to work and all the technical specs. The big roadblock for me is knowing how to go about building the application in a way that I can prove [product market fit] before I raise money.</p><p><strong>Tyler:</strong> Yeah. So it seems like there's at least two parts of this. One is what skills would the ideal technical co-founder have and all that? The other one is how do you find that person?</p><p><strong>Rick:</strong> Yeah, and I would say there's a third element. So one is, yes, skillset. Two is how do you find them, and then the third is what do you call them and how do you pay them? Is it a co-founder? Is it a contractor? Is it an [outsourced] shop? Is it an employee? And what's their title? Is it engineer? Is it co-founder? Is it CTO?</p><p><strong>Tyler:</strong> Right. Okay, so where do you want to start here?</p><p><strong>Rick:</strong> Skills.</p><p><strong><br>What type of software application are you building?<br></strong><br></p><p><strong>Tyler:</strong> So you're talking about a web-based application, right? And this is something that absolutely doesn't require genius-level technical knowledge to build. Do you know the term CRUD? This is a CRUD app.</p><p><strong>Rick:</strong> CRUD sounds bad. Is CRUD bad?</p><p><strong>Tyler:</strong> No. It's Create, Read, Update, Delete. It's basically the four main database functions, and a lot of software out there is nothing more than putting stuff into a database, taking stuff out of a database, and then putting a [user interface] (UI) on top of it.</p><p><strong>Rick:</strong> Yes, and I would say that the UI for this is critical, because it's going to be a low ACV (or annual contract value) product and self service is really key.</p><p><strong>Tyler:</strong> Yeah, so the UI design might be more important than the actual technical implementation here because, with most CRUD apps, and I consider a CRM to be one as well, you don't need a <a href="https://careers.google.com/how-we-hire/">Google</a>-level genius computer science PHD to build it. Maybe you need someone who has more empathy for customers and stuff like that. Do you think the person you're talking about is going to design it, or do you think someone else is going to?</p><p><strong><br>What skills do you need to build the application?<br></strong><br></p><p><strong>Rick:</strong> So, maybe I could talk about what my skills are. It sounds like this is going to be variable based on what compliments I need. I am a terrible designer from a “look and feel” standpoint. I can wireframe a usable product. I can wireframe a vision for something, but in terms of making it an exciting experience for a user, from colors to a style, to even specific placement of elements, that's not me. But in terms of writing requirements, describing the high level technical requirements, describing the user persona, the strategy around marketing this, that's all I'm really strong at. I would love someone that is as passionate about the user experience as me, but I can't do the design, I can't code the design.</p><p><strong>Tyler:</strong> So you either need a designer and a programmer, or a jack-of-all-trades who's going to be able to do both of those? A lot of companies would have two different people for these two different roles.</p><p><strong>Rick:</strong> Well, let's assume for this conversation that I'm looking for one person to fill this void, and I'm open to calling them a co-founder. I'm also open to calling them whatever is appropriate to call them. Employee. Contractor. Outsource shop. If this is going to be one person, what are all the skills that they would need to be able to design, code, and, I guess, launch?</p><p><strong>Tyler:</strong> Yeah. So where you leave off is basically a requirement doc. Maybe you could do the wireframe, but it sounds like where does stuff...</p>]]>
      </content:encoded>
      <pubDate>Thu, 08 Aug 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/0247aac0/08875a20.mp3" length="53944514" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>3250</itunes:duration>
      <itunes:summary>In this episode, we talk about how a non-technical co-founder can launch a software product. What are the possible ways to bring on technical talent whether it be as a co-founder, a first hire, or by outsourcing?</itunes:summary>
      <itunes:subtitle>In this episode, we talk about how a non-technical co-founder can launch a software product. What are the possible ways to bring on technical talent whether it be as a co-founder, a first hire, or by outsourcing?</itunes:subtitle>
      <itunes:keywords>Saas, founder, startup, full-stack, programming</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>How an employee handbook can help with recruiting</title>
      <itunes:episode>5</itunes:episode>
      <podcast:episode>5</podcast:episode>
      <itunes:title>How an employee handbook can help with recruiting</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">326a70f4-8fd1-4b87-be43-1df283a8ab2f</guid>
      <link>https://share.transistor.fm/s/4a792376</link>
      <description>
        <![CDATA[<p><strong>What’s an employee handbook?<br></strong><br></p><p><strong>Tyler: </strong>The topic this week is employee handbooks. This has been on my mind because we redid our whole employee handbook this last spring leading up to hiring some new people. So I rewrote it and put a lot of thought into it, but I wanted to talk through it with you. I'd like to cover things like what should actually go into it. And one thing that I hadn't thought of prior to now is when and how should the information in an employee handbook be communicated. What we used to do is everybody would start working here, and then we'd give them the employee handbook and say, "read this." And more and more, I'm realizing a lot of this information might be relevant earlier in the [hiring] process. I'm interested in your thoughts on how this should work. </p><p><strong>Rick: </strong>Yeah. When I hear employee handbook. I associate it with zero value to employees and 100 percent cover your ass (CYA) for the company. I don't think that's what you're talking about here. So what do you mean by employee handbook?</p><p><strong>Tyler: </strong>Fair enough. Maybe there's a different term for this that at the end of this podcast we will have figured out. What I mean is that, over the years, we have amassed a lot of institutional knowledge on how we do things and our philosophy on things. Plus, there are a lot of policies and stuff like that. I've actually recently split it up into three things. One is company philosophy. One is information about how compensation and benefits work. And the third one is all of the various policies like: You want to take a vacation day? Here's how you do it. You want to use the nap room? Here's how you book it. That type of stuff.</p><p><br></p><p><strong>Rick: </strong>And where does the CYA, or cover your ass stuff, fit in?</p><p><strong>Tyler: </strong>We probably do that less than a lot of companies would. We do have random stuff people sign when they start like, "acknowledge that we're providing all of the benefits required by law" and stuff like that. So I think we're covering our ass to some extent, but probably not as much as some companies do. </p><p><strong>Rick: </strong>So let's call that a fourth bucket, which is different than unique policies to the company. So, one is philosophy. Second is compensation and benefits. Third, policies. And fourth, CYA. </p><p><strong>Tyler: </strong>I'm least interested in CYA because some lawyer writes that up, and no one reads it and no one cares. I'm probably more interested in the other three. What's the right information to include? And the thing that has really been on my mind is, "when?"  Should this information be made 100 percent public and used as a marketing tool for recruiting?</p><p><br></p><p><strong>Rick: </strong>I 100 percent think so. Yes. I'll give you my experience with employee handbooks. I'm unique in that, at my last company, I was there for twelve years. I've never experienced another employer, but we went through lots of iterations of the company as you well know. At first, I was the 13th employee of the company. Then, I was one of 35 employees. Then, we went down to four people. You, of course, were one of those four people. Then, we went up to 60 something 70 employees. Then we went back down to 35. Then, we were down to 20. Now, I don't even know how many people are there. And every time there was a big switch, someone at the board would say, "we need a new employee handbook." It wasn't until probably three years ago that I really took ownership of what an employee handbook was. Before that, and I think this is what most people think, I believed employee handbooks were CYA material. My experience as an employee getting an employee handbook was: "This is unhelpful. I can't understand the language. This seems like something that you're trying to screw me with."</p><p><strong>Tyler: </strong>Yeah. When you say CYA, it's so employees can't sue you and [claim] you didn't provide some piece of information. You'll be like, "look you signed this thing that said we gave you this document."</p><p><br></p><p><strong>Rick: </strong>So, over the years we had different versions of this. One was there from before I got there. Then, you know, the board was like, "we have to have an employee handbook". I was like, "why?" And they were like, "because we have to cover our asses," you know. And, I said, "OK". So we hired some third party to come in and build an employee handbook that provided no value because they had no idea about our business. So it was, again, all these new rules that I didn't even really care about honestly. It created more problems. Every time we rolled out an employee handbook, it created more problems than it solved. The last time I let someone else do this was probably four or five years ago where we had a really really smart senior vice president who knew that employee books were important.  So, she brought a third party in. I was uninvolved in the building of the handbook because I didn't care about it. I didn't think it was a priority, but I was listening to the person who was more experienced and smarter. And she was right. But, I think that an employee handbook that doesn't have your imprint on it [as the CEO] could be a really bad thing because it can send the wrong message. But the point here is that when that handbook came out, I saw it I was like, "holy crap this could provide so much value because it did touch on the philosophy stuff and it did touch on the things that employees needed to know to be successful at the company. So, I actually wrote my own handbook after that. And now the employee handbook, to me, is the most important tool of a CEO to communicate to their employees consistently and clearly. </p><p><strong>Tyler: </strong>OK. So at the beginning of this you said, "you think it's a CYA tool." You used the term employee handbook and just kind of redefined what that means to you and then thought of it as a really high priority for you. </p><p><strong>Rick:</strong> Absolutely. It went from a high company value tool with low value to employees to a very high employee value and high company value tool. </p><p><strong>Tyler: </strong>Once you decided to take ownership of it and decided this is going to be really valuable for employees, what did you put in there and did you get any feedback on it? </p><p><strong>Rick: </strong>I don't know how helpful my iterations are gonna be because I would say I learned more about what not to do than what to do. </p><p><strong>Tyler: </strong>I think those are the most valuable lessons. </p><p><strong>Rick: </strong>Well, I think you've done this well for a long time. When I started thinking about this, and I don't know if you remember this, but I said, "hey Tyler, can you send me your employee handbook?" Do you remember sending that to me? </p><p><strong>Tyler:</strong> Yeah. </p><p><strong>Rick: </strong>[Your handbook] was actually really useful. Once I realized this employee handbook thing was a good thing and not a bad thing for employees, there were a couple of companies that I looked at it [as examples]. I looked at yours. I looked at <a href="https://github.com/basecamp/handbook">Basecamp’s [employee handbook]</a>, who shares it publicly. </p><p><strong>Tyler:</strong> Yeah, there's is on <a href="https://github.com/">GitHub</a>, and you can just read the whole thing.</p><p><strong>Rick:</strong> So I looked at [Basecamp's] and I thought theirs was good, but it was a little bit different than the culture I wanted to build. And then I looked at yours, and I thought yours was really useful it. It was in a Google Doc. It was twent...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>What’s an employee handbook?<br></strong><br></p><p><strong>Tyler: </strong>The topic this week is employee handbooks. This has been on my mind because we redid our whole employee handbook this last spring leading up to hiring some new people. So I rewrote it and put a lot of thought into it, but I wanted to talk through it with you. I'd like to cover things like what should actually go into it. And one thing that I hadn't thought of prior to now is when and how should the information in an employee handbook be communicated. What we used to do is everybody would start working here, and then we'd give them the employee handbook and say, "read this." And more and more, I'm realizing a lot of this information might be relevant earlier in the [hiring] process. I'm interested in your thoughts on how this should work. </p><p><strong>Rick: </strong>Yeah. When I hear employee handbook. I associate it with zero value to employees and 100 percent cover your ass (CYA) for the company. I don't think that's what you're talking about here. So what do you mean by employee handbook?</p><p><strong>Tyler: </strong>Fair enough. Maybe there's a different term for this that at the end of this podcast we will have figured out. What I mean is that, over the years, we have amassed a lot of institutional knowledge on how we do things and our philosophy on things. Plus, there are a lot of policies and stuff like that. I've actually recently split it up into three things. One is company philosophy. One is information about how compensation and benefits work. And the third one is all of the various policies like: You want to take a vacation day? Here's how you do it. You want to use the nap room? Here's how you book it. That type of stuff.</p><p><br></p><p><strong>Rick: </strong>And where does the CYA, or cover your ass stuff, fit in?</p><p><strong>Tyler: </strong>We probably do that less than a lot of companies would. We do have random stuff people sign when they start like, "acknowledge that we're providing all of the benefits required by law" and stuff like that. So I think we're covering our ass to some extent, but probably not as much as some companies do. </p><p><strong>Rick: </strong>So let's call that a fourth bucket, which is different than unique policies to the company. So, one is philosophy. Second is compensation and benefits. Third, policies. And fourth, CYA. </p><p><strong>Tyler: </strong>I'm least interested in CYA because some lawyer writes that up, and no one reads it and no one cares. I'm probably more interested in the other three. What's the right information to include? And the thing that has really been on my mind is, "when?"  Should this information be made 100 percent public and used as a marketing tool for recruiting?</p><p><br></p><p><strong>Rick: </strong>I 100 percent think so. Yes. I'll give you my experience with employee handbooks. I'm unique in that, at my last company, I was there for twelve years. I've never experienced another employer, but we went through lots of iterations of the company as you well know. At first, I was the 13th employee of the company. Then, I was one of 35 employees. Then, we went down to four people. You, of course, were one of those four people. Then, we went up to 60 something 70 employees. Then we went back down to 35. Then, we were down to 20. Now, I don't even know how many people are there. And every time there was a big switch, someone at the board would say, "we need a new employee handbook." It wasn't until probably three years ago that I really took ownership of what an employee handbook was. Before that, and I think this is what most people think, I believed employee handbooks were CYA material. My experience as an employee getting an employee handbook was: "This is unhelpful. I can't understand the language. This seems like something that you're trying to screw me with."</p><p><strong>Tyler: </strong>Yeah. When you say CYA, it's so employees can't sue you and [claim] you didn't provide some piece of information. You'll be like, "look you signed this thing that said we gave you this document."</p><p><br></p><p><strong>Rick: </strong>So, over the years we had different versions of this. One was there from before I got there. Then, you know, the board was like, "we have to have an employee handbook". I was like, "why?" And they were like, "because we have to cover our asses," you know. And, I said, "OK". So we hired some third party to come in and build an employee handbook that provided no value because they had no idea about our business. So it was, again, all these new rules that I didn't even really care about honestly. It created more problems. Every time we rolled out an employee handbook, it created more problems than it solved. The last time I let someone else do this was probably four or five years ago where we had a really really smart senior vice president who knew that employee books were important.  So, she brought a third party in. I was uninvolved in the building of the handbook because I didn't care about it. I didn't think it was a priority, but I was listening to the person who was more experienced and smarter. And she was right. But, I think that an employee handbook that doesn't have your imprint on it [as the CEO] could be a really bad thing because it can send the wrong message. But the point here is that when that handbook came out, I saw it I was like, "holy crap this could provide so much value because it did touch on the philosophy stuff and it did touch on the things that employees needed to know to be successful at the company. So, I actually wrote my own handbook after that. And now the employee handbook, to me, is the most important tool of a CEO to communicate to their employees consistently and clearly. </p><p><strong>Tyler: </strong>OK. So at the beginning of this you said, "you think it's a CYA tool." You used the term employee handbook and just kind of redefined what that means to you and then thought of it as a really high priority for you. </p><p><strong>Rick:</strong> Absolutely. It went from a high company value tool with low value to employees to a very high employee value and high company value tool. </p><p><strong>Tyler: </strong>Once you decided to take ownership of it and decided this is going to be really valuable for employees, what did you put in there and did you get any feedback on it? </p><p><strong>Rick: </strong>I don't know how helpful my iterations are gonna be because I would say I learned more about what not to do than what to do. </p><p><strong>Tyler: </strong>I think those are the most valuable lessons. </p><p><strong>Rick: </strong>Well, I think you've done this well for a long time. When I started thinking about this, and I don't know if you remember this, but I said, "hey Tyler, can you send me your employee handbook?" Do you remember sending that to me? </p><p><strong>Tyler:</strong> Yeah. </p><p><strong>Rick: </strong>[Your handbook] was actually really useful. Once I realized this employee handbook thing was a good thing and not a bad thing for employees, there were a couple of companies that I looked at it [as examples]. I looked at yours. I looked at <a href="https://github.com/basecamp/handbook">Basecamp’s [employee handbook]</a>, who shares it publicly. </p><p><strong>Tyler:</strong> Yeah, there's is on <a href="https://github.com/">GitHub</a>, and you can just read the whole thing.</p><p><strong>Rick:</strong> So I looked at [Basecamp's] and I thought theirs was good, but it was a little bit different than the culture I wanted to build. And then I looked at yours, and I thought yours was really useful it. It was in a Google Doc. It was twent...</p>]]>
      </content:encoded>
      <pubDate>Thu, 01 Aug 2019 17:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/4a792376/11748a89.mp3" length="46436627" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2807</itunes:duration>
      <itunes:summary>This week we talk about what type of information should go in an employee handbook, and how that content can be repurposed to help with recruiting.</itunes:summary>
      <itunes:subtitle>This week we talk about what type of information should go in an employee handbook, and how that content can be repurposed to help with recruiting.</itunes:subtitle>
      <itunes:keywords>SaaS, recruiting, employee handbook</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Working remotely vs. working in an office</title>
      <itunes:episode>4</itunes:episode>
      <podcast:episode>4</podcast:episode>
      <itunes:title>Working remotely vs. working in an office</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">3f890bc6-7590-40fa-b65a-4b6c41f62188</guid>
      <link>https://share.transistor.fm/s/18122d06</link>
      <description>
        <![CDATA[<p><strong>Tyler: </strong>In this episode, we're gonna talk about the pros and cons of remote work, such as when does it make sense for a company to have employees altogether in an office versus fully remote or something in between.</p><p><strong>Rick: </strong>I personally get this all of the time. I've heard of four core models that . One is “single site” which means everyone works in the same office environment. Second, is “multi-site” where you have multiple locations with everyone working within the office. And then the third is “satellite”, in which most of the team is together, but a few people are remote. In other words, it's more of a hybrid model. And then at the complete other end of the spectrum is “remote-first” meaning everyone works from a separate location by default and then comes together when necessary to meet in-person. Does that cover the gamut of options in your opinion? </p><p><strong>Tyler: </strong>Yeah. It's kind of a sliding scale so everything in between is fair game. But, yeah. More and more, I think people work at a company with lots of people, but they work remotely or they work in coworking spaces or whatever. So the world is trying to figure out what makes sense for which companies here.</p><p><strong>Rick: </strong>In my most recent consulting project, I'm working remotely. It's the first time I've actually worked remotely for a company before. So, that was an interesting experience. I'm interested in what your experiences are with this. Do you feel like there's a right way to do this?</p><p><strong><br>“There's not a one-size-fits-all, right solution”<br></strong><br></p><p><strong>Tyler: </strong>100 percent, no. There's not a one-size-fits-all, right solution. I see a lot of arguments in favor of remote, but my experience is that, in practice, doing remote has a lot of challenges that I think get glossed over when people talk about it. So, I think there's there's pros and cons to both. Philosophically, I want remote to be the answer. But, in practice, I haven't seen that to be true so far. </p><p><strong>Rick: </strong>Before we go into pros and cons, tell me why you want remote to be the future. </p><p><strong><br>“Talent is global… if you limit yourself to a specific location, you’re limiting the talent pool”<br></strong><br></p><p><strong>Tyler: </strong>Just to name a few people [and companies] who are advocates. <a href="https://basecamp.com/books/remote">Basecamp</a> is remote-first. <a href="https://doist.com/blog/how-doist-works-remote/">Doist</a> is remote-first. If you follow the founders on Twitter, they talk about this a lot. I buy the argument that talent is global. It's spread out all over the place, and your company should be trying to hire the best people possible. And if you limit yourself to a specific location, you’re limiting the talent pool. The other [argument] is that we are all adults. There’s something that seems almost like an industrial-age assembly line about having everyone commute to the same place and sit in desks next to each other in order to get work done. The internet is a thing. It doesn't seem like we should need to be next to each other. So that's why I feel like it should work. </p><p><strong>Rick: </strong>So one [argument] is that [remote-first] allows you to attract a better breadth of talent from different locations. More diversity and people that you would never even think of hiring at a co-located place. And then on the second argument, I understand that you don't like the industrial nine-to-five feel of an office. But, what is it that you would replace it with?</p><p><strong>Tyler:</strong> Well I like the idea of if you get your work done, as the boss, it’s not my business how it happens. Historically, I feel like too many employers felt like they owned their employees. I mean historically they actually did and that was obviously terrible. </p><p><strong>Rick: </strong>Are you talking about slavery?</p><p><strong>Tyler: </strong>Yes. We haven't broken out of that fully, we're still, I think-- plutocrats exert way too much control over the people who work for them.</p><p><strong>Rick:</strong> Wait, what's a plutocrat?</p><p><strong><br>A plutocrat is a person whose power derives from their wealth.<br></strong><br></p><p><strong>Tyler: </strong>Rich people who run the world, basically.</p><p><strong>Rick: </strong>Are you a plutocrat?</p><p><strong>Tyler: </strong>I'm working on it. [laughs]</p><p><strong>Rick: </strong>All right. Sorry. Keep going.</p><p><strong>Tyler: </strong>Basically, like what you and I are doing right now. You're in Utah. I'm in Missouri. This is fine. We're both adults. We're getting this thing done. Should I have to fly to you every week in order to record a podcast? Of course not. Why does everyone have to drive to the same office to get work done?</p><p><strong><br>Employees gain autonomy and flexibility from remote work<br></strong><br></p><p><strong>Rick: </strong>There's a lot of benefits [to co-location] that we'll go through later, but what I'm trying to get to is what is it that you gain from [remote-first] as an employee?</p><p><strong>Tyler: </strong>I think it's autonomy. You get to decide where you live, you get to decide, "Do I want a standing desk? What kind of chair do I want?" You just have total control of your work environment. </p><p><strong>Rick: </strong>Flexibility. Employee flexibility. Got it. Yes, it's the ultimate flexibility. Get the job done, work when you need to. I don't think that always applies. For some roles, you will need to be available whether you're remote or co-located at a certain time.</p><p><strong>Tyler: </strong>Yes, there is time flexibility, but that's maybe orthogonal<strong> </strong>to environment flexibility.</p><p><strong>Rick: </strong>You're killing me with these words. What's orthogonal?</p><p><strong><br>In statistics, orthogonal means statistically independent<br></strong><br></p><p><strong>Tyler: </strong>Perpendicular. It's like an unrelated thing.</p><p><strong>Rick: </strong>They cross over each other?</p><p><strong>Tyler: </strong>Yes, it's just that they're pointing in different directions. These are two points. Your time flexibility is almost completely independent of your location flexibility. Support needs to be on at a certain time, they don't necessarily need to be in the office to do their job.</p><p><strong>Rick: </strong>Location flexibility is really what you're arguing for here?</p><p><strong>Tyler: </strong>Yes.</p><p><strong>Rick: </strong>I like it. There's also work environment flexibility, which gives the employee choice on the desks and stuff. I get it. What's stopping us, in your opinion, from getting to where everyone's working remote?</p><p><strong><br>“It's very, very lonely to work remotely”<br></strong><br></p><p><strong>Tyler: </strong>My company is not remote for the most part. We have a little bit of a hybrid model, but we’re mostly not remote. Obviously, despite my philosophical agreement with it, I think there are some real practical problems. I can just rattle off a few. One is, it's very, very lonely to work remotely, especially if that means you're working from home. Remote can also mean going to a co-working space and being around people, but those aren't the people you're working with, so I think there's still an opportunity for loneliness there. I don't know if you've ever done that type of thing.</p><p><strong>Rick: </strong>I am a little bit different in this regard. I actually like to be by myself, so I can't relate to this. In fact, when I see ...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Tyler: </strong>In this episode, we're gonna talk about the pros and cons of remote work, such as when does it make sense for a company to have employees altogether in an office versus fully remote or something in between.</p><p><strong>Rick: </strong>I personally get this all of the time. I've heard of four core models that . One is “single site” which means everyone works in the same office environment. Second, is “multi-site” where you have multiple locations with everyone working within the office. And then the third is “satellite”, in which most of the team is together, but a few people are remote. In other words, it's more of a hybrid model. And then at the complete other end of the spectrum is “remote-first” meaning everyone works from a separate location by default and then comes together when necessary to meet in-person. Does that cover the gamut of options in your opinion? </p><p><strong>Tyler: </strong>Yeah. It's kind of a sliding scale so everything in between is fair game. But, yeah. More and more, I think people work at a company with lots of people, but they work remotely or they work in coworking spaces or whatever. So the world is trying to figure out what makes sense for which companies here.</p><p><strong>Rick: </strong>In my most recent consulting project, I'm working remotely. It's the first time I've actually worked remotely for a company before. So, that was an interesting experience. I'm interested in what your experiences are with this. Do you feel like there's a right way to do this?</p><p><strong><br>“There's not a one-size-fits-all, right solution”<br></strong><br></p><p><strong>Tyler: </strong>100 percent, no. There's not a one-size-fits-all, right solution. I see a lot of arguments in favor of remote, but my experience is that, in practice, doing remote has a lot of challenges that I think get glossed over when people talk about it. So, I think there's there's pros and cons to both. Philosophically, I want remote to be the answer. But, in practice, I haven't seen that to be true so far. </p><p><strong>Rick: </strong>Before we go into pros and cons, tell me why you want remote to be the future. </p><p><strong><br>“Talent is global… if you limit yourself to a specific location, you’re limiting the talent pool”<br></strong><br></p><p><strong>Tyler: </strong>Just to name a few people [and companies] who are advocates. <a href="https://basecamp.com/books/remote">Basecamp</a> is remote-first. <a href="https://doist.com/blog/how-doist-works-remote/">Doist</a> is remote-first. If you follow the founders on Twitter, they talk about this a lot. I buy the argument that talent is global. It's spread out all over the place, and your company should be trying to hire the best people possible. And if you limit yourself to a specific location, you’re limiting the talent pool. The other [argument] is that we are all adults. There’s something that seems almost like an industrial-age assembly line about having everyone commute to the same place and sit in desks next to each other in order to get work done. The internet is a thing. It doesn't seem like we should need to be next to each other. So that's why I feel like it should work. </p><p><strong>Rick: </strong>So one [argument] is that [remote-first] allows you to attract a better breadth of talent from different locations. More diversity and people that you would never even think of hiring at a co-located place. And then on the second argument, I understand that you don't like the industrial nine-to-five feel of an office. But, what is it that you would replace it with?</p><p><strong>Tyler:</strong> Well I like the idea of if you get your work done, as the boss, it’s not my business how it happens. Historically, I feel like too many employers felt like they owned their employees. I mean historically they actually did and that was obviously terrible. </p><p><strong>Rick: </strong>Are you talking about slavery?</p><p><strong>Tyler: </strong>Yes. We haven't broken out of that fully, we're still, I think-- plutocrats exert way too much control over the people who work for them.</p><p><strong>Rick:</strong> Wait, what's a plutocrat?</p><p><strong><br>A plutocrat is a person whose power derives from their wealth.<br></strong><br></p><p><strong>Tyler: </strong>Rich people who run the world, basically.</p><p><strong>Rick: </strong>Are you a plutocrat?</p><p><strong>Tyler: </strong>I'm working on it. [laughs]</p><p><strong>Rick: </strong>All right. Sorry. Keep going.</p><p><strong>Tyler: </strong>Basically, like what you and I are doing right now. You're in Utah. I'm in Missouri. This is fine. We're both adults. We're getting this thing done. Should I have to fly to you every week in order to record a podcast? Of course not. Why does everyone have to drive to the same office to get work done?</p><p><strong><br>Employees gain autonomy and flexibility from remote work<br></strong><br></p><p><strong>Rick: </strong>There's a lot of benefits [to co-location] that we'll go through later, but what I'm trying to get to is what is it that you gain from [remote-first] as an employee?</p><p><strong>Tyler: </strong>I think it's autonomy. You get to decide where you live, you get to decide, "Do I want a standing desk? What kind of chair do I want?" You just have total control of your work environment. </p><p><strong>Rick: </strong>Flexibility. Employee flexibility. Got it. Yes, it's the ultimate flexibility. Get the job done, work when you need to. I don't think that always applies. For some roles, you will need to be available whether you're remote or co-located at a certain time.</p><p><strong>Tyler: </strong>Yes, there is time flexibility, but that's maybe orthogonal<strong> </strong>to environment flexibility.</p><p><strong>Rick: </strong>You're killing me with these words. What's orthogonal?</p><p><strong><br>In statistics, orthogonal means statistically independent<br></strong><br></p><p><strong>Tyler: </strong>Perpendicular. It's like an unrelated thing.</p><p><strong>Rick: </strong>They cross over each other?</p><p><strong>Tyler: </strong>Yes, it's just that they're pointing in different directions. These are two points. Your time flexibility is almost completely independent of your location flexibility. Support needs to be on at a certain time, they don't necessarily need to be in the office to do their job.</p><p><strong>Rick: </strong>Location flexibility is really what you're arguing for here?</p><p><strong>Tyler: </strong>Yes.</p><p><strong>Rick: </strong>I like it. There's also work environment flexibility, which gives the employee choice on the desks and stuff. I get it. What's stopping us, in your opinion, from getting to where everyone's working remote?</p><p><strong><br>“It's very, very lonely to work remotely”<br></strong><br></p><p><strong>Tyler: </strong>My company is not remote for the most part. We have a little bit of a hybrid model, but we’re mostly not remote. Obviously, despite my philosophical agreement with it, I think there are some real practical problems. I can just rattle off a few. One is, it's very, very lonely to work remotely, especially if that means you're working from home. Remote can also mean going to a co-working space and being around people, but those aren't the people you're working with, so I think there's still an opportunity for loneliness there. I don't know if you've ever done that type of thing.</p><p><strong>Rick: </strong>I am a little bit different in this regard. I actually like to be by myself, so I can't relate to this. In fact, when I see ...</p>]]>
      </content:encoded>
      <pubDate>Thu, 25 Jul 2019 18:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/18122d06/d5ae0355.mp3" length="44550814" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2696</itunes:duration>
      <itunes:summary>Rick and Tyler talk about the pros and cons of a company having a remote workforce vs. having everyone working in the same office.</itunes:summary>
      <itunes:subtitle>Rick and Tyler talk about the pros and cons of a company having a remote workforce vs. having everyone working in the same office.</itunes:subtitle>
      <itunes:keywords>Saas, Remote, office, culture</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>The role of a CEO</title>
      <itunes:episode>3</itunes:episode>
      <podcast:episode>3</podcast:episode>
      <itunes:title>The role of a CEO</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">8a3507e7-45a9-4103-b51a-9c3a4f47133c</guid>
      <link>https://share.transistor.fm/s/db8db725</link>
      <description>
        <![CDATA[<p><strong>The role of a small business or startup CEO<br></strong><br></p><p><strong>Tyler: </strong>In this episode, we're going to talk about what the role of a CEO should be at a small business or a startup. I always hesitate to call myself a CEO, depending on who I'm talking to because it seems a little pretentious. I run a 17-person company and some days, I don't do any CEO stuff: I just write code or design something. And some days I'm in meetings and brainstorming long term product vision and I feel more like a CEO. I'm a little unclear on when's the right time for a founder, especially a bootstrapped founder, where you're not representing shareholders or anything like that, when's the right time for them to let go of the individual contributor role and just really embrace, “my role is to be the boss of the company” and all the actual work that gets done is getting done by other people?</p><p><strong>Rick: </strong>I don't know exactly where to start with this. I'm very interested in the subject too. My immediate reaction is, I don't think that this is written in stone. It seems very circumstantial and honestly, subject to what the person has decided what their role is going to be, how they're going to play the CEO role, how they're going to spend their time. I guess, you keep saying CEO role. Maybe we can start with, what is uniquely the CEO role at all stages of companies?</p><p><strong>Tyler: </strong>Yeah and you probably know this better than me because I think you've experienced different stages. What I have seen myself is, there's individual contributor work. If you come from sales, go to sales. If you're a marketer, do marketing. There's management, which I feel like I've stepped into. We're big enough at this point where it's, “okay, there's a programmer who needs a manager.” We don't have a manager for that person, so I'm their manager. There's a manager of managers, where I've got someone who manages the customer service team but someone needs to talk to him and then I guess there's other stuff, right? Do you agree with those three categories at least? Those kind of evolutionary steps as a business grows?</p><p><strong>Rick: </strong>I would say that that's the different types of management but not necessarily… I know CEOs who have one report.</p><p><strong>Tyler:</strong> Yeah, absolutely. I kind of think of all three of those as not fully CEO work but I'm not sure what ... There's some fourth category which is CEO work. What do you think that is?</p><p><strong>Rick: </strong>I guess I would look at it a different way. I wouldn't look at it as, primarily a ... I wouldn't look at it from a people management standpoint, I would say there are three ... I'm going to butcher this but someone told me this once and I'll try to remember it as best I can. The role of the CEO is three or four things. The first is making sure that there's enough money in the bank. The second is making sure everyone is aligned on what the priorities are for the company. The third is building a cohesive team to ... and whatever that means retaining, training, managing, recruiting…</p><p><br></p><p><strong>Tyler: </strong>Just making sure it happens.</p><p><strong>Rick:</strong> … making sure you have the right people and I can't remember the fourth.</p><p><strong>Tyler:</strong> Yeah and I actually think I coincidentally saw someone retweet this today.</p><p><strong>Rick: </strong>I kind of look at a CEO's role as, either those three things are happening or they're not and if they're happening, the CEOs doing a good job, right? If you've got enough money in the bank, everyone is clear on what the priorities are, the team is cohesive and you've got a solid pipeline of talent to fill future needs, then the CEO is probably doing a pretty darn good job. How much time is it taking him to do that?</p><p><strong>Tyler:</strong> Right, maybe none-</p><p><strong>Rick: </strong>Maybe none.</p><p><strong>Tyler:</strong> -depending on the company.</p><p><strong>Rick: </strong>And if there's free time, maybe there's some opportunities to dabble as an individual contributor. If it's taking all of your time to do those three things, maybe some of those things you're doing as an individual contributor.</p><p><strong>Tyler:</strong> Yeah, I can relate to the second one, having a vision or whatever. At <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a>, we don't have a strategy aside from the product. The whole company is about execution and then the strategy is, where is the product going? And that's my individual contributor work. Product design. So I think that's an example of what you're saying.</p><p><strong>Rick: </strong>Yup, yup and so it sounds like you do a lot of individual contributions on setting, what are the priorities for the company? And that's great. </p><p><strong>Tyler:</strong> And I love that stuff.</p><p><strong>Rick: </strong>And I guess stepping back, when you say individual ... I'm interested in why you brought this up, number one, is this something that's bothering you? And two, what do you mean by individual contribution? I understand now what you mean by CEO role but what crosses into individual contributor work versus non individual contributor work?</p><p><strong>Tyler: </strong>Yeah, so I wouldn't say this is something I'm worried about or that I have a problem or anything but what I notice in myself is, from time to time, I enjoy having periods where I'm meeting with a lot of people and having high level brainstorming and stuff like that but I really really love it when I have a day or ... I never have a full week but a good chunk of the week where I'm just not talking to anybody, on my computer, either designing or programming. When I say individual contributor work, I guess what I mean is, I'm not managing or leveraging other people's work but instead I'm saying, "The work I'm doing is directly moving the company where it's going, rather than setting a vision that other people are going to follow."</p><p><strong>Rick: </strong>Would you consider that, setting the vision, individual contributor work?</p><p><strong>Tyler: </strong>Yeah, I mean I guess it's on the border. It's half and half but so for me, I'm doing the design because I think it's cool. Oh, I really want to design this, versus, I can't wait for the rest of the team to follow this grand vision, you know?</p><p><strong>Rick: </strong>It sounds like, if we agree that the role of the CEO is to do those three things, make sure there's enough money in the bank, set the vision, make sure the priorities are clear, create clarity and then build the team, then anything outside of that, that is done as an individual contributor, on your own, would be what you're talking about.</p><p><strong>Tyler:</strong> Right, so writing code is definitely individual contributor work.</p><p><strong>Rick:</strong> Yeah, okay.</p><p><strong>Tyler:</strong> Design is ... If it's like, we need this feature and I'm designing it, that's IC work. If it's what is the-</p><p><strong>Rick: </strong>IC?</p><p><strong>Tyler:</strong> Individual contributor.</p><p><strong>Rick:</strong> Is this the new lingo? Is this an acronym?</p><p><strong>Tyler:</strong> I don't know. That's how they write it on the Twitters.</p><p><strong>Rick: </strong>The Twitters?</p><p><strong>Tyler:</strong> Yeah but if I'm designing some future project that maybe we will or won't do but it's a strategic thing, then that's probably CEO work. Okay, I buy that distinction.</p><p><strong>Rick:</strong> Okay. What types of individual contributor work do y...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>The role of a small business or startup CEO<br></strong><br></p><p><strong>Tyler: </strong>In this episode, we're going to talk about what the role of a CEO should be at a small business or a startup. I always hesitate to call myself a CEO, depending on who I'm talking to because it seems a little pretentious. I run a 17-person company and some days, I don't do any CEO stuff: I just write code or design something. And some days I'm in meetings and brainstorming long term product vision and I feel more like a CEO. I'm a little unclear on when's the right time for a founder, especially a bootstrapped founder, where you're not representing shareholders or anything like that, when's the right time for them to let go of the individual contributor role and just really embrace, “my role is to be the boss of the company” and all the actual work that gets done is getting done by other people?</p><p><strong>Rick: </strong>I don't know exactly where to start with this. I'm very interested in the subject too. My immediate reaction is, I don't think that this is written in stone. It seems very circumstantial and honestly, subject to what the person has decided what their role is going to be, how they're going to play the CEO role, how they're going to spend their time. I guess, you keep saying CEO role. Maybe we can start with, what is uniquely the CEO role at all stages of companies?</p><p><strong>Tyler: </strong>Yeah and you probably know this better than me because I think you've experienced different stages. What I have seen myself is, there's individual contributor work. If you come from sales, go to sales. If you're a marketer, do marketing. There's management, which I feel like I've stepped into. We're big enough at this point where it's, “okay, there's a programmer who needs a manager.” We don't have a manager for that person, so I'm their manager. There's a manager of managers, where I've got someone who manages the customer service team but someone needs to talk to him and then I guess there's other stuff, right? Do you agree with those three categories at least? Those kind of evolutionary steps as a business grows?</p><p><strong>Rick: </strong>I would say that that's the different types of management but not necessarily… I know CEOs who have one report.</p><p><strong>Tyler:</strong> Yeah, absolutely. I kind of think of all three of those as not fully CEO work but I'm not sure what ... There's some fourth category which is CEO work. What do you think that is?</p><p><strong>Rick: </strong>I guess I would look at it a different way. I wouldn't look at it as, primarily a ... I wouldn't look at it from a people management standpoint, I would say there are three ... I'm going to butcher this but someone told me this once and I'll try to remember it as best I can. The role of the CEO is three or four things. The first is making sure that there's enough money in the bank. The second is making sure everyone is aligned on what the priorities are for the company. The third is building a cohesive team to ... and whatever that means retaining, training, managing, recruiting…</p><p><br></p><p><strong>Tyler: </strong>Just making sure it happens.</p><p><strong>Rick:</strong> … making sure you have the right people and I can't remember the fourth.</p><p><strong>Tyler:</strong> Yeah and I actually think I coincidentally saw someone retweet this today.</p><p><strong>Rick: </strong>I kind of look at a CEO's role as, either those three things are happening or they're not and if they're happening, the CEOs doing a good job, right? If you've got enough money in the bank, everyone is clear on what the priorities are, the team is cohesive and you've got a solid pipeline of talent to fill future needs, then the CEO is probably doing a pretty darn good job. How much time is it taking him to do that?</p><p><strong>Tyler:</strong> Right, maybe none-</p><p><strong>Rick: </strong>Maybe none.</p><p><strong>Tyler:</strong> -depending on the company.</p><p><strong>Rick: </strong>And if there's free time, maybe there's some opportunities to dabble as an individual contributor. If it's taking all of your time to do those three things, maybe some of those things you're doing as an individual contributor.</p><p><strong>Tyler:</strong> Yeah, I can relate to the second one, having a vision or whatever. At <a href="https://www.lessannoyingcrm.com/">Less Annoying CRM</a>, we don't have a strategy aside from the product. The whole company is about execution and then the strategy is, where is the product going? And that's my individual contributor work. Product design. So I think that's an example of what you're saying.</p><p><strong>Rick: </strong>Yup, yup and so it sounds like you do a lot of individual contributions on setting, what are the priorities for the company? And that's great. </p><p><strong>Tyler:</strong> And I love that stuff.</p><p><strong>Rick: </strong>And I guess stepping back, when you say individual ... I'm interested in why you brought this up, number one, is this something that's bothering you? And two, what do you mean by individual contribution? I understand now what you mean by CEO role but what crosses into individual contributor work versus non individual contributor work?</p><p><strong>Tyler: </strong>Yeah, so I wouldn't say this is something I'm worried about or that I have a problem or anything but what I notice in myself is, from time to time, I enjoy having periods where I'm meeting with a lot of people and having high level brainstorming and stuff like that but I really really love it when I have a day or ... I never have a full week but a good chunk of the week where I'm just not talking to anybody, on my computer, either designing or programming. When I say individual contributor work, I guess what I mean is, I'm not managing or leveraging other people's work but instead I'm saying, "The work I'm doing is directly moving the company where it's going, rather than setting a vision that other people are going to follow."</p><p><strong>Rick: </strong>Would you consider that, setting the vision, individual contributor work?</p><p><strong>Tyler: </strong>Yeah, I mean I guess it's on the border. It's half and half but so for me, I'm doing the design because I think it's cool. Oh, I really want to design this, versus, I can't wait for the rest of the team to follow this grand vision, you know?</p><p><strong>Rick: </strong>It sounds like, if we agree that the role of the CEO is to do those three things, make sure there's enough money in the bank, set the vision, make sure the priorities are clear, create clarity and then build the team, then anything outside of that, that is done as an individual contributor, on your own, would be what you're talking about.</p><p><strong>Tyler:</strong> Right, so writing code is definitely individual contributor work.</p><p><strong>Rick:</strong> Yeah, okay.</p><p><strong>Tyler:</strong> Design is ... If it's like, we need this feature and I'm designing it, that's IC work. If it's what is the-</p><p><strong>Rick: </strong>IC?</p><p><strong>Tyler:</strong> Individual contributor.</p><p><strong>Rick:</strong> Is this the new lingo? Is this an acronym?</p><p><strong>Tyler:</strong> I don't know. That's how they write it on the Twitters.</p><p><strong>Rick: </strong>The Twitters?</p><p><strong>Tyler:</strong> Yeah but if I'm designing some future project that maybe we will or won't do but it's a strategic thing, then that's probably CEO work. Okay, I buy that distinction.</p><p><strong>Rick:</strong> Okay. What types of individual contributor work do y...</p>]]>
      </content:encoded>
      <pubDate>Thu, 18 Jul 2019 18:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/db8db725/5871c7aa.mp3" length="47387181" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2959</itunes:duration>
      <itunes:summary>In this episode we talk about Rick's customer development efforts, Tyler's new mastermind group, and what the role of a CEO should be as a company grows.</itunes:summary>
      <itunes:subtitle>In this episode we talk about Rick's customer development efforts, Tyler's new mastermind group, and what the role of a CEO should be as a company grows.</itunes:subtitle>
      <itunes:keywords>SaaS, bootstrap, CEO</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Impostor syndrome and fear-based decision making</title>
      <itunes:episode>2</itunes:episode>
      <podcast:episode>2</podcast:episode>
      <itunes:title>Impostor syndrome and fear-based decision making</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b2ef92a8-f73f-4b2c-aaf2-00944ee07d3e</guid>
      <link>https://share.transistor.fm/s/822fa4f3</link>
      <description>
        <![CDATA[<p><strong>Tyler: </strong>In this episode, we're going to talk about impostor syndrome. Do you want to kind of explain what you had in mind here?</p><p><strong>Rick:</strong> Yeah. So you know this. I left PeopleKeep after 11 years. For most of the time, I was the leader of the company under various titles, most recently CEO. I left in October. So it's been about nine months now.</p><p><br></p><p><strong>Rick:</strong> One of the big reflections I had was sometimes how I treated people. Sometimes I was super impatient with people and put certain immediate business goals over really trying to make people feel good about what we were doing or where we were going. And I regret those moments because it was so short sighted, right? And so, as I look back and analyze why did I do that? I think a lot of those situations where fear-based. I was scared of missing a short-term goal, or I was scared of what I want to talk to you today about. Feeling like I might be found out as a fraud, as a CEO. And so I want to talk to you about this because I wonder if you ever feel this way? I guess impostor syndrome could be defined as a fear of being found out as a fraud. But I would go a step further and say, do you ever feel like a fraud in your job or catch yourself making decisions not based on what's right but out of fear?</p><p><strong>Tyler: </strong>Yeah, I mean, okay. So I definitely feel like a fraud all the time. I'm of the opinion that the only people who aren't are sociopaths. Everyone I've ever talked to no matter how accomplished they are, everyone's like, “Oh, I don't belong here. Everyone's smarter than me,” and all that. I definitely feel that way just constantly, yeah. It's surprising to me to hear that you did so much.</p><p><strong>Rick: </strong>Oh, yeah. Constantly. And I think it caused me to work a lot more than I needed to. That's the fear of failure. It caused me to stress and worry about things that were outside of my control unproductively, and I think it caused me in certain situations to make the wrong decision.</p><p><strong>Tyler:</strong> Interesting. Yeah. Well, so the reason I was surprised to hear that is because on the surface maybe more than anyone I've ever met you seem like the classic CEO type.</p><p><strong>Rick:</strong> Are you calling me a sociopath?</p><p><strong>Tyler:</strong> No, no. What I mean is you're type A personality. Do you agree with that?</p><p><strong>Rick: </strong>Define a type A personality?</p><p><strong>Tyler: </strong>Like you... Well, yeah, maybe I don't have the best definition. But I interpret that to mean like, you aren't afraid of conflict. You kind of say what you mean. You're just kind of a person who's in control and likes being in control. And maybe this was me just not seeing what's beneath the surface, but you work really hard. You read a million books, you network, you make connections. To be honest, half my impostor syndrome comes from looking at you and being like, oh, no, that's what a CEO looks like. I'm not doing any of that stuff.</p><p><strong><br>Fear-based decisions and regret<br></strong><br></p><p><strong>Rick:</strong> The interesting thing to me isn't to discuss whether people feel this way because I think everyone does. I think what's scary is... I think what I reflected on was not necessarily that I had this, it's how I dealt with it.</p><p><strong>Tyler: </strong>Okay.</p><p><strong>Rick: </strong>And so, I think that, let's assume for purposes of this part of the conversation that everyone has some feelings of impostor syndrome or being fraud. And that's a fear thing. What I think in certain situations I did was, let that dominate my emotions. And that could have resulted in me not being thoughtful about how I was communicating with someone in a moment, or making a decision that was fear-based versus opportunistic. I hypothesize that a lot of decisions leaders make, they make out of fear and maybe those are the decisions that they regret the most. Does that resonate with you?</p><p><br></p><p><strong>Tyler: </strong>Yeah. I think I have a very different reaction to it than you do. I think that using kind of generic words like fear and regretting a decision, I think those still apply, but like, it takes a very different form for me. But yeah, definitely. I'm trying to think of the worst decisions that I've made.</p><p><strong>Tyler:</strong> The number one worst one was certainly made out of fear, although I'm not sure it's a fear that was rooted in feeling like an impostor. And that was that I had an employee that I needed to fire. It was obvious to me that I did but I was just like, oh, I'll make it work, this or that. And I just waited for him to quit and he did eventually, thankfully, because it could have dragged on forever. But that's by far when I look back at myself as a leader. That's my weakest moment ever. It was fear-based. I don't think it was impostor syndrome based for me.</p><p><strong>Rick: </strong>What was the fear?</p><p><strong>Tyler: </strong>Well, first of all, I just hate confrontation. I guess this is maybe a little different from impostor syndrome. Part of it is that I took a big risk hiring him and I convinced him to take a big risk accepting the offer. And you're admitting you failed is one of the things. Now, I'm normally not too afraid of failure, but when it's really impacting another person's livelihood or something like that, the pressure is really high. And I think I was just afraid to say, I'm putting an end to this. I don't know.</p><p><br></p><p><strong>Tyler:</strong> I've definitely had other moments though, where... The thing is, I think my reaction to impostor syndrome is to remove all of the things that I feel unconfident about. And so it's less. I think maybe it sounds like you were saying you kind of lash out almost. I do the opposite. I withdraw and say, "Oh, well. I don't think I'm good enough of a leader to do this thing. I'm just not going to do it." The company doesn't do that. That's not in our core competency.</p><p><strong>Rick: </strong>Interesting. So yeah, maybe it kind of gets into fight or flight.</p><p><strong>Tyler:</strong> Mm-hmm (affirmative).</p><p><strong>Rick: </strong>I have a fight response, while you have a flight response.</p><p><strong>Tyler:</strong> Yeah, when you were talking I was thinking exactly that. You're one of those animals that gets real violent when they're backed into a corner.</p><p><strong>Rick: </strong>Yeah, when I've been under the anesthesia for surgeries before, and I had to learn this, I always forget because I don't get surgeries very often, but I do know this now. Before I go under, I have to tell them when they bring me out of the anesthesia they have to tie me down because… </p><p><strong>Tyler: </strong>Wow.</p><p><strong>Rick:</strong> ... I come out and I come out swinging. Which isn't great when you're getting a shoulder surgery.</p><p><strong>Tyler:</strong> Yeah, seriously. Wow. I didn't even know that was a thing. But yeah, I mean, I don't want to...</p><p><strong>Rick:</strong> You probably come out going boohoohoo!</p><p><strong>Tyler: </strong>Yeah, probably crying about something awkward I did in third grade. But yeah, okay. So I think we're saying we experience the same things, but we have very different reactions to them.</p><p><br></p><p><strong>Rick:</strong> Yeah, but do you regret that reaction? I guess, do you feel like you're missing out on... Are you fleeing from something and making decisions for the company that are fear-based, flight-based that aren't the right decisions?</p><p><strong>Tyler: </strong>This may be taking...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Tyler: </strong>In this episode, we're going to talk about impostor syndrome. Do you want to kind of explain what you had in mind here?</p><p><strong>Rick:</strong> Yeah. So you know this. I left PeopleKeep after 11 years. For most of the time, I was the leader of the company under various titles, most recently CEO. I left in October. So it's been about nine months now.</p><p><br></p><p><strong>Rick:</strong> One of the big reflections I had was sometimes how I treated people. Sometimes I was super impatient with people and put certain immediate business goals over really trying to make people feel good about what we were doing or where we were going. And I regret those moments because it was so short sighted, right? And so, as I look back and analyze why did I do that? I think a lot of those situations where fear-based. I was scared of missing a short-term goal, or I was scared of what I want to talk to you today about. Feeling like I might be found out as a fraud, as a CEO. And so I want to talk to you about this because I wonder if you ever feel this way? I guess impostor syndrome could be defined as a fear of being found out as a fraud. But I would go a step further and say, do you ever feel like a fraud in your job or catch yourself making decisions not based on what's right but out of fear?</p><p><strong>Tyler: </strong>Yeah, I mean, okay. So I definitely feel like a fraud all the time. I'm of the opinion that the only people who aren't are sociopaths. Everyone I've ever talked to no matter how accomplished they are, everyone's like, “Oh, I don't belong here. Everyone's smarter than me,” and all that. I definitely feel that way just constantly, yeah. It's surprising to me to hear that you did so much.</p><p><strong>Rick: </strong>Oh, yeah. Constantly. And I think it caused me to work a lot more than I needed to. That's the fear of failure. It caused me to stress and worry about things that were outside of my control unproductively, and I think it caused me in certain situations to make the wrong decision.</p><p><strong>Tyler:</strong> Interesting. Yeah. Well, so the reason I was surprised to hear that is because on the surface maybe more than anyone I've ever met you seem like the classic CEO type.</p><p><strong>Rick:</strong> Are you calling me a sociopath?</p><p><strong>Tyler:</strong> No, no. What I mean is you're type A personality. Do you agree with that?</p><p><strong>Rick: </strong>Define a type A personality?</p><p><strong>Tyler: </strong>Like you... Well, yeah, maybe I don't have the best definition. But I interpret that to mean like, you aren't afraid of conflict. You kind of say what you mean. You're just kind of a person who's in control and likes being in control. And maybe this was me just not seeing what's beneath the surface, but you work really hard. You read a million books, you network, you make connections. To be honest, half my impostor syndrome comes from looking at you and being like, oh, no, that's what a CEO looks like. I'm not doing any of that stuff.</p><p><strong><br>Fear-based decisions and regret<br></strong><br></p><p><strong>Rick:</strong> The interesting thing to me isn't to discuss whether people feel this way because I think everyone does. I think what's scary is... I think what I reflected on was not necessarily that I had this, it's how I dealt with it.</p><p><strong>Tyler: </strong>Okay.</p><p><strong>Rick: </strong>And so, I think that, let's assume for purposes of this part of the conversation that everyone has some feelings of impostor syndrome or being fraud. And that's a fear thing. What I think in certain situations I did was, let that dominate my emotions. And that could have resulted in me not being thoughtful about how I was communicating with someone in a moment, or making a decision that was fear-based versus opportunistic. I hypothesize that a lot of decisions leaders make, they make out of fear and maybe those are the decisions that they regret the most. Does that resonate with you?</p><p><br></p><p><strong>Tyler: </strong>Yeah. I think I have a very different reaction to it than you do. I think that using kind of generic words like fear and regretting a decision, I think those still apply, but like, it takes a very different form for me. But yeah, definitely. I'm trying to think of the worst decisions that I've made.</p><p><strong>Tyler:</strong> The number one worst one was certainly made out of fear, although I'm not sure it's a fear that was rooted in feeling like an impostor. And that was that I had an employee that I needed to fire. It was obvious to me that I did but I was just like, oh, I'll make it work, this or that. And I just waited for him to quit and he did eventually, thankfully, because it could have dragged on forever. But that's by far when I look back at myself as a leader. That's my weakest moment ever. It was fear-based. I don't think it was impostor syndrome based for me.</p><p><strong>Rick: </strong>What was the fear?</p><p><strong>Tyler: </strong>Well, first of all, I just hate confrontation. I guess this is maybe a little different from impostor syndrome. Part of it is that I took a big risk hiring him and I convinced him to take a big risk accepting the offer. And you're admitting you failed is one of the things. Now, I'm normally not too afraid of failure, but when it's really impacting another person's livelihood or something like that, the pressure is really high. And I think I was just afraid to say, I'm putting an end to this. I don't know.</p><p><br></p><p><strong>Tyler:</strong> I've definitely had other moments though, where... The thing is, I think my reaction to impostor syndrome is to remove all of the things that I feel unconfident about. And so it's less. I think maybe it sounds like you were saying you kind of lash out almost. I do the opposite. I withdraw and say, "Oh, well. I don't think I'm good enough of a leader to do this thing. I'm just not going to do it." The company doesn't do that. That's not in our core competency.</p><p><strong>Rick: </strong>Interesting. So yeah, maybe it kind of gets into fight or flight.</p><p><strong>Tyler:</strong> Mm-hmm (affirmative).</p><p><strong>Rick: </strong>I have a fight response, while you have a flight response.</p><p><strong>Tyler:</strong> Yeah, when you were talking I was thinking exactly that. You're one of those animals that gets real violent when they're backed into a corner.</p><p><strong>Rick: </strong>Yeah, when I've been under the anesthesia for surgeries before, and I had to learn this, I always forget because I don't get surgeries very often, but I do know this now. Before I go under, I have to tell them when they bring me out of the anesthesia they have to tie me down because… </p><p><strong>Tyler: </strong>Wow.</p><p><strong>Rick:</strong> ... I come out and I come out swinging. Which isn't great when you're getting a shoulder surgery.</p><p><strong>Tyler:</strong> Yeah, seriously. Wow. I didn't even know that was a thing. But yeah, I mean, I don't want to...</p><p><strong>Rick:</strong> You probably come out going boohoohoo!</p><p><strong>Tyler: </strong>Yeah, probably crying about something awkward I did in third grade. But yeah, okay. So I think we're saying we experience the same things, but we have very different reactions to them.</p><p><br></p><p><strong>Rick:</strong> Yeah, but do you regret that reaction? I guess, do you feel like you're missing out on... Are you fleeing from something and making decisions for the company that are fear-based, flight-based that aren't the right decisions?</p><p><strong>Tyler: </strong>This may be taking...</p>]]>
      </content:encoded>
      <pubDate>Thu, 11 Jul 2019 12:00:00 -0500</pubDate>
      <author>Rick Lindquist and Tyler King</author>
      <enclosure url="https://media.transistor.fm/822fa4f3/e36f0e09.mp3" length="38785719" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist and Tyler King</itunes:author>
      <itunes:duration>2422</itunes:duration>
      <itunes:summary>In this episode we talk about about making decisions under pressure, and how fear can lead to mistakes. The topic started out as "impostor syndrome" and turned into something that neither of us really expected.</itunes:summary>
      <itunes:subtitle>In this episode we talk about about making decisions under pressure, and how fear can lead to mistakes. The topic started out as "impostor syndrome" and turned into something that neither of us really expected.</itunes:subtitle>
      <itunes:keywords>SaaS, leadership, failure, impostor syndrome</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
    <item>
      <title>Salary transparency</title>
      <itunes:episode>1</itunes:episode>
      <podcast:episode>1</podcast:episode>
      <itunes:title>Salary transparency</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">954f8788-a2b4-4e59-84c6-bf303537102d</guid>
      <link>https://share.transistor.fm/s/955473a2</link>
      <description>
        <![CDATA[<p>In this episode, we discussed salary transparency. After some back and forth, we concluded that a company’s salary transparency policy should be based on its personnel strategy. In other words, how you handle salary transparency, whether it's no transparency, partial transparency or full transparency, entirely depends on the people you have and more importantly the people you want to attract.</p><p>Before you decide on a compensation strategy, you should identify the people you need to hire to execute your business plan. This includes what the job functions are and who you want to recruit. If some version of salary transparency will help you recruit and retain those people, go for it! If not, it might be best to shy away.</p><p><strong><br>The philosophical idea of transparency vs application in the real world<br></strong><br></p><p><strong>Tyler:</strong> So today we're going to talk about salary transparency and I mean, who knows where this will go. But, this has been on my mind recently. I recently gave a presentation to our company about how we think about salary and how people get raises and that type of thing. The question I'm posing here is, should companies tell everybody, “here's what every single person at the company makes” (full salary transparency), or should they not be transparent at all so that each person only knows their own salary. Or is there something in between? </p><p><strong>Rick:</strong> Yeah, so when you mentioned this is going to be the deep dive today, my initial reaction was, “I love it.” But then I started thinking about how this conversation could go and the way I look at this is that, philosophically, I believe in full transparency with most things in life, if not all things. I just don't think people can handle it. Most people are not equipped emotionally, myself included in a lot of cases, to handle the burden of transparency.</p><p><br></p><p><strong>Tyler: </strong>And so when you say they can't handle it, I assume what you mean is you hear that the person next to you makes 5% more. And then it's just like in the back of your mind, like, "Well, why is that person better than me?" Or something like that?</p><p><strong>Rick:</strong> The best way to summarize it is “ignorance is bliss”, right? And new information causes change cycles to happen. And when you go through a change cycle, you become an evil person. You become the worst person you are when you have to deal with change because it creates this fear and it brings out all these primal emotions and people do really crazy things when they have that type of change cycle.</p><p><strong>Rick: </strong>So from a philosophical standpoint, I love it. I want all people in the world to be able to talk about all things and have a really good conversation about it and make the best decision together without emotion being a negative factor.</p><p><strong>Tyler:</strong> Yeah. But there is emotion.</p><p><strong>Rick:</strong> That rarely plays out when I see full transparency happening. Most people take it personally.</p><p><strong><br>What does salary transparency accomplish for an organization?<br></strong><br></p><p><strong>Tyler:</strong> Okay. So if I hear what you're saying, you're basically, it's philosophical belief versus what happens in reality and they kind of clash with each other. But there's a reality on the other side, which is even if you don't have transparency, in this day and age, can you actually keep it a secret? And if not, maybe the reality goes in the other direction where it's like, “I agree with all the problems you have, but if it's going to come out anyway, don't you want to control that message?”</p><p><strong>Rick: </strong>So I guess the question is what do we want to accomplish as an organization and what are we trying to do? So I would say if I had my way in the world, I would go, "Let's do full transparency with everything to cash balance.” I would start there and my main goal with that is let's have full trust, number one, so that everyone knows where they stand and two, let's provide everyone context, or the same information I have as the CEO, so that people are more empowered to make the right decisions across the organization. That's the core goal with transparency for me.</p><p><strong>Rick: </strong>Now when you start going, "Oh, well, there are all these other problems that salary transparency can solve," I'd rather talk about those problems as the topic and say, "Okay, well let's figure out how we solved that." And maybe salary transparency is a way to go about that. But when I think about salary transparency and a problem, I'm thinking about, "Okay, I'm going to increase trust with employees. I'm going to give them information to help them make better decisions."</p><p><strong>Tyler:</strong> Maybe these are subsets of what you just said, but there's definitely an element of equity and fairness in it, which statistics say basically some people are more likely to negotiate on their behalf. And so if you don't give this information to people, what you end up with is what looks like things like a gender pay gap or a racial pay gap and things like that, which is very real, but it's really because people don't even know that they should have gone to negotiate or something like that.</p><p><strong>Rick:</strong> Yeah, so that's a good example of a problem I would say that I would not first go to salary transparency to solve that problem because of the cons of salary transparency. In my opinion, the person who, and I'm interested in your opinion on this because you always have a different view on this type of stuff than me. My opinion is let's train the person how to talk about money confidently before we give them all the information about all the money people are making. If they aren't comfortable negotiating, what are they going to do with information that they don't even feel comfortable talking about their own information about? In other words, if they're uncomfortable talking about their own pay, imagine how their brain is going to discuss internally with themselves other people's pay relative to theirs.</p><p><strong>Tyler: </strong>Well, it may not be that they aren't comfortable talking about their pay. It may be that they don't even know that they need to. Like they may think they're fairly paid and they're not.</p><p><strong>Rick: </strong>Then what's the problem we're trying to solve?</p><p><strong>Tyler: </strong>Well, the company, A, might care about fairness just for personal values, setting aside business, but B, you're sitting on a landmine when they do find out. What effectively happened is you've been underpaying them for a long time and they didn't know it.</p><p><br></p><p><strong>Rick: </strong>Well, who's saying underpaid? I guess this is the philosophical question related to this problem: what is fairness and when you say someone is being underpaid, what does that mean?</p><p><strong>Tyler:</strong> So what I'm talking about, I'll put this in very like dollars and cents capitalist terms here. If you have two people who are providing equal value to the business, they should probably be paid the same amount. But if one went and negotiated and the other one didn't even realize that they were not paid what their full market rate was, you're creating this scenario where effectively the company's kind of taking advantage of this person because they're uninformed. Now maybe they can get away with it forever and one might argue that's fine. But to my landmine comment, as soon as it comes out, and especially if it comes out and then you find out, "Oh, there's demographic trends here," that's a real bad look for the company.</p><p><strong>Rick:</strong> I react to that as, “why does t...</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>In this episode, we discussed salary transparency. After some back and forth, we concluded that a company’s salary transparency policy should be based on its personnel strategy. In other words, how you handle salary transparency, whether it's no transparency, partial transparency or full transparency, entirely depends on the people you have and more importantly the people you want to attract.</p><p>Before you decide on a compensation strategy, you should identify the people you need to hire to execute your business plan. This includes what the job functions are and who you want to recruit. If some version of salary transparency will help you recruit and retain those people, go for it! If not, it might be best to shy away.</p><p><strong><br>The philosophical idea of transparency vs application in the real world<br></strong><br></p><p><strong>Tyler:</strong> So today we're going to talk about salary transparency and I mean, who knows where this will go. But, this has been on my mind recently. I recently gave a presentation to our company about how we think about salary and how people get raises and that type of thing. The question I'm posing here is, should companies tell everybody, “here's what every single person at the company makes” (full salary transparency), or should they not be transparent at all so that each person only knows their own salary. Or is there something in between? </p><p><strong>Rick:</strong> Yeah, so when you mentioned this is going to be the deep dive today, my initial reaction was, “I love it.” But then I started thinking about how this conversation could go and the way I look at this is that, philosophically, I believe in full transparency with most things in life, if not all things. I just don't think people can handle it. Most people are not equipped emotionally, myself included in a lot of cases, to handle the burden of transparency.</p><p><br></p><p><strong>Tyler: </strong>And so when you say they can't handle it, I assume what you mean is you hear that the person next to you makes 5% more. And then it's just like in the back of your mind, like, "Well, why is that person better than me?" Or something like that?</p><p><strong>Rick:</strong> The best way to summarize it is “ignorance is bliss”, right? And new information causes change cycles to happen. And when you go through a change cycle, you become an evil person. You become the worst person you are when you have to deal with change because it creates this fear and it brings out all these primal emotions and people do really crazy things when they have that type of change cycle.</p><p><strong>Rick: </strong>So from a philosophical standpoint, I love it. I want all people in the world to be able to talk about all things and have a really good conversation about it and make the best decision together without emotion being a negative factor.</p><p><strong>Tyler:</strong> Yeah. But there is emotion.</p><p><strong>Rick:</strong> That rarely plays out when I see full transparency happening. Most people take it personally.</p><p><strong><br>What does salary transparency accomplish for an organization?<br></strong><br></p><p><strong>Tyler:</strong> Okay. So if I hear what you're saying, you're basically, it's philosophical belief versus what happens in reality and they kind of clash with each other. But there's a reality on the other side, which is even if you don't have transparency, in this day and age, can you actually keep it a secret? And if not, maybe the reality goes in the other direction where it's like, “I agree with all the problems you have, but if it's going to come out anyway, don't you want to control that message?”</p><p><strong>Rick: </strong>So I guess the question is what do we want to accomplish as an organization and what are we trying to do? So I would say if I had my way in the world, I would go, "Let's do full transparency with everything to cash balance.” I would start there and my main goal with that is let's have full trust, number one, so that everyone knows where they stand and two, let's provide everyone context, or the same information I have as the CEO, so that people are more empowered to make the right decisions across the organization. That's the core goal with transparency for me.</p><p><strong>Rick: </strong>Now when you start going, "Oh, well, there are all these other problems that salary transparency can solve," I'd rather talk about those problems as the topic and say, "Okay, well let's figure out how we solved that." And maybe salary transparency is a way to go about that. But when I think about salary transparency and a problem, I'm thinking about, "Okay, I'm going to increase trust with employees. I'm going to give them information to help them make better decisions."</p><p><strong>Tyler:</strong> Maybe these are subsets of what you just said, but there's definitely an element of equity and fairness in it, which statistics say basically some people are more likely to negotiate on their behalf. And so if you don't give this information to people, what you end up with is what looks like things like a gender pay gap or a racial pay gap and things like that, which is very real, but it's really because people don't even know that they should have gone to negotiate or something like that.</p><p><strong>Rick:</strong> Yeah, so that's a good example of a problem I would say that I would not first go to salary transparency to solve that problem because of the cons of salary transparency. In my opinion, the person who, and I'm interested in your opinion on this because you always have a different view on this type of stuff than me. My opinion is let's train the person how to talk about money confidently before we give them all the information about all the money people are making. If they aren't comfortable negotiating, what are they going to do with information that they don't even feel comfortable talking about their own information about? In other words, if they're uncomfortable talking about their own pay, imagine how their brain is going to discuss internally with themselves other people's pay relative to theirs.</p><p><strong>Tyler: </strong>Well, it may not be that they aren't comfortable talking about their pay. It may be that they don't even know that they need to. Like they may think they're fairly paid and they're not.</p><p><strong>Rick: </strong>Then what's the problem we're trying to solve?</p><p><strong>Tyler: </strong>Well, the company, A, might care about fairness just for personal values, setting aside business, but B, you're sitting on a landmine when they do find out. What effectively happened is you've been underpaying them for a long time and they didn't know it.</p><p><br></p><p><strong>Rick: </strong>Well, who's saying underpaid? I guess this is the philosophical question related to this problem: what is fairness and when you say someone is being underpaid, what does that mean?</p><p><strong>Tyler:</strong> So what I'm talking about, I'll put this in very like dollars and cents capitalist terms here. If you have two people who are providing equal value to the business, they should probably be paid the same amount. But if one went and negotiated and the other one didn't even realize that they were not paid what their full market rate was, you're creating this scenario where effectively the company's kind of taking advantage of this person because they're uninformed. Now maybe they can get away with it forever and one might argue that's fine. But to my landmine comment, as soon as it comes out, and especially if it comes out and then you find out, "Oh, there's demographic trends here," that's a real bad look for the company.</p><p><strong>Rick:</strong> I react to that as, “why does t...</p>]]>
      </content:encoded>
      <pubDate>Sat, 29 Jun 2019 16:00:00 -0500</pubDate>
      <author>Rick Lindquist &amp; Tyler King</author>
      <enclosure url="https://media.transistor.fm/955473a2/29e90a8e.mp3" length="37986299" type="audio/mpeg"/>
      <itunes:author>Rick Lindquist &amp; Tyler King</itunes:author>
      <itunes:duration>2372</itunes:duration>
      <itunes:summary>The topic this week is salary transparency: when does it make sense for a company to share salary information with all employees, and when does it make sense to keep that information private. We dive into how transparency can impact morale and culture, the ethics around sharing information, and more.</itunes:summary>
      <itunes:subtitle>The topic this week is salary transparency: when does it make sense for a company to share salary information with all employees, and when does it make sense to keep that information private. We dive into how transparency can impact morale and culture, th</itunes:subtitle>
      <itunes:keywords>startups, management, salary, negotiation, culture</itunes:keywords>
      <itunes:explicit>Yes</itunes:explicit>
    </item>
  </channel>
</rss>
