We Made the Final Round. We Didn't Win. Here's Everything We Did Anyway

This is Article 2 in our series Why Do We Fall? - about the projects that didn't go to plan, and why we're writing about them anyway.

Let's start with the punchline: we didn't get the gig.

One of the UK's most prominent regional membership organisations ran a competitive tender last autumn to replace the creaking digital infrastructure their whole operation depended on.

We went for it. We made it through to the final stage. We presented in person to their panel. And then we didn't win.

So why are we writing about it?

Because the work we did - the thinking, the scoping, the creative approach, the technical architecture - is genuinely good. And it'd be a shame for it to just sit in a folder.

More than that: there are organisations out there with exactly the same problem that this organisation had. And they deserve to know what a properly thought-through solution to that problem looks like.

What was actually needed

Before you write a single line of code, you have to understand what the problem actually is. And this organisation's problem was pretty common for membership organisations of their size and ambition.

The existing website was built on a bespoke in-house CMS that was being retired. It was doing some things - membership sign-up, event bookings, a member hub - but doing them with friction. Staff were working around it. Members were putting up with it. And the data wasn't flowing properly between the website and the systems around it: their CRM (Microsoft Dynamics), their finance platform (Xero), their marketing platform (Dot Digital), their payment setup (Stripe and GoCardless).

The brief was clear: fix all of that. Build something that works for everyone - members, prospects, the press, sponsors, the team - and make sure it lasts.

A budget of £35,000 + VAT for year one. Go live target: May 2026. (Which, as it happens, is now.)

What we proposed

We're not a "here's a WordPress theme, that'll do" kind of agency. So we didn't propose that.

Instead, we put together a full technical architecture built on WordPress at the core, with a carefully chosen stack around it:

Elementor for page building
MemberPress for membership management and tier-based access control
The Events Calendar Pro for event management and ticketing
Crocoblock / JetEngine for dynamic directories and custom content types
DotDigital for marketing automation
Stripe for payments
Complianz for GDPR
Yoast for SEO

Everything integrated. Everything documented. Nothing bolted on and hoped for.

The architecture covered:

Multi-tier membership (individual and corporate, with sub-account management)
Self-serve member dashboards - update your own profile, manage your subscriptions, view invoices, without calling anyone
Event and training management with gated access based on membership level
A member directory with searchable, filtered listings
Landing page creation for lead generation campaigns, with GA4 event tracking and CRM integration for re-marketing
Automated email workflows through DotDigital (welcome sequences, renewal reminders, event confirmations)
Full MS 365 integration, because that's what the team runs on

We also built a simple microsite in Wix, to help bring our proposal to life - rather than just handing over a document. It was a bit of a risk, but we were told it landed well.

The bit most agencies skip

Here's what we believe, and what we tried to show in our pitch: what we're proposing / recommending is only as good as the thinking that goes into it before a single page is designed.

The discovery and scoping phase is where the real value lives. It's where you map out user journeys - not just "member clicks join button" but the full emotional arc of what it feels like to discover the organisation, understand what membership means for your business, join, attend your first event, and become genuinely engaged. It's where you do the SEO audit, interview internal stakeholders, map data flows, and make sure the thing you build is the thing that actually needs building.

We laid that out in detail in our submission: solution design and technical scope, data flows, analytics review, stakeholder interviews, user journeys, information architecture, feature maps, wireframes, testing and feedback loops.

The Fresh Meet piece

One of the things we're proudest of - and one of the things that genuinely differentiates us - is our connection to Fresh Meet CIC.

Fresh Meet is a not-for-profit we run alongside Bravand. It gives young people paid work experience on the real, commercial projects we deliver. Not simulated briefs. Not shadowing. Real client work, real responsibility, real pay at the Real Living Wage.

So when you work with Bravand, you're also creating a route into tech / creative / digital careers for young people. That's not a badge or a marketing line - it's the model. The income from projects funds the opportunities.

This is relevant to any business in any region. An agency that puts social value front and centre, by investing in the future talent pipeline, not just billing project fees.

The feedback

The prospect was gracious about it. We were told the proposal was one of a number of high-quality submissions, and that it was a particularly difficult decision. The specific feedback we got was:

"Demonstrated strong technical capability with a clear overview of the proposed tech stack. The team was enthusiastic and presented with confidence in their ability to deliver the project effectively."

That's encouraging. We know we did good work. Bids are competitive, and on this occasion someone else's work was stronger. That happens.

What we take from it: the thinking was right, the solution was right, the team was right. We're ready to do this again - for the right organisation.

Who this is actually for

If you're reading this and you run a membership organisation, a professional association, a trade body, or any kind of community-facing organisation with systems and processes that are working against you instead of for you - this article is for you.

The problems outlined above are certainly not unique to the organisation that was seeking help. We see versions of these problems everywhere:

A CMS that's difficult to update without a developer
Members who have to call to renew, upgrade, or fix their account
Events that require manual admin at every step
Systems that don't talk to each other, so data lives in four places and is accurate in none of them
A website that doesn't actively bring in new members - it just sits there

If any of that sounds familiar, we'd genuinely love to talk. And if you want to see what we've actually delivered for membership organisations, here are three projects worth a look:

"Powering Collaboration Across 100+ Organisations": reimagining the digital platform for London's Knowledge Quarter, connecting people across a hundred-plus member organisations.
"From a Fledgling Membership Site to a Global Community and Learning Platform Built to Scale": taking a Version 1 starting point and building it into a serious international platform for a global professional membership body.
"Modernising Tradition: How Bravand Helped the Catenians Attract a New Generation": brand refresh, recruitment website and a year-long social campaign for a longstanding membership body finding its footing with a new generation.

One more thing

You might not have this problem yourself. But you might know someone who does.

If you introduce Bravand (and / or Fresh Meet CIC) to an organisation that becomes a client, we'll say thank you with 10% of the first project revenue. That can be a donation to a charity or good cause, Bravand service credit, a gift card (we're partial to the Sheffield Gift Card, but there are many more towns and cities that have their own), or cash.

Good moments to make an introduction? When you hear: