Skip to content
For Sellers

How to Price Source Code and Web App Scripts

A practical method for pricing the source code of a web app or SaaS script: three price anchors, a worked example, how editions and support plans fit in, and when to raise your price. Written for developers selling one-time licenses.

• Nov 17, 2026 • 12 min read
How to Price Source Code and Web App Scripts

The short answer: price source code against what the buyer would otherwise spend, not against what it cost you to write. A complete web application replaces either months of custom development or years of SaaS subscription fees, so your price should sit well below both of those numbers and well above the price of a theme or a plugin. Then adjust it with evidence: comparable listings, your conversion rate and the questions buyers ask before they purchase.

This guide gives you a repeatable method for one-time license pricing. It is one part of our broader guide on how to sell your web app or SaaS source code, which covers packaging, where to sell and getting your first sales. Here we focus only on the number on the price tag and the decisions around it.

If you are still unsure whether your product will sell at any price, read the sections on buyers and anchors first. If you already have a price and want to know whether it is too low, jump to the section on signals that tell you to raise it.

Why pricing source code is different from pricing SaaS

SaaS pricing is about recurring value: you charge per seat, per month, and the customer keeps paying as long as they use the product. Source code is sold once. The buyer pays, downloads the code, runs it on their own server and may never pay you again unless they renew support or buy an upgrade. That changes three things.

  • The buyer carries the operating cost. They pay for hosting, installation and maintenance. Your price has to leave room for that, or self-hosting stops making sense compared with a subscription.
  • The buyer is taking a risk. They cannot cancel next month if the product disappoints. Anything that lowers that risk (a live demo, clear documentation, a visible changelog) lets you charge more.
  • Your revenue comes from volume and add-ons. Without monthly payments, your income depends on how many licenses you sell and on extras such as extended support. Pricing too high can cost more in lost volume than it gains per sale.

If your product only makes sense as a hosted service, look at SaaS pricing models instead. The rest of this guide assumes a one-time license for self-hosted code.

Who is buying, and what are they comparing you to?

Your price is always judged against an alternative. Different buyers compare against different things:

BuyerWhat they compare your price toWhat makes them pay more
Small business ownerThe yearly cost of a SaaS tool for their teamNo per-user fees, data on their own server, a working demo
Agency or freelancerTheir own hours to build the same features for a clientClean code, easy customization, a license that covers client work
Founder launching a SaaSMonths of development before the first paying customerMulti-tenancy, billing, admin tooling, a credible update history
Developer learning or prototypingFree open-source projects and tutorialsA free edition first; they rarely pay for a full license on day one

Pick the buyer you most want and price for them. A booking system aimed at salon owners and a booking system aimed at agencies building for salon owners can be the same code at different prices, because the alternatives are different.

Three anchors for a one-time license price

Use three independent estimates and look for the range where they overlap. Each one alone is misleading; together they give you a defensible number.

Anchor 1: replacement cost

Estimate how long it would take a competent developer to build what you are selling, from an empty repository to the same level of polish. Count everything a buyer gets: authentication and roles, every module, the admin panel, the installer, the tests, the documentation. Multiply the hours by a typical freelance rate in your buyer's market. This is the ceiling. Nobody pays close to it, because buying code still means installation, learning and some risk, but it tells you how much value is on the table.

Anchor 2: subscription alternative

Find the SaaS products that solve the same problem and work out what a typical customer would pay over two or three years. For a business buyer this is the most persuasive comparison, because it is the decision they are actually making: rent or own. Keep it honest and add the self-hosting costs to your side (a server, someone to install updates). Our article on SaaS vs self-hosted total cost of ownership walks through that calculation from the buyer's side.

Anchor 3: comparable listings

Look at similar complete applications on marketplaces, in the same category and with a similar feature depth. Ignore themes, UI kits and single-feature scripts; they are not your competitors. Note the range, not the average, and note which listings have demos, recent updates and documentation. Products with those signals can charge at the upper end of the range.

Rule of thumb: your price should be a small fraction of the replacement cost, clearly below one year of the subscription alternative for a typical customer, and within the upper half of comparable listings if your product is better documented and maintained.

A worked example

All numbers below are illustrative, not market data. Replace them with your own research.

Imagine you are selling a self-hosted appointment and client management app for small service businesses.

  1. Replacement cost. You estimate 600 hours to rebuild it. At an illustrative freelance rate of $60 an hour, that is $36,000. This is your ceiling, and it tells you even a few hundred dollars is a small fraction of the value.
  2. Subscription alternative. A comparable SaaS tool costs around $40 a month for a five-person team in this example, or $1,440 over three years. A self-hosting buyer also pays for hosting, say $10 a month, which is $360 over the same period.
  3. Comparable listings. Complete apps in the same category on marketplaces range from $49 to $299 in this example, and the ones at the top have live demos and a changelog.
  4. Your range. The overlap is roughly $149 to $249: well below three years of subscription after hosting, in the upper half of comparables, and a tiny fraction of replacement cost.
  5. Your net per sale. On AppTrovo you keep 90% of each sale. At a $199 price, your share before payment processing is $179.10. Check Stripe fees and payment settings to see how processing fees are handled for your account.

Start at the lower-middle of the range ($179 in this example) if you have no reviews yet, and plan to move up as reviews and update history accumulate.

How should editions and add-ons affect the price?

A single price is easy to understand, but many sellers earn more by structuring what a buyer can choose. On AppTrovo there are exactly two editions per product, plus optional support time.

Community and Commercial editions

