Customer Exclusion Policy
Help someone deliberately identify and exclude non-ideal customers to improve product outcomes, community quality, and long-term margins — using Ramit Sethi’s framework from My First Million.
When to Use
The user is dealing with customers who aren’t getting results, a community that feels diluted, or a business that keeps attracting the wrong buyers. They might say:
- “Our refund rate is too high”
- “We get a lot of customers who complain but don’t follow through”
- “How do we attract better clients?”
- “Some people are just exhausting to serve”
- “I feel like I’m accepting anyone who swipes a card”
- “How do I make our paid community more valuable?”
The Core Principle
From Ramit Sethi (40cZdzYHd2I.md):
“I don’t allow people with credit card debt to join our flagship programs, the higher-end ones. That costs us millions of dollars every year. And it’s funny, people will plagiarize our sales pages, they’ll plagiarize our email copy. For some reason, they don’t plagiarize that policy. I wonder why that is, because 90% of their customers would disappear overnight.”
The instinct of almost every business is to maximize acceptance — to say yes to anyone willing to pay. Ramit’s insight is the opposite: accepting the wrong customer is expensive, not just in refunds and support costs, but in the damage it does to the community, the product’s reputation, and the operator’s ability to deliver great outcomes.
Exclusion is not scarcity theater. It is a genuine commitment to the customer’s success.
Step 1: Define What “Getting a Result” Requires
Before identifying who to exclude, clarify what your ideal customer actually needs in order to succeed with the product.
Ask the user:
- What does a successful outcome look like for your customer?
- What does a customer need to bring to the table — in terms of resources, mindset, situation — to achieve that outcome?
- What does a failed customer look like? What was true about them before they bought?
Most businesses can identify this in retrospect but have never written it down as an entry requirement.
Output for the user: A two-column table — “Customer will succeed if…” and “Customer will struggle if…”
This becomes the foundation for the exclusion policy. Every exclusion should be traceable to one of the “Customer will struggle if” rows.
Step 2: Audit Current Customers for the Pattern
Non-ideal customers tend to cluster around predictable traits. The goal is to find the pattern in the failures — not to blame individual customers, but to identify a screener.
Ask the user:
- Look at your last 10 refunds or churns. What did those customers have in common?
- Look at your last 10 support-intensive customers. What were they like at the point of purchase?
- Do you have customers you privately dreaded after they signed up?
Common patterns in failed-customer profiles:
- Financial stress — they needed the product to work to afford the product (Ramit’s credit card debt rule targets exactly this)
- Outcome mismatch — they wanted something different from what the product delivers
- Readiness gap — they needed to solve a prerequisite problem first
- Community mismatch — in a community product, they lower the value for everyone else
Ask the user: If you had to write a rule that would have screened out 80% of your problem customers, what would it be?
Step 3: Translate the Pattern into a Concrete Policy
The policy needs to be specific enough to actually apply at the point of sale. Vague policies don’t work — “we want motivated buyers” is not a policy.
Ramit’s policy is specific: no credit card debt for flagship programs. It is measurable, enforceable, and directly tied to outcome data. A person carrying credit card debt who buys a $2,000 personal finance course is unlikely to implement the strategies — the financial stress that drove them to buy is the same stress that will prevent them from doing the work.
Help the user write their policy in this format:
“We do not accept customers who [specific condition] because [outcome reason].”
Examples of real policies:
- “We do not accept clients who have not yet completed their first [prerequisite milestone].”
- “We do not admit members who are primarily looking for [outcome X] — this community is for people pursuing [outcome Y].”
- “We require a brief call before purchase to confirm fit — if the fit isn’t right, we refer them elsewhere.”
Ask the user: Would you be willing to put this on your sales page? If not, the policy isn’t firm enough yet.
Step 4: Design the Rejection Experience
Turning someone away is only as good as the alternative you provide. A bare “we don’t think you’re a fit” leaves the rejected customer worse off and the business looking arrogant.
Ramit’s version includes a graceful exit: “Enjoy my free material. Use it for as long as you want. When you are ready, I will be here.”
The exclusion policy and the Theory of Preeminence work together. You turn away the customer who isn’t ready — and simultaneously point them toward what they need to get ready.
Ask the user:
- What would the excluded customer need to do or achieve before they’d be a good fit?
- Can you point them to a resource, a prerequisite step, or a lower-commitment entry point?
- Can you tell them when to come back?
Output for the user: Draft language for the rejection — specific, warm, with a path forward.
Step 5: Understand the Long-Term Economics
The counterargument to exclusion is always: “We’re leaving money on the table.” Walk the user through the actual economics.
Every non-ideal customer costs money in ways that don’t show up in the revenue line:
- Support costs — non-ideal customers generate disproportionate support volume
- Refund costs — they are more likely to request refunds
- Community dilution — in community products, they reduce the value for everyone else
- Reputation costs — a customer who doesn’t get results and tells people is more damaging than a lost sale
- Operator energy — the psychological cost of dreading certain customers
Ramit’s framing: “even though it costs us in the short term, it benefits us tremendously in the long term.”
Ask the user: If you removed your bottom 20% of customers by outcome, what would happen to your refund rate, your support volume, and the testimonials you collect?
The answer usually reveals that the “lost revenue” is largely illusory — the non-ideal customer costs more to serve than they contribute.
Quick Reference
| Without Exclusion Policy | With Exclusion Policy |
|---|---|
| Any paying customer in | Only customers who can succeed |
| High refund and churn rates | Lower refunds, better retention |
| Community dilution | Tight, high-value community |
| Testimonials are mixed | Testimonials are consistent |
| Support volume high | Support volume manageable |
| Revenue looks higher, margins are not | Revenue may drop short-term, margins improve |
Search the Archive
grep -ri "ideal customer\|exclusion\|turn.*away\|who.*not.*for\|fire.*customer\|refund" transcripts/
grep -ri "credit card debt\|not ready\|qualify\|community.*quality" transcripts/
Output
After the session, deliver:
- Ideal customer profile — what success requires the customer to bring
- Failed customer pattern — what your refunds and churns have in common
- Exclusion policy statement — the specific, enforceable rule
- Rejection language — warm, specific, with a path forward for excluded customers
- Long-term economics brief — the real cost of non-ideal customers
Source
Why You Should Have a Diversified Investment Portfolio — Sam Parr and Shaan Puri interview Ramit Sethi on My First Million.