How to find your first white-label SaaS customer

Your first white-label SaaS customer is not going to be a stranger who finds your landing page in Google and pays the full price. That person arrives at customer thirty, not customer one. Customer one is someone who already trusts you, or someone you can warm up to a trust threshold inside a single phone call, and the job of the first ninety days is to find that person and put your product in front of them before they remember a hundred reasons to wait.

This post is the version that does not pretend cold outbound or content marketing is going to land customer one. They might land customer ten. Customer one is a warm-intro game, and the operators who acknowledge that publicly are the ones who get out of the zero-customer stage in weeks instead of quarters. Below is the playbook — who to ask, what to offer them, what to hand over, how long the whole thing should take, and the trap that keeps most operators stuck at zero longer than the work warrants.

Who your first white-label SaaS customer should be#

Three categories of person, ranked by how fast they'll close.

Someone you have worked with directly. A previous client at your day job. A small business whose marketing you helped on the side. The agency next door that you've had coffee with twice. They've seen your judgment up close. The product doesn't have to carry the trust — your prior work does. Warm intros from this band convert at 35 to 60 percent inside two weeks, based on the indie-operator interviews compiled in the IndieHackers solo-SaaS revenue threads and in Stripe's report on small-business payment patterns. The number sounds high until you realise the denominator is small — five well-targeted asks produce two to three serious conversations, not five hundred.

A friend's small business. Their gym. Their restaurant. Their dad's law firm. The trust is borrowed but it carries far enough to clear the "is this a scam" hurdle that every cold buyer applies to a brand with no reviews. The mutual friend is the proof. Conversion sits around 20 to 35 percent, slower than direct-prior-work but faster than anything cold.

Your previous employer, if you parted on good terms. This is the one most operators skip out of awkwardness. They shouldn't. The previous employer knows your work, knows the specific gap your product fills (you saw it from the inside), and has a budget that doesn't require board approval at the size you're charging. Conversion ranges wildly here — 10 to 50 percent depending on how you left — but the deal sizes tend to be larger because the buyer already understands the value.

What customer one is not: a stranger on r/SaaS who replied to your launch post, a name on a cold list from Apollo, a Twitter follower who liked three tweets, anyone who has not put their job or reputation alongside yours in a measurable way. Those people are real customers later. They are not customer one.

The offer for customer one is not the offer for customer thirty#

The mistake most operators make is showing customer one the same pricing page they'll show customer thirty. Customer thirty pays full price because the product has reviews, case studies, and a public deployment they can copy. Customer one has none of that. The price for customer one is whatever covers two things: the case study and the public-domain example.

Concretely, this looks like one of three offers:

Free for six months in exchange for a written testimonial and permission to name them. This works when the customer is a small business whose name carries weight in your target audience. The trade is honest — they get the product, you get the proof. Six months is long enough that the testimonial reflects real use, not first-week enthusiasm.

Half-price for the first year in exchange for a case study. Better when the customer would pay a meaningful amount at full price and you'd rather capture some revenue than none. Half-price feels generous enough that the conversation is short. The case study commitment is small — a thirty-minute interview, a paragraph they approve.

Free entirely for the first ninety days in exchange for hosting their live tenant on your subdomain and letting you link to it. This is the strongest offer when your audience is "people who want to see what the product looks like in production". A live tenant on their-business.yourdomain.com with their real logo and their real links is worth more to your sales page than three written testimonials.

The thing all three offers share: a clear deliverable that benefits both sides, a defined window that ends, and a customer who agrees in writing to the terms. The deliverable matters because operators who treat customer one as a favour-based arrangement tend to lose both the customer and the case study when the window ends. Treat it as a trade.

What to hand them on day one#

A live tenant on your subdomain with their logo, their colours, and at least three real links or QR codes pre-populated. Not a demo video. Not a Loom walkthrough. Not a landing page mock-up. The actual product, branded for them, working today.

