One app, two quite different jobs.
A membership network and a company want almost nothing in common from the same product. So there are two, at the same price, and each starts with the half that is yours switched on.
MyPeople Community
Networks, associations, alumni and member communities
A directory worth opening, events worth coming to, and enough in the membership that the fee makes sense.
A directory of people, not follower counts
Who is actually in your community, searchable, with the fields you decide are worth showing.
Events, including the ones you charge for
Dates, venues, RSVPs and a waitlist. Sell tickets with payments built in, and let somebody who is not a member yet register from your public page.
Perks and tiers
Partner offers, a ladder members can climb, and an offer that unlocks when somebody earns it rather than because they asked.
Sub-groups that run themselves
Chapters, committees, year groups and special interest groups, each with its own roster and its own organiser who does not need to be an admin of everything.
A page people can find, and email that sounds like you
Your own public page, and email from your own name with saved audiences, templates and a confirm step that states the exact number of people.
Billing you can see
What you pay for the platform, in the same place you run everything else.
Live the same day. There is no app to build and no store review to wait for: the app already exists, and your community goes into it under your own name and colours.
Talk to us about your communityMyPeople Workplace
Companies, and the people who work there
Your company already has an HR system and a payroll. This is the part they do not do: the place your people actually look.
Policies people have genuinely read
Publish a policy at a version and see who has not confirmed it. When you change it, you decide whether that means everybody reads it again. The outstanding list comes out as a spreadsheet.
Courses you write yourself
Modules in order, a question at the end of each, a written reflection, and points when somebody finishes. A follow-up question arrives a few days later, when what they learned has either stuck or it has not.
A read-only line into the HR system you already run
We connect to BambooHR, you agree the field mapping, and you see a dry run before anything is written. There is a list of fields we will never fetch at all. We never write back.
Leave balances without a second system
Each person sees their own annual balance, read live from your HR system. Managers see who is away. The leave type is never shown, because on sick leave next to a colleague's name is health information about that colleague.
A reporting line, and one place to tell everyone something
The org chart, and a notification that tells you exactly how many phones it will reach before you confirm it.
Perks and rewards worth having
Partner offers, points for the things you want more of, and a reward somebody approves before it goes out.
The HR connection is read-only by design. It never writes back to your HR system, and there is a list of fields it will never fetch at all, which is code with a test behind it rather than a line in a contract.
Talk to us about your workplaceNot sure which one you are?
Some organisations are genuinely both, and nothing stops you switching on a feature from the other side. Read the full list and pick, or tell us what you are trying to run and we will tell you which part of it you need.