A free, feature-limited Community edition and a paid Commercial license work like a free plan that never expires. Buyers can install the Community edition, even in production, learn the codebase and recommend it; when they need the full feature set and your support, they buy the Commercial license. The free edition also builds reviews and search visibility before you have many paid sales.

The trade-off: some people who would have paid will be satisfied with the free version. Decide what the Commercial license adds beyond the right to commercial use, such as modules, support or features, and make that difference obvious on the listing. The exact license wording is on the license terms page.

Support as a separate value

Every license includes a support period. You can set how long it is and offer longer support at checkout or as a renewal later. This lets you keep the entry price moderate while buyers who want more help pay for it. If you go this route, write a clear support policy first; our guide to support, updates and versioning includes a template.

Single-company and SaaS editions

If your app can run multi-tenant, that is a different product for a different buyer. A founder who will resell your software to dozens of customers gets far more value than a single business running it for itself. List the SaaS version as its own product at a higher price, with its own title and description, instead of trying to cover both buyers with one listing.

Common pricing mistakes

  • Pricing like a theme. A complete CRM priced like a landing page template tells buyers it is a toy. Low prices also attract the buyers who expect the most free help.
  • Pricing from your hours. "It took me 400 hours, so it should cost a lot" is not how buyers think. They care about their alternative, not your effort.
  • Too many tiers. Five versions with overlapping features cause confusion and support tickets. Two editions and an optional support extension are enough for most products.
  • Discounting by default. Permanent "sale" prices train buyers to wait. Use occasional, time-limited promotions with a real reason, such as a major release.
  • Ignoring support cost. If each buyer sends five tickets that take an hour each, a low price can turn every sale into a loss. Estimate support time per sale before you set the number.
  • Forgetting regional buyers. Listings on AppTrovo are shown in seven languages, so some buyers compare your price with local salaries and local alternatives. A price that is easy in one market can be a hard decision in another; that is a reason to keep a free edition, not to underprice everywhere.

Pricing checklist before you publish

  1. Write down the replacement cost estimate, the subscription alternative and the comparable range.
  2. Choose a price inside the overlap and write one sentence explaining why it is fair. If you cannot, the price is probably wrong.
  3. Decide whether you will offer a free Community edition, and what the Commercial license adds.
  4. Set the included support period and estimate your support time per sale.
  5. Calculate your net per sale after the 10% platform fee and payment processing.
  6. Make sure the listing justifies the price: a demo, screenshots of real screens, requirements and what is included. Our guide to writing a product listing that sells code covers this.
  7. Set a date, for example 60 days after launch, to review the price against the signals below.

When should you raise or lower your price?

A price is a hypothesis. Collect signals for a few weeks before you change it, and change one thing at a time so you know what worked.

SignalWhat it suggestsPossible action
Steady sales with almost no pre-sale questionsBuyers see clear value; you may be underpricedRaise the price by 15–25% and watch for a month
Many demo visits, few purchasesThe price or the listing does not match what buyers seeFix the listing and demo first, then revisit price
Many questions about whether it fits their use casePositioning problem, not a price problemAdd a "who it is for" section and FAQs
Buyers asking for discountsNormal at any price; not a signal by itselfOffer a clear Community edition rather than ad hoc discounts
Support load growing faster than salesThe price does not cover the help buyers needImprove documentation, raise the price or shorten included support

Raising prices after a major release is natural and easy to explain: the product does more than it did. Existing buyers keep what they bought, and new buyers pay for the newer, larger product. Announce the change in your changelog so the price history is transparent.

How your price turns into income on AppTrovo

AppTrovo charges a 10% platform fee, so you keep 90% of each sale, and there is no exclusivity: you can sell the same product on your own site too. How the money reaches you depends on the order. If an order contains only your products and your Stripe Connect account is active, your share is transferred to your Stripe account at the moment of sale, and Stripe then pays out on its own schedule. Otherwise AppTrovo collects the payment, holds earnings for 7 days by default, and you request a payout once you reach the minimum ($50 by default). The details are in understanding payouts, and the revenue calculator on the Sell on AppTrovo page lets you test prices against your expected volume.

For general guidance on estimating your own business costs, including the time you will spend on support and maintenance, the U.S. Small Business Administration has a useful guide to calculating business costs. If you sell internationally, confirm how sales income is taxed in your country with a qualified accountant.

Frequently asked questions

How much should I charge for a script?

Charge based on the buyer's alternative, not your effort. A small single-feature script competes with plugins and free code, while a complete application competes with months of development or years of SaaS fees. Use the three anchors in this guide (replacement cost, subscription alternative and comparable listings) and start in the range where they overlap.

Is a one-time license better than a subscription for source code?

For self-hosted source code, a one-time license is what most buyers expect, because they are paying for ownership and running the software themselves. You can still earn ongoing revenue through support renewals and major-version upgrades. If you want recurring revenue from hosting, that is a SaaS business rather than a code sale.

Should I offer a free version of my web app?

A free, feature-limited Community edition often helps, because buyers can run the code with no risk and recommend it to clients who then buy the Commercial license. It works best when the features you reserve for the Commercial license are clearly valuable. If your product only appeals to businesses, a strong live demo may do the same job.

How often should I change my price?

Review it about 60 days after launch and then after each major release. Change one thing at a time and give each change at least a few weeks, so you can tell whether sales changed because of the price or because of something else, such as a new listing or a seasonal pattern.

Do I need to price differently for a SaaS-ready edition?

Yes. A multi-tenant edition lets the buyer earn recurring revenue from their own customers, so it is worth more to them than a single-company install. List it as a separate product with its own price and description, and link the two listings to each other.