Product-led growth doesn't need $300/month SaaS tools

There's a quiet assumption baked into most PLG content: you need expensive tooling to do product-led growth properly. Appcues at $300/month. Pendo at $25,800/year minimum. Userpilot somewhere in between. The messaging is consistent. Pay us or your users won't activate.

That framing is wrong. PLG is a product design strategy, not a line item.

We built Tour Kit as a solo developer. The entire onboarding stack (product tours, checklists, hints, analytics, feature adoption tracking) runs on open-source code and costs nothing to deploy. This article isn't a pitch for Tour Kit specifically. It's an argument that the $300/month onboarding tax is optional for most teams, and the alternatives are better than you'd expect.

npm install @tourkit/core @tourkit/react

The problem: PLG advice comes from PLG tool vendors

Most product-led growth content is written by companies selling PLG tools, which means the advice always ends with "buy our product." Appcues publishes guides on PLG strategy that end with "try Appcues." Userpilot writes about activation metrics and recommends Userpilot for tracking them. Pendo's blog is a funnel for Pendo contracts. The solution to every PLG challenge, according to PLG tool vendors, is another monthly subscription.

The actual data tells a different story. According to Bessemer Venture Partners, 68% of developers abandon trials because of setup friction: too many steps, too much configuration, too long to reach value. Only 12% cite pricing as the reason they leave.

That stat reframes the entire problem. The adoption killer isn't a missing Appcues flow. It's a confusing first-run experience that no amount of tooltip layering will fix.

What $300/month actually buys you

Onboarding SaaS tools charge based on monthly active users, and the numbers add up fast for growing products. As of April 2026, a bootstrapped SaaS with 2,500 MAUs would pay $3,600 to $10,000+ per year depending on which vendor they pick. Here's the full breakdown:

Pendo's pricing is famously opaque. Vendr marketplace data shows contracts ranging from $25,800 to $132,400 per year. Some early-stage startups report being quoted $30,000 annually.

Here's what that money gets you: a visual flow builder, user segmentation, built-in analytics, and non-technical team access. Those are real features. For a 200-person company with a dedicated product ops team, that value proposition makes sense.

For a 3-person startup? A bootstrapped SaaS? An indie dev shipping their first product? The math doesn't work.

The bootstrapped PLG stack (under $100/month)

