The story · EO Arizona

Built by an EO chair, for EO chairs.

OurChapter OS isn't a product that started in a boardroom. It started as a Learning Chair's frustration on a Tuesday night, in EO Arizona, a working chapter where it still runs today.

One Learning Chair, one frustration.

John-Scott was Learning Chair at EO Arizona, a chapter with a packed year of programming and a board running fast. The job had a dozen moving parts. Speaker outreach, contract negotiation, venue logistics, fee budget, SAP relationships, member feedback. The tools were a tangle of spreadsheets, Google Calendars, and Slack threads. Anything important was "in someone's head."

So he built it for himself.

A simple way to plan the year's speakers, track contracts, and keep the budget from drifting. Nights and weekends. Just enough software to make his own job calmer.

Then he built it for other chairs in his chapter.

The President wanted to see across the calendar. The SAP Chair wanted partners visible to the board. The Engagement Chair didn't want to schedule a navigator mixer the same week as a speaker. The Executive Director wanted chapter-wide budget visibility. One chair's tool became the whole board's operating system.

Then for other Learning Chairs.

Word travels fast in EO. Other Learning Chairs at other chapters asked the same question: "Can we have what you have?" So a single-chapter app got reshaped to support many chapters. Each with its own data, its own people, its own fiscal year, its own theme.

Then for the Regional Learning Chair Expert.

The Regional Learning Chair Expert advises across many chapters. She needs to see what's actually happening in each one, without violating member privacy. So a new role got built: read-only across her region, blocked from anything member-private (reflections, lifeline, forum content), with a regional dashboard that surfaces what each Learning Chair is working on this year.

Now it's a chapter operating system.

Every chair role gets their own surface. The board gets a shared calendar that warns when chairs schedule conflicts. Members get a private space for reflections, lifeline, and forum tooling. SAP partners get their own portal where they can only see what's been opened to them. It all started as one chair's frustration. The philosophy hasn't changed: built by an EO chair, for EO chairs, running real chapters today.

Running on the love of EO.

Want this for your chapter?

We're working with a small set of chapters early on. If you're a board member or chapter ED, the fastest way in is a quick conversation. There's no per-seat fee, no chapter license. Best of all, it's free.

Bring this to your chapter

Prefer email? jdixon@aidantaylor.com