How to decide which features to build as a bootstrapped SaaS founder

Executive overview

Founders face a constant trade-off: build what customers ask for, or build toward a strategic vision. Pure feature voting leads to a fragmented roadmap that isn't owned by anyone. The answer is a blend — spot repeated customer patterns, filter through strategic vision, and give bigger bets enough runway via structured cycles.

Product development is the art of disappointing customers at a rate they can accept.

The problem with feature voting

• Customers don't always know what they need — they can't be expected to be inventive on your behalf.
• Optimising for the most-upvoted request doesn't mean optimising for the right direction.
• Public upvote boards create pressure to build things that may not align with strategy.
• The right question is: what problems does my target group experience, and how can I address those?

When to act on customer requests

• When you hear the same request multiple times in a short window — multiple people, different phrasings.
• When the request is broadly applicable, clearly valuable, and low effort.
• Quick wins generate goodwill and signal responsiveness.
• You can't be purely reactive, but dismissing patterns is a mistake.

Six-week cycles for bigger bets

• Without structure, teams default to quick wins because they deliver faster dopamine hits.
• Six-week cycles carve out protected time for one ambitious project per cycle.
• Smaller wins fill in around the big project — they don't disappear, they get scheduled.
• The cycle length is long enough to ship something meaningful, short enough to course-correct.

Weighing cost and opportunity cost

• Every feature carries an engineering cost, maintenance burden, and opportunity cost.
• The bigger the team, the bigger the bets — early on you're risking time; later, you're risking significant payroll.
• A feature that takes three months needs stronger justification than one that takes a week.
• The uncomfortable reality: you're betting with incomplete information every time.

Freemium as a strategic entry point

• SavvyCal launching meeting polls as a free feature — a Doodle-style group scheduling tool.
• Chosen because it's additive, not cannibalising any existing paid feature.
• Free users still connect their calendar, setting up their account for the full paid experience.
• Contrasted with engineering-as-marketing: this is a genuine first link in the freemium chain, not a standalone tool that happens to share a brand.

SavvyCal product updates

• Squadcast integration: each booking now spins up a separate room rather than dumping all recordings into one.
• Close CRM integration: potentially first scheduling tool to natively integrate with that ecosystem.
• Target customer for Close integration aligns closely with the SavvyCal persona — teams not ready for Salesforce.

The founder decision-making mindset

• Most of being a founder is making hard decisions with incomplete information.
• Standard education trains you for clear next steps; entrepreneurship has none of that scaffolding.
• Getting comfortable with autonomous decision-making is a learned skill, not an innate trait.
• Growing the team introduces new financial pressure — hitting revenue milestones doesn't mean feeling wealthy once payroll scales.

Things that added disproportionate value

• Under $100: stovetop coffee roasting kit (~$65) — beans from Sweet Maria's, 15 minutes a week, significantly cheaper than pre-roasted whole-bean coffee.
• Under $100: Amazon Echo Show in the kitchen — intercom across a multi-floor house, timer management, smart plug automation.
• Under $1,000: BedJet (~$700–800) — air-pump system under sheets for temperature control; consistent sleep improvement in a well-insulated apartment.
• Under $1,000: 38-inch curved ultrawide Dell monitor — doubles as a USB-C docking station, single cable to laptop, eliminates dongle chaos.