own product · 01 · in alpha
cohesion.
one platform that runs your association, not fourteen spreadsheets and a whatsapp group. members, disciplines, instruction, equipment. GDPR and audit log sit in the architecture, not in a switch you can flip on.
why this exists
the rules keep piling up.
the board keeps shrinking.
that is the gap.
the problem
gdpr, internal discipline, federation reporting, financial transparency. something is added every year, while every year there is one fewer person to handle it.
the symptom
ten spreadsheets. three group chats. one secretary who keeps it all in their head and steps down next year. one gdpr request from a member and the panic sets in.
what cohesion does
members, planning, equipment and communication in one system. every sensitive action in an audit log that cannot be edited afterwards. continuity sits in the platform, not in one volunteer.
members.
modular.
audit log.
a foundation, a set of building blocks, and a log that cannot be edited afterwards. turn on what your association needs, and do not pay for the rest.
members + GDPR
not a separate module, the foundation. roles and permissions you configure yourself, membership status, sign-up through a public page that the board approves. field-level encryption on sensitive data, and in the member portal everyone sees what is on record about them.
- · roles and permissions configurable per association
- · aes-256 field-level encryption on sensitive data
- · every change to a member logged with before and after values
modular per association
turn on what you need, nothing more. today that means check-in, equipment, courts, instruction scheduling, stock, teams, news, sanction records and incident logging. finance, meetings and competitions are on the roadmap.
- · check-in covering equipment hand-out and return, with a full audit trail
- · instruction scheduling with fair distribution based on qualifications
- · equipment, courts, stock with low-stock alerts
an audit log that holds up
for discipline cases, inspections and federation reporting. every sensitive action logged with actor and timestamp, tied together with a sha-256 hash chain. anyone editing it afterwards breaks the chain visibly.
- · every write with actor and timestamp
- · sha-256 hash chain, so tampering shows
- · before and after value per change, so you see what actually changed
four kinds of associations
with this problem.
cohesion is built with shooting sports as its starting point. that is the corner i know, and it is the corner with the heaviest regulatory load: federation reporting, equipment you have to account for, internal discipline. what holds up there holds up anywhere. the data model is kept generic for that reason, with a "session" and an "asset" rather than a shooting session and a weapon.
sports associations
participation tracking, court and equipment management, instruction scheduling. from shooting clubs to tennis to bowling.
homeowner associations (VvE)
meetings, votes, minutes you can actually find. decisions with date and signature, not lost in email. on the roadmap for the public release.
community and student associations
members, volunteers, treasury, without scattering across six apps and three treasurers.
music and culture ensembles
rehearsal planning, instrument tracking, dues. who plays what, who borrowed which case.
early access:
cohesion alpha.
i am looking for five associations to build with. clubs willing to push the system hard and give feedback that sharpens the product.
-
free: the alpha period costs nothing
-
direct line: weekly call, no ticket queue
-
you help decide which module gets built next
-
migration help: i move you off whatever you run today
