Union Membership Management Software: Custom Build vs UnionWare and UnionTrack
Buy UnionWare or UnionTrack ENGAGE. Most locals under about 8,000 members, with one or two dues formulas and a handful of remitting employers, will spend far less and get more by configuring a product than by commissioning one.
On this page
Buy UnionWare or UnionTrack ENGAGE. Most locals under about 8,000 members, with one or two dues formulas and a handful of remitting employers, will spend far less and get more by configuring a product than by commissioning one. Build once your dues rules differ by collective agreement, once dozens of employers remit in incompatible formats, or once a grievance deadline has already lapsed inside a spreadsheet.
What UnionWare, UnionTrack and Aptify actually do well
Two weeks a month disappear into matching employer remittances against the roll. That is the reason you are reading this, and it is worth knowing that a product may well fix it.
UnionWare was written for unions rather than adapted from a customer relationship system, and it treats membership, dues and grievances as one domain instead of three modules bolted together. It holds the roll, the employer, the worksite, the classification and the dues history in a shape a membership secretary recognises. UnionTrack ENGAGE comes at it from communication and organising, which is where a lot of union investment now goes, and it is stronger than UnionWare at reaching members on a phone. Aptify and iMIS both serve large internationals as association management systems with real reporting depth, and if your national office already runs one, extending it downward is often cheaper than anything else on the table.
All of them beat what most locals run today, which is a database somebody built in 2009 plus four spreadsheets and a filing cabinet. If your local has one or two employers, a single dues formula and under a couple of thousand members, stop here and buy. The total cost sits far below a build, the implementation takes weeks rather than quarters, and the money is better spent on a second organiser. We lose work by saying that and we say it every month.
Where they stop: the dues formula is contract law, not a subscription
Dues in this sector are not a monthly price. They are a calculation negotiated at a bargaining table, and that is the specific workflow generic products model badly.
One agreement charges two hours pay per month at the member's classified rate, with a lower rate for apprentices and a different treatment for part timers and retirees. Another charges a percentage of gross wages capped at a monthly maximum. A third adds a working dues assessment on hours worked that applies only to members under that one agreement, and only on hours above a threshold. Every one of those is a formula whose inputs arrive on the employer remittance file, and every one changes on a date set by ratification rather than by your billing cycle.
Packaged products expose the common shapes and handle the remainder as manual adjustments. Manual adjustments are where the errors live, and the errors matter more here than in most categories, because dues paid through a period determine good standing, and good standing determines who may vote and who may run for office. Under the Labor-Management Reporting and Disclosure Act an incorrect eligibility determination is not a clerical matter, it is a challengeable election.
The second gap is the grievance clock. A grievance carries contractual step deadlines that differ by agreement, counted in working days against a calendar, and a missed step can extinguish a meritorious grievance permanently. Generic case tools give you a due date field. They do not compute the next deadline from the agreement, the step and the date of the triggering event, and they do not escalate before it expires.
The arithmetic: cost per member per month against the cost to build
Run this with your own renewal figure rather than a published price. Membership products in this sector are priced per member per month, sometimes banded by roll size, sometimes with modules for grievances and self service charged separately. Take your annual invoice, divide by twelve, divide again by your paid roll, and you have your real rate. Most locals have never seen that number written down.
Then add the part the invoice does not carry. Count the hours your membership staff spend on remittance matching, arrears letters, per capita assembly and reproducing seniority lists, and cost them at fully loaded rates. In locals we have worked with, that second figure is routinely larger than the licence, and it is the figure that decides the comparison.
Against that, a first release sits in the band below. Amortised over five years with support, the midpoint lands near $30,000 a year. On a single dues formula the crossover falls around 12,000 members, because below that a product plus disciplined process is simply cheaper. Change one variable and the crossover collapses: once you take remittances from more than roughly 40 employers in incompatible formats, or run more than four genuinely different dues formulas, it drops to about 4,000 members. Complexity moves this line far more than headcount does.
What a custom build actually costs, including migration and year two
In Digital Heroes delivery experience, a first release covering the membership roll, employer remittance import and matching, dues calculation driven by the collective agreement, arrears and derived good standing runs $75,000 to $150,000 in 12 to 18 weeks. A full system adding grievance and arbitration management with step deadlines, seniority and referral lists, per capita reporting to the international, member self service and strike or benefit fund administration runs $180,000 to $400,000 across 8 to 14 months.
Data migration runs 10 to 25 percent of build cost, and in this sector it lands high. The reason is dues history: you cannot import a balance, you have to import the periods a member paid through, because that is what good standing is derived from and what an election challenge will test. Expect at least two rehearsals with a reconciliation that ties converted arrears to your existing ledger member by member.
Year two and each year after runs 15 to 20 percent of build cost annually. In a union that is not optional maintenance, it is bargaining: every renegotiated agreement is a new rule version, and a system nobody funds after go live stops matching the contracts within two rounds.
What pushes cost up here specifically: the number of distinct agreements and how genuinely different their dues rules are, the number of employers and remittance formats, referral or dispatch lists for the building trades which are effectively a second system with a very attentive audience, and statutory reporting. Your annual LM-2 is due within 90 days of your fiscal year end and requires officer and employee disbursements allocated across functional categories. No membership product produces that allocation, and building toward it saves weeks every spring.
The four situations where building wins
Regulatory fit. Your constitution and your agreements are the specification. Suspension procedures, eligibility to vote and hold office, per capita obligations and trusteeship rules are written documents with dates, and when a product cannot express them your staff become the workaround. Add the reporting obligations under the Labor-Management Reporting and Disclosure Act, filed as LM-2 above $250,000 in annual receipts, LM-3 between $10,000 and that threshold, and the case gets sharper.
Scale economics. Above the crossover described above, per member pricing compounds against you every year your organising succeeds. A dues system whose cost rises with the thing you are trying to grow is a strange thing for a union to sign.
A workflow that is your advantage. For building trades locals that is the referral or out of work list, because dispatch order decides who eats. Members will find every error in it, the list has to be reproducible as it stood on a date fourteen months ago, and no generic product models your trade's referral rules.
Integration sprawl across three or more systems. Count them: the membership database, employer remittance files, a payroll deduction feed, your accounting package, the international's per capita portal, a benefit or pension administrator, and whatever holds grievances. Once a monthly cycle crosses three of those, somebody is keying the same fact repeatedly, and that person is your reconciliation risk.
How to decide in a week: the remittance reconciliation test
Take last month's remittances from your five largest employers and put them on a table with your roll. Then answer four questions in writing. How many members on the roll did not appear on any remittance. How many names on the remittances could not be matched automatically. How many dues amounts differed from what the applicable agreement says they should be. And how long did answering the first three take.
The last number is the decision. Under two working days across your five biggest employers, buy a product and tighten your process. Over a week, and the problem is structural rather than a staffing shortfall, because the same work will recur every month for as long as the local exists.
Then run one more check before spending anything. Ask your senior steward to reproduce the seniority list as it stood on a specific date last year. If nobody can, you have an evidence problem that predates any software decision, and it belongs in the specification.
Then commission a paid discovery phase rather than accepting a free proposal. At Digital Heroes that produces a signed product requirements document before a line of code exists: the agreement model, the dues rule versions, the matching logic, permissions, reporting outputs, acceptance criteria and a fixed price. You keep that document whichever way you go, and it is what makes competing quotes comparable.
Who we are wrong for: a local under 2,000 members on one dues formula should not hire us, and we will tell you so on the call. We work as India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, the union owns the repository from the first commit, and you meet the named engineers before signing rather than a bench in month two. More than fifty specialists, over 2,000 projects delivered, and our own products ShopScore, HeroCheckout and Section Vault. Checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
- Gartner projects self-service and live chat will overtake traditional assisted channels as the leading customer service technologies by 2027, reflecting the shift toward deflection-oriented, lower-cost-per-contact support. Source: Gartner (2025) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- The performance gap between digital and AI leaders and laggards is widening: McKinsey reports leaders pull ahead on shareholder returns, and the average maturity spread between top and bottom performers jumped ~60% (from 10 points in 2016-19 to 16 points in 2020-22), reinforcing that the returns to transformation concentrate among top performers. Source: McKinsey & Company (2023) →
Frequently asked questions
How long does a custom union membership system take to build?
Twelve to eighteen weeks for a first release covering the roll, remittance import and matching, dues calculated from the collective agreement, arrears and derived good standing. Grievance and arbitration management, seniority and referral lists, per capita reporting and member self service add a further six to ten months. The usual cause of a slipped date is agreement language nobody has translated into rules before kickoff.
Who owns the membership data if we stop working with a developer?
You should own the repository, the cloud accounts, the database and the right to hire any other firm, all agreed in writing before kickoff. A union in particular should never hold its membership record inside a vendor's account, because that record carries employment, earnings and sometimes health related information about people whose employers would find it useful. At Digital Heroes the client owns everything from the first commit.
What happens if a collective agreement is renegotiated mid build?
Nothing breaks if the agreement is modelled as a versioned object with an effective period and dues rules attached to it. You add a version, and every calculation after that date follows it while historical periods stay computed the way they actually were. If the build instead put a rate field on the member record, every renegotiation becomes a data migration, which is the failure worth designing against.
Can we keep our accounting package and build only the dues side?
Yes, and it is usually the right sequencing. The dues engine computes what is owed and what was paid, then posts summarised journals into your existing accounting package rather than replacing it. Locals that try to build general ledger functionality alongside membership double the scope for no benefit. Decide early who owns cash receipts, because that boundary defines the interface.
Should a small local build anything at all?
No. Under about 2,000 members with one or two employers on a single dues formula, a product plus a disciplined monthly process is cheaper and faster, and we would say so rather than quote. The one narrow exception is a referral or dispatch list in a trade whose rules no vendor models, which can be built as a small standalone system alongside a purchased membership database.
What is the difference between membership software and association management software?
Membership software here means the union specific chain: employer remittance, dues derived from an agreement, arrears, good standing, grievances and seniority. Association management software such as Aptify or iMIS is broader and more generic, strong on events, communications, committees and finance, and weaker on anything the collective agreement dictates. Large internationals often run the second and still need the first underneath it.
How much does migrating dues history from an old database cost?
Budget 10 to 25 percent of build cost and expect the upper end. Balances are easy and almost useless. What you must carry across is the period each member paid through, under which rule version, evidenced by which remittance line, because that is what good standing derives from and what an election challenge tests. Plan two rehearsals with member level reconciliation before cutover.
Can members see and update their own record safely?
They can, and self service reduces call volume quickly, but decide separately what a member may view and what a member may change. Address, contact details and communication preferences are safe to edit. Classification, employer, seniority date and dues status are derived records that a member should see with an explanation and dispute through a process, never overwrite. Getting that split wrong creates work rather than removing it.
What happens if a grievance deadline is missed because of the software?
That is exactly the exposure worth engineering against, because a lapsed step can extinguish a meritorious grievance permanently. The system should compute the next deadline from the agreement, the step and the triggering event against a working day calendar, warn a named person before it lands, and refuse to let a step close silently. Ask any vendor to demonstrate that on your own contract language.
Should we build member self service before or after grievances?
After. Self service is visible and popular, which is why it gets prioritised, but grievances carry legal consequence and dues accuracy carries constitutional consequence. Build the roll, the remittance matching and the dues engine first, prove them across a full quarter, then add grievances, then release self service as a read only view before allowing any updates. That order costs less in total and fails more safely.
How much does a custom CRM cost for a small business?
Most small business CRMs we build at Digital Heroes land between $15,000 and $40,000 for a first working version, while builds with multiple pipelines, role hierarchies, and several third-party integrations run $60,000 to $150,000. Across 2,000+ delivered projects, the biggest cost driver is integration count, not screen count. A 5-person sales team tracking leads, deals, and follow-ups usually sits at the bottom of that range.
At what team size does building a custom CRM get cheaper than paying for Salesforce?
The crossover usually lands between 15 and 25 users. Salesforce Enterprise lists at $165 per user per month, so a 20-person team pays roughly $39,600 a year indefinitely, while a $45,000 custom build plus $8,000 to $12,000 in annual upkeep breaks even in about 18 months. Below 10 users, Salesforce or Zoho is almost always the cheaper path and a good agency will tell you that.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
Who owns the source code when an agency builds my CRM?
You should own it completely, through a written IP assignment that transfers copyright on final payment, with the code sitting in a repository you control from day one. Watch for contracts that only grant a "license to use," which quietly keeps ownership with the agency and locks you in for every future change. Open-source libraries inside the project keep their own licenses, which is normal; your business logic must be exclusively yours.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
What happens to our CRM if the agency shuts down or we stop working with them?
Nothing dramatic, provided three things were set up at the start: the code in a repository you own, hosting and domain accounts in your name with the agency as an invited collaborator, and documentation plus a handover clause in the contract. Under those conditions any competent team can pick up a mainstream-stack CRM within a couple of weeks. If an agency insists on owning the hosting account or the repository, walk away before the build starts, not after.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What should I prepare before contacting an agency about a custom CRM?
Three things: a written list of the 5 to 10 jobs the system must do phrased as tasks (like "produce a quote from a site-visit photo"), an export or screenshots of whatever you use today, and a realistic budget range. You do not need a formal specification; a good agency writes that with you during discovery. Arriving with those three cuts weeks off scoping and gets you a firm quote instead of a padded one.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How does a custom CRM handle GDPR, HIPAA, or other compliance requirements?
Compliance has to be designed in from the schema up: field-level encryption, role-based access, audit logs, retention rules, and for GDPR a working way to export and delete a person's data on request. Custom can actually be the stronger option because you decide exactly where data lives, including keeping it in-country or on your own servers, which off-the-shelf tools do not always allow on lower tiers. If HIPAA applies, confirm the agency will sign a business associate agreement and has shipped healthcare systems before, because that experience is not implied.
Who can build a custom CRM software system?
Digital Heroes builds custom CRM software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other CRM software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Aria.
Senior Account Manager · Retail · Sydney · 2 posts on the site
Published · Last updated .
