Dave Hickling, Author at Bond Software

A Platform Reality Check

From the platform side.

One of the most common frustrations I hear from boards and executive teams is that their membership platform feels harder to live with each year, even after it has been upgraded or replaced.

One of the most common frustrations I hear from boards and executive teams is that their membership platform feels harder to live with each year, even after it has been upgraded or replaced.

The mistake is assuming this is a software problem.

In most cases, it isn’t.
It’s a history problem.

Over time, membership platforms tend to become a reflection of whoever happened to be in charge when key decisions were made. A membership team optimises for day-to-day operations. A marketing team pushes for campaign capability. A CFO prioritises reporting and controls. A CEO wants scale and visibility.

Each decision makes sense on its own.

So the platform adapts. Workarounds appear. Processes are bent. Customisations accumulate. Nothing breaks outright, but the system slowly takes on a shape that only makes sense to the people who were there at the time.

Then leadership changes.

This usually surfaces in a very familiar way.

A new leader asks a simple question in their first few weeks.
“Why does the system work like this?”

No one gives a bad answer. There are just a lot of answers.

Each explanation is reasonable. Each reflects a genuine need at the time. Taken together, they tell a story of decisions made under pressure, for good reasons, across different eras of the organisation.

By the end of the conversation, the conclusion feels inevitable.

The platform is the problem.

From the platform side, this pattern is depressingly familiar.

An organisation replaces its system. There is a surge of optimism. New platform, new energy, a sense of momentum. For a period, things genuinely improve. The interface feels cleaner. Processes feel lighter. The decision feels justified.

Then the same pressures reappear.

New tools are added to cover gaps. Experience fragments again. Ownership becomes unclear. Reporting starts to require explanation rather than confidence. Complexity creeps back in under a different name.

From the outside, it looks like churn.
From the inside, it feels like déjà vu.

What is actually happening is not failure. It is continuity.

The organisation hasn’t changed its operating model. It has changed its supplier.
That distinction matters more than most technology reviews are willing to admit.

This is the moment where many organisations recognise the pattern, even if they don’t name it.

Different leaders, different priorities, different pressures, all reshaping the same system in different ways. Each transition feels justified. Each change feels necessary.

Most organisations don’t have a platform problem.
They have a repetition problem.

Not because they failed to think long term, but because they were solving for immediate stability. The system worked. The pressure eased. Everyone moved on.

Until it didn’t.

The real cost is not the licence fee or the implementation project.

It is the organisational reset that follows. Months spent relearning. Internal trust quietly eroded. Teams fatigued by another change that was meant to fix things but never quite does.

At some point, replacing the system feels like progress. In reality, it often just resets the same cycle.

It’s important to say this clearly. This pattern isn’t something we’re pointing at from a distance. We were part of it. We built within the same constraints, responded to the same pressures, and supported organisations trying to make imperfect systems work in a changing world.

The difference is that we chose not to normalise it.

The organisations that break this cycle don’t start by asking which system to buy next. They start by asking a harder question.

Which decisions about our platform should remain stable, regardless of who is in the room at the time.

That shift matters. Because once a platform has a clear governing role, something changes. Decisions stop being reactive. The system stops being reshaped to suit each new set of priorities. Technology becomes a source of continuity, not a casualty of change.

This was the real lesson for us. Not that organisations were choosing the wrong platforms, but that the industry had normalised a cycle that no amount of feature upgrades could fix.

Breaking that cycle requires a different kind of platform. One designed to survive change, not just support the present moment.

Recognising that distinction is usually the point at which progress finally begins.

See you next week. The Platform Realist.

This article is part of The Platform Reset series, examining why membership platforms fail to deliver continuity, and what it takes to break the cycle.

The End of the AMS Era

For more than two decades, the Association Management System sat at the centre of most membership organisations.

It stored records. It processed renewals. It handled compliance. It supported administration well enough that few organisations questioned the model itself. The AMS became infrastructure. Stable, familiar, and largely invisible.

That era is now ending.

Not because these systems stopped working, but because the conditions they were designed for no longer exist.

A system built for administration, not experience

The AMS emerged in a period where membership was stable, digital expectations were low, and communication was largely one-directional. Organisations spoke. Members received. The database existed to support internal workflows, not to shape member experience.

For a long time, this was sufficient.

