Founder Decision Frameworks
Decision trees for the calls every founder eventually has to make about people, pricing, and platforms.
Should You Open Source Your Product? A Strategic Read
Open sourcing your product changes your distribution, your competition, and your monetization permanently.
Founder Decision FrameworksShould You Build a Mobile App at All?
A mobile app adds cost, complexity, and app store friction. Here is when it is actually worth it.
Founder Decision FrameworksShould You Build a Marketplace, a SaaS, or a Service Business?
Three business models, three very different bets. Here is how to pick the one that matches your actual situation.
Founder Decision FrameworksBuild vs Buy vs Partner: A Founder Decision Tree
Build means you own and run the surface. Buy means you license or subscribe to a vendor's offering. Partner means you bring another company's capability into your product through a structured agreement that goes deeper than buy and stops short of build. Partner sits between the two and is the right answer more often than founders expect.
Founder Decision FrameworksThe Decision to Walk Away
Walking away from a company means making the deliberate decision to stop, not because external forces compelled it but because the founder has decided the cost of continuing exceeds the expected value of what continuing might produce. It is the hardest decision in the founder's decision set because it requires separating identity from outcome, accepting the sunk cost, and making a choice that will be second guessed from every direction.
Founder Decision FrameworksThe Decision to Sunset a Product
Sunsetting a product means shutting it down permanently, migrating or releasing customers, and removing it from active development and support. Unlike sunsetting a feature, a product sunset affects all customers simultaneously and requires comprehensive communication, data export, and contract management. How a company shuts down a product tells customers and the market as much about the company's values as how it launched one.
Founder Decision FrameworksThe Decision to Sell the Company
Selling a company is an irreversible decision made under significant time pressure, information asymmetry, and emotional complexity. The buyer has done many acquisitions. The founder has done zero. The acquirer's legal team has reviewed hundreds of term sheets. The founder's lawyer may be seeing the first one. Understanding what the terms actually mean and what the alternatives are is the work that must happen before the negotiation begins.
Founder Decision FrameworksThe Decision to Sunset a Feature
Sunsetting a feature means removing functionality that currently exists and that at least some users depend on. Every feature removal creates a migration problem for those users and a trust question about whether the product will continue to evolve in ways that disrupt established workflows. Handled with notice and a real migration path, a feature sunset reduces maintenance burden and sharpens product focus. Handled as a surprise, it generates churn and damages the product's reputation for reliability.
Founder Decision FrameworksThe Decision to Build a Second Product
Building a second product is one of the highest risk decisions a SaaS founder can make. It splits the team's attention, the codebase's evolution, the go to market investment, and the customer support capacity. The founders who do it well treat the second product as a separate company with its own resources, not as a feature addition to the first product's roadmap.
Founder Decision FrameworksThe Decision to Productize a Service
Productizing a service means turning a repeatable workflow that you currently deliver manually for clients into a software product that delivers the same outcome automatically. The promise is leverage: a product can serve hundreds of customers simultaneously while a services business is limited by the number of hours its team can bill. The reality is that most services that seem productizable have enough variation per client to make true productization difficult.
Founder Decision FrameworksThe Decision to Add Enterprise Sales
Enterprise sales is a separate motion from self serve SaaS. It requires dedicated headcount, longer sales cycles, custom contracts, compliance documentation, and a product that can be customized to enterprise requirements. Adding it before you are ready is expensive and distracting. Adding it too late means leaving large contracts on the table while you wait for inbound to scale.
Founder Decision FrameworksThe Decision to Change Pricing
Changing pricing is one of the most impactful decisions a SaaS founder can make and one of the most avoided. The fear is losing customers. The reality is that underpricing costs more revenue than overpricing. A pricing change that is grounded in the value the product delivers, communicated clearly, and grandfathered appropriately for existing customers is achievable without customer churn.
Founder Decision FrameworksThe Decision to Remove a Free Plan
Removing a free plan means telling a portion of your user base that the product they have been using at no cost will now require payment. This is one of the most emotionally difficult decisions a founder can make and one of the most operationally complicated to execute. Done well, it filters for users who get real value from the product. Done poorly, it generates negative press, user backlash, and a lost acquisition channel.
Founder Decision FrameworksThe Decision to Add a Free Plan
Adding a free plan is a distribution decision, not a pricing decision. Done right, it creates a self serve acquisition channel where users try the product, see value, and convert to paid without needing a sales call. Done wrong, it fills your user base with people who will never pay, increases your support burden, and signals to serious buyers that the product is not worth paying for.
Founder Decision FrameworksThe Decision to Outsource Customer Support
Outsourcing customer support means transferring ticket resolution to a third party team that is not employed by the company. The economic case is clear: lower cost per ticket than internal headcount, coverage in time zones where the company does not have staff. The strategic risk is equally clear: the support team is where the company learns about product problems, and an outsourced team is a worse conduit for that feedback than an internal one.
Founder Decision FrameworksThe Decision to Hire Your First Operations Person
An operations hire owns the systems that keep the company running: vendor relationships, internal processes, compliance administration, finance operations, and the coordination work that does not fall cleanly to engineering or sales. The role is justified when the founder is spending more than 10 hours per week on operational tasks that are not strategic and could be owned by someone else.
Founder Decision FrameworksThe Decision to Build a Customer Success Team
A customer success team owns the relationship between a SaaS company and its paying customers after the sale closes. Their job is to ensure customers get value from the product, renew their contracts, and expand their usage over time. Building this team is the right call when churn is high enough to threaten growth and when the customer relationship requires active management that the product alone cannot provide.
Founder Decision FrameworksThe Decision to Hire Your First Marketing Person
The first marketing hire is one of the most misused positions in early stage SaaS. Founders hire a marketing person when growth is slow, expecting them to find the acquisition channel. But finding the acquisition channel is the founder's job. The marketing hire should scale a channel that the founder has already proven works, not discover a channel from scratch in their first 90 days.
Founder Decision FrameworksThe Decision to Move to a Tech Hub or Stay Remote
A tech hub provides three things that remote environments cannot fully replicate: serendipitous introductions, investor proximity, and a peer community of founders who understand the specific pressures of building a startup. Whether these three things are worth relocating for depends entirely on what the company needs in the next twelve months and whether the founder's existing network can substitute for geographic proximity.
Founder Decision FrameworksThe Decision to Apply to an Accelerator
An accelerator is a fixed term program that provides early stage companies with funding, structured mentorship, and access to a network of investors in exchange for equity. The decision to apply is a trade: three to six months of intense focus and a percentage of your company for capital, introductions, and credibility. Whether that trade is worth making depends entirely on what your specific company needs right now.
Founder Decision FrameworksThe Decision to Hire a PR Firm or Stay Indie
A PR firm creates media coverage for your company by building and maintaining relationships with journalists, pitching stories, and managing the timing of news releases. For early stage SaaS companies, most PR firm engagements cost $5,000 to $15,000 per month and produce results that are difficult to attribute to revenue. The exceptions are launch events, funding announcements, and crisis situations where professional PR has clear value.
Founder Decision FrameworksThe Decision to Build a Channel Partnership
A channel partnership routes your product to customers through a third party, typically a reseller, system integrator, or platform. The partner has existing customer relationships and distribution. You have a product the partner can add to their offering. The trade is revenue share in exchange for distribution leverage. The partnership works when both sides benefit. It fails when the incentives diverge.
Founder Decision FrameworksThe Decision to Charge Money Before You Have a Product
Charging money before a product exists is the most reliable form of market validation. Free signups signal interest. Paid commitments signal willingness to pay, which is the actual question early stage founders need to answer. A founder who collects $500 from five potential customers before writing a line of code knows more about their market than a founder who gets 500 email signups.
Founder Decision FrameworksThe First Customer Decision: Land or Anchor?
The first customer decision is whether to acquire customers who represent your eventual target market or to acquire customers who are available and willing to pay but are not representative of the market you want to build for. Landing customers who represent the target market validates the product for the right audience. Anchoring on customers who are accessible but not representative creates revenue that disguises a product that is not suited for the intended market. The choice is consequential and often made without recognizing it as a choice.