Anyone can say 'one platform'. Here is how to tell.
Every vendor in this market now says the same sentence: one platform, one member record. The words are free. This is how a buyer with no technical background tells the difference, in twenty minutes, in any demo, including ours.
One was built as a home. The other is three flats with the walls knocked through.
From the street the listing photos look the same. The word "renovated" does a lot of work. You discover the difference in winter, paying three power bills, in a hallway that steps down half a metre between what used to be separate buildings, where no single tradesperson will take responsibility for the wiring.
In a demo, both houses look the same.
The screens match, the logo is consistent, the data appears wherever the presenter clicks. A costume is exactly as convincing as its tailor, and this market has good tailors. The difference does not show on the day you are being sold to. It shows later.
What the demo shows
- Consistent screens, because one design was applied across several products.
- Data appearing everywhere, because the presenter knows which order to click in.
- One brand across the whole session, which tells you nothing about what is underneath.
- A prepared dataset that has never been through a renewal cycle.
What survives year two
- One record, so there is no sync to fail at 2am and nothing to reconcile in the morning.
- One release schedule, so an update to one part cannot quietly break another.
- The checkout your members pay through is the same product as the record you report from.
- One member record that means one record, not one nightly copy.
Some suites in this market are assembled on general-purpose foundations: a website front, a separate checkout, a CRM connected behind, plugins in between. These are honest tools and real businesses run on them. But general-purpose assembly wearing enterprise language is still assembly, and it carries assembly's costs: version drift, plugin risk, sync lag, and the quiet job of reconciling systems that nobody was hired to do.
Five questions. Ask them of any vendor, including us.
You do not need to be technical. You need these five, asked out loud, in the demo, with someone taking notes. Open each one for what a clear answer sounds like and what to listen for.
01Is the member website the same application as the CRM, or a separate system synchronised to it?
A clear answer sounds like
One application is named, and the member record and the public page are shown rendered by that same system, live, in the one session.
What to listen for
An answer that describes the result rather than the architecture. If you hear that it all works together, ask again: which application serves the page.
02Do members and staff sign in once, or does each part carry its own login?
A clear answer sounds like
One sign-in carries a member across the site, events, learning and payments. Staff sign in once for everything they administer.
What to listen for
A separate portal with its own login, described as a feature rather than as a second system. Ask how many passwords a member can hold.
03Was each part built in the product, or acquired and connected? Ask for the history of each component.
A clear answer sounds like
A straight account of what was built, when, and by whom, including anything acquired and what happened to it afterwards. Vendors who built one thing find this question easy.
What to listen for
History given at brand level when you asked at component level. The founding date of the company does not answer the question.
04When a member acts, does the record update live, or wait for a sync to run?
A clear answer sounds like
Immediately, or a stated interval in minutes. Then ask them to do it in front of you: make a change as a member, refresh the staff view.
What to listen for
Near real time, with no interval attached. Every sync has a number. Ask for it, and ask what happens to the record when the sync fails.
05Show one member's whole activity, joining, events, learning and payments, on one screen, without switching systems.
A clear answer sounds like
One screen, one member, the whole history, produced live from the hardest example you can give them.
What to listen for
A report prepared earlier, or a presenter moving between systems while describing it as one. Watch the address bar, not the slide.
An assembled suite can survive one of these questions with a good answer. It cannot survive all five.
What one product actually buys you.
Not an architecture preference. Four costs you stop paying.
No sync to babysit.
There is nothing to sync, so there is no overnight job, no failure to notice in the morning, and no reconciliation nobody was hired to do.
No version drift.
There are no parts on separate release schedules, so an update to one thing cannot quietly break another.
One vendor accountable.
No meeting where two suppliers explain why the problem belongs to the other one.
One home for the member.
One login, one place, and an organisation that visibly has its act together.
This page cuts both ways, deliberately.
A test you only apply to other people is marketing. Ask us the same five questions, in the demo, on the record, with the hardest version of your own data.
Nexy is one product with one member record, hosted in Australia on Microsoft Azure. We would rather prove that under scrutiny than assert it in a font.
Asked before the first call.
Is this just a way of attacking your competitors?
What if a vendor answers all five well?
Does an assembled suite ever make sense?
How do we ask these without sounding hostile?
Where is the technical version of this argument?
Bring the five questions. Bring your hardest example.
See what one product looks like against your organisation's actual requirements, or run the numbers yourself first. Both are on the table, in the open.