In the two decades we've been serving associations, the model for buying technology hasn't changed.
A big upfront project. Tens of thousands even up to six-figure invoices. A finished product handed over with a warranty period. Then years of awkward conversations every time you need a change — each one a separate quote, a separate timeline, a separate negotiation about whether it's covered or extra.
This isn't anyone's fault. It's just how the industry has worked. Agencies bill projects because projects are how agencies make money. Vendors charge implementation fees because implementation is expensive. The model fits the suppliers. It just doesn't fit the buyers.
For associations especially, this model is broken in ways that matter.
Why project-based buying punishes associations
Most associations can't actually afford a £100k upfront capital project. So they don't do them. They limp along on the website they built in 2017, the CRM they bought in 2014, and the email platform somebody set up before the current Marketing Director joined.
When something finally breaks badly enough to force action, they go through a procurement process that takes most of a year, sign off on the smallest viable rebuild, and then pray nothing needs to change for the next five years. Because every change costs money, and money is the thing they don't have.
This is why association digital infrastructure ages so badly. It's not neglect. It's that the buying model makes ongoing improvement financially impossible, so things don't improve until they break.
The buying model is the problem. Not the technology, not the suppliers, not the budgets. The shape of the transaction.
A different shape
We built our service around a different question. Not "how much does this project cost?" but "what would it take to give an association a permanent technology partner for the price they can actually afford?"
The answer was a subscription. One monthly payment, no upfront cost, no implementation fee, no separate quotes for changes. Hosting included. Disaster recovery included. A 99.9% uptime SLA included. Ongoing development capacity included — not as a bolt-on, but as the core of the service.
The number that matters: this works out to roughly the cost of a single minimum-wage employee, spread across the year.
For that, an association gets what would traditionally have been a £100k+ technology programme, plus the team to keep building on it indefinitely. Not a fixed scope. Not a defined number of hours. The ongoing capacity to keep improving the platform as your needs change.
This isn't a discount on the old model. It's a totally different model.
Why "unlimited capacity" isn't a marketing claim
Most agencies can't offer unlimited ongoing capacity, because their economics don't allow it. Every hour their team spends on your work is an hour they're not billing someone else. Capacity is the constraint, so capacity has to be metered and charged.
Our economics are different, for the reasons we covered in the previous pieces. AI collapses the time required for most tasks. The platform we built handles in minutes what generic platforms take weeks to do. A dedicated team works on your account, and the same patterns and integrations get reused across every association we serve.
What used to take six developer-weeks now takes an afternoon. So the same team can serve more associations, and each association gets more capacity, and the unit economics work without anyone cutting corners.
"Unlimited" doesn't mean infinite — there are sensible limits, and we're transparent about them. It means we don't bill you per change request. It means you stop asking "can we afford to make this change?" and start asking "should we?" It means the conversation between you and your technology partner becomes about strategy, not invoices.
That shift is the whole point. Most associations have a technology supplier. We're trying to be a technology partner — the difference being that a partner's incentives are aligned with yours over time, not with the next project quote.
What this changes
When the buying model changes, what associations can do changes with it.
You can fix the broken thing in your member journey this month, instead of putting it in next year's budget cycle or waiting 2 months for the next Board of Trustee meeting to get approval on the budget. You can launch the new membership tier in a fortnight, instead of waiting until you've saved up for the CRM customisation. You can run the experiment, see if it works, and either keep it or kill it — without the experiment itself becoming a £10k commitment.
You can stop treating your digital infrastructure as a thing you replace every five years and start treating it as something that gets better every quarter.
That's what's actually on offer here. Not a cheaper website. Not an AI gimmick. A different relationship with the technology your association runs on — one where improvement is the default state, not the exception.
For most associations, that's a bigger change than any single feature could ever be.
If you've read all four pieces and want to talk about what this could look like for your association, book a conversation. No deck, no discovery fee — just a conversation about whether the model fits.