An association does not need custom software just because its membership register is messy. If a subscription product can manage members, collect dues, issue receipts and give the treasurer a reliable report, buy it. A custom membership portal starts making sense when your approval rules, chapters, levies or reporting needs cannot fit a standard product without constant spreadsheet work.
For a Nigerian association planning a custom build in 2026, these are illustrative project-scoping allowances, not surveyed market prices or a quotation:
| What you need | Initial build allowance | Typical scope |
|---|---|---|
| Focused member portal | ₦1.5m–₦4m | Member accounts, application review, basic directory, admin dashboard |
| Membership and dues platform | ₦4m–₦10m | Multiple dues types, verified payments, receipts, reports, permissions and migration |
| Multi-chapter institutional system | ₦10m+ | Branch-level controls, complex approvals, integrations, historical data and stronger support |
A public information website without member accounts is a different, usually smaller project. Hosting, payment-processing fees, SMS, data cleanup and ongoing support are not automatically included in these allowances. The actual quote depends on the workflows and risks, not the number of dashboard screens.
When a subscription is the better purchase
Start by testing existing membership software against real association tasks. Can your secretary approve an application? Can a member check their dues balance on a phone? Can the treasurer export a report without editing it manually?
A standard product is usually the sensible choice when you have one membership class, simple annual dues, a small leadership team and no unusual integration. A subscription also gives you a working system sooner, with less responsibility for maintaining software.
Before subscribing, ask for a demonstration using your own sample membership rules. Check the member limit, payment fees, SMS allowances, export format, administrator permissions and what happens to your records if you stop paying. Do not compare only the advertised monthly price.
When custom development earns its cost
Custom work is more defensible when the association operates across state chapters, has multiple membership classes or requires different approval powers for a national secretariat, branch officers and a treasurer.
It can also be justified when members owe several independent obligations: annual dues, development levies, event fees and arrears. A single “paid/unpaid” field cannot explain which obligation was settled.
For example, imagine 400 members each owing ₦25,000 in annual dues. That creates ₦10 million in receivables, not ₦10 million collected. If some members pay half, some pay twice and others pay by bank transfer, the system must distinguish obligations, payments, allocations and outstanding balances. Otherwise a polished dashboard can still show misleading figures.
In my work on bookkeeping and property-management systems, the difficult part is rarely the form that records a payment. It is preserving an accurate history when payments are partial, reversed, delayed or associated with different obligations. That same discipline matters in a membership portal.
What actually makes the quote expensive?
Membership rules. Define who can apply, who approves, when membership becomes active, what happens on suspension and whether an expired member can still access documents. Decide whether a membership number survives renewal or transfer to another chapter.
Dues and reconciliation. Each charge needs a period, amount, member, status and payment history. A bank transfer awaiting manual verification must not appear as settled merely because someone uploaded a receipt. For online collections, Paystack’s transaction verification guidance explains how a server confirms payment status. Its webhook documentation explains signature verification and delivery retries. Design the system so one transaction cannot credit a member twice.
Permissions and governance. A branch secretary should not automatically see every national member’s private records, and a treasurer should not necessarily be able to change membership approvals. If the system uses Supabase, its Row Level Security guidance describes enforcing access rules at the database layer. Hidden buttons are not an authorization system.
Migration. Old Excel files often contain duplicate people, inconsistent membership numbers and years of unverified payments. Importing the file is quick; deciding which record is authoritative takes work. Agree on the cutoff date, reconciliation process and who signs off the opening balances.
Member experience. Many members will use a phone, not a laptop. Make the core tasks short: sign in, check standing, pay a due, download a receipt, update permitted details and contact the secretariat. An elaborate native mobile app is not automatically necessary for version one.
Privacy and continuity. Membership records contain personal information. Review the Nigeria Data Protection Commission’s guidance on data protection responsibilities, and define retention, access, backups, incident handling and account removal with appropriate advice. The association should control its domain, production accounts, data exports and code handover arrangements.
A practical buy-versus-build comparison
| Decision | Subscription software | Custom portal |
|---|---|---|
| Initial cost | Usually lower | Higher discovery and build cost |
| Time to first use | Often faster | Depends on agreed scope |
| Dues and membership rules | Limited to supported settings | Designed around approved rules |
| Updates and maintenance | Mostly vendor-managed | Association or developer responsibility |
| Data portability | Depends on export terms | Must be specified and tested |
| Integrations and chapters | Depends on plan and product | Can be built, at additional cost |
The right comparison is three-year ownership cost, not subscription price against the first custom-development invoice. Include setup, data migration, gateway fees, messaging, staff training, annual maintenance, hosting and future changes. A subscription that works today may save years of unnecessary development.
For a broader explanation of multi-role software budgets, see my client portal development cost guide. If payments are a major part of the project, the Nigeria payment integration cost breakdown covers the difference between adding checkout and building reliable financial records.
What I would put in the first version
Before asking for proposals, agree on one complete journey:
- A person applies for membership and submits only the required details.
- The right officer approves or rejects the application, with a recorded reason.
- The system creates the correct dues obligations for that member and period.
- The member pays online or submits a bank-transfer reference for review.
- A verified payment is recorded once, allocated correctly and reflected in the member’s balance.
- The member can see standing and receipts; authorized officers can reconcile the same figures.
Then add a realistic exception: a member pays only part of the annual due, changes chapter, or receives a reversal. If the proposed software cannot explain that case, the scope is not ready.
Digital elections, welfare funds, public directories, native apps and complex event management can be later phases unless they are essential to the association’s first launch. For event-specific registration requirements, use the separate event registration cost guide.
Questions to ask before hiring a developer
Ask who owns the GitHub repository, domain, database, payment account and hosting; how member permissions will be tested; whether financial corrections leave an audit trail; how historical records will be migrated; what acceptance tests prove the balances; and who responds if a payment succeeds but the portal still says unpaid.
A responsible proposal should also name exclusions, delivery milestones, training, support after launch and the process for handing the system to another developer. Avoid paying for a long feature list before the association has agreed on its membership and finance rules.
If you manage a professional body, alumni association or multi-chapter organization, tell me how your membership and dues process works. I can help scope whether an existing product is enough or a focused custom MVP would remove the work your team is currently doing by hand.