SavvyCal founder on competition, validation, and when to quit

Executive overview

Competing in a crowded market is not fundamentally different from any other market — you still need to show up where buyers have intent and present differentiated positioning. Features are not moats; open-source competitors with $40M can copy your interface overnight.

The defensible advantages are trust, brand, and product virality. For bootstrapped founders, the decision to quit comes down to whether viable ideas remain on the table and whether the motivation to pursue them survives.

The only real moat for a small SaaS is the trust and responsiveness that a VC-funded competitor cannot replicate.

The most painful feature: group scheduling mode

• Allows multiple people to book the same time slot (webinars, group coaching).
• Appears simple — one setting for max attendees — but touched almost every part of the scheduling infrastructure.
• Previous assumption baked throughout the codebase: one booking = one blocked time slot.
• Edge cases multiplied: adding an attendee to an existing event, rescheduling one attendee out while another stays, lateral moves between two already-booked slots.
• Required formalising a change-event system (scheduled, attendee added, attendee rescheduled) that will make future integrations easier.
• Team regularly re-evaluated mid-project: "Is this still worth it?" — continued because infrastructure benefits extended beyond the feature itself.

When to give up on a SaaS idea

• Key reasons to bail: no demand, buyers not problem-aware, no willingness to pay, platform risk, no viable distribution channel.
• Work backwards: if you don't know whether those are true, design the cheapest test to find out.
• Validation is not a formula — it's directional research and founder gut working on incomplete information.
• Level (Derek's prior startup) failed because enthusiastic users were downstream of the actual buyers; managers loved Slack's instant-ping dynamic and wouldn't fund the alternative.
• Bootstrapped companies fail when the founder runs out of motivation, not money.
• As long as viable ideas remain on the table, keep going — consult peers, look for angles you haven't tried.
• If you face "viable ideas exist but I have no energy left," take a deliberate pause before deciding; let the idea of stopping sink in.
• SaaS cannot be left on autopilot; if you're not investing effort, redirect it to something else.

Competing in a crowded market with a dominant player

• Show up where buyers have purchase intent, then position meaningfully — copying the leader's H1 is a recipe for failure.
• Blocking-and-tackling distribution: get listed in listicles, review articles, and integration blogs (e.g. Zapier); these compound over time.
• SavvyCal's structural advantage: inherent virality — every booking exposes the brand to the recipient, seeding future customers.
• Virality is hard to attribute through the full funnel but surfaces clearly in "how did you hear about us?" responses.
• Owned/proprietary traffic channels (strong SEO, a personal audience) can substitute for or amplify differentiation.
• You can grow with differentiation alone or with owned traffic alone — both together is the goal, but either can work.
• Mature competitive markets are often large and growing, which is exactly why they attract competition.

How open-source, funded competition sharpened SavvyCal's positioning

• A well-funded open-source competitor copied interface decisions; features are not protectable in software.
• Initial reaction is disheartening; the productive outcome is clarity on what is actually defensible.
• SavvyCal's brand refresh was driven by this: distil why customers choose SavvyCal beyond feature lists.
• Customer interviews and survey data pointed to trust, responsiveness, and attention to detail — values a VC-funded growth machine depots fast.
• Positioning shifted toward "small and nimble, listens to customers" — fuzzier than a feature comparison but more durable.

The redesign: outcomes and approach

• Refreshed marketing site, new logo, updated H1, and a revamped link editor (core editing interface) shipped together.
• Design goal: avoid the generic "blue and white startup corporate" look; make the aesthetic communicate the same values as the copy.
• Shipped alongside the group scheduling feature — created a moment of energy and news to amplify.
• Best sales month in a long time followed; hard to attribute directly but momentum compounds.

Vertical vs horizontal positioning

• SavvyCal launched horizontally to pick up signals on who gets the most value.
• Current customer base is diverse — good signal for general-purpose fit, but makes it harder to identify the highest-value segment to double down on.
• Experimented with feature sprints targeting sales teams without committing the home page H1 to that vertical.
• Full vertical pivot requires a hypothesis strong enough to accept actively excluding other buyers — not reached that bar yet.
• The riskier call: the more mature the business, the more a strategic pivot to a niche costs in existing momentum.

Podcasting: what's next for Derek

• Ran The Art of Product with Ben Orenstein for five to six years; built audience and community but was an energy drain.
• Weekly cadence imposed pressure to summarise learnings smartly — felt taxing, not energising.
• Retired from the weekly format; now appearing as a recurring guest on Startups for the Rest of Us every six to eight weeks.
• Standing open invite — no recurring calendar event, just a natural ongoing conversation.

How SavvyCal was validated and chosen

• Started with a list of tools the business paid for; evaluated each for bootstrappability, incumbent weakness, and a wedge.
• Calendly stood out: not innovating, customers felt unheard, product hadn't shifted much despite being the household name.
• Pre-validation hook: recurring Twitter discourse that Calendly links feel rude — a technology-plus-etiquette problem worth solving.
• Built a manifesto landing page around the power dynamic problem; collected emails and had conversations before writing production code.
• MVP shipped within a few months; existing audience used as kindling, not a sustainable channel on its own.

Derek's idea filters (written 2019, pre-SavvyCal)

1. Market must already exist — no category invention.
2. MVP shippable within a few months.
3. Product should not be mission-critical (no severe downtime consequences).
4. Sale should not require more than a few decision makers.
5. Native mobile apps should not be a minimum requirement.
6. Market should overlap with existing audience.