Skip to content

How to Sell Your Web App or SaaS Source Code

A practical guide for developers: who buys source code, how to package and price a web app, where to sell it, and how to turn one codebase into a single-company edition and a resellable SaaS edition.

• Nov 17, 2026 • 5 min read
How to Sell Your Web App or SaaS Source Code

You built a web app that works — a CRM, a booking system, an HR tool, a SaaS starter. Maybe it ran a client project, maybe it was a side product that never found enough subscribers. Either way, the code itself has value: there are businesses and developers who would rather buy a working, self-hosted application than build one from scratch or rent a SaaS forever. This guide covers how to turn that codebase into something people actually buy.

Who buys web app source code?

  • Small and mid-size businesses that want software they own — no per-user subscription, their data on their own server.
  • Agencies and freelancers who deliver client projects faster by starting from a proven application instead of a blank repository.
  • Founders who want to launch a SaaS without spending a year on the boring 80% — auth, billing, tenancy, admin panels.
  • Developers who want a reference implementation or a starter kit for their own product.

Each group searches differently. Business buyers search for the job the software does ("school management system", "inventory software with barcode scanner"). Founders search for "SaaS script" or "multi-tenant". Write your listing for the buyer you actually want.

Get the product ready to sell

Buyers judge source code in minutes. Before you list, make sure a stranger can go from download to running app without messaging you:

  • A clean install path. A documented installer or a short, tested set of commands. A failed install is the fastest route to a refund request.
  • A live demo. Seeded with realistic data and demo logins for each role. A buyer who can click through the admin panel converts far better than one reading a feature list.
  • Documentation. Requirements, installation, configuration, upgrading, and the two or three customisations everyone asks for.
  • Screenshots that show real screens. Dashboards, key workflows, mobile views. Skip the marketing mock-ups.
  • No secrets in the repository. Strip API keys, real customer data and hard-coded credentials, and ship an .env.example.
  • A changelog. It signals the product is maintained, which is the main worry anyone has when buying code.

On AppTrovo, the product submission checklist lists exactly what reviewers look for.

Price it like software, not like a theme

A complete, production-ready application replaces months of development or years of subscription fees, so price it against that — not against a $20 template. A few patterns that work:

  • One-time license for a single business. Clear, easy to buy, and the main thing self-hosting buyers want: no recurring bill.
  • A free community edition plus a paid commercial license. The free edition earns trust and search visibility; serious users upgrade for commercial use and support.
  • A separate SaaS edition. If your app can run multi-tenant, sell that as its own product at a higher price — see below.

One codebase, two products: single-company and SaaS editions

Many buyers want to run software for their own company; others want to resell it to their customers. These are different products with different buyers, and they deserve separate listings:

  • The single-company edition is self-hosted for one organisation. Its listing talks about the business problem it solves.
  • The multi-tenant SaaS edition adds tenant isolation, subscription billing and a super-admin panel. Its listing talks to founders: launch your own SaaS, keep the recurring revenue.

Give each edition a distinct name and title and link them to each other, so both buyers and search engines can tell them apart instead of seeing two near-identical pages.

Where to sell: your own site or a marketplace?

Selling from your own website keeps 100% of the price, but you also own everything else: checkout, tax handling, license keys, download delivery, refunds and — hardest of all — traffic. A marketplace trades a share of each sale for buyers who are already looking, plus the selling infrastructure.

When you compare marketplaces, look past the headline audience size:

  • Revenue share — 50–70% is common for authors; some marketplaces pay more.
  • Exclusivity — can you also sell on your own site and elsewhere?
  • Payout speed — monthly payouts with thresholds versus payouts per sale.
  • Licensing — does the platform issue license keys and offer a verification API, or do you build that yourself?
  • Focus — a marketplace for complete applications attracts different buyers than one built around themes and plugins.

Selling on AppTrovo

AppTrovo is built for complete, production-ready web applications. Authors keep 90% of every sale (a 10% platform fee), get paid through Stripe Connect directly to their bank account, and can keep selling the same product anywhere else — there is no exclusivity. Every product gets a built-in license system with domain activation and a verification API, and listings are shown in seven languages.

  1. Create an author account — free, takes a couple of minutes. See getting started as an author.
  2. Upload your product — the ZIP, screenshots, a demo link, a description and your price.
  3. Pass review — automated quality checks plus a manual review, usually within about 24 hours. If something needs fixing you get specific feedback and can resubmit.
  4. Get paid — read understanding payouts and Stripe fees and payment settings to choose who absorbs processing fees.

Use the revenue calculator on the Sell on AppTrovo page to estimate what your app could earn.

Get your first sales

  • Write the title for the search, not for yourself. "Acme — Self-Hosted Inventory Software with Barcode Scanning" is found; "Acme v2 Ultimate" is not.
  • Answer buyer questions on the page. Hosting requirements, what the license allows, how updates work, whether there are recurring fees.
  • Publish a walkthrough. A tour of the main workflows, with screenshots, ranks for long searches and answers the "what does it actually do?" question.
  • Ship updates and say so. A visible changelog and recent version date reassure buyers that the code is alive.
  • Reply to pre-sale questions quickly. For source code, the speed of your answer is a preview of your support.

Ready to list your app? Start selling on AppTrovo.