Twenty-one questions, answered before the meeting.Twenty-one questions, answered before the meeting.

The association. Source code in a repository it controls, data in a PostgreSQL database in its account, hosting and domain accounts in its name, from day one. Not a licence and not an export on request.

Yes. Screens, data model and documentation are deliverables, handed over with the code.

Yes. Everything the audit produces belongs to the association. Occasionally that is exactly what happens.

Under the hood, yes. That is engineering practice. What you own is your platform, designed for your association, and nothing in it depends on another client's system.

The audit is roughly $5,000 to $15,000 and ends with a fixed quote. Builds typically run $60,000 to $200,000 by scope. Running the platform is a monthly fee sized to it, usually well under what the old subscriptions cost.

Because no honest one exists until every tool, workaround and record has been counted. A number given before that is a sales number.

Over five years, not one. Subscriptions, the integrator and staff hours against audit, build and run. The calculator on this site does the arithmetic; the audit replaces the inputs with your real ones.

It cannot without a signed change, because the quote is fixed to the blueprint. New ideas go on the improvement backlog for after launch.

It is read during the audit, cleaned with your membership lead, and migrated in three passes with the old systems frozen only for the final one. Nothing is deleted from the old systems until you say so.

One login, for everything. Members are invited to set a password once, or sign in through their organization if it uses single sign-on. The old logins retire.

That is the usual way: website, portal and directory together, renewals before the next dues cycle, events before registration opens, chapters one region first.

About four hours from the executive director across the audit, a morning from whoever does the workarounds, a review session with the membership lead in each migration pass, and two training sessions before launch.

Permissions are enforced in the database with row-level security, so a member sees only what their role allows even if a screen has a bug. Encrypted at rest and in transit. Daily backups with a tested, dated restore.

Only the people building and supporting the platform, with named access you can see and revoke, through accounts you own.

Through Google Workspace or Microsoft 365, so a leaving staff member loses access the moment their account is closed.

WCAG 2.1 AA is the target for every platform we build, in both themes, with a statement your association can publish. Associations are increasingly asked for one.

The platform stays. It runs in your accounts on an open, widely used stack, with a documented codebase and a written handoff. Any competent product team can take it over.

No. Run is a service you can buy from us, from another team, or bring in-house. The hosting bill goes to you either way.

Because ownership is structural, not personal. Accounts in your name, code in your repository, a stack any team knows. The risk of a small studio is real; the design removes it.

Because the AMS, the association management system most vendors sell, was built for the vendor's average customer. This is built for your members. Keep the tools staff love and connect them; do not build inside them.

The one named proof is HollywoodCast, a two-sided marketplace we own and built end to end on the same stack. Everything else belongs to the people who paid for it, so it is described by sector, not named.