My revenue is 80% one enterprise customer. Does that kill my sale?

Asked by makers — answered by AXIS. This question comes up repeatedly in listing intake and onboarding conversations; we have reworded it so no individual maker is identifiable.

The question: "My AI app does $9k MRR — $7.2k of it from one enterprise customer on an annual contract, the rest from ~40 small accounts. I want to sell within a year. Every valuation thread here lists concentration as a discount; at 80%, is it a discount or a dealbreaker?"

The answer. At 80%, it's a structural problem, not a pricing haircut — but structural problems have structures, and yours contains more options than the dread suggests. What actually happens when concentrated apps meet buyers, and the year of moves available:

How buyers price it, honestly: a buyer underwriting your $9k MRR is really buying two assets — a $1.8k MRR forty-account SaaS (priced normally, per the whole valuation curriculum) and a single customer relationship worth $7.2k/month that could end by one procurement decision they don't control. The second asset gets priced somewhere between heavily-discounted and zero depending on its evidence: contract length remaining, renewal history, switching costs, and — the item sellers forget — whether the contract survives the sale at all (the change-of-control audit from the checklist thread is urgent for you: an assignment-consent clause in that enterprise MSA means your anchor customer holds approval rights over your exit, and you want to know that this year, not in escrow negotiations).

The moves, in order of impact-per-month available:

1. Convert concentration into contract. The single highest-leverage negotiation available: renew the enterprise deal early, longer, and assignable — a 24-month renewal with assignment consent pre-granted (or a clause silent on assignment, which for the buyer's counsel is next-best) converts your riskiest asset into your most documented one. Enterprise customers renew early for consideration all the time (pricing lock, roadmap commitment, support tier) — and note the reframe: you're not asking a favor; you're trading real value for term length, which is a normal enterprise conversation.

2. Grow the denominator, tell the trendline. You likely can't out-grow 80% concentration in a year — but 80%→60% with the small-account cohort demonstrably compounding is a trendline story ("concentration declining N points per quarter"), and trendlines reprice structural reads (the same mechanism as the margin-repair and partial-Passport threads: direction plus evidence outperforms position). The forty accounts are also your durability evidence — their retention curve is proof the product works without the anchor's specifics.

3. Document the relationship's depth. If the anchor is genuinely embedded — integrations, workflow dependence, switching costs — evidence it: usage depth metrics, the integration inventory, stakeholder breadth (three departments using it beats one champion; a champion-dependent account is concentration squared, and buyers ask exactly this). The relationship's transferability is the diligence question; pre-answer it.

4. Consider the structural resolutions. Where the concentration won't dilute in time: the anchor as buyer (the customer paying $86k/year for a tool they depend on is sometimes its most rational acquirer — strategic-fit logic from the valuation thread, sitting in your inbox; approach carefully and late, since a failed overture complicates the relationship the sale depends on), and earnout-shaped bridges (deal terms sharing the anchor-renewal risk: base price on the diversified revenue, contingent consideration on the anchor's renewal — the micro-earnout skepticism from the transition thread applies, but this is the narrow case earnouts exist for: a single, binary, observable risk both sides can name).

The honest answer to "dealbreaker?": at 80% static and undocumented, close to it — expect offers pricing mostly the diversified fraction. With a year of the moves above — contract termed and assignable, trendline bending, relationship documented — you're selling a normal small SaaS with a well-evidenced anchor account, at a discount measured in fractions of a multiple rather than fractions of the price.

Which move is available to you first — and does your enterprise MSA have the assignment clause? (Go read it. This thread will wait.)

AXIS Editorial

Follow-up from maker intake: "Read the MSA. Assignment requires written consent, 'not to be unreasonably withheld.' How bad, and what now?"

Middle case, and common: 'not unreasonably withheld' is materially better than bare consent-required (it constrains refusal and gives a negotiating framework) while still being a process your closing timeline must contain — the buyer's counsel will want the consent in hand, not the clause's comfort, before funds move. The now-moves: (1) don't raise it as assignment yet — raise it as the early-renewal conversation from the thread's move 1, and negotiate the assignment language in the renewal (pre-granted consent for acquirers meeting defined criteria — financially capable, service-continuity commitments — is a clause enterprise counsel sign regularly when it arrives inside a renewal they want); (2) build the consent case file as if you'll need it anyway: the service-level history, the continuity commitments a buyer would make, the relationship documentation from move 3 — the 'reasonableness' standard means a well-evidenced consent request is hard to refuse, and preparing it costs nothing if the renewal route lands first; (3) calendar the mechanics: consent processes at enterprises run through legal-and-procurement at enterprise speed (weeks-to-months), so your eventual deal timeline should start that clock early with the buyer's identity protected as long as feasible (consent requests can be staged — willingness-in-principle first, named party under NDA later). The reframe for morale: you now know — which puts you ahead of most concentrated sellers, who discover the clause from a buyer's counsel memo with the deal on pause behind it.

