Build, sell and run
Create your offer, connect infrastructure, take payment and care for members.
- 1Brand
- 2Packages
- 3Payments
- 4Servers
- 5Launch
- 6Optimise
The friendly, practical map of the whole platform: what everything is for, how the pieces work together, and the shortest path through the jobs you do most.
Pick your path
Start with the journey closest to your role, then dip into the chapters when you need detail.
Create your offer, connect infrastructure, take payment and care for members.
Work from shared customer, ticket, request and operational views.
Choose a plan, receive access, manage billing and get help from one branded portal.
The chapters
Search by feature, task or outcome. Each chapter explains the area and gives you practical routes through it.
A live view of revenue, customers, renewals, incidents and the work that needs attention.
Search, understand and manage every customer from first checkout to renewal and retention.
Design packages, accept supported payments, manage renewals and understand revenue movement.
Connect Plex, Jellyfin and Emby capacity, monitor service health and coordinate member access.
Connect events to repeatable actions across billing, access, communications and external tools.
Shape the public buying journey and the private member experience without disconnecting them from operations.
Combine self-service guidance with a shared support workspace when a person needs help.
Extend the core subscription experience with add-ons, referrals and optional digital commerce.
Configure the operator workspace, preferences, roles and platform-facing requests.
A live view of revenue, customers, renewals, incidents and the work that needs attention.
A fast business pulse with KPIs, activity and useful next actions.
Health, queues and exceptions brought into one operational view.
Trends, cohorts and signals that turn activity into decisions.
A clear, branded service-health view for your members.
Outcome: Know whether the business and service need attention.
Search, understand and manage every customer from first checkout to renewal and retention.
Identity, subscription, payments, access, activity and notes in one record.
A readable history of meaningful customer events and team actions.
Health, engagement and retention signals for better prioritisation.
Capture reasons, offer suitable alternatives and learn why members leave.
Outcome: Create a complete member record without checkout.
Outcome: Move access and billing together.
Design packages, accept supported payments, manage renewals and understand revenue movement.
Pricing, billing periods, limits, benefits, availability and server routing.
Customer checkout through connected payment providers and supported manual flows.
Upcoming charges, failures, retries and recovered revenue.
Credits, offers and rewards that support flexible growth.
Operator connections, balances and partner earnings.
Outcome: Put a coherent offer on the storefront.
Outcome: Help a member recover without losing context.
Connect Plex, Jellyfin and Emby capacity, monitor service health and coordinate member access.
Server inventory, health, capacity, agents and service controls.
Create, update, suspend and restore member access as lifecycle state changes.
Live sessions, history, usage patterns and operator-defined signals.
A member request flow connected to supported media-management tools.
Optional package routing and lifecycle management for connected reseller panels.
Outcome: Make a server available for health and lifecycle operations.
Outcome: Separate a transient warning from member impact.
Connect events to repeatable actions across billing, access, communications and external tools.
Trigger-and-action workflows for onboarding, recovery and lifecycle moments.
Account linking, role synchronisation, community commands and optional moderation tools.
Send selected Memberra events to compatible external systems.
Route approved content requests into supported downstream services.
Outcome: Give every new customer a consistent start.
Shape the public buying journey and the private member experience without disconnecting them from operations.
Logo, colour, imagery and tone shared across customer touchpoints.
Composable pages for campaigns, storefront content and helpful information.
Memberra subdomains and eligible custom domains for branded access.
Consistent transactional email identity and presentation.
Self-service subscription, billing, access, requests, downloads and support.
Outcome: Use a branded HTTPS address for the customer portal.
Outcome: Deliver one coherent journey from landing page to first login.
Combine self-service guidance with a shared support workspace when a person needs help.
Branded, searchable articles organised into practical categories.
Threaded customer conversations with status, priority, ownership and context.
Route conversations to the right team or area.
Keep the team aware of work that deserves attention.
Outcome: Help the member and preserve useful context.
Outcome: Prevent repeat questions without sounding robotic.
Extend the core subscription experience with add-ons, referrals and optional digital commerce.
Optional recurring or one-off extras attached to a customer relationship.
Deliver eligible files, keys or links after purchase.
Reward customers for introducing new members.
Track attributed growth and configurable partner earnings.
Outcome: Offer an extra without confusing the core package.
Configure the operator workspace, preferences, roles and platform-facing requests.
Business identity, defaults and shared operator configuration.
Invite colleagues and give them an appropriate working role.
Personal identity, preferences and connected account choices.
A separate platform-owner workspace for Memberra-wide operations.
Outcome: Give a colleague the access they need to work.
Outcome: Return to normal operator work without signing out.
The Memberra way
Useful defaults for making decisions across the platform.
Billing, access and communication should tell the same story.
Healthy routine work stays quiet; meaningful problems become visible.
Every message should explain what happened and what comes next.
Use the customer record and timeline before taking action.
Show timing, amount and consequence before confirming a change.
Workflows should be understandable, observable and reversible through normal product controls.
Storefront, portal, status and email should feel like one service.
Guidance should help a person complete a task, not merely describe a screen.
Price, access and benefits must remain coherent from checkout through renewal.
Useful language
Shared words make shared work much easier.
Now explore the representative workspace, or start building your own. The Bible will still be here when you need a map.