What does union management software cost? A total cost of ownership guide for locals
On this page
- How much does union management software cost?
- How vendors price union software
- One-time union software costs: what implementation should cover
- Ongoing union software costs after go-live
- Union software costs that never appear on a quote
- The Five-Year TCO Worksheet: union software total cost of ownership, line by line
- Questions to ask every vendor about union software cost
- Is the cheapest union software quote the lowest cost?
- What most unions get wrong about union software cost
- How eMembership prices, and who it fits
We're an eMembership publication, and this guide ends with a clearly labeled section on how we price. Everything before that section is written to work on any vendor's quote, including quotes from vendors we compete with. It draws on public federal cost-estimating guidance and on our own published pricing and service terms.
- There is no honest single price for union management software. Vendors price on different bases and scope differently, so any one number would mislead most of the people reading it. What a local can do is read every quote against the same five cost buckets.
- The five buckets are implementation, subscription, add-ons, services billed outside the subscription, and internal costs nobody invoices. Most quotes are clear on the first two. The other three are where quotes stop being comparable.
- The pricing model shapes the five-year number more than the first-year price does. Per-member and per-seat pricing rise as a local grows. A flat fee by module holds steady as membership and staff grow, and it has a floor.
- A fixed written quote after scoping is worth more than an early estimate. An estimate leaves scope open, and open scope tends to get priced after the contract is signed.
- "Included" is a list, not a word. Support hours, releases, hosting, backups, training after go-live, and data export each need a yes or a no in writing.
- Run the Five-Year TCO Worksheet on every quote. One row per cost line, five years across, and a column for who carries each cost. Blank cells are questions, not zeros.
How much does union management software cost?
It depends on what your local needs the software to do and on how the vendor builds its price. That's an unsatisfying answer, so here's the useful version of it.
Union software vendors rarely publish price lists, and the main reason is scope. A local running member records and dues has a very different configuration from an international running dispatch, grievances, and a member app across several regions. A single figure on a web page would be wrong for most locals reading it, in one direction or the other.
What doesn't vary is the structure. Every union software quote can be read against five cost buckets:
- One-time implementation, which covers scoping, data migration, configuration, integrations, and initial training.
- The annual subscription.
- Add-ons, meaning modules or member-facing products priced on top of the base.
- Services billed outside the subscription, such as extra support hours, later training, custom reports, custom development, and extra storage.
- Internal costs nobody invoices: staff time, data cleanup, running two systems during the move, and getting your data out if you ever leave.
The real answer to "how much" is the sum of all five over the years you expect to run the system. The worksheet in this guide uses five years. That is long enough for a pricing model to show how it behaves, and short enough for an executive board to plan around.
A quote tells you what the vendor will charge. The five-year total tells you what the local will spend.
How vendors price union software
Before comparing amounts, compare what each price follows. The basis of a price decides how it behaves over five years, and that matters more than where it starts. Most quotes use one of four models, or a mix of them.
Per member
The price follows your membership count. It is easy to understand and easy to budget in the first year. The trouble arrives later, because every successful organizing campaign raises the bill while the vendor's work stays the same. Ask which members count toward the total (active, retired, inactive) and how often the count is taken.
Per user or per seat
The price follows the number of people who log in. This model is standard in general-purpose CRM software, and its effect on a local is predictable: logins get rationed. Stewards and field reps end up phoning the office for information they could have looked up themselves, which pushes work back onto the staff the system was bought to relieve. Ask whether steward, read-only, and part-time logins count as seats.
Flat subscription by module
The price follows what the software is configured to do. Growth in members or staff doesn't change it, which makes it the most predictable of the four over five years. The trade-off is a floor. Every subscription carries the same hosting, security, support, and releases whatever the local's size, so a very small local can end up paying for more platform than it uses. This is the model eMembership pricing follows, and the floor is real. Ask what happens to the fee when a module is added after go-live.
Modular base with add-ons
The price follows a base package, with some modules or member-facing products priced separately. eMembership prices this way in part, since its member portal and Member Mobile App are add-ons. The risk sits in how the demo and the quote line up. A demo usually shows a full product, and the quote may price only the base. Ask which of the modules you saw in the demo are in the number.
| Pricing model | What the price follows | How it behaves over five years | The question to ask |
|---|---|---|---|
| Per member | Membership count | Rises with every organizing win | Which members count, and when is the count taken? |
| Per user or seat | Number of logins | Rises as you give stewards and reps access | Do steward, read-only, and part-time logins count? |
| Flat by module | Modules configured | Holds steady as members and staff grow; has a floor | What happens when we add a module later? |
| Base with add-ons | Base package plus priced extras | Depends on which extras you turn on | Which demo modules are in this number? |
The demo shows the whole platform. The quote may price part of it.
One-time union software costs: what implementation should cover
Implementation is the cost of getting from the system you run today to a working new one. On a five-year worksheet it lands almost entirely in Year 1, and it has six parts worth separating on any quote.
Scoping
Before anything is configured, someone has to document how your local actually runs: how dues are calculated, how employers remit, how grievances move, what reports the board expects. Scoping may be folded into the sales process or run as its own paid project. Either can work. What matters is what it produces. Ask whether it ends in a written scope and a fixed price, and whether your local keeps those documents if it walks away.
Data migration
Most locals arrive with years of records in a legacy system or spread across spreadsheets. Moving them means mapping old fields to new ones, deciding what to do with duplicates and gaps, and testing the result. Ask whether migration is in the quote, how many sources it covers, and who does the mapping.
Configuration
Dues rules, classifications, contract rates, employer setups, and user roles all have to be built into the new system. The more of your operation the quote covers, the larger this line becomes.
Integrations
Connections to accounting and payroll systems are usually scoped individually, because every local's environment is different. Ask which integrations are in the number and which would be quoted later.
Payment processor setup
If members will pay dues online, the system has to connect to a payment processor. Ask whether setting up, or later switching, a processor is a one-time implementation item or a separate project.
Initial training
Ask how many hours of training come before go-live, for which roles, and whether it is delivered remotely or on site.
The point to hold onto across all six lines is the difference between an estimate and a fixed quote. An early estimate is a vendor's best guess about a local it hasn't studied yet. When the guess runs low, the gap tends to surface after signing, as change orders, once the real data and the real processes come into view. A fixed written price produced after scoping moves that discovery to before the contract, which is where your local wants it.
Implementation length belongs on the worksheet too, even though it isn't a price. Every month a project runs is a month of staff time in review sessions and testing, and often a month of paying for the old system as well.
Ongoing union software costs after go-live
Ongoing costs fill Years 2 through 5 of the worksheet, and they are where quotes differ most in what they quietly leave out.
The subscription itself
Write down what it is based on (members, seats, or modules) and what it covers, line by line. A subscription that covers hosting, security, and releases is a different product from one that covers access to the software and nothing else, even if the two figures look alike.
Add-ons
A member portal, a member mobile app, or a module you plan to turn on in Year 2 all belong in the rows for the year you expect to start paying for them.
Payment processing
Online dues payments run through a payment processor, and the processor charges its own fees. The question for the software vendor is whether it adds a fee of its own on each transaction. Over five years of monthly dues, a per-transaction markup is charged on every payment, so ask for it in writing even if the quote is silent.
Support
When support is sold as an allowance of hours, treat it like any other budget, because it can run out. Ask how many hours are included each year, what counts against them (questions, training, data updates), and what an extra hour costs. Ask about helpdesk hours and response commitments too, since a slow fix during payroll week has a cost even when nobody bills for it.
Training after go-live
Staff turn over. New officers are elected. Ask how training for new people is paid for once the initial hours are used.
Custom reports and custom development
Boards, auditors, and internationals ask for reports nobody planned for. Ask whether staff can build their own reports, and how custom work is quoted when they can't.
Storage
Most locals will never notice this line. Ask how much document storage is included, and what more costs, only if your local keeps large document archives in the system.
Releases and upgrades
Ask whether new versions arrive as part of the subscription or as a separate upgrade project, and whether you can test a release before it reaches your live system.
Hosting, security, patching, backups, and hardware
Ask, for each, whether it is the vendor's job or your local's. If any of it is yours, it belongs on the worksheet as a cost. The build cost ledger in our build versus buy guide lists these ownership obligations line by line, and every one that a quote doesn't cover stays with the local.
Union software costs that never appear on a quote
The fifth bucket is the one no vendor will fill in for you, because none of it is billed. It is still real money, paid in staff hours and in budget that could have gone elsewhere.
Federal cost estimators make the same point about large programs. The U.S. Government Accountability Office's cost estimating guide describes a life cycle cost estimate as an accounting of the work to operate and maintain a system as well as to build it, counted regardless of which budget pays. A local evaluating software is running a much smaller version of that exercise, and the principle carries over: a cost belongs on the sheet whether it arrives as an invoice or as a week of the membership director's time.
Staff time during the project
Scoping sessions, review cycles, testing migrated data, and learning the new system all come out of the same hours your staff already use to run the local. Put them on the worksheet in hours if you won't put them in dollars. Hours are enough to make them visible.
Data cleanup
Migration exposes every duplicate record, outdated address, and inconsistent classification your current system has been carrying. Someone at the local has to decide what each one should be, and that work is yours whichever vendor you choose.
Running two systems
A local that keeps its old system running until the new one has proven itself pays for both during that window, in subscription or license costs and in double entry for whoever has to keep the two in step. Plan the length of that overlap before it starts. Our guide to running multiple systems goes further into how split systems create cost and risk.
Getting your data out
The cheapest moment to ask about exit costs is before you sign. Ask whether you can export all of your data, in what format, and whether there is a fee. A system you can't leave without a large bill has a cost on the worksheet even in a year you don't use it.
The Five-Year TCO Worksheet: union software total cost of ownership, line by line
This worksheet turns any union software quote into a five-year number you can compare against another vendor's. It has no vendor-specific rows. Fill in one copy per quote, using the quote and the vendor's written answers to your questions.
| Cost line | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Five-year total | Who carries it (vendor or local) | Fixed or estimate? |
|---|---|---|---|---|---|---|---|---|
| 1. One-time implementation | ||||||||
| Scoping or discovery | ||||||||
| Data migration | ||||||||
| Configuration | ||||||||
| Accounting and payroll integrations | ||||||||
| Payment processor setup | ||||||||
| Training before go-live | ||||||||
| 2. Annual subscription | ||||||||
| Subscription fee (note the basis: members, seats, or modules) | ||||||||
| Hosting, security, patching, backups | ||||||||
| Releases and upgrades | ||||||||
| 3. Add-ons | ||||||||
| Member portal | ||||||||
| Member mobile app | ||||||||
| Modules added after go-live | ||||||||
| 4. Services billed outside the subscription | ||||||||
| Support hours beyond the included allowance | ||||||||
| Training after go-live | ||||||||
| Custom reports and custom development | ||||||||
| Per-transaction fees on online payments, if any | ||||||||
| Extra storage | ||||||||
| 5. Internal costs nobody invoices | ||||||||
| Staff hours in scoping, reviews, and testing | ||||||||
| Data cleanup before migration | ||||||||
| Running the old system during the transition | ||||||||
| Data export if you leave | ||||||||
| Total |
How to fill it in
Year 1 carries every one-time line. Years 2 through 5 carry only what recurs, plus any add-on or module you plan to turn on in that year. A quote that looks light in Year 1 and heavy in Years 2 through 5 is telling you something about its pricing model.
For any quote priced per member or per seat, fill Years 2 through 5 at the membership and staffing you plan to have, not the count you have today. If your local is organizing, the worksheet should show what that success costs under each model.
Mark every line "fixed" or "estimate" in the last column. An estimate is a line that can still move, so read the five-year total of a mostly estimated quote as a floor, not a figure.
Treat a blank cell as a question. Write the question beside it, collect the list, and send it to the vendor. A vendor that answers in writing has given you something to hold it to.
Use the "who carries it" column honestly. Hosting, patching, and backups are either the vendor's job or your local's. If they are yours, they need a number, even a rough one, before the total means anything.
Reading the result
Compare five-year totals only after every line on every worksheet is either filled in or marked as not applicable. Two worksheets with different blanks aren't comparable yet. Once they are, the gap between the lowest Year 1 figure and the lowest five-year total is usually the most useful number on the page, because it shows how much of the first-year saving the pricing model takes back.
A blank line on a quote isn't a zero. It's a price that will be set later, after you've signed.
Questions to ask every vendor about union software cost
These questions fill the blanks on the worksheet. Ask for the answers in writing, so they can be compared side by side and held to after signing.
- Is this quote fixed or an estimate, and what would change it?
- What does "included" cover, line by line?
- How many support hours are included each year, what counts against them, and what does an extra hour cost?
- How much training comes before go-live, and how is training paid for after that?
- Are new releases included in the subscription, and can we test each one before it reaches our live system?
- Is data migration included, which sources does it cover, and who maps our old data to the new system?
- Do you add a fee to online dues payments, on top of the payment processor's own fees?
- What happens to our price as our membership or staff grows?
- Can we export all of our data at any time, in what format, and is there a fee?
Is the cheapest union software quote the lowest cost?
Often it isn't. A low first-year quote and a low five-year cost are different things, and they separate at five predictable points.
1. Growth
Under per-member pricing, organizing raises the bill. Under per-seat pricing, giving stewards and field reps access raises it. A quote that is lowest for the local you are today can be the highest by Year 4 for the local you intend to become.
2. Support hours that run out
A small included allowance keeps the subscription figure low. When the allowance runs out in the third quarter, each additional hour becomes a new line in Bucket 4.
3. Upgrades sold as projects
If new versions arrive as separate upgrade projects, the five-year cost includes at least one project that the first-year quote never mentions. If they arrive inside the subscription, it doesn't.
4. Estimates that become actuals
An estimate is low by design, because it is written before anyone has seen your data. The difference between an estimate and the real figure shows up after signing, in the lines that were least defined.
5. Staff time a weaker system consumes
This divergence is the hardest to put on a quote and often the easiest to see afterward, in what staff stop doing once a system handles the work.
A northeast local that moved its member communications, surveys, and ballots from postal mail to email and SMS in eMembership redeployed the two full-time employees who had run its mailroom to other work. The redeployment followed from retiring the postal channel as a whole, which the software made possible.
ILWU Local 13 reported a 40% drop in inbound member calls within twelve months of launching its member portal and member mobile app. The portal and app were one part of a wider change at the local, which also retired its spreadsheets and moved employer remittance files to direct upload, so the drop is best read as the result of that whole change. Moving remittance files to direct upload also ended the monthly temporary staff the local had used to key them in by hand.
Neither result appears on a software quote. Both show up in the fifth bucket of the worksheet, as staff hours a local either keeps spending or gets back.
The first-year number is mostly one-time costs. The five-year number is mostly the pricing model.
What most unions get wrong about union software cost
The most common mistake is comparing first-year totals. A first-year figure is dominated by implementation, which happens once. The pricing model, which happens every year, barely shows in it. Two quotes can sit close together in Year 1 and far apart by Year 5.
The second mistake is pricing the local as it is today. Locals buy software in the middle of organizing drives, contract campaigns, and staff changes. The membership count and the number of people who need a login on the day of signing are the least useful numbers for a five-year decision.
Price the local you plan to be in Year 3, not the one you are on the day you sign.
The third mistake is accepting "included" without the list behind it. Two vendors can both say support is included and mean an unlimited helpdesk in one case and a small annual allowance in the other. The word only means something once it has been written out line by line.
The fourth mistake is leaving staff time off the sheet because no one sends an invoice for it. Discovery sessions, data cleanup, testing, and months of running two systems are paid for in the hours of people who already have full jobs. A local that counts those hours honestly will sometimes find that a slower, cheaper project costs more than a faster, pricier one.
How eMembership prices, and who it fits
This section is about our own platform. Everything above applies whichever vendor a union chooses.
eMembership is priced as a flat annual subscription plus a one-time implementation. There are no per-member fees and no per-seat fees, and staff seats are unlimited, so the subscription doesn't rise as membership grows or as more stewards and staff log in. The platform has 18 configurable modules. A core set gets a local started, and each added module raises both the implementation and the annual subscription. The member portal and the Member Mobile App are add-ons, fully integrated rather than third-party products. Our union software pricing page sets out every cost driver.
How a local gets its number
The path has three steps. An intro call confirms whether eMembership fits the local at all. Then come one or more full product demonstrations, in which several members of our team walk the local's officers and staff through the modules they would use, built around the problems raised on the intro call. Then comes Discovery, a separate, paid project of about four weeks and four to six interactive sessions. Discovery maps how the local runs today and produces a written scope, a fixed implementation cost, and a milestone schedule. It creates no obligation to continue, and the local keeps the deliverables.
The value of Discovery is that it removes risk. The local processes are documented before anything is configured, and the price is fixed before the local commits, so nothing gets discovered after signing. The implementation fee covers data migration, configuration, integration setup, and staff training. Implementation then runs on the milestone schedule fixed in the Discovery Package.
How it fills in the worksheet
The subscription covers a local's configured modules, infrastructure, security, support, and platform releases. Each release is staged to the local's test environment with a 30-day approval window before it goes live, and a brand-new module is quoted separately. Each subscription includes up to 48 hours a year of operational support, covering questions, additional training, data analysis, and data updates, and up to eight hours of training before go-live; later training draws on the support hours, and more hours can be added. The help desk runs 9 AM to 6 PM ET, Monday through Friday, with severity-based response targets in the contract and service level credits when they are missed. Every client has a dedicated Project Manager and Account Manager. The full terms are on our service and subscription page.
eMembership runs in Winmill's own data center, inside a SOC 1 (SSAE 18) and SOC 2 audited, ISO 27001 certified facility. Server hardware is refreshed every three to four years at no charge, all operating system, framework, and database patching is handled, and backups run nightly, encrypted, to an offsite vault. For online dues, each local connects its own payment processor. Our integrations page lists PayPal, Stripe, Authorize.net, Converge, Braintree, and EPN. Your local keeps its own processor rates and its relationship with the processor. Each implementation includes 20 GB of document storage, which very few clients outgrow.
Outside the subscription, quoted individually when a local asks: custom development, additional modules, custom reports, extra support or training hours, and documentation of a local's own business processes. Full export of the local's data is available at any time.
Who it fits, and who it may not
eMembership is a real investment, and it isn't the right fit for every local's budget. The flat fee scales down through module count, but it has a floor, because every subscription carries the same infrastructure, security, support, and releases. A local that wants to start smaller can phase modules in over time, beginning with what it needs most. Group terms can be discussed when several locals, or the locals of an international, evaluate together.
The model is built for locals whose operations have outgrown simpler tools: dues across many employers, grievances with deadlines, dispatch, member self-service. eMembership serves 55+ labor union clients, from locals under 1,000 members to a statewide union of more than 247,000, and six clients each represent 20,000 or more members. If a local runs the worksheet and finds it needs less platform than the floor buys, that's a useful result too, and we'd rather it learned that early. If the numbers do fit, our pricing overview explains what shapes a local's quote.
Frequently asked questions
How much does union management software cost?
Why don't union software vendors publish their prices?
Is per-member or per-user pricing better for a local?
What costs are usually left out of a union software quote?
Is data migration included in a union software quote?
How long does union software implementation take?
Is eMembership affordable for a small local?
Comparing union software quotes right now?
Run them through the Five-Year TCO Worksheet first. Then, if you'd like to see how ours fills it in, book a short intro call. It's a fit check: we'll walk through how your local runs today and tell you plainly whether eMembership is likely to fit before anyone talks about demos or Discovery.
Book an Intro Call