How much to charge for a membership website
How much to charge for a membership website comes down to one question: how much recurring revenue will this site collect and protect for the client? A coach putting a few videos behind a login and a business running paid tiers, drip content and a member directory are not the same job, even though both have a sign-in page. Price the build on a share of the value it creates, add lines for payments, access rules, content setup, migration and launch, and quote a monthly plan. Do not price on pages or hours.
Claude Code makes the build itself quick. The pages, the login and the member dashboard come together fast. That speed is exactly why the code is the wrong thing to charge for. The slow, risky parts are the money and the access: renewals that charge correctly, failed payments that are handled, cancellations that actually remove access, and members who can always reach what they paid for.
Who buys membership websites, and what they are really paying for
Membership sites are bought by people whose business runs on recurring payments. The site is not the product. Access is. Ask how they make money today before you talk about features.
Common membership site buyers and what the site is worth to them
| Buyer | What they need | What it is really worth |
|---|---|---|
| Coaches and course creators | Paid content behind a login, drip lessons, member accounts | Recurring income instead of one-off launches, and content they control |
| Associations and professional groups | Member tiers, renewals, a directory, member-only resources | Renewals that collect themselves instead of being chased by email |
| Gyms, studios and local clubs | Member accounts, class or resource access, billing | Fewer missed payments and less front-desk admin |
| Publishers and niche experts | Paywalled articles, newsletters, archives | Readers turned into paying subscribers |
The best client already has an audience and a reason people would pay every month. If they can tell you how many members they expect and what each pays, that is the start of your price. If they cannot, the first job is not a website. It is proving people will pay.
The CCC Membership Site Quote
Seven parts of a membership website quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Base build | The member site and the experience behind the login | How many members do you expect, and what will each pay? |
| Payments and billing | Plans, renewals, failed payments, cancellations, refunds, receipts | How do members pay today, and what happens when a card fails? |
| Access rules | Tiers, drip content, trials, what each plan unlocks | Should every member see everything, or does it depend on the plan? |
| Content setup | Loading lessons, videos, files and pages | Who is putting the content in, you or us? |
| Member migration | Moving existing members and their billing from another platform | Do you have paying members somewhere else right now? |
| Launch | Testing real sign-ups and payments, emails, a guide for the client | Who answers members when they cannot log in? |
| Keep plan | Monthly monitoring, fixes, updates and small changes | Who do members contact when something breaks? |
Base build. Start with the revenue. Ask how many members they expect and what each will pay. Price the build at a fraction of one year of that revenue so the client can see it pay for itself. A simple single-plan site with a few protected pages sits at the low end. Multiple tiers, drip schedules and community features sit much higher, because they carry more of the business.
Payments and billing. This is the line that matters most. Recurring billing has more moving parts than a checkout: upgrades, downgrades, failed renewals, cancellations, refunds and tax settings. Each one has to change the member's access correctly. Price it as its own line, and test every path with real test payments before launch. How to add Stripe payments with Claude Code covers the build side, and the payment account should always belong to the client.
Access rules. Who can see what is the product. A member on the basic plan seeing premium content is lost revenue. A paying member locked out is a refund request and an angry email. Decide the tiers, what unlocks when, and what happens to access when a payment fails. Adding authentication with Claude Code covers the login side.
Content setup and migration. Loading dozens of lessons and files is real work, so either price it or put it clearly on the client. Moving existing paying members from another platform is the riskiest part of the whole project, because their billing has to move without double charges or gaps. Price migration separately and plan it with the client before you quote.
Ask these before you quote
- Would an existing membership platform do the job? If a hosted platform covers what they need, a custom build may cost them more to own. Say so. That honesty is how you get the next, bigger project.
- Who owns the accounts? The domain, hosting, payment account and email service should all be in the client's name, with you given access. A membership business that lives in your accounts leaves with you.
- What is the content, and is it ready? Videos, downloads and lessons that do not exist yet will stall the launch. Agree who produces them and by when.
- Are there existing members? If yes, migration is a project of its own and the quote should say so.
- What do members need besides content? Forums, events, a directory or messaging each add real scope.
More questions that prevent a bad quote are in client discovery questions before you quote.
Always quote the Keep plan
A membership site takes money every month, so it cannot quietly break. Payment providers change, libraries need security updates, emails stop arriving, and the client wants a new tier or a new course section once members start paying. If nobody owns that, the first sign of trouble is a member who was charged and cannot log in.
Quote a monthly plan in the original proposal. Say what it covers: checking that sign-ups, renewals and access still work, updates and security fixes, hosting if you manage it, and a set amount of small changes. Say what it does not cover: new features and new integrations, which are quoted separately. How to price a maintenance retainer covers the structure.
How to present the membership website quote
- Lead with the outcome in their words. One line on the recurring revenue the site makes possible, then the price.
- Itemize it. Base build, payments and billing, access rules, content setup, migration, launch, then the Keep plan. Itemized quotes get trimmed, not rejected.
- Gate payments on proof. A deposit to start, a payment when a test member can sign up, pay and see the right content, and the final payment after launch. How to structure milestone payments for an AI project covers the schedule.
- Write the scope down. The plans, what each unlocks, who loads content and who owns which account. How to write a statement of work for an AI project has the template.
And skip hourly. Claude Code makes the build fast, so hourly pricing turns that speed into a pay cut. I covered why in why I stopped charging hourly for AI builds.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a membership website?
Price it on the recurring revenue it makes possible for the client. Charge a fraction of one year of that revenue for the build, add lines for payments, access rules, content setup, migration and launch, and quote a monthly plan.
What makes a membership website more expensive to build?
Multiple plans and tiers, drip content, trials, community features like forums or a directory, moving existing paying members from another platform, and a lot of content to load.
Should I charge a monthly fee for a membership website?
Yes. The site takes payments every month, so renewals, access and emails need to keep working. A monthly plan covers checks, updates, security fixes and small changes.
Should I build a custom membership site or use a platform?
Use whatever is cheapest for the client to own for what they actually need. If a hosted membership platform covers it, say so. Build custom when they need something platforms cannot do, and price that difference.
Should I charge hourly for a membership website?
No. Claude Code makes the build fast, so hourly pricing punishes you for that speed. Price on the value of the recurring revenue the site supports, with each part itemized.
Last reviewed by Duncan Rogoff on October 19, 2026
