You are three months into an AMS selection. The shortlist has four names on it, you have sat through four demos, and you have four pricing sheets in a folder. It reads like a competitive process, which is the point of running one. Then somebody on the committee notices that two of the sales engineers used the same slide template, and the question that follows is the one nobody budgeted time for: how many companies are actually in this room?
For a large share of the association management software market, the answer is fewer than the brand names suggest. That is not a scandal and it is not a reason to walk away from any of these products. But it changes what a competitive shortlist means, and it changes which questions are worth asking in an RFP.
Who Owns What
Momentive Software is the company formerly known as Community Brands, which itself was formed by combining YourMembership, Abila and Aptify. Its own website lists the association management products it sells, and the list is longer than most selection committees realize:
- MemberClicks, YourMembership and Wild Apricot, the small-to-midsize end of the portfolio, positioned at organizations graduating from spreadsheets or running with volunteer staff.
- NetForum and Aptify, the mid-market and enterprise membership platforms, Aptify having arrived through the original Community Brands combination.
- Nimble AMS, the Salesforce-based platform, positioned at organizations that want an AMS on a mainstream CRM.
- Cobalt, acquired in May 2025, an association and certification platform built on Microsoft Dynamics 365, serving roughly 200 enterprise organizations.
- Personify, acquired in January 2026. Momentive put the combined client count at approximately 37,000 organizations, with Personify contributing more than 17,000.
Four of those are platforms this blog has reviewed as separate products. We have written individual integration guides for Nimble AMS, Aptify, MemberClicks and Personify, on the reasonable assumption that they were separate products from separate companies with separate roadmaps. Two of those three things are still true. The third is not.
Where this comes from. The ownership list above is from Momentive's own product pages and press releases and from the acquisition announcements themselves. The client counts are the company's figures, not independently verified, and they are the kind of number that gets rounded generously. What is not in dispute is which brands sit under which corporate parent, because the vendor publishes that itself.
What Is Genuinely Independent
Consolidation stories are easy to overstate, so the other half of the list matters just as much. Several platforms associations commonly evaluate are not part of this portfolio:
- iMIS, from Advanced Solutions International, which remains independently held.
- Fonteva, which sits under Togetherwork, a different consolidator, which is its own conversation.
- Impexium, now re:Members, and MatrixMaxx from Matrix Group, both operating outside the Momentive portfolio.
So the market is not a monopoly, and nobody should tell you it is. What it is, is a market where two or three names on a typical shortlist of five may answer to one board. That is a meaningfully different negotiating position from the one a selection committee usually thinks it is in.
Why This Matters for the Website Specifically
For most of what an AMS does, dues, events, certification, member records, common ownership is close to irrelevant in the short term. The place it shows up first is the integration layer, which is the part of the AMS your website actually touches.
API investment follows product strategy, and product strategy follows the portfolio. When one company owns five overlapping membership platforms, it does not fund five equally capable APIs forever. Some products get the integration roadmap and some get maintenance. Nobody announces which is which, and you generally find out by noticing that a documentation site has not changed in two years.
Your alternative-vendor leverage may be smaller than it looks. The standard response to an AMS that will not prioritize your integration request is to raise the possibility of moving. That threat carries less weight when the obvious destination is another product owned by the same company, and the account team can see that as clearly as you can.
Consolidation cuts the other way too, and it is fair to say so. A larger parent can fund a serious platform investment that a smaller independent could not, and a product being acquired is often the reason its API finally gets modernized. The honest position is that common ownership is a variable to price in, not a verdict.
The Signals That Tell You Where a Product Sits
You cannot get a straight answer about internal product strategy, and you should not expect one. What you can do is read the public artifacts, which are harder to manage than a sales conversation. Three of them are worth checking before you sign anything:
The changelog and the developer documentation. A platform receiving active investment ships visible API changes and documents them. One that has become a maintenance product tends to have a docs site that still looks the way it looked when it was acquired.
Where the vendor sends its own conference attention. Vendors put their launch announcements against the products they intend to keep selling. If the annual-meeting keynote is about three products in a portfolio of six, that is a roadmap statement even though nobody framed it as one.
Whether migration offers exist between the vendor's own products. A published path from one of a company's platforms to another is generally good news for the destination and a signal about the origin. It is also the single most useful thing to ask about during a renewal, because the answer tells you which side of that line the account team thinks you are on.
What to Actually Ask
None of this changes the shape of a selection process. It adds four questions, all of which a straight vendor will answer directly and an evasive one will not:
- Who owns this product, and when did that last change? Ask it plainly and write the answer down. It is public information and there is no reason for a sales team to be cagey about it.
- Which other products in the portfolio overlap with this one? Where two products in the same family serve the same segment, one of them is eventually the strategic one.
- What has shipped in the public API in the last eighteen months? Roadmap slides are aspirational; a changelog is evidence. If there is no public changelog, that is itself the answer.
- What does getting our own data out look like? Not whether it is possible, in what format, through which endpoint, at what frequency, and whether it includes the custom fields. This question is worth asking of every vendor regardless of who owns them.
Track the Owner, Not the Brand
The practical change is small. Keep a note of which corporate parent each product on your shortlist reports to, and revisit it when you renew rather than only when you buy. Brands in this market change hands faster than associations change AMS platforms, which means the company you signed with is frequently not the company you are renewing with, and nothing in the renewal paperwork will point that out.
This is also why product-by-product comparisons age badly. A review of two platforms written when they were competitors describes a different situation from the one you are in once they share a roadmap. We are keeping our own integration guides on those four products because the technical detail in them is still accurate, but the competitive framing in anything written before January 2026 needs this footnote attached to it.
Bring Us Your Shortlist
Send us the names on your AMS shortlist and what you need the website to do with member data. We will tell you which of them share a corporate parent, what each one's public API actually supports against your requirements, and where the integration work is genuinely different between them rather than just differently marketed. If two of your finalists turn out to be the same company, you should know that before the pricing conversation rather than after it.