Reseller SaaS — license a tool, brand it, resell it

Reseller SaaS is the legal way to own a software product without writing the code. You buy a license from the vendor that built the tool, swap the branding for your own, set a price you choose, and sell it to customers who never see the upstream name. The model has been around as long as software has — every white-label phone system, every rebranded help-desk widget, every QR code service running under a small agency's logo is a reseller SaaS at the bottom of the stack. What's changed in the last few years is how cheap and how legal it has become for a one-person operation to run one. The mechanics are not complicated. The trade-offs are. Most people reading a reseller-license clause for the first time also need a calendar, which is what the 90-day plan from license-shopping to the first ten paying customers lays out week by week.

This post walks through what a reseller SaaS license actually buys, what the margin math looks like at typical prices, the four contract clauses that decide whether the deal is good or bad, and the surprises that catch first-time resellers in their first ninety days. Most of this is sitting in plain English in license agreements people don't read. The rest comes from watching small operators trip over the same problems in roughly the same order.

What reseller SaaS actually means#

The phrase covers two different things, and the difference matters because the contract clauses look almost identical until you read closely.

Source-code reseller SaaS. You pay a one-time fee — typically $300 to $5,000 on marketplaces like CodeCanyon — for the source code of a working application. You install it on your own server, put your brand on it, and sell it to your customers. You are the operator. You handle uptime, security patches, customer support, billing integrations, and every word of marketing copy. The vendor's role ends roughly the moment your bank transfer clears, modulo six to twelve months of bug fixes if the listing promised them.

Hosted reseller SaaS. You pay a license fee — sometimes one-time, sometimes recurring, sometimes a hybrid — for the right to put your brand on a tool the vendor still hosts. The vendor handles servers, uptime, patches, and the unglamorous infrastructure. You bring the brand, the customers, the pricing, and the relationship. Your customers see your name on every surface — login, dashboard, emails, checkout — and never know about the vendor underneath. Linked.Codes is in this category, as are Vendasta, GoHighLevel, and most of the white-label CRM and email tools agencies resell.

Both arrangements are legal. Both let you sell software as if you built it. The first puts more weight on you (more control, more work, more risk). The second puts more weight on the vendor (less control, less work, less risk). Which one is right depends on whether you'd rather own a server or own a customer list. The buy-vs-build cost math spells out the labour cost on the source-code side, and most operators who run the spreadsheet honestly land on the hosted side once they price their own time at anything above zero. Agencies weighing reseller against the simpler affiliate route can compare both in the stack-or-pick decision tool for agencies — most agency books end up reseller at the two or three platforms that anchor delivery and affiliate at the rest.

The margin math nobody runs#

Most reseller SaaS pitches handwave the margins with a phrase like "you keep what you charge minus what we charge". That's accurate and useless. The honest version of the calculation includes payment fees, support time, refund rate, and the cost of acquiring the customer in the first place.

Take a typical hosted reseller deal. You pay the vendor $20 a month per active customer. You charge your customer $79 a month. The headline margin is $59 — about 75%. Now subtract the parts the headline skips:

