How many software systems does the average association actually run?
The complete list is rarely sitting with one person inside the building. Part of it is public, takes about a second per organization to read, and can give you a starting count in about a minute. The method is incomplete, but it can still tell you more than asking someone to work from memory. Here is what it shows and what it misses.
Why can nobody inside an association answer this?
Because keeping the count is nobody's job. Systems are added one at a time over many years, often by different departments solving an immediate problem. No role in a typical association maintains the running list. The total is not added up on one budget line, and no one person carries all of it in their head.
The events team needed something the membership database could not do. Marketing needed to send a newsletter without filing a ticket first. Someone had a conference in six weeks and found a company that could go live in three. Each decision made sense when it was made. The systems simply never got added up.
Ask a chief executive how many things the organization runs and you are asking that person to inventory the whole organization from memory, out loud, while you wait.
Nobody does that well.
What happens when you ask an executive to count?
During a research interview last year, an executive at a mid-sized professional society estimated that her organization used somewhere between five and ten tools. She had already named more than ten in the same conversation. Before the hour ended, she named four more. The full count was fifteen, roughly twice the top of her estimate.
"every time you bring that question, I'm like, oh, I have another thing that I didn't tell you."
She was a capable operator describing an organization she helps run, and she was making a real effort to be accurate. The problem was the question. It asked her for a number that was not written down anywhere, including in the heads of the people closest to the work. She knew what her own people logged into. Nobody held the total.
One case cannot establish a rate, and we are not treating it as one. It does show that an executive's estimate and the final count can differ by a factor of two, even when the person answering knows the organization well and is trying to get it right.
We saw the same gap when money came up. Most of the executives in these conversations could not say what their organizations spent on software. One senior leader at a large trade association started somewhere between millions and tens of millions, then settled on a figure above $15 million a year while hedging twice. A one-minute check of the organization's public Form 990 did not support that estimate. Another executive went through an entire hour without naming a dollar figure for any tool.
There were exceptions. One leader produced three exact figures in eleven seconds. But not knowing was more common, and it was not a failure on the executive's part. The number was simply nobody's job to keep.
Can you count an association's systems from the outside?
You can count part of them, and that partial count may already be more dependable than a guess. Every organization that sends email publishes an SPF record in DNS. That record lists the services allowed to send email using the organization's name. It is public, free to read, and takes about a second to check. We read it for 1,128 association and association-adjacent domains.
If an association has allowed a marketing platform, an email service, a survey tool, and an event platform to send from its domain, all four appear in public records. That remains true even if nobody inside remembers who signed up for them. Here is what we found:
- 1,104 of the 1,128 organizations, or 97.9 percent, publish an SPF record.
- The median organization authorizes 3 services. The mean is 3.26. The highest count we observed is 13.
- After removing the organization's own mail provider and spam filter, the median organization still authorizes 2 outside services to send email in its name. About one-third authorize 3 or more, and 9 percent authorize 5 or more.
- The most common services in the set were SendGrid at 14.8 percent of organizations, HubSpot at 12.1 percent, Amazon SES at 11.1 percent, Salesforce at 10.3 percent, and Mailchimp at 8.7 percent.
Three caveats matter here.
First, these are organizations we had a reason to examine, not a random sample of American associations. Every share should be read as "of the organizations we looked at."
Second, this is a low floor. SPF sees only services that send email. A finance system does not send email. A membership database or learning platform usually does not either. The professional society that ultimately counted fifteen systems would show up here with only two or three.
Third, about 9 percent of the organizations route their SPF through a hosted service that hides the underlying list behind one entry. Everything inside that service is invisible to us, pulling the observed average down rather than up.
Check your own count in about a minute
You do not need IT for this. Go to mxtoolbox.com/spf.aspx, which is free and does not require an account. Enter your association's domain, the part after the @ in staff email addresses. Each "include" entry is a service your organization has allowed to send email in its name.
Set aside Microsoft 365 or Google Workspace and your spam filter. Count what remains. That is the public floor of your list. If the number is already higher than you expected, you have reproduced our finding on your own organization. The full count will be higher.
What does the count miss even when somebody does count?
It misses the people. At one large national union, keeping one in-house connection running so two purchased products can talk to each other takes about four people. A former employee now invoices as a full-time consultant. One or two additional consultants work beside him, and an internal database specialist does nothing else. None of those people appears on a software line.
The organization does not view this as a technology problem. When we asked about it directly, the executive rejected that framing three times. His answer was that this is simply how an organization of that size operates.
He is not wrong. Those four people sit on payroll and outside-services lines, where no one counts them as part of the cost of keeping two systems talking to each other. A total built only from software invoices leaves them out. It does the same anywhere someone is paid to move information from one place to another by hand.
Does the public financial record confirm any of it?
Not as often as you might expect. Every tax-exempt organization's Form 990 includes a line for information technology in its expense table, Part IX line 14. We reviewed 694 organizations. Of those, 81.8 percent reported an amount, with a median around $185,000 a year. Another 16 percent left the line blank, and blank does not mean zero.
The detail comes from 705 filings pulled and 694 that were readable:
- 568 of the 694 filings, or 81.8 percent, report an amount above zero on line 14. The median among those is about $185,000 a year. Reported amounts range from $170 to $15.6 million.
- 15 filings, or 2.2 percent, report an explicit zero.
- 111 filings, or 16.0 percent, leave the line blank.
The filing usually provides a dollar figure. It does not explain what sits behind that number. Comparing the SPF and tax records produces no clear pattern. Among organizations with no outside sending service in DNS, 77.5 percent report technology on its own line. The share rises to 92.9 percent among those with three or four services, then falls to 80.9 percent among those with five or more.
Whether the filing shows software spending on its own line appears to depend more on the accountant than on how many systems the organization runs.
The contractor schedule gives a narrower view. Part VII Section B names the five highest-paid outside contractors receiving more than $100,000. Across the 694 filings, only 25 organizations listed a recognizable technology company among those five. When one appeared, it was usually a membership database company or a related service, with payments ranging from roughly $105,000 to $2.9 million.
That tells us how often a technology company is paid enough to outrank the building lease, insurance broker, lobbying firm, or audiovisual company. It does not tell us how many organizations pay a technology company six figures.
A blank line 14 means the filing does not put technology on its own line. It does not mean the organization spends nothing. The line is optional in practice, and software gets booked under office expense, professional fees, a management contract, or a program line depending on the accountant. Reading a blank line as zero creates the same problem as reading an executive's guess as a count.
So what is the actual number?
We are working toward one with a method readers can inspect. The Association Technology Stack Report will reconstruct what a set of mid-sized associations actually runs using only public records. Every number will be tied to a source the reader can open. There will be no interviews, surveys, or guesses in the count.
The source list includes DNS and subdomain records, Form 990 contractor schedules, job postings that name the systems an organization hires someone to run, published customer stories, and the organizations' own websites.
What the method finds for one organization
Here is what the method finds for one organization. The National Pest Management Association is a trade association in Fairfax, Virginia, with about $11 million in revenue. Public records alone identify 16 systems and services, from its membership database to the company hosting its DNS.
Its Form 990 contractor schedule shows recurring database-support payments to its membership database company: $234,175 in fiscal 2024, $199,822 the year before, and about $216,000 the year before that. Its SPF record also gives four services permission to send email in the association's name: Microsoft 365, HubSpot, Higher Logic, and SendGrid.
Every figure above comes from a free public source. No one inside the organization had to answer a survey or grant permission. If the pattern from our interviews holds, an executive asked to name the full list from memory would identify about half of it.
This research comes from Ksense Technology Group. We help associations get their systems in order and reduce the places where staff have to move information by hand. If you would rather see this reconstruction run on your organization than wait for the report, start at https://ksensetech.com/associations.
What should you do about your own count in the meantime?
Do not begin by asking someone how many systems the organization has. Start with the SPF check to establish a public floor. Then count the handoffs, the places where a person moves information between systems by hand. Staff can usually name those places exactly, even when nobody can produce the full system list.
Set aside 45 minutes with the two or three people who touch a member record most often. They are usually in membership, events, or finance.
Choose one person who joined during the past year and trace that record out loud from the day of joining through the first renewal. Use the noun your organization uses, whether that is member, operator, local, patient, or something else.
Mark every point where someone retyped information, exported and uploaded a file, or copied something from one screen into another.
You will leave with the places where a person is doing work the systems should handle, along with the names of the people doing it. That count is more useful than a list of logos. It shows where time is going, and the people moving the information can tell you exactly how much time it takes.
Frequently asked questions
How many software systems does the average association use?
There is no defensible published average. When someone quotes one, ask how it was produced. Public records can establish a floor. Across the 1,128 association domains we reviewed, the median organization allowed three services to send email in its name. The true system count is higher because anything that does not send email is invisible to this method. In the one interview where we established a complete count, an executive estimated five to ten and the final number was fifteen.
Why do associations underestimate what they are running?
Because nobody owns the count. Departments adopt systems one at a time over many years, usually to solve an immediate problem. A typical association has no role responsible for keeping the full list. In one documented case, the executive best positioned to know estimated five to ten. The organization actually ran fifteen.
How can you audit an association's technology stack from public records?
Begin with the SPF record in DNS, which lists services allowed to send email using the organization's domain. Add subdomain records that point to member portals and learning platforms. Review the Form 990 Part VII contractor schedule, Part IX line 14, job postings that name the systems someone will run, and customer stories published by software companies. Each source is free.
How do I check my association's SPF record?
Go to a free SPF lookup tool such as mxtoolbox.com/spf.aspx and enter the part of your staff email addresses after the @. Each "include" entry identifies a service allowed to send email in your organization's name. Remove your mail provider and spam filter. What remains is the public floor of your system count. The check takes about a minute and requires no technical background.
Does a blank technology line on a Form 990 mean the organization spends nothing on technology?
No. About one in six filings we reviewed left Part IX line 14 blank. The expense may be recorded somewhere else in the return. A blank means only that the filing does not report technology on a separate line. Even a completed line is a floor because it leaves out the people paid to keep systems talking to each other.
We publish the research as it is completed. The Association Technology Stack Report is next.
Want a Clearer View of Your Association's Technology Stack?
Ksense helps associations identify the systems they are running, the handoffs staff are managing by hand, and the integration gaps creating unnecessary work.
Talk to Us About Association Technology