Why we created Reunionsoft

I created Reunionsoft because planning my 25-year high school reunion turned into a second job. Finding classmates, collecting RSVPs, deciding on a venue, and tracking payments all took more work than I expected.

At the beginning, I was confident. I'm a software architect. I figured a spreadsheet, a form, and our Facebook group would be enough to get everyone together for a night.

I called the high school and got a list of classmates. I imported it into a Google Sheet, attached a Google Form for RSVPs, and started posting in the Facebook group we had created for our class.

It felt like a pretty good system. Until I actually had to use it.

The class list was just the beginning

Having a list of names and being able to reach those people turned out to be two very different things.

We tried the last phone numbers and email addresses we had. So many led to dead ends. People had moved, changed names, or stopped using the contact information on file. Posting in our Facebook group helped us reach some classmates, but it did nothing for the people who weren't there to see it.

We started calling people manually and asking friends if they knew how to reach someone else. Every connection mattered, but every one took work. The reunion was supposed to bring the whole class back together. I didn't want our guest list to depend on who happened to still be easy to find.

You need a headcount before you can make a plan

Next came the question that drove almost every other decision: how many people were actually interested?

We needed RSVPs to get a sense of the venue size and what we could afford. But people understandably wanted to know the date, location, and price before committing. We were trying to measure interest while still working out the very details people needed to decide.

Even after we tracked down classmates, there were dates to compare, locations to discuss, and a budget to figure out. A form could collect an answer. It couldn't organize all the conversations around that answer.

What I had imagined as a manageable side project had become a massive job.

Then we had to collect the money

Once we had most people either in or out, and the location and venue were set, it was time to sell tickets.

I thought my Venmo account would be good enough. Then someone didn't have Venmo. So we added PayPal. Then Cash App. Then Zelle.

Now the planning was spread across a spreadsheet, a form, a Facebook group, phone calls, and several payment apps. Knowing who had said yes was one thing. Knowing who had paid was another. Keeping everything straight became another job on top of the reunion itself.

The problem wasn't that any one tool was useless. It was that I had become the connection between all of them. Every update depended on someone moving information from one place to another.

I kept coming back to the same thought: there had to be a better way.

So I built the platform I wished I'd had

As a software architect, solving problems is what I do. This one was personal. I wanted to build the easiest reunion platform I could, so the next person who volunteered wouldn't have to piece together the same system I did.

That became Reunionsoft.

The idea is simple: keep the work of bringing your class together in one clean interface.

• Find classmates: import your class list and use contact lookups to help reconnect with people you've lost touch with. A search won't find everyone, but it gives you another place to start beyond an old phone number.
• Create a community: give your class a private space for posts, photos, and polls. Ask about dates and plans where everyone in the group can follow the conversation.
• Keep personal information private by default: share the reunion details publicly while keeping the class list and private group out of public view.
• Sell tickets for the whole reunion: organize one event or a weekend with multiple events, with ticket options that fit your plans.
• Accept payments in one place: use Stripe-powered checkout and payouts to the organizer's connected bank account, instead of reconciling a collection of personal payment apps. Stripe's payout timing applies.
• Keep the committee organized: bring the budget, tasks, schedule, and check-in into the same workspace.

What I'd tell the next person who volunteers

Start finding your classmates before you get attached to a venue. Ask about realistic dates and price ranges, and remember that an expression of interest isn't the same as a paid ticket. Give people one place to check the final plan, and give yourself one place to track the work.

Those are the lessons behind our guide to organizing a class reunion in 2027, including a sample budget and a ticket-price calculation you can adapt to your own event.

The point is to enjoy your own reunion

The software is there to make room for the good part: seeing people you haven't seen in years, hearing their stories, and picking up conversations you thought you had forgotten.

I built Reunionsoft because organizing my own reunion showed me how much work sits between “we should all get together” and actually getting everyone into the same room. I wanted to make that distance a little shorter for the next organizer.

Try Reunionsoft. I want you to be happy with the results, and the reunion fee comes with a 30-day money-back guarantee: email us within 30 days of the charge and we'll refund that fee in full, no questions asked.

I'd love to help you bring your class back together.

Tyler

About the author

Tyler Clark is the founder of Reunionsoft and a software architect. His experience organizing his own 25-year high school reunion inspired him to build a platform that brings classmate outreach, community, ticketing, and committee planning together.