A customer explains how they actually buy. An alum mentions the industry she'd hire from. A board member tells you what went sideways last time. Those moments are the reason you put everyone in a room — and they're the first things to vanish when it's over. Subtex keeps them, and hands them back the moment they matter again.
The roster, the profiles, and everything your people wrote down while the conversations were still fresh. Nobody has to reconstruct who was in the room.
The useful part of any meeting is something a person volunteered. How they buy. What went wrong the last time somebody tried this. The reorg coming in the fall. Right now that lives in one head and one notebook, and it surfaces again only if the same person happens to be in the next room.
In Subtex it sits on the record with the person it came from. In the car before the meeting, a year later, or when someone else from your team picks up the conversation — it's one question away.
Your account team spends a week assembling bios, org charts and talking points. It gets printed the night before. Your executives carry it into the room, write the genuinely useful part in the margin next to a bio — and then it's recycled, or filed as a PDF nobody opens again. Next year the team starts from scratch, and the margin notes never existed. Worth noticing too: everything in that binder was assembled about the person, not by them.
Joined Meridian in 2019. Leads a 400-person operations organization across nine regions. Previously at Cavendish Communications. Board member since 2024.
“Rebuilding the field ops team — hiring is her whole year. Daughter plays at Syracuse. Wants to talk about the 2027 rollout, not this one.”
Left behind · May 2026Asked eleven months later, from a car on the way to the meeting — and answered before you get there.
Invite your list or hand out a team code. Membership is real from the moment the invitation goes out, so you're never reconciling a spreadsheet against a sign-in sheet afterward.
Define the fields that matter to your organization and they appear across every member and every team. Edit them as you learn what you actually need.
A prepared read on a person — background, working style and shared history — governed by rules you set for who can see what, and scoped so event context stays inside the event.
Who was invited, who joined, and what was captured. Pull it the week after, or three years later when someone asks who was actually in the room.
A program isn't one audience. There are the players on the roster right now, the alumni who wore the same jersey twenty or forty years ago, and an alumni development office trying to understand who is genuinely still connected. A campaign page speaks to one of those. A team hub can hold all three — and each group's activity makes the hub more useful to the other two.
A roster is four years long. A program is fifty. Players see who came before them, where those people ended up, and that the jersey connects to something that outlasts their eligibility.
Most alumni know the fifteen people they played with and nobody else. The hub makes the other decades visible — who's nearby, who's coming back for the weekend, who works in the industry you're hiring in.
Not a mailing list of everyone who ever enrolled. The people who accepted the invitation, joined the hub and came back for something — visible to the office that needs to know where a conversation is worth having.
Subtex holds the relationship up to the hand-off. Pledges, gift records and financial terms stay in your alumni development system where they belong — what you gain here is the context a gift officer walks in with, and a much better sense of where that conversation is worth having.
Golf clubs, sailing clubs, summer communities. No single event introduces everyone — the membership is too large, people come and go by season, and the connections that do form happen by accident on the dock or the first tee. A directory gives you a name and a phone number. It doesn't give you a person.
The same card he'd hand to anyone on the dock.
Met him at the spring dinner. Said to come find him if I ever wanted to learn the Wednesday series.
The front is the introduction. The back is what Hal chose to share — how he got into it, what he does when he's not here, the answers to the questions the club decided were worth asking.
Underneath that is what you added. Where you met him, what he offered, and the tags that will bring him back the next time you go looking. His half and your half, on the same card.
The club writes the questions. A sailing club asks about boats and first crossings. A golf club asks how you came to the game. A summer community asks which weeks you're around. Members answer once, and those answers travel with them for as long as they belong.
Nobody on your team is compiling this. The customer fills out their own card. The alum tells you the industry she's in now, not the one she was in when she graduated. The member answers the questions your club wrote. It's theirs, so it's current — and they can change it whenever they want.
This is the part that makes it work. People fill it out because it's useful to them, and the organization ends up with something more accurate than any enrichment tool could produce. Nobody has to be talked into it.
Advisory boards, customer summits, partner councils. Replace the printed briefing binder with something that survives the event, and give your executives total recall of the last conversation before they walk into the next one.
One hub serving three groups at once: current players who see the program they've joined, alumni who find the teammates and decades they never knew, and an alumni development office that finally has a real read on who's still connected.
Golf and sailing clubs, summer communities, associations and boards. Make a large membership navigable — what each member chose to share about themselves, answered once against questions the club wrote, plus whatever you add after you meet them.
Teams and Organizations plans are billed flat annually — not per seat — so inviting one more person is never a budget conversation. See the plans.
Not a rollout. A single summit, reunion or chapter meeting, run the way you'd run it anyway — with a record at the end of it.
Create the event, write the questions your people should answer, and invite your list — or hand out a team code. The roster is real from the invitation forward.
Your customers, alumni or members answer in their own words. Nobody on your team is compiling profiles the week before.
People see who else is there and what they're about, and add their own notes and tags while the conversations are still fresh.
Pull the report the following week. Then find it again a year later, when the same names come back around.
Most organizations start here rather than with a platform decision. One event is enough to see whether the record is worth having.
Subtex for Organizations is the Teams and Organizations side of Subtex. You create an event, invite your list or hand out a team code, and your people fill out their own cards. What they learn in the room — notes, tags and context — stays on the record and is there the next time those names come back around.
Three groups. Enterprises running advisory boards, customer summits and partner councils. University athletics and alumni development offices running programs that serve current players, alumni and development staff at once. And clubs and seasonal communities — golf and sailing clubs, summer communities, associations and boards.
Teams and Organizations plans are billed flat annually rather than per seat, starting at $4,000 a year, so inviting one more person is never a budget conversation. Every member of the organization gets the full Subtex One feature set at no extra per-person cost. See the plans.
Most organizations start with a single event rather than a platform decision — one summit, reunion or chapter meeting, run the way they'd run it anyway, with a record at the end of it. Usually a 30-minute conversation and a look at your next event on the calendar.
Bring Subtex to a single summit, reunion or chapter meeting and see what it captures. Then decide what it's worth across the whole organization.
Usually a 30-minute conversation and a look at your next event on the calendar.