We all felt the same thing: there has to be a better way of doing this.
Those headaches guided the core decisions behind NestPoint. The goal is simple: keep the people, programs, payments, and daily work of your organization connected and easy to understand.
One member record, 15 connected modules
You decide what information belongs on a member record and who can access it. Organize members into membership tiers that match your organization.
Households stay together. A spouse, a grandchild, a caregiver are one household from the start, so family pricing applies at registration instead of getting fixed later.
That same record works across all 15 modules. Staff can check a member in, register them for a program, add them to a group, schedule a ride, record a meal, take a payment, and include the activity in reporting without creating another version of the person.
Everything else here follows from that.
The front desk
The front desk is where you serve members face to face. A new member signing up, a returning member with a badge to scan, or a caller who needs an answer. The goal is to keep the common tasks close together so staff can stay focused on the person in front of them.
Check members in by scanning a badge or searching a name, and log what they're here for as you go. Check in a whole household or a group of regulars together. Turn on check-outs if you need time in the building. Or offer a member kiosk for people who prefer to check themselves in.
More than one building
Plenty of organizations run more than one site. Set up multiple centers, each with its own schedule and activities, over one roster of members. Decide which centers each staff account can work in, and which each member belongs to. Someone who uses two of your sites is still one person with one history.
Email campaigns are included
The Communications module is part of NestPoint on every plan, so member records and audience selection stay connected to the messages your team sends.
Reach members who've stopped coming in. Members from a region, members of a group, participants in an activity. You build the audience by describing it instead of exporting a list and pasting it somewhere else. Start with a reusable template, then send now or schedule the message for later.
Reporting without the rebuild
Reporting is a headache by definition. We didn't remove it. We spent a lot of time making it a smaller one.
Start with saved report views for recurring questions from staff, boards, partners, and funders. Filter the people and dates, review the underlying records, and export the result in the format your team needs. Trends help you compare activity over time without rebuilding the same analysis from scratch.
This is quick because of the first section. The numbers are already there. A badge scan, a meal tally, and a shift check-out recorded them as they happened.
Why every plan includes everything
You shouldn't have to work out which version of the product you need before you've used any of it. So we didn't build versions.
The reason is that the modules are not really separate. A check-in is what makes the attendance report true. A rental payment and a class payment are both money your organization took in, and you cannot answer what you brought in this month if they sit in two different systems. Sell those pieces one at a time and you have sold somebody half a record, which is the problem they came to you with.
So Starter, Growth, and Scale are the same product. All 15 modules and product support, on every one of them. What changes is how many active members you have, and the pricing page shows exactly how that is counted. Nothing to assemble, and nothing that appears two plans up.
Most of the teams we build for are nonprofits and community organizations counting the money carefully. If NestPoint is going to be a line on that budget every month, you are owed a plain answer about what it buys.
The answer is all of it. Pick the member capacity that fits and use the parts you need. If you never turn on rides, you are not paying extra for the people who did.