The reason this matters: your buyer at this stage has zero capacity to imagine the finished thing from a slide. Their judgment is shaped by what they see in the browser when they click the link you send. If the dashboard says "Linked.Codes" in the top-left when they expected to see their own logo, the conversation dies right there. If the URL is yourplatform.com/account/123, same outcome. If the live links work and the QR scans and their logo is in the right place, the buyer asks "how much" instead of "how does it work".

The hand-over kit, in order of importance:

1. The subdomain on your domain, configured. theircompany.yourdomain.com, TLS valid, their logo loaded, their colours applied. This takes ten minutes inside a properly built whitelabel platform — the agency-mode docs walk the create-account flow, and the whitelabel email docs cover the from-address question that the buyer always asks but never first.
2. Three pre-built short links or QR codes pointing at their real pages. Their homepage, their booking page, their menu — whatever they actually share with customers. Generic example links read as a sales pitch. Their own links read as evidence.
3. A one-page walkthrough document. Two paragraphs and four screenshots. Not a manual. The buyer wants to know enough to feel safe, not enough to teach a class.
4. A standing offer to log in as them for the first month and fix anything that breaks. Agency mode handles this — log-in-as is one click. The buyer hears "I'll handle the setup myself" and stops worrying about the support gap.

Hand all four over inside a single ten-minute call on day one. If the call ends with the buyer logged into their own tenant and clicking around, you have closed customer one. The contract follows.

Customer #1 pipeline planner#

Three inputs decide how fast you can land customer one and what offer fits your hand. Drop your numbers in and the planner names a realistic days-to-customer estimate and the offer shape that fits.

The number the planner shows is realistic, not aspirational. The operators who beat the estimate consistently do one thing different: they have five named people they could ask tomorrow, and they actually ask them this week, not next quarter. The planner punishes "I could maybe ask my old boss eventually" because that is the same as zero intros. The list either exists or it doesn't.

The trap of waiting for "the right customer"#

Most operators in the zero-customer stage have a story about why the next customer is the wrong one. They want someone in the right industry. Someone who'd be a flagship logo. Someone with a budget that justifies the price. Someone who'd refer ten more. The story sounds responsible. It is, in practice, the most expensive way to stay at zero.

Customer one's job is not to be representative. It is to prove the product runs in production with someone other than you logged in. The case study, the testimonial, the live tenant — those are the real outputs. Whether the buyer is in your eventual core audience matters approximately zero at this stage. The first paying tenant for almost every solo SaaS in this category is a friend's small business, a former client, or the operator's own previous employer. Six months later, the operator forgets the awkwardness of that first deal entirely. They remember the case study.

The cost of waiting is concrete. Every month you do not have customer one, you do not have a case study, which means you cannot run cold outbound, which means the long-payback channels cannot start compounding, which means the timeline to twenty customers slips a quarter. The first month of zero is the most expensive month of the whole journey. The honest read on that math is in the agency-to-SaaS leap timing breakdown — the operators who flounder are the ones who treated customer one as a milestone rather than a foundation.

The script for the warm-intro ask#

The conversation that lands customer one is short and unsexy. The shape that works most of the time:

The opening names the relationship and skips the warm-up. "I built a thing that does X. I think it'd save your team Y hours a week. Can I show you?" Five sentences, no preamble. The buyer either says yes or they say no — both are useful answers and both arrive faster than a long pitch ever produces.

The middle is a screen-share. Not a slide deck. Open the dashboard, the one with their logo already on it because you set up the demo tenant before the call. Walk through three workflows that map to things you know they actually do. Stop after twenty minutes whether they have questions or not. Long demos lose customer one more often than short ones.

The close is the offer. "Here is the trade. You use it for six months free. At month two we record a thirty-minute interview I can write up as a case study. After six months, you decide whether to keep going — most people do, but no commitment." Or whichever offer the planner above pointed you at. The trade is named explicitly so they hear it as a deal, not a favour.

