What we've shipped
What SorrelSites can do that it couldn't a month ago
SorrelSites is built by a small engineering team that takes its direction from the organizations it serves. This is the record: the capabilities shipped most recently, each with the reason an organization would care. Judge the pace from the dates.
— self-serve signup is open, and every capability below is running for real organizations, not a demo.
Will you build what my organization needs?
If it fits what SorrelSites is for, yes — and you scope it with the person who would build it, not a ticket queue.
Most of what an organization asks for — a volunteer scheduling tool, a field on the join form, a way to stop one person buying two tickets — is something every organization would use, and those we build for you and for everyone. What we won't do is build a one-off that works for one organization and breaks for the rest, or reach outside what SorrelSites is for: deep double-entry accounting, a learning-management system and a branded native app are deliberate non-goals. If your need is one of those, you'll hear it on the call rather than after you've moved.
The way in is the same as everything else here: half an hour with Jeff. Bring the thing that is in your way.
Recently shipped
Reply to any email your organization sends, and something happens
- What it does
- Every message goes out from Sprout, your organization's assistant — receipts, renewal notices, agendas, announcements — and a member can simply reply. “Did you get my payment?” is answered from the ledger. “Stop emailing me” is honored. Anything Sprout can't answer itself reaches whoever currently holds the position responsible for it, with the original message attached.
- Why it matters
- Organization email normally arrives from no-reply@, so a member who answers it is talking to a wall — and the answer becomes a phone call to the treasurer on a Sunday. Here the reply itself does the job, and the treasurer is found by what their position covers, not by someone remembering their name.
The agenda goes out to the right people, with no mailing list to keep
- What it does
- Approve a meeting's agenda and SorrelSites works out who it is for — the committee holding the meeting, plus the people behind whatever it is about — shows you each group by name and size, and sends the agenda itself with a calendar file attached.
- Why it matters
- A distribution list for a board that rotates every year is somebody's unpaid job, and it goes stale the week it is made. This one is derived from what the meeting is for, so it is right the day the board changes — and the agenda arrives as text in the email, not as a link to a login screen.
The fields your organization tracks, filled in by the people they describe
- What it does
- Define what you need to know — T-shirt size, emergency contact, chapter, dietary needs — and it is asked on the join form, editable by members in their own profile, and each member is told what of theirs is still missing.
- Why it matters
- Custom fields elsewhere are an admin's data-entry job: the field exists, and someone has to chase three hundred people and type in the answers. Asked at the moment someone joins, the record is complete before anyone has to chase anything.
Tickets that say “pick one of these, not both”
- What it does
- Group your tickets and tell the group how it behaves — “choose just one,” or “exactly one.” Someone adding both the Racer ticket and the Non-Racer ticket is told while they are still choosing, not after they have paid.
- Why it matters
- Every event has combinations that make no sense together. The usual answer is a sentence in the description and a hope, and then the coordinator spends the week before the race issuing refunds.
Every field you define is an email variable
- What it does
- Anything you have defined — on members, events, registrations, sessions, locations — shows up as a variable you can drop into any email template.
- Why it matters
- The fields an organization invents are usually the ones worth mentioning in an email: the size you ordered, the chapter you belong to, the answer you gave at registration. Most systems let custom fields stop at the database, so the emails still only know a name and a renewal date.
Announce an event early, open registration later
- What it does
- Publication and registration are separate settings. Put the annual dinner on the calendar in March, open registration in May, and close it the Friday before.
- Why it matters
- An event is normally either published — and therefore buyable — or invisible. That forces a choice no organization wants to make between filling the calendar early and taking money before the price, the menu or the venue is settled.
The “Board of Directors” page that updates itself
- What it does
- Publish a committee to your website as a grid, carousel or spotlight of its people — photo, position, a short biography — drawn from the roster itself. Elect a new secretary and the page re-renders.
- Why it matters
- Every membership website has this page and most of them are out of date, because the website editor knows nothing about who holds which position and someone has to retype the names each time the board rotates.
Last year's budget spreadsheet becomes this year's budget
- What it does
- Attach the spreadsheet to the event's Budget and Sprout reads it into line items for you to review. Upload a corrected version later and it updates what is there instead of duplicating it.
- Why it matters
- Every treasurer already has the working budget in a spreadsheet, and every system asks them to retype it — which is why the budget usually stays in the spreadsheet and the software never learns what the event was supposed to cost.
Sign-ups at the door
- What it does
- Add a walk-in on the spot, record the cash or check they handed you, and their registration is confirmed exactly like someone who paid online — same roster, same check-in, same ledger.
- Why it matters
- Money taken at the door is the money most systems never see. It lands on a clipboard next to a laptop and gets reconciled from memory, or not at all.
Your organization's own Sprout address
- What it does
- Every organization gets sprout@yourname.sorrelsites.com. Forward it the meeting recap and it drafts the minutes; ask for something in plain words and it writes back with what it proposes to do — you approve by replying.
- Why it matters
- The volunteers who do the work are not sitting in an admin console; they are in their inbox on a Tuesday night. Anything that requires signing in first is work that quietly does not get done.
This list is kept by hand and shows capabilities an organization would notice — not fixes, and not everything that goes into the product. Every entry is live today.
Not ready to start a trial?
Get what we're building for clubs and associations, who asked for it, and what we decided not to build.
Want a look at your own setup? Half an hour with the founder, and your first two months are free if you join. Book half an hour →
Something in your way?
Tell us on the call. If it fits what SorrelSites is for, we build it — and you'll be able to point at it on this page.