Can we track the things that are specific to our organization?

Yes. Alongside the details every organization keeps, you add your own — chapters, credentials and their expiry, class year, a boat name. Describe what you keep track of and Sprout proposes the fields, which you approve before anything is saved.

Who can see a member's contact details?

Your organization decides what the directory may show, and each member can hold any field back further than that. Staff with the right permission see the full record. Contact details are held back from Sprout by a rule enforced in code.

Can members pay dues by card and renew automatically?

Yes. Dues renew on their own each year, with a reminder in advance and follow-up when a card is declined. Dues land in your organization's own Stripe account — you pay your processor and nothing extra to us.

Members & dues

Your roster, and the questions you ask it.

One record per person, dues that renew themselves, and a way to ask your own data a question without building a report.

A question typed in plain English — which members have lapsed, and the plan they were on — with the answer already on the page beside it: Sprout's review card naming the report and its 48 rows, and the live table beneath it with a name, a plan and an email address on every row. — Real screenshot. Example organization, sample data.

Ask your data

Ask a question in plain words. Get the report.

Type "who hasn't renewed since March, by chapter" and Sprout builds the report — over your own custom fields as readily as the standard ones. No query builder, no export to a spreadsheet.

Sprout writes the pattern; SorrelSites runs it against your data.
No member's contact details are ever sent to the model.

Your fields

The fields your bylaws call for.

Chapters, committees, class year, a boat name, the certification that expires in March. Tell Sprout what your organization keeps track of and it proposes the fields for you to approve.

An organization's SorrelSites dashboard: total membership, dues collected so far this year, and the next few events, all on one screen. — Real screenshot. Example organization, sample data.

One record

One record per person, start to finish.

The person who joined, the person who bought a gala ticket and the person on your mailing list are one record — no second contacts database to reconcile, and no import between the two halves of your own roster.

The member import's mapping review, step 4 of 6: each column of the uploaded export beside what Sprout proposed for it — built-in fields matched, a membership-level column set to enrol on a plan, an Organization column mapped to a custom field — with the real first row as a sample and what Sprout found in the column (its type, how many values, how full it is). — Every column of the old export, read and matched — the membership level enrolled on a plan, the unknown columns proposed as new fields for you to accept. Real screenshot. Example organization, sample data.

Moving in

Your list comes across with its renewal dates intact.

Upload the export from your current system and Sprout reads it column by column, lining your levels up against your plans and carrying each member's anniversary across. You review the mapping before a record is written.

And all the things you'd expect.

Members join and pay on your website — day or night, no one at a desk.
Dues renew themselves, with reminders before and follow-up when a card fails.
Every member gets their own billing page and their own login.
A member directory your organization controls, field by field.
Lapsed members stay in your records and stop counting toward your plan.
Sign in with a password, Google, a face or fingerprint, or a one-tap email link.
Dues land in your organization's own Stripe account.
Contact details are held back from Sprout by a rule enforced in code.

It's one record per person that stays whole and stays with the organization, not a volunteer — see how that holds up when the board changes over. The longer answers live in the guides.

Members & dues — common questions

Can we track the things that are specific to our organization?: Yes. Alongside the details every organization keeps, you add your own — chapters, credentials and their expiry, class year, a boat name. Describe what you keep track of and Sprout proposes the fields, which you approve before anything is saved.
Can we bring our member list across from another system?: Yes. Upload the export as a spreadsheet and Sprout reads it column by column, matching the standard details, lining your levels up against your plans, and carrying each member's renewal anniversary across so nobody's year restarts. You review the whole mapping first.
Who can see a member's contact details?: Your organization decides what the directory may show, and each member can hold any field back further than that. Staff with the right permission see the full record. Contact details are held back from Sprout by a rule enforced in code.
Can members pay dues by card and renew automatically?: Yes. Dues renew on their own each year, with a reminder in advance and follow-up when a card is declined. Dues land in your organization's own Stripe account — you pay your processor and nothing extra to us.

Bring your roster across this week.

Half an hour with the person who builds SorrelSites — your list, your dues year, and whatever is making it hard today.

Start your evaluation Or start free in two minutes