SHEET 02 · WHAT IT SOLVES
What do you need to sort out?
People do not go looking for “an operations platform”. They go looking for a way to stop chasing volunteers, or to find out who has paid. These are the ones we hear most — each answer says what actually happens, and links to the parts it is made of.
You can create an account and look around for free before talking to anybody.
01PROBLEMS PEOPLE ARRIVE WITH
Twelve things we get asked to fix.
“We spend more time chasing volunteers than running the event”
In EveryonePlans a volunteer sign-up is a real list of slots attached to the event, not a thread or a shared document. People claim a slot themselves, everyone can see what is still open, and reminders go out on their own before the day. Nobody has to reconcile a reply-all chain, and the person who ran it last year is not the only one who knows what was agreed.
Scheduling and availability · Tasks and projects · Messaging and notifications · Events and ticketing
“Nobody can tell me who has actually paid”
EveryonePlans records money against the person who paid and the thing they paid for, so "who still owes?" is a list you open rather than a spreadsheet you rebuild. Dues, subs, match fees, tickets, class passes and donations all sit on the same member record, and the treasurer can see the accounts without being given the keys to everything else.
Quotes, invoices and payments · Balances, passes and check-in · People, roles and permissions · Reporting
“Every year the committee changes and half of what we knew leaves with them”
In EveryonePlans the records belong to the organization, not to whoever set them up, and access is a role you reassign rather than a password you pass on. The outgoing treasurer’s role goes to the incoming one, the member list, the accounts, the files and the notes stay exactly where they are, and a handover takes a few minutes instead of a box of paperwork and a shared login.
People, roles and permissions · Files and documents · Discussion and questions · Everything you own, in one registry
“Everything important is in one person’s spreadsheet”
EveryonePlans replaces the spreadsheet with a shared member list where each person has a history — what they paid, what they signed up for, which family or team they belong to, when you last spoke to them. Several people can work in it at once with different levels of access, so there is one version of the truth instead of three, and it does not stop working when its author is on holiday.
Contacts and pipeline · People, roles and permissions · Files and documents · Reporting
“Decisions get made in the group chat and then nobody can find them”
EveryonePlans keeps a question and its answer on the record instead of in a stream that scrolls away: somebody asks how the hall gets booked, it is answered once, and the next person searches and finds it. You can also log a note against a person, a company, a job or a booking — what was agreed, who to call, the fact that the hall key sticks — so the next person to open it starts from what you knew.
Discussion and questions · Files and documents · Contacts and pipeline · Tasks and projects
“We never know how many people are actually coming”
EveryonePlans turns an invitation into a count: people reply against the event itself, tickets and free registrations are tracked the same way, and on the day there is a list to check arrivals against. Afterwards the event still holds its own record — who came, what it cost, what it raised — so next year starts from evidence rather than memory.
Events and ticketing · Balances, passes and check-in · Messaging and notifications · Reporting
“Building the rota takes all evening and someone always turns out to be unavailable”
EveryonePlans asks people for their availability and shows you the overlap, so a rota is built from what people have already said rather than from guesswork and a follow-up round of texts. Shifts and fixtures carry who is assigned and who is qualified for them, and the reminders go out without anybody remembering to send them.
Scheduling and availability · People, roles and permissions · Courses and training · Messaging and notifications
“We are paying for six tools and they do not talk to each other”
EveryonePlans puts contacts, scheduling, tasks, invoicing, forms, messaging and files on one system, so an enquiry becomes a job becomes an invoice without anybody typing it three times. Most of the admin in a small operation is not work — it is reconciling tools that were never introduced to each other, and that reconciliation is the thing that disappears.
Contacts and pipeline · Quotes, invoices and payments · Workflows and rules · Forms and intake
“Enquiries come in from everywhere and some of them just get lost”
A form on your own website posts straight into EveryonePlans as a real record with an owner and a next step, instead of an email somebody meant to answer. From there it can be quoted, scheduled, done and invoiced without leaving the system, and you can see at any point which enquiries are still waiting on you.
Forms and intake · Contacts and pipeline · Workflows and rules · Your public page and listings
“I need people to help without giving them access to everything”
Access in EveryonePlans is built from individual permissions, so the treasurer can see the money without seeing everything, a class rep can run a sign-up without touching the accounts, and a contractor can be handed one job without seeing your margins. It is the difference between sharing the work and sharing the password.
People, roles and permissions · Trust between parties · Tasks and projects · Files and documents
“Our household runs on sticky notes and everybody forgets something”
EveryonePlans works for a household as well as a business: one calendar everybody can actually see, recurring jobs that come back on their own instead of being remembered, and documents kept with the thing they belong to — the boiler service with the boiler, the policy with the car. It is the same system a club uses, with a menu that fits a home instead of an office.
Scheduling and availability · Tasks and projects · Files and documents · Everything you own, in one registry
“At the AGM somebody asks what we actually achieved and we scramble”
Because the work, the money and the people live in one system in EveryonePlans, the annual questions are answered from the records rather than reconstructed from four sources the week before: what came in, what is owed and how old it is, what is scheduled, who attended which event, and what has not moved in a fortnight. Being able to account for it is usually what the next grant depends on.
Reporting · Quotes, invoices and payments · Tasks and projects · Contacts and pipeline
Do not see yours? It is very likely still covered — the full list of everything the platform does is below, and the contact page reaches a person who will tell you straight if it is not.
02EVERYTHING IT DOES · TWENTY CAPABILITIES
Capability index
This is the detailed half, and it is here rather than at the top on purpose. Each capability has its own page explaining what it does, what breaks without it, how it works, a worked example and a screenshot. They share one database and one permission model — the part that matters, and the part a feature list cannot show you.
EveryonePlans capabilities
- Contacts and pipelineLeads, customers, organizations and the relationships between them — with the history kept against the record rather than in somebody’s inbox.
- People, roles and permissionsGranular roles rather than admin-or-nothing. A subcontractor sees the job, not the margin; a bookkeeper sees the ledger, not the pipeline.
- Scheduling and availabilityCalendars, bookable time, and group availability polling for the cases where a shared calendar is not enough. Public booking pages included.
- Tasks and projectsWork broken down, assigned, sequenced and tracked to done — including recurring work, which is where most task tools quietly give up.
- Quotes, invoices and paymentsPriced work turned into a document, sent, paid and reconciled, against a double-entry ledger.
- Messaging and notificationsEmail and SMS that come from your brand, are logged against the record, and can be reviewed before they go out.
- Forms and intakePublic forms that land as structured records, not as an email you have to read and re-key. Drop one into a site you already own.
- Workflows and rulesWhen this happens, do that — enrolment, waiting, branching, human approval steps. Automation a person can read back a month later.
- Files and documentsAttachments that belong to the record they describe, with the same permissions as everything else attached to it.
- ReportingThe numbers that decide next week: what came in, what is scheduled, what is owed, what is stuck.
- Events and ticketingPublic event pages, registration, entry, and the attendee list as first-class records rather than a spreadsheet export.
- API and webhooksA versioned REST API over the whole system, with idempotency keys, cursor pagination, signed webhooks and a sandbox.
- Everything you own, in one registryPlaces, spaces and things in a single list — and whether each can be booked, rented or counted is a property of the item, not a separate system.
- Balances, passes and check-inIssue credits, punch cards, member balances or door codes, and check people in at the door — without cash boxes or a paper list.
- Needs and offersPost what you need and let people respond — requests for quotes, service requests, volunteer asks, wishlists, briefs.
- Discussion and questionsA place for the group to ask, answer and decide — with the answers kept, not scrolled past.
- Courses and trainingA course catalogue and enrolments — for onboarding crew, training volunteers, running a customer academy or issuing certifications.
- Referrals and rewardsTrack who introduced whom and grant a reward for it, with a review step before anything is paid out.
- Trust between partiesHold a payment until the work is done, verify who you are dealing with, record agreement to terms, handle disputes — and erase a person’s data when they ask.
- Your public page and listingsControl what the world can see — what is listed, bookable or for sale — from the same records you run on.
Not sure which parts you need?
Most people need about a third of this and are not sure which third — and nobody works that out from a list. Create a free account today and look around; it costs nothing and you do not have to talk to us first.
Building on top of it rather than using it as-is? The API guide is the contract, and bringthefront.com is a site built that way that you can open right now.