Skip to main content

Pay What You Can Pricing Without the Spreadsheet Nightmare

Sliding scale pricing and scholarship seats can widen your community without wrecking your income, but only if you build the structure first. Here is how to set the tiers, what to say, what never to ask for, and how to keep it from becoming a second job.

In this post 9 sections
  1. Decide what problem you are solving
  2. Never build an open ended slider
  3. Cap it, and say the cap out loud
  4. Do not make people prove they are poor
  5. The words matter enormously
  6. What to do about the person who emails you anyway
  7. Watch two numbers, not five
  8. When to stop
  9. Do this this week

Someone is going to email you and say they love what you are building and cannot afford it. It will be a good email. It will be from exactly the kind of person you started this for. And you will sit there with your cursor blinking, trying to decide between two answers you do not like: a full price you know they cannot pay, or a quiet freebie you will feel weird about in four months.

There is a third answer, and it is older than the creator economy. Sliding scale. Pay what you can. Scholarship seats. Different names, same idea: the price is not one number, it is a range with a shape.

Done carelessly, this turns into an administrative swamp and a slow revenue leak. Done deliberately, it widens who gets to be in the room without costing you the business. The difference is entirely in the structure you build before you say yes to anybody.

Decide what problem you are solving

Before you touch a price, get honest about the motive, because there are three different ones and they need three different designs.

The first is access. You genuinely want people in the room who cannot pay your standard rate, because their presence makes the community better and because you believe in the work. That is a good reason and it deserves real structure.

The second is conversion. You think a lower option will capture people who are hesitating. That is not a sliding scale, that is a cheaper tier, and you should design it as one and name it honestly.

The third is discomfort. You feel bad charging money and a flexible price makes the guilt quieter. I say this with love: fix that separately. Pay what you can built on founder guilt collapses within a year, because the guilt does not go away, it just moves. It becomes guilt about the people paying full price, or guilt about needing the money, and the whole structure warps around it.

Only the first reason justifies the work. If it is the first reason, keep reading.

Never build an open ended slider

The instinct is to write "pay whatever feels right" and let people choose. Resist it, for a reason that has nothing to do with trust.

An unbounded choice is a burden. Most people, given no anchor, will either pick something at the bottom because they cannot tell what is normal, or they will avoid the decision altogether and not join. You have not been generous, you have handed a stranger a maths problem about your finances and asked them to solve it while feeling judged.

Give three anchors instead, and label them by circumstance rather than by amount.

Something like: the standard rate, which is the real price of the work. A supported rate, roughly sixty to seventy percent of standard, for people whose situation is tight right now. And a supporting rate, above standard, for people whose situation is comfortable and who want to hold a seat open for someone else. Three lines of plain text explaining who each one is for, and you have replaced an awkward negotiation with a self service decision.

The upper tier matters more than people expect. Without it, a sliding scale is a discount program. With it, it is a mutual arrangement, and members who choose the higher rate get something real in exchange: the knowledge that they are the reason a specific seat exists. Say that plainly. Do not dress it up.

Cap it, and say the cap out loud

The number one way this goes wrong is unlimited supply. If the supported rate is always available to everyone forever, over time a large share of your community drifts into it, and your average revenue per member quietly falls while your workload does not.

So cap it. A percentage of your membership, or a fixed number of seats, refreshed on a schedule you choose. "Ten supported seats, reviewed each quarter" is a complete policy. When they are full, they are full, and you say so: "all supported seats are currently taken, the next ones open in January, join the notify list and I will tell you first."

A cap does three useful things. It protects your income. It makes the supported rate feel like a real thing rather than a coupon, which counterintuitively makes people more comfortable asking for it. And it gives you a clean, non personal way to say no, which is the sentence you will be most grateful for.

Do not make people prove they are poor

This is the ethical heart of the whole thing, so let me be direct. Do not ask for income figures. Do not ask for tax documents, bank details, benefit letters, or medical explanations. Do not ask people to describe their hardship in a text box for you to evaluate.

You are not a granting body. You do not have the training, the legal footing, or the emotional bandwidth to sit in judgment on people's circumstances, and requesting that information means you are now storing sensitive financial data about your members, which is a responsibility you do not want and did not sign up for.

Self selection is the answer. Write the descriptions of each tier clearly enough that people can place themselves, then trust them. Yes, some people will choose the supported rate who could have paid more. That is the cost of the system, it is smaller than you fear, and it is far cheaper than the alternative, which is building a means testing bureaucracy inside a creative business.

If you want a light friction point, ask for one sentence, optional, about what they are hoping to get out of the community. That is a useful question you would ask anyone. It is not a financial audit.

The words matter enormously

The language you use around a supported rate determines whether people use it with dignity or with shame, and shame produces quiet members who cancel in month three.

Write it as a normal option, not a charity. Compare these two.

"If you are struggling and cannot afford the full price, email me and I will see what I can do."

"There are ten supported seats at a lower rate. They exist because good people have tight years, and I would rather have you in the room. Pick that option at checkout, no explanation needed."

The first makes someone beg. The second makes it a choice, on the same page, in the same font. Same money, completely different experience, and the second version costs you nothing extra.

Also, never label anyone publicly. No badge, no different colored name, no separate channel. Inside the community, everyone is a member, full stop. Which tier someone pays is between you, them, and your payment processor, and it should never be visible to anyone else. Treat it with the same care you would treat any other private financial detail.

What to do about the person who emails you anyway

Some people will still write the email. Answer it in three lines and point at the structure.

"Really glad you want to be here. There are supported seats at a lower rate, and you can just pick that at signup, no need to explain anything to me. If those are full, tell me and I will put you first in line when they open."

You have been kind, you have not negotiated, and you have not created a bespoke arrangement you will have to remember forever. Bespoke arrangements are the actual spreadsheet nightmare. Every one off deal is a permanent exception that has to be tracked, honored through price changes, and explained to a future you who has forgotten why it exists. Keep everything inside the published structure and your admin stays boring, which is the goal.

Watch two numbers, not five

Track the share of your members on each rate, and check it once a quarter. If the supported share climbs past the cap you set, the cap is not being enforced, usually by you, informally, over email.

Then track what a mixed community actually earns compared with a single price. Multiply out your tiers and look at the real total. Sometimes the honest answer is that the upper tier is being chosen by enough people to fully fund the lower one, which is a lovely thing to discover. Sometimes the honest answer is that it is not, and the program is costing you a real amount of money. That is allowed, as long as you know the number and have decided it is worth it. What is not allowed is not knowing.

When to stop

A sliding scale is a choice, not a moral obligation, and you are permitted to end it. If your own year gets hard, if the program is unbalancing the business, if you simply cannot carry it right now, close new supported seats, honor the ones you have promised for their current term, and say plainly that the program is paused. Nobody who has been treated well will begrudge you that. The founders who get into trouble are the ones who keep an unsustainable promise silently until they resent everyone in the building.

Do this this week

Write your three rates on one page: standard, supported, supporting. Put a number of seats on the supported one and a date when it gets reviewed.

Then write the fifty word explanation in the tone of a normal option rather than an act of charity, and read it aloud. If it sounds like it would make you feel small to click it, rewrite it.

And go find that email you have been avoiding, the good one from the person who cannot afford it. You now have a three line answer that is generous, structured, and does not commit you to anything you will resent. Send it today.

Put it into practice.

Start a community on MemberPad. Free to create, and we only earn when you do.