• Stripe fee. 2.9% + $0.30 on $79 is $2.59. Margin drops to $56.41.
• Refund risk. The first three months of a SaaS relationship have the highest churn and the highest refund rate. Bake in a 5% expected refund cost across early months — about $4 a month against a fresh customer. Margin drops to $52.41.
• Support time. A new customer averages 30 to 60 minutes of support across the first month — questions about setup, billing, things the docs don't explain clearly enough. At $40 an hour for your time, that's $20 to $40 per first month. Margin in month one drops to $12 to $32.
• Customer acquisition cost. If you spent $40 to land that customer (a paid ad, a content asset's allocated cost, the time on a sales call), the first month is at break-even or slightly negative.

So a $79 sale against a $20 wholesale is not a $59 win. Month one is roughly $0 to $32. Months two through twelve, with support tapering off and acquisition cost amortised, are closer to $52. The lifetime value math depends on how long the customer stays, which in this category averages 14 to 24 months for small business customers, longer for agencies who embed the tool into client deliverables.

The version of this conversation that goes wrong is the one where someone hears "75% margin" and decides the business is a money printer. The real shape is a six-month payback on customer acquisition, then a decent recurring net for as long as the customer stays. Build the marketing engine for the long net, not the headline.

What you can — and cannot — change about the product#

Every reseller SaaS license has a list of things you can change and a list of things you cannot. The list varies by vendor. The clauses below come up in roughly nine out of ten reseller agreements in this category.

You can usually change: the brand name and logo on every customer-facing surface, the accent colour, the font, the marketing copy on the public pages, the price you charge customers, the domain the product runs on, and the email templates customers receive. These are the deliverables that make the product feel like yours.

You cannot usually change: the underlying feature set, the database schema, the API endpoints, the way analytics are computed, the URL structure of the dashboard. These are the deliverables that make the vendor's life sustainable — if every reseller customised them, the vendor couldn't ship a single update without breaking dozens of forks.

The grey area: small CSS tweaks, custom doc pages, an extra page slotted into the marketing site, custom Stripe products you sell on top of the vendor's pricing. Some vendors allow this freely; others require it to go through a feature request. Read the license carefully on this — the line between "I added a custom page to the docs" and "I forked the docs system" is where reseller arguments happen most often.

Know which side of the line every customisation lives on before you promise it to a customer. The number-one source of reseller-vendor disputes is a reseller who told a customer "yes we can do that" and then asked the vendor whether they could do that. The right order is the other one.

The four clauses to read before you sign#

A reseller agreement is usually 8 to 20 pages and most of it is boilerplate. Four clauses do the actual work of deciding whether the deal is good. Read these four carefully even if you skim the rest.

The exclusivity clause. Are you the only reseller in your country, your industry, your customer list — or is the vendor also reselling to ten other people who are about to compete with you on the same product? Most modern reseller deals are non-exclusive (the vendor sells to everyone). That's fine, but it means your differentiator is your audience and your brand, not the product itself. If you want exclusivity, expect to pay 5x to 50x what a non-exclusive license costs.

The termination clause. What happens if the vendor decides to stop the program — to your customers, to your data, to your monthly fees? A clean termination clause spells out a data export window (90 to 180 days is typical), a refund schedule for any pre-paid fees, and a path for you to migrate customers to a successor product. A messy termination clause says "we may terminate at any time with 30 days' notice" and walks away. The first is signing a partnership; the second is signing a flip-of-a-coin.

The pricing clause. Can the vendor raise the wholesale rate at will, with what notice, capped at what amount? A reseller business with surprise wholesale increases is a business with surprise margin compression you have to either eat or pass on. The cleanest version: vendor commits to a fixed wholesale rate for 12 to 24 months, with annual increases capped at CPI or 5%, whichever is higher. The dirtiest version: "wholesale rates may be revised at vendor's discretion."

The branding-removal clause. Is the vendor's name allowed to surface anywhere your customer might see — login emails, error pages, footers, share previews, OAuth screens? In a true whitelabel deal, the answer is no, on every surface. In a half-whitelabel deal, the answer is "no on the dashboard, but customer emails come from us." The half-whitelabel deals are everywhere and most resellers don't notice until a customer screenshots an email signed by someone other than them.

A reseller deal is a marriage with a corporate exit clause. Read the exit clause first — the rest of the contract is decoration.

The five gotchas that catch first-time resellers#

These don't appear on marketing pages. They appear at month two, three, or six, when you've already onboarded customers.

Customer-support load is yours, not the vendor's. Even on a hosted whitelabel deal, your customer emails you, not the vendor. If a feature is broken, you escalate to the vendor and relay their answer in your voice. This is the line item that makes operators quit reselling — they imagined "passive income" and signed up for a part-time helpdesk job. Plan a minimum of 30 minutes per active customer per month for the first six months and 10 minutes per customer per month afterward. The running a reseller link platform piece covers the operational side of this in more depth.

Stripe radar and chargeback liability stay with you. Every Stripe account has a chargeback rate. If your reseller customers churn unhappily and dispute charges, your Stripe account takes the hit, not the vendor's. A 1% chargeback rate triggers Stripe risk reviews. A 1.5% rate puts your account in jeopardy. The cleanest defence: clear refund policy, easy cancel button, prompt support replies. Refund liberally in months one and two — the customer who asked for a refund is cheaper than the customer who chargeback-disputes.

The vendor's roadmap is not your roadmap. If you're selling QR codes and the vendor pivots to add invoicing, your marketing copy doesn't change but your product surface does. Customers see new buttons. Some like them; some get confused; some ask why they're paying for invoicing they didn't sign up for. You don't get a vote — you get to write the changelog post explaining the new buttons. Pick a vendor whose roadmap direction roughly matches your own, because you'll be living with their priorities.

Tax and merchant-of-record rules are a real cost. When you sell software internationally, somebody needs to collect VAT in the EU, GST in Australia, and a dozen state-level sales taxes in the US. If you're the merchant of record, that someone is you. Tools like Paddle or Lemon Squeezy take this off your plate by being the merchant of record for you, in exchange for a fee (typically 5% on top of your processor fee). Stripe Tax handles the calculation but not the remittance. Budget at least a Saturday afternoon for figuring out which structure works for your sales geography.

The price you set is not the price you keep. First-time resellers price too low — they see a $20 wholesale, set a $39 retail, and underprice the entire support and acquisition stack. Six months later they raise prices and lose 10% of customers in protest. The cleaner play is to price closer to the market norm from day one (research three to five comparable products, take the median), explain the value clearly, and accept that 5% of inbound prospects will say it's too expensive. They are not your customer. The customer who balks at $79 a month is also the customer who'll chargeback at month two.

The reseller margin calculator#

Plug in your wholesale rate, your retail price, your support estimate, and your acquisition cost. The widget computes month-one net, ongoing monthly net, and lifetime value at typical tenure.

Defaults are typical for the SMB-tier reseller arrangements that show up most often in this category. The "customers needed for $5k/mo net" line is the one most worth staring at — it tells you whether your model needs 50 customers or 500 to clear the same monthly net, which is the difference between a side income and a full-time job.

Where reseller SaaS works — and where it doesn't#

The model fits some businesses. It doesn't fit others. Five fit patterns and three anti-patterns from the field.

Fit: agencies who already serve clients in a niche. A web agency with twenty restaurant clients can resell a QR-menu tool to all twenty in a quarter. The customer acquisition cost is roughly zero because the relationships exist. This is the highest-margin reseller use case in the category — the qr code reseller business economics breakdown walks the revenue, time, and support load through ten, fifty, and a hundred customers if you want the plateau-by-plateau view.

Fit: solopreneurs with an audience. A creator with 20,000 newsletter subscribers in a clear niche can resell a tool that solves a specific niche problem and earn a substantial percentage of subscribers' attention. Margins are headline-good because acquisition piggybacks on existing distribution.

Fit: regional resellers in markets the upstream vendor ignores. If the vendor is US-only and you can run customer support in Spanish for Latin America, you have a real differentiator that justifies the resale. The vendor benefits from market reach; you benefit from a moat the vendor can't easily compete with.

Fit: industry consultants productising their advice. A marketing consultant who keeps recommending the same email tool, then keeps doing the same setup work for clients, can resell that tool with the setup pre-baked. The product is the consulting, the SaaS is the delivery vehicle.

Fit: B2B referrers tired of unreliable affiliate payouts. Reselling pays per-customer-per-month for as long as the customer stays, which is structurally better than a one-time bounty for many B2B affiliates. The recurring vs one-time affiliate rates analysis covers the math case for picking ongoing payouts over flat bounties.

Anti-fit: someone who wants pure passive income. Reselling has support obligations and customer churn. It's not a referral fee. Treat it as a small business and the math works; treat it as a yield product and the math doesn't.

Anti-fit: someone with no audience and no industry. If you have no existing channel, every customer costs paid-acquisition money. The math gets thin fast unless you can find a content or SEO angle that works in your niche. The zero to $5k MRR on a single tool walkthrough covers the channel-building side honestly.

Anti-fit: someone who wants to compete on the product itself. Reselling means the product surface is the vendor's. If you want to differentiate on features, you're building, not reselling.

What to do in the first ninety days#

A short version of the playbook the operators who survive their first year tend to follow.

Days 1–14. Buy the license. Set up your branding everywhere — domain, logo, email From address, accent colour. Write your pricing page. Write your terms of service (your own, not the vendor's — you're the merchant of record on your customers' invoices). Test the full signup-to-cancel loop on your own brand using a test card. If anything still says the vendor's name, fix it before any customer sees it.

Days 15–30. Find your first five customers. They are not strangers from the internet. They are people who already trust you — past clients, newsletter subscribers, colleagues, the friend who's been complaining about needing this exact tool. Charge them full price; do not give discount codes. The first five real-money customers tell you more than a hundred free trials.

Days 31–60. Write the docs the vendor's docs don't cover — your own onboarding, your own FAQ, your own refund policy. Build the email cadence (welcome, onboarding day 3, check-in day 14). Set up monitoring on your own brand (status page, uptime alerts, error-rate notifications). If the vendor goes down, you find out before your customer does.

Days 61–90. Start the channel that scales. Pick one — content, paid ads, partnerships, outbound — and commit a real schedule to it. Your first ninety customers came from your network; the next ninety need a repeatable channel. Resellers who skip this step plateau at twenty to fifty customers and conclude that the model doesn't work; the model works fine, the channel was missing.

What Linked.Codes is in this picture#

This site is one of the products on the buy column. The model is hosted whitelabel: one-time license fee for the lifetime tier, then modular hosting layers if you outgrow the free hosting tier — see /pricing for the current figure and any active discount. You bring the domain, the logo, the customers, and your own Stripe; we run the servers, ship the features, and stay out of every customer-facing surface. The setup walkthrough lives in the getting-started doc and the customisation surface is in the branding doc.

Worth being honest about what reselling Linked.Codes does and doesn't get you. It gets you a working short-link and QR platform under your brand on day one, customers who can pay you in your own Stripe, and a team that ships features without you having to commission them. It doesn't get you a unique product surface — every reseller on the platform sells roughly the same set of features, so your differentiator is your brand, your audience, and your support. If you're trying to compete on product novelty, this isn't the right column. If you're trying to land paying customers in a niche where you already have a relationship, the math usually works out.

How reseller SaaS compares to the alternatives#

Three other models compete with reselling for the same operator attention. Quick honest comparison.

Affiliate marketing. You promote someone else's product, take a cut of the sales, never touch the product surface or the customer relationship. Lower work, lower margin, no brand control, no ownership. Right answer if you have audience but no time. Wrong answer if you want a business asset that compounds.

Building from scratch. You write the code, own everything, take six to nine months to get to first revenue. Higher work, higher control, longest payback. Right answer if you have technical skill and runway. Wrong answer if you want to test a niche cheaply.

Pure SaaS subscription via a generic platform. You pay a third party (HighLevel, Vendasta, etc.) on a monthly basis, sell to your customers under their brand, and take whatever margin remains. Lower one-time cost, ongoing fee compounds, less own-able than reselling on a one-time license. Right answer for very early validation. Wrong answer once volume justifies the lifetime model.

A small operator in a clear niche almost always lands on reselling once they've thought through these alternatives honestly. The combination of one-time license cost, full brand control, and immediate revenue is hard to beat for the audience that actually exists for this kind of business.