Solo Community Enterprise Pricing About Request a Demo

Founded by a member , not a vendor.

Groupable wasn't born in a boardroom or a startup incubator. It started with a hand raised at a town hall — and 20 years of building software for organizations we actually belong to.

How It Started

"I didn't know it. I asked, I got on."

Mark was a young Freemason — a member of the Grand Lodge of the State of New York — when he attended a town hall meeting with the Grand Master. One of the officers was forming a technology committee. Mark volunteered to be on it and was appointed. This was, apparently, a shock to the members of his lodge. Generally speaking, you have to be a Past Master or a past Grand Lodge officer before you ever get on a Grand Lodge committee. Mark didn't know that. He raised his hand, and he got on.

The year 2000 was rolling around, and the Grand Lodge was having serious problems with a DOS FoxPro system that a consultant had been charging them for years to update. The web had arrived, and Mark proposed building a portal — a place where secretaries could submit initiation dates, degree dates, and basic financial records online. The Grand Secretary agreed.

Then the original developer couldn't deliver. The Grand Lodge came to Mark's team in a panic: could they take over the whole thing? They did. And that's how MORI — the original product — was born.

"The Grand Lodge was going to still maintain their Fox-based system, but after the developer couldn't deliver, they came to us in a panic saying, 'Well, could you take over the whole thing and do the whole thing?' Which we eventually did."

That was more than 20 years ago. Mark hasn't stopped building since.

How We Got Here

Screen by screen. Function by function. Zero downtime.

MORI was built in early Java web technologies — Struts, EJBs, an older application server. It worked, but the code was hard to extend. Every client ran a customized version with one-off business logic. Hundreds of thousands of lines of Java, with very little overlap between organizations.

About seven years ago, Mark started the project to replace MORI with a new platform — M2, and eventually Groupable. But there was never going to be a big-bang cutover. Not with thousands of lodges, chapters, and organizations depending on the system. Not with hundreds of thousands of members under management.

"There was no day when we turned off MORI and we turned on M2. We did it literally function by function, screen by screen."

The migration took seven years of continuous work — maintaining full operational stability for every client, every day. No organization lost access. No data was disrupted. The old system and the new one ran side by side until every function had been ported, tested, and adopted.

The result was a fundamental architectural shift. The old MORI system ran on customized code — one-off versions for every client. The new Groupable system was built from the ground up for configuration, not customization . A universal rules engine replaced the sprawl.

"Hundreds of thousands of lines of Java that we have reduced down to about three to four thousand lines of Ruby."

That rules engine — the one that handles member lifecycle events, multi-membership, interlocking statuses, billing eligibility, and organizational hierarchies — took 18 years and three rewrites to get right. It's why Groupable's data is accurate. And it's what finally made a single-group product possible.

Our Identity

Service, not just software.

This isn't a tagline. It's how we operate.

Groupable runs a help desk that supports every user of the platform — not just the staff at headquarters. From the member who joined last night and logged in for the first time, all the way up to the CEO or Grand Master. Everyone gets support.

"We support everyone from the brand-new member all the way up to the CEO."

We run roughly 100 training sessions a year — eight to ten events every month. We do in-person training at annual conferences. We sit down with executive leadership at retreats to talk about technology strategy that goes beyond our software. For Solo and Community groups, concierge onboarding is included. For enterprise clients, we offer professional onboarding services — because proper onboarding for a jurisdiction with hundreds of local groups takes real work, and we think that's worth doing right.

During COVID, when in-person meetings were illegal in some states, we helped organizations figure out Zoom, online voting, hybrid meetings, and vote-counting systems so they could still hold their annual sessions. That's not in any contract. That's just what we do.

The result: our recent enterprise clients are at 95-100% adoption across all of their local groups.

"Honestly, in our vertical, we're the only ones that get there."

Independence

Your data is yours. Your roadmap is yours.

Groupable is independently owned. No competing organizations sit on our board, govern our platform, or have access to your data.

This matters more than it might seem. When a software vendor is owned by organizations that compete with its own clients, questions arise: Who influences the product roadmap? Who can see the data? Whose interests come first?

With Groupable, the answer is simple. We serve our clients. That's it. Your member data belongs to you. Your feature requests compete on merit, not politics. And no competitor gets a seat at the table where decisions about your platform are made.

25+
Parent Organizations
2,800+
Local Groups
300,000
Members Managed
900,000+
Total Records
$190M+
In Local Receipts Tracked
99.998%
Uptime
20+
Years in Operation
~100
Training Sessions per Year

We'd love to show you what we've built.

Whether you run a single local group or an entire parent organization, Groupable was built by people who understand your world — because we're part of it. Request a demo and see for yourself.

Request a Demo