The buyer almost always asks one of three questions: how does the billing work, what happens if you disappear, can I cancel without it being a thing. Answer all three concretely. "Stripe charges go to your card on your dashboard." "If I disappear, you keep your domain and your data exports — here is what the migration looks like." "Cancel any time, you keep the case study, we shake hands and move on." A buyer who hears all three answers in plain English signs in the next call.

What you do not need yet#

There is a list of things operators in the zero-customer stage spend time on that does not move customer one. Cataloguing it is worth a section because the time spent on these is time not spent on the warm list.

You do not need a landing page that converts cold traffic. Customer one is not arriving from cold traffic. The landing page is a year-two project.

You do not need a content engine. The five-channel playbook for selling white-label SaaS without a sales team lays out when writing becomes the right priority — and the honest answer is "after customer three, not before". Writing in the zero-customer stage is procrastination dressed as work.

You do not need a tightly-scoped niche. Customer one's job is to prove the product runs. Picking a niche before you have one customer is theatre — the actual niche emerges from the first three paying tenants telling you what they care about.

You do not need a sales funnel, a marketing automation tool, a Notion CRM, a Calendly with three calendar types, a contact form, or a press kit. You need a working tenant, a phone, and the list of five warm names.

You do not need an MVP. If you are reading this, you have already chosen a platform — yours or one you licensed. The platform is the MVP. Building more product before customer one is the most common form of zero-customer procrastination, and the most painful to spot because it feels like progress. The employee-to-SaaS-owner 90-day plan covers this trap in detail — the operators who never get out of building are the ones who never accept that customer one is not a product problem.

The honest numbers behind warm intros#

Three numbers worth knowing before you start the warm list.

A researched list of five warm intros, asked in a single week with the script above, lands one to three paying customers inside thirty days. The variance is real — some weeks land three from five, others land zero. The number that matters is the cumulative one. Over a quarter of running the warm-intro pattern consistently, the conversion settles in the 35 to 60 percent range named earlier.

The deal sizes are usually small. Customer one is paying $20 to $80 a month in the median solo-SaaS case, sometimes nothing for the first six months by design. That is fine. The asset is not the MRR — it is the case study and the live tenant. The pricing-fit conversation happens at customer five.

The time to live tenant from first ask is seven days when the platform is properly built and three weeks when it is not. The white-label SaaS to resell shortlist names the five platforms in this category that can ship a live branded tenant in under a day — picking one of them is the difference between "I can demo this on Wednesday" and "I'll have it ready next month". The build versus license question is downstream of the customer-one timeline, not upstream of it.

The buyer almost always says yes faster than the operator expected. The voice in the operator's head that says "they'll think the price is too high" or "they'll want features I don't have" is almost never the buyer's voice. The buyer wants the problem solved. If you show them the problem solved, they buy.

How Linked.Codes ships this#

Two specific affordances make the customer-one hand-over fast on this platform. The first is the agency-mode create-account flow that provisions a sub-tenant directly from your dashboard, with their colours, their logo, and an optional setup link mailed straight to them. Ten minutes from "yes" to "here is your dashboard". The second is the log-in-as feature in the same admin surface — once the tenant is live, you can step into their dashboard at any time and fix things they don't have the bandwidth to fix themselves. The first month of customer one almost always includes one of these "I'll handle it" moments, and shipping it as a built-in instead of an awkward screen-share is the difference between a customer who refers and a customer who churns.

The lifetime tier is part of the same story. A buyer evaluating a white-label platform for the first time is implicitly asking "what happens to my domain if you go away" and the lifetime model answers it differently than a monthly subscription does. You have already paid for the platform. The data exports work. The DNS migration path is documented. Customer one hears that and stops being nervous about the dependency, which is most of what stops them signing.

The other side of that conversation — the pricing trade-offs, when one-time wins versus subscription — sits on the pricing page, which the white-label QR code business playbook cross-references for the agency-audience version of the same decision.