Small, independent software products and recurring-revenue businesses.
Showing 1–8 of 8 dossiers
New SaaS cohort data challenges the habit of waiting six months to pitch an upgrade. The strongest seat and plan expansion window is the first month, while year-one renewal creates a second chance; AI-native customers are more likely to reactivate after churn.
Buttondown’s 'Great Pruning' is a small-SaaS operations story about deleting architecture rather than adding it. The company removed duplicated or over-retained request and email-event data after changing how those workloads were processed.
The useful small-SaaS lesson is not that SEO is dead or AI search has won. DocsBot’s own numbers show how a channel can remain the largest share of conversions while the total funnel underneath it shrinks, and how 'Direct' can conceal the discovery path that actually influenced a sale.
The useful part of Kanbanchi’s case is that it did not need a new product category or a giant ad budget. A 25-person bootstrapped team changed the economics and presentation of an existing product, made team savings visible and progressively moved its customer mix toward multi-seat accounts.
Stripe is seeing more new SaaS-style platform businesses, not fewer: new platform launches rose more than 180% year over year, and recent cohorts are reaching meaningful payment volume faster. The dataset is vendor-produced, but unusually concrete.
This is a small-company capital-access story rather than a generic AI opinion. Founders who expected a fall TinySeed intake lose that funding window, while TinySeed is explicitly revising the operating assumptions it uses to judge early-stage SaaS businesses.
Zigpoll is a useful tiny-team pricing case because the claimed gain came from segment fit rather than simply charging everyone more. The founder says moving integrations down to the standard plan removed friction for agencies managing many client stores; current product pricing remains tiered primarily by survey-response volume.
Zipchat is useful as an operating case study, not a comeback story. Founder-reported figures show how a prior platform dependency failure influenced a new AI SaaS model built around reply-based pricing, channel diversification, revenue-based financing and tighter hiring discipline.
Indie SaaS combines software leverage with the constraints of a tiny company. Product scope, support load, infrastructure choices and acquisition cost all land on the same few people, so a seemingly small platform or pricing change can reshape the business.
This page follows developments that matter specifically to independent software operators. BTN looks at product opportunities, tooling, distribution and economics without assuming the goal is venture scale. Coverage is interested in durable, understandable businesses and the trade-offs behind them. The aim is to help a builder decide where a new capability creates leverage, where a dependency adds fragility and which operating lessons travel beyond the company that shared them.
Coverage also recognises that independence comes in degrees. A small product may rely on app stores, payment providers, cloud platforms and model APIs while remaining independently owned. The relevant question is whether those dependencies are understood and whether the business has a credible response when one of them changes.