Use cases
For teams who build the same kind of app again and again
CRMs, portals, membership and voting systems, admin back offices: build them from one library, consistently, without copy and paste.
Use case
Membership CRM
Members, memberships, renewals and notices, with approval for new members and search across them all.
Use case
Voting Management System
Elections, ballots, candidates and votes, with roles for officers and a record of every result.
Use case
Customer Portal
Customers, accounts and requests, with sign-in, notifications and an API for the rest of your systems.
Membership CRM
Member and Membership entities from Contact Information and Money bundles, with CRUD management, search, soft deletes, an approval workflow and notifications.
- Member, Membership and Renewal entities
- Approval workflow for new members
- Notifications on renewal
Voting Management System
Elections, ballots and candidates related in one package, with roles and permissions for officers and voters, and tests for every rule.
- Election, Ballot, Candidate and Vote entities
- Roles and permissions per office
- Generated tests for every entity
Customer Portal
Customers, accounts and requests with authentication, notifications and a routes-and-API layer, deployed with configuration per environment.
- Authentication and two-factor
- Routes and API generated
- Staging and production environments
Which one do you build most?
Start with it, and the next one starts from the same library.