AXIS Editorial

Follow-up from maker intake: "The 'anchor as buyer' move — how do I even explore that without torching the relationship if they're not interested? The asymmetry is terrifying: they learn I want out; I learn nothing."

The asymmetry is real and the staging exists to manage it: (1) never open with sale — the explorable-safely versions are adjacent conversations you have honest reasons for anyway: the early-renewal negotiation (which reveals their commitment depth by how they engage), a roadmap-partnership conversation ('what would make this indispensable for you long-term' — their answer maps their strategic valuation of you), or the build-vs-buy question surfaced from their side (procurement reviews sometimes ask it; your champion knows if it's been asked); (2) read the tells before telling — acquisition-receptive anchors show it: they've acquired tooling before, they've asked about your company's continuity ('what happens if you get hit by a bus' from a customer is diligence-curiosity wearing concern), your tool appears in their internal strategy language; (3) if the tells are present, the approach that preserves deniability is the banker's-question form, deliverable by you without a banker: 'we're periodically approached about acquisition; before anything ever got serious I'd want to understand whether [customer] would see strategic value — how would that conversation even work here?' — hypothetical, flattering, and answerable without either side committing; (4) if the tells are absent, don't — run moves 1-3 and sell to a third party with the contract termed; the anchor-as-buyer path is the dessert menu again, not the plan. And the risk-bounding note: everything above happens after the renewal is signed, never during — the renewal is the relationship's load-bearing wall, and you don't test walls mid-construction.

Jonathan (AXIS Launch)

Marketplace mechanics for concentrated apps, since this profile shows up in intake regularly: the anonymized public auction layer handles your shape better than open listing would — 'AI [category] tool, $9k MRR, 80% anchored by 24-month enterprise contract (renewed 2026), assignment pre-consented, 40-account diversified base growing' is a publishable headline that concentration-tolerant buyers (they exist: operators with enterprise-account management DNA price anchor relationships as assets, not risks — one profile's poison is another's pipeline) can self-select into, while the bidder-room layer holds the sensitive specifics (the customer's identity above all — anchor-customer anonymity through diligence is a legitimate seller requirement buyers accept, with identity disclosed at defined depth under the NDA). What the concentration does change on the platform side: metrics verification for your listing will state the concentration explicitly — the badge system verifies what's true, and '80% single-customer' is a material fact the dated verification covers, not a detail curation smooths. Buyers finding it in diligence instead of the listing is the integrity failure this platform exists to not have — and per the whole trust thesis, the disclosed version sells better anyway: the buyers who proceed are the right ones, pre-selected.

AXIS Editorial

Follow-up from maker intake: "Inverse question from the 40-account side: I'm diversified but tiny-ticket — 200 customers averaging $18/month, nobody over 2%. Is maximal diversification just... good, or is there a concentration-shaped problem hiding in my shape too?"

There's a hiding one, and naming it completes the thread's picture: concentration risk generalizes to dependency risk, and diversified-tiny-ticket apps typically re-concentrate one layer down — in channel (200 customers who all arrived through one marketplace, one SEO cluster, or one platform's app store is one dependency wearing 200 hats — the consumer-durability thread's stop-pouring test applies), in platform (the wrapper thread's provider-feature risk hits small-ticket tools hardest, because $18/month customers churn frictionlessly to a native feature), and in support economics (200 accounts at $18 generates enterprise-grade ticket volume at hobby-grade revenue-per-ticket — buyers price the support-hours-per-dollar ratio, and tiny-ticket shapes often fail the actually-a-job arithmetic from the valuation thread on support load alone). Your diligence prep therefore emphasizes different artifacts: channel-mix evidence (the acquisition-source breakdown, trending), the churn-and-replacement engine's economics (CAC payback at your ticket size), and support-automation receipts (the deflection rate, the docs, the ticket volume trendline). The symmetric conclusion: neither shape is clean — the anchor seller proves the relationship transfers; you prove the machine runs itself. Buyers price whichever proof is missing.