Today, it is a structural constraint.

Members now compare their professional organisations to the digital products they use every day. Not to other associations. Not to what feels reasonable for a non-profit. To platforms that are trusted, intuitive, and responsive.

Most AMS platforms were never designed for that comparison. They were designed to optimise internal efficiency, not external relevance.

The drift from system to stack

As expectations rose, organisations responded pragmatically.

They added a community platform. A marketing tool. A learning system. Analytics software. Identity and access spread across multiple vendors. Each addition solved a specific problem. None addressed the whole.

Over time, the organisation stopped running a system and started managing a stack.

At first, this looked like progress. Capability increased. Functionality expanded. Choice multiplied. But something else happened quietly in parallel.

Experience fragmented. Data became harder to govern. Reporting required reconciliation instead of insight. Responsibility for the member relationship became distributed, and eventually unclear.

This is where many organisations misdiagnose the issue.

They assume they need better tools.

What they actually need is a governing model.

Integration is not the problem. Absence of ownership is.

The failure of the AMS era is often framed as a failure of integration. Too many systems. Too many connectors. Too much technical complexity.

That diagnosis is incomplete.

Integration is not the problem. Integration without ownership is.

Modern organisations will always rely on specialist systems. Financial truth belongs in financial systems. Campaign delivery belongs in campaign tools. Advanced analytics belongs where it can be done properly.

The problem arises when no platform is responsible for governing how these systems relate to one another. When identity is duplicated. When permissions are inconsistent. When no single layer owns experience, data flow, and accountability end to end.

This is not a tooling issue. It is an architectural one.

When technology decisions become governance decisions

Once member data and communication are spread across multiple platforms, the questions change.

Where does the authoritative record live.
Who governs consent and permissions.
Which system owns communication history.
How is accountability enforced when something fails.

These are no longer IT questions. They are governance questions.

Boards feel this tension instinctively. Executives feel it when reporting becomes harder instead of clearer. Members experience it as friction, inconsistency, and declining trust, even if they cannot articulate why.

The AMS was never designed to operate in this environment. It assumed centrality. The modern stack is decentralised by default.

That mismatch cannot be solved by adding another tool.

The illusion of modernisation

Many organisations believe they have modernised because they replaced one AMS with another.

The interface is cleaner. The vendor language sounds contemporary. There may be references to automation or artificial intelligence. But the underlying model remains unchanged.

A monolithic system designed to manage records, surrounded by an expanding ring of external tools required to make it usable in practice.

This is not transformation. It is continuity under a new name.

The outcomes are predictable. Costs rise. Complexity increases. Reliance on specialist knowledge deepens. Strategic flexibility narrows.

The organisation invests more and understands less.

What actually ends with the AMS era

The end of the AMS era does not mean administration disappears. Records still matter. Compliance still matters. Financial systems still matter.

What ends is the assumption that a single, inward-facing system can sit at the centre of a modern membership organisation and remain fit for purpose.

What ends is the belief that experience can be bolted on after the fact.

What ends is the idea that adding tools is the same as becoming more capable.

The platform shift

The organisations that will remain relevant over the next decade are already making a different set of decisions.

They are moving away from system-centric thinking and towards platform-centric operating models.

Not platforms as a marketing label, but platforms as a governing layer.

A clear identity framework.
A trusted environment for communication.
Community treated as core infrastructure, not a feature.
Learning and value delivery embedded into the member journey.
Data governance designed in from the outset.
Integration treated as a principle, not a patch.

This is not about eliminating third-party systems. It is about restoring coherence.

A reset, not an upgrade

The most important thing to understand is that this shift is not incremental.

You cannot upgrade your way out of the AMS era. You have to reset how you think about the role technology plays in your organisation.

That is uncomfortable, particularly for organisations that have invested heavily in their existing stack. But it is also clarifying.

Because once you stop trying to stretch an ageing model beyond its limits, better decisions become possible.

This article is the first in The Platform Reset series, examining why membership systems are changing, what replaces them, and how organisations can move forward without compounding complexity or risk.

The AMS era had its place.

That place is behind us.

This article is part of The Platform Reset, a series examining how membership organisations are rethinking technology, governance, and member experience in 2026 and beyond.

The next article explores the hidden cost of “good enough” member experience, and why it is quietly undermining renewal, trust, and organisational clarity.