The platform
Built for one association. Yours.
Most AMS products, the association management systems most associations rent, sell one system to everyone, and most CRMs do the same. MemberWright designs and builds one system for one association: the CRM, member portal, directory, renewals and events that fit how your members, chapters and staff actually work.
What a custom platform includes
Six parts, one member record underneath.
Nothing to integrate, because it was never separate. Every screen below reads and writes the same record.
CRM
One record per member organization and person: dues, chapters, events, requests and every conversation, in a standard PostgreSQL database in your name.
Member portal
Designed like a consumer product, not a database. Members log in because it is useful, not because they were told to.
Directory
Built around how your members find and work with each other: search by region, service or chapter, then message or send a request directly.
Renewals
Dues cycles, invoices and payments on the same record, with reminders that know what a member has already done.
Events
Conference and chapter registration on the member's own account. The attendee list staff see updates the moment someone registers.
Website
The public site and the portal from the same system, so the news, the directory and the calendar never disagree.
Sample screens
Events, chapters and member-to-member work, on one account.
Every build is designed for one association. These screens belong to Northbridge Alliance, the fictional association we design and test against.
Sample data for Northbridge Alliance, a fictional association. Any resemblance to real organizations is coincidental.
Annual conference · Lisbon
Chapter · Benelux
Member-to-member request
What replaces what
Five systems and an integrator, or one platform.
What most associations run today
What MemberWright builds instead
What most associations run today: An AMS with a login members avoid
What MemberWright builds instead: A member portal designed like a consumer product
What most associations run today: A directory plugin bolted to the website
What MemberWright builds instead: A directory built around how your members find and work with each other
What most associations run today: Renewals in one tool, events in another, email in a third
What MemberWright builds instead: One CRM and member record, with renewals, registration and communication on top of it
What most associations run today: An integrator paid to keep the plugins talking
What MemberWright builds instead: Nothing to integrate, because it is one system
What most associations run today: A vendor's roadmap
What MemberWright builds instead: Your roadmap, your code, your data
Our stack, stated plainly
We build on our own stack. We connect to yours.
Keep the tools you love and we will connect to them: HubSpot, Mailchimp, QuickBooks, Stripe, single sign-on. We just will not build your platform inside Salesforce, Oracle, iMIS or a plugin marketplace.
Application
Next.js (React, TypeScript)
Modern, fast, and the most widely hired-for web framework. Easy for another team to take over.
Database and auth
PostgreSQL on Supabase, with row-level security
Your data in a standard database you own, with member-level permissions enforced at the data layer.
Interface
Tailwind and shadcn/ui
Consistent, accessible components. The platform looks like a product, not a plugin.
Hosting
Cloudflare, AWS, Vercel or Netlify, accounts in your name
No lock-in to MemberWright. You hold the keys from day one.
Ownership and handoff
The board's questions, answered in plain words.
The association. Full source code, data and infrastructure accounts in its name from day one. Not a licence, not an export on request.
An open, widely used stack, a documented codebase and a written handoff. Any competent product team can take it over.
Permissions are enforced in the database itself, so a member sees only what their role allows. Encrypted at rest and in transit, daily backups, and single sign-on for staff.
Yes. The platform connects to them and stays the system of record.
Who it's for
Networks where members need to find each other.
Four kinds of association we design for. Each page shows what they run on today, the three jobs the platform does, and sample screens for a fictional association of that kind.
- Who it's for
Hospitality and travel associations
Hotels, lodges, campgrounds and destinations whose members are also each other's referrals.
- Who it's for
Franchise and operator associations
Owners and operators who need a voice, a peer network and a record of their own.
- Who it's for
Professional societies with chapters
Individual members, credentials, continuing education and chapters that need their own space.
- Who it's for
Trade and industry networks
Independent member companies who do business with each other across borders.
Built from scratch on the same stack
HollywoodCast
The one named proof, because MemberWright owns it. HollywoodCast is a two-sided casting marketplace built end to end on Next.js and PostgreSQL: profiles, a searchable directory, subscriptions, verification and messaging between two kinds of members.
It is not an association product. It is evidence that the studio ships working platforms, not slides about them.
Find out what one record would retire.
Start with a three-week audit: every tool mapped, a blueprint and a fixed quote. No demo, no sales deck.