How to Automate WordPress Membership Sites with Claude Code

I've built three membership sites in the last year, and every time a client asks if we should use MemberPress or Restrict Content Pro, I give the same answer: let's build it with Claude Code instead. Not because membership plugins are bad — they're fine for most people — but because custom-built membership logic gives you control that no plugin can match, and it costs less over time.

Here's how I automate WordPress membership sites with Claude Code, what you can realistically expect to build, and when a plugin still makes more sense.

What a Custom Membership System Actually Does

A membership site is just a WordPress installation with three additional layers: payment processing, content restriction, and user lifecycle automation. Most people reach for a plugin because the idea of building those layers from scratch sounds overwhelming. It's not — at least not with Claude Code.

The core components I build for every membership project:

• Payment integration — usually Stripe, sometimes PayPal, handling checkout sessions and subscription webhooks
• Role-based content gating — WordPress already has roles; we just extend them with custom capabilities and restrict access accordingly
• Member dashboard — a custom page template where users see their subscription status, download history, and account settings
• Automated emails — welcome sequences, payment reminders, content drip notifications

Each of these has been a recurring pattern across multiple builds, which means I have working templates. A new membership site doesn't start from zero — it starts from a proven foundation that gets customized to the client's logic.

How Claude Code Handles Stripe Webhooks

The most critical piece of any membership system is payment sync. When someone subscribes on Stripe, WordPress needs to know immediately so it can grant access. When a payment fails, access gets revoked. This all happens through webhooks.

I use Claude Code to build a custom WordPress REST endpoint that listens for Stripe events. The main ones I care about:

• checkout.session.completed — a new subscriber just paid
• customer.subscription.updated — plan changed or renewal succeeded
• invoice.payment_failed — subscription lapsed
• customer.subscription.deleted — user canceled

When the webhook fires, Claude Code reads the event data, finds the corresponding WordPress user (matched by email or Stripe customer ID stored in user meta), updates their role, and optionally triggers an email. The entire flow is server-side. No front-end JavaScript, no third-party sync plugin.

The advantage of building this yourself: you decide what happens when a payment fails. Do they lose access immediately, or do they get a 7-day grace period? Does the site send one reminder email or three? A plugin forces you into its logic. Claude Code lets you define your own.

Content Restriction Logic

WordPress has built-in user roles and capabilities. Most membership plugins ignore this and build their own parallel system. I don't. I extend the existing roles with custom capabilities, then gate content using those capabilities.

For example, a coaching site I built has three membership tiers: Foundation, Growth, and Elite. Each tier is a custom role. Certain post types and pages are restricted to users with the access_growth_content or access_elite_content capability.

The restriction happens in two places:

1. At the template level — if the current user doesn't have the required capability, they see an upgrade prompt instead of the content
2. At the query level — restricted posts don't appear in archives or search results for users without access

This approach integrates cleanly with WordPress's existing permissions system, which means it plays nicely with other plugins and doesn't break when WordPress updates.

Drip Content and Release Scheduling

A common membership site pattern: you want to release content over time so users don't consume everything on day one. This is called drip scheduling.

I handle this with a custom post meta field that stores a "days after signup" value. When a post is created, you specify: "This unlocks 14 days after the user subscribes." Claude Code checks the user's signup date (stored in user meta when they first subscribe) and compares it to the current date. If enough days have passed, the post becomes visible.

This logic runs as a filter on the main WordPress query, so it applies everywhere: single post views, category archives, search results. No separate drip plugin needed.

Member Dashboard and Account Management

Every membership site needs a place where users can see their subscription status, update payment info, and download invoices. Most plugins give you a generic dashboard with limited customization options. I build custom page templates instead.

The dashboard pulls data directly from Stripe's API and WordPress user meta. It shows:

• Current plan and renewal date
• Payment method on file
• Invoice history with download links
• Content unlock schedule (if drip logic is active)
• Account settings (email, password, notification preferences)

Because it's a custom template, you have full design control. You're not stuck with the plugin's CSS or layout constraints. If the client wants the dashboard to match their brand perfectly, you can do that.

Automated Email Sequences

When someone subscribes, they should get a welcome email. When their payment fails, they should get a reminder. When new content unlocks, they should get a notification. All of this is just WordPress transactional email triggered by specific events.

I use Claude Code to set up email templates as custom post types, then trigger them based on webhook events or scheduled checks. For example:

• When checkout.session.completed fires, send the welcome email
• When invoice.payment_failed fires, send the payment failed email
• Run a daily cron job that checks for newly unlocked drip content and sends unlock notifications

The emails are plain text by default (higher deliverability), but you can template them with HTML if needed. All copy is stored in WordPress, so the client can edit it without touching code.

When You Should Still Use a Plugin

I'm not anti-plugin. There are scenarios where building custom membership logic doesn't make sense:

• You need affiliate tracking and commission splits — this is complex logic that plugins like Paid Memberships Pro handle well
• You're managing a large team with non-technical admins who need a GUI for everything
• The site requires complex dunning management (multiple retry schedules, conditional grace periods based on user history)
• You need the site live in under a week and don't have time for custom development

In those cases, I'll recommend a plugin. But for most coaching businesses, course creators, and niche communities, a custom-built membership system is faster to maintain and cheaper in the long run.

Real Example: Vancouver Fitness Coaching Site

A Vancouver-based fitness coach came to me with a membership site that was already live on MemberPress. The plugin worked, but it was slow, the dashboard looked generic, and they were paying $400/year for a Pro license plus another $200/year for the drip content add-on.

We rebuilt the entire membership layer with Claude Code over six days. The new system:

• Syncs with Stripe in real-time (no 5-minute polling delay)
• Has a fully branded member dashboard that matches their site design
• Uses custom drip logic that unlocks content based on workout completion, not just time
• Sends personalized progress emails based on user activity

Total cost: about the same as two years of MemberPress licenses. After that, zero recurring fees. And when they wanted to add a referral bonus system three months later, we added it in an afternoon instead of waiting for the plugin developer to release a new feature.

Getting Started If You Want to Build This

If you're a developer or agency owner who wants to build custom membership sites with Claude Code, here's the path I'd recommend:

1. Start with a simple paid content gate — one post type, one membership tier, Stripe checkout only
2. Add webhook handling for subscription lifecycle events
3. Build a basic member dashboard that pulls data from Stripe
4. Layer in drip scheduling if the project needs it
5. Add email automation last — it's easy once the other pieces are stable

The entire stack uses WordPress core functions, Stripe's PHP SDK, and Claude Code to wire it together. No exotic dependencies. No fragile plugin chains.

For more on how this fits into broader WordPress automation workflows, I've written about that separately. And if you're curious about payment automation beyond memberships, this post on Stripe subscription automation covers the underlying patterns.

If you want to talk through a specific membership site build, book a call and I'll walk you through exactly how I'd approach it. And if you're still deciding between custom and plugin, the FAQ has a breakdown of when each makes sense.