A complete, code-first PLG stack for early-stage teams costs almost nothing because every category now has a strong free or open-source option. Here's what we'd recommend (and this isn't a Tour Kit infomercial, most of these tools are independent projects).

Onboarding and product tours: An open-source library. Tour Kit, Shepherd.js, Intro.js, or Driver.js. All MIT-licensed (except Shepherd, which uses AGPL). All free. Pick the one that fits your stack.

// src/components/OnboardingTour.tsx
import { TourProvider, useTour } from '@tourkit/react';

const steps = [
  { target: '#create-project', content: 'Start here — create your first project' },
  { target: '#invite-team', content: 'Invite your team to collaborate' },
  { target: '#dashboard', content: 'Track progress from the dashboard' },
];

function App() {
  return (
    <TourProvider steps={steps}>
      <YourApp />
    </TourProvider>
  );
}

Analytics: PostHog offers product analytics, session replay, feature flags, and A/B testing under a generous free tier. GA4 is free and covers basic event tracking. Mixpanel has a free plan for up to 20M events.

Session recording: PostHog includes this. Hotjar starts at $32/month if you want a dedicated tool.

Feature flags: PostHog again, or LaunchDarkly's free tier, or roll your own with a JSON config and a React context.

Activation tracking: Custom events piped to your analytics tool. Five lines of code, not a SaaS subscription.

Total cost for a bootstrapped team: $0 to $100/month. Compare that to Appcues alone at $3,600/year.

The real argument: PLG is product design, not tooling

PLG companies grow at 50% year-over-year versus 21% for traditional SaaS, according to OpenView Partners (the firm that coined "product-led growth" in 2016). But that growth comes from product design decisions, not from which onboarding software sits on top of the product.

ProductLed's 2026 predictions set the bar clearly: "Can a user get value in under 60 seconds?" That's a UX challenge. No amount of Appcues flows will compress a confusing product into a 60-second aha moment.

Consider what actually drives PLG adoption:

1. Time-to-value. How fast can someone accomplish something real? This is architecture and UX, not tooltip placement.
2. Self-service onboarding. Can users figure it out without a sales call? Open-source libraries handle the guided bits. Product design handles the rest.
3. Viral loops. Does using the product create reasons to invite others? Tally, the no-code form builder, hit $70K MRR bootstrapped by making shared forms carry their branding. No onboarding SaaS involved.

The PLG success stories from bootstrapped companies keep proving this. Solo open-source developers reaching $14.2K/month. Indie hackers hitting $32K MRR through PLG and SEO alone. None of them started with a $300/month onboarding tool.

A two-year cost comparison

PLG tool vendors never show the 2-year total cost of ownership alongside the cost of a one-time engineering integration, because the math doesn't favor subscriptions. Here's the comparison they skip.

Scenario: A bootstrapped B2B SaaS with 2,500 MAUs needs product tours, onboarding checklists, and basic analytics.

Option A, Appcues:

• $300/month x 24 months = $7,200
• Plus annual contract lock-in
• Plus MAU overages as you grow
• Realistic 2-year cost: $8,000-$12,000

Option B, open-source stack:

• Engineer spends 2 days integrating a tour library: ~$2,400 (at $150/hour)
• PostHog free tier for analytics: $0
• Hotjar starter for recordings: $32/month x 24 = $768
• Total 2-year cost: ~$3,168

The open-source approach saves $5,000 to $9,000 over two years. And you own the code. No vendor lock-in, no MAU-based scaling costs, no annual contract negotiations.

But the savings aren't the best part. The best part is flexibility. When your product changes (and it will), you edit code instead of rebuilding flows in a visual editor that maps to someone else's abstraction layer.

The counterargument: when expensive tools earn their cost

Paid onboarding platforms genuinely earn their cost in four specific situations, and pretending otherwise would weaken the argument. Here's when the subscription math works out.

Non-technical teams own onboarding. If your product manager needs to update tour flows weekly and doesn't write code, a visual builder is worth paying for. Open-source libraries require engineering involvement for every change.

Enterprise scale (50,000+ MAUs). At this volume, sophisticated segmentation, A/B testing of flows, and retroactive analytics become critical. Pendo's Forrester TEI study shows a composite organization achieving $3.81M in benefits over three years from a $765K investment, a 396% ROI. But that's a company with the scale to justify it.

Mobile SDK requirements. If you need native iOS and Android onboarding alongside web, Appcues and Pendo have mobile SDKs. Most open-source libraries don't. Tour Kit is React 18+ only, no React Native.

Compliance and audit trails. Some enterprise contracts require specific vendor certifications. A self-built stack might not pass procurement review.

The honest answer is: if three or more of those apply to you, evaluate the paid tools. If none of them do, you're paying for features you won't use.

What we'd do differently (the practical recommendation)

If we were launching a bootstrapped SaaS today, here's the exact stack we'd use at each stage, with monthly costs. We built Tour Kit, so take this with appropriate skepticism, but most of this advice applies regardless of which tour library you choose.

Months 1-6 (pre-PMF):

• Open-source tour library for onboarding flows
• GA4 + PostHog free tier for analytics
• Total: $0/month
• Focus: ship fast, measure time-to-value, iterate on the product itself

Months 6-12 (early traction):

• Add session recording (PostHog or Hotjar at $32/month)
• Build feature flags with your tour library or PostHog
• Total: $0-$32/month
• Focus: identify where users drop off, fix the product, not the tours

Months 12-24 (scaling):

• Evaluate if you've outgrown the stack
• If non-technical team needs flow editing → consider a paid tool
• If still engineering-led → keep the open-source stack, invest in code quality
• Total: $0-$100/month (or graduate to paid if the ROI is clear)

The key insight from Smashing Magazine's onboarding research is that 90% of downloaded apps are used once and deleted. The fix for that statistic isn't better tooltips. It's a better product with faster time-to-value. Spend your budget there first.

The quiet advantage of code-first onboarding

Engineers understand their products better than any SaaS vendor's visual builder, and that understanding shows up directly in onboarding quality when the flows are written in code. When a developer writes an onboarding flow, they're encoding product knowledge: which features matter, what order makes sense, where users get confused.

That knowledge lives in the codebase, versioned with git, reviewed in pull requests. When the product changes, the onboarding changes with it. No separate system to maintain, no syncing between a visual editor and your actual UI.

As of April 2026, developers have access to product analytics (PostHog), session replay (PostHog, Hotjar), A/B testing (PostHog, GrowthBook), feature flags (LaunchDarkly free tier, Flipt), and complete onboarding UI libraries (Tour Kit, Shepherd, Intro.js). All free or under $100/month.

The $300/month PLG tool market exists because non-technical teams needed a way to build onboarding without engineering support. That's a valid need. But for technical teams and bootstrapped startups, the tooling gap has closed. The expensive SaaS tool isn't the only path to product-led growth anymore.

Frequently asked questions

Can you do product-led growth without paid tools?

Product-led growth centers on the product delivering value before any sales conversation. Open-source tools cover onboarding (Tour Kit, Shepherd, Intro.js), analytics (PostHog, GA4), and feature flags at $0/month. Tally reached $70K MRR bootstrapped without paid onboarding SaaS. The constraint is engineering capacity, not tooling budget.

What does Appcues actually cost in 2026?

Appcues starts at $299/month for 1,000 MAUs on their Essentials plan, with annual contracts typically required. The Growth plan runs around $1,000/month. Pricing scales with monthly active users, so costs increase as your product grows. Pendo is even less transparent, with Vendr data showing contracts between $25,800 and $132,400 per year.

When should a startup pay for onboarding tools?

Consider paid onboarding SaaS when non-technical team members need to edit flows without engineering support, when you exceed 50,000 MAUs and need advanced segmentation, or when mobile SDK support (iOS/Android) is required. For engineering-led teams under 10,000 MAUs, open-source product tour libraries combined with free analytics tools cover the same use cases at a fraction of the cost.

What is the best free PLG analytics stack?

Combine PostHog (product analytics, session replay, feature flags on a free tier), GA4 (traffic and conversion tracking, free), and an open-source tour library like Tour Kit (MIT license) to cover 90% of what Appcues or Pendo offer. Total monthly cost: $0. The tradeoff is setup time. Budget 1-2 days of engineering effort for initial integration.

Is Tour Kit a replacement for Appcues?

Tour Kit replaces the onboarding UI layer: product tours, checklists, hints, and feature adoption tracking. It doesn't replace Appcues' visual flow builder, user segmentation, or managed analytics dashboard. Tour Kit is built for React developers who want code-level control. If your team includes non-technical flow editors, Tour Kit isn't the right fit. React 18+ only, no mobile SDK.

Related articles

Thought LeadershipApr 11, 2026 · 11 min read

How AI will change product onboarding (and what won't change)

AI will personalize onboarding timing, content, and sequencing. But trust, accessibility, and user control still require human decisions. A developer's take.

Read article

Thought LeadershipApr 11, 2026 · 8 min read

Why the best onboarding software in 2026 is a React library

Code-first React libraries beat SaaS onboarding platforms on cost, performance, and control. Pricing data, bundle sizes, and architecture compared.

Read article

Thought LeadershipApr 11, 2026 · 7 min read

GitHub stars don't pay the bills (but they help)

A solo developer's honest look at what GitHub stars actually do for an open-source library. Real numbers on the gap between stars and revenue.

Read article

Thought LeadershipApr 11, 2026 · 10 min read

From 0 to 1000 GitHub stars: the Tour Kit playbook

How I grew a React product tour library from zero to its first 1,000 GitHub stars as a solo developer. Real tactics, real numbers, no paid ads.

Read article