Membership site specsScope of Work Outline

Specification for a membership or community website

Usually ready in 15 minutesRevisions includedQuality check
Packages
Payment protectionDetails
  • Revisions within the package are free.
  • If you do not respond within 3 days of delivery, the work is accepted automatically.

The money is reserved when you pay and released only once you accept the work.

Specification for a membership or community website

Example result

Example for the Standard package

Specification: a paid community for home bakers

Goal

A paid community where bakers watch lessons, ask questions and share photos of their bread; 500 members in the first year.

Tiers

TierPriceAccess
Free$03 sample lessons, newsletter
Member$12 a month or $120 a yearAll lessons, forum, a monthly live Q&A
Pro$39 a monthEverything above + one video review of your bread each month

Must-have features

  1. Sign-up and login with email or Google, password reset
  2. Card payments through Stripe, upgrade and downgrade, cancel in 2 clicks
  3. Lesson library: video (Vimeo), PDF recipes, progress tracking
  4. Forum with categories, photo uploads up to 10 MB, email notifications
  5. Admin area: member list, CSV export, discount coupons

Not in version 1

Mobile app, single lessons for sale, a points system.

Acceptance criteria (examples)

  • A member who cancels keeps access until the end of the paid period
  • A free user who opens a member lesson sees a 2-minute preview and a "Join" button

Delivered

An 11-page specification, user flows for sign-up and cancellation, and a list of questions to ask the agencies.

Client: The Sourdough Circle, a baking teacher with 9,000 Instagram followers launching a paid community Task: a specification for developers to get quotes from 3 agencies: membership tiers, access rules, features and payments

The client and all details are made up.

About this service

Membership and community sites live on rules: which tier sees which content, what happens when a payment fails, when access ends after cancellation, who can post, moderate or invite. We write a specification that sets these rules out together with the pages, member profiles, community features, content drip, payments and emails, whether you build on WordPress, a platform like Circle or a custom stack. Developers and you agree on the logic before anything is built.

What is included

  • What you getA specification with goals, membership tiers and access rules, payment and renewal scenarios, community and moderation features, pages, emails and open questions, as formatted text; any time or cost figures are rough guidance, not a quote.
  • Tiers and accessWhat each level can see and do
  • Payment scenariosTrials, renewals, failed cards, cancellations
  • Community featuresProfiles, posts, comments, events, moderation
  • Content dripWhat opens when, by date or by tier
  • Member emailsWelcome, renewal reminder, payment problem

How it works

  1. 1
    BriefYou describe the club and its tiers
  2. 2
    RulesWe set out access, payments and community
  3. 3
    SpecYou get a specification for developers

What we need from you

What the club or community offers, the membership tiers and prices you plan, what members can do on the site, how content is released, the platform you lean toward and examples you like.

We will ask you:

  • What do members get?
  • Which tiers and prices do you plan?
  • Which platform are you considering?
  • Who will moderate the community?

Compare packages

PackagesBasic$19Standard$39Premium$79
What is includedOne-page briefSpec up to 10 pagesFull spec up to 20 pages
Deadline1 day3 days5 days
Revisions123
Length1 pageup to 10 pagesup to 20 pages
Payment and renewal scenariosKey onesYesYes
User stories and acceptance criteriaNoNoYes
Order BasicOrder StandardOrder Premium

Payment protection

You pay when you order, but the money is released only for accepted work.

  • Fixed priceThe package price does not change after you pay.
  • The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
  • Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
  • Free revisionsAsk for changes within your brief as many times as the package allows.
  • Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
  • Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
How it works →

Questions and answers

Should I use a ready platform or build my own?

The spec helps decide: once rules are written down, you can check which platform supports them and what would need custom work.

Do you cover what happens after a member cancels?

Yes. Access end dates, grace periods for failed payments and what the member keeps are spelled out.

Can you write the community rules too?

The spec lists moderation roles and tools. The text of community guidelines can be ordered as a separate legal template service.

Did not find your answer?

Packages