5 Questions Every NGO Should Ask Before Choosing a Web Partner (And How We'd Answer Them)

There's a post doing the rounds on LinkedIn right now — five questions to ask before hiring a Webflow agency. It's sharp. The questions cut through portfolios and case studies and get to something more useful: does this partner build websites, or do they build systems?

The questions weren't written for NGOs specifically, but they should have been. Because when you're a nonprofit running a site that supports fundraising, programme visibility, and stakeholder trust across multiple countries, the difference between a website and a system isn't academic. It's the difference between a platform your team can run and a pretty thing you can't touch without calling someone.

Here are the five questions — and exactly how we'd answer them.

1. "Who updates the site six months after launch — your team, or do we come back to you for every change?"

Your team. Full stop.

If a consultant hesitates here, that tells you everything. It means the site wasn't built to be handed over. It means the CMS is either missing or decorative. It means every time your Communications Director needs to publish a campaign page or your Fundraising team wants to update a donation appeal, they're writing an email and waiting three days for a reply.

We build every site so that your team owns the day-to-day. Pages, blog posts, team bios, event listings, resource libraries — all managed through structured CMS collections with guardrails that keep the design intact. Your content editors don't need to understand code. They need a system that respects their time.

That said, we don't disappear after launch either. Our Monthly Partnership model means we stay on as your technical partner — handling platform updates, performance checks, and the bigger structural changes that genuinely need a specialist. But the routine? That's yours from day one.

2. "Show me a project where the client added 30+ pages after launch — without your team's involvement."

This is the question most vendors can't answer, because most vendors build pages, not infrastructure.

When we build an NGO site, we're thinking about what happens in month eight when the new programme launches, or in month fourteen when the regional office wants their own section. The CMS architecture — collections, templates, dynamic filtering — is designed around your team's real publishing patterns, not a launch-day sitemap that becomes obsolete.

A good test: ask yourself whether your current site could absorb a new thematic area, complete with its own landing page, filtered resource library, and news feed, without a developer touching it. If the answer is no, you don't have a system. You have a brochure.

3. "What's your standard for Core Web Vitals on launch, and what happens if you don't hit it?"

If they don't have a number, they don't measure it.

Our standard is green across the board on Google's PageSpeed Insights — for both mobile and desktop. That means Largest Contentful Paint under 2.5 seconds, Cumulative Layout Shift under 0.1, and Interaction to Next Paint under 200ms.

Why does this matter for NGOs specifically? Because your audiences are global. A programme officer in Nairobi, a donor in Geneva, a journalist in New York — they're all hitting your site on different devices and different connections. A 4-second load time doesn't just feel slow. It quietly erodes trust, tanks your search rankings, and costs you the engagement you worked so hard to earn.

Performance isn't a nice-to-have. It's infrastructure.

4. "If we change our positioning in 18 months, is that a redesign or a restructure? What's the cost difference?"

This is the question that separates vendors who think in projects from partners who think in systems.

The honest answer is: it depends entirely on how the foundation was built. If your site was constructed around a defined content model, with a modular component library and a CMS that separates structure from presentation, then a positioning shift is a restructure — new messaging, updated visuals, maybe some new page templates. Weeks, not months. A fraction of the original cost.

If, on the other hand, the site was built as a collection of bespoke pages with hard-coded content and layout decisions baked into every section, then yes — you're looking at a redesign. Possibly from scratch.

This is exactly why we start every engagement with a Blueprint Audit. Before any build begins, we map your current architecture, your content model, your integrations, and your team's capacity. The whole point is to make sure the foundation supports the next iteration, not just the current one.

A vendor that gives you a flat quote without asking these questions is telling you they'll build whatever you describe today. They're not thinking about what you'll need in 18 months. You should be worried about that.

5. "What do you delete from a typical website that other vendors leave in?"

Strong partners have opinions. Weak ones say "we build what you ask for."

Here's what we consistently remove or argue against on NGO sites:

Auto-playing carousels. Nobody reads slide three. They reduce engagement, hurt performance, and create a maintenance burden. Replace them with a single, intentional hero message.

Stock photography masquerading as authenticity. If you work with communities, show your actual work. A polished stock image of smiling people in a field actively undermines your credibility with savvy donors and partners.

Mega-navigation with 40 links. If your visitor needs a map to navigate your menu, your information architecture has a problem that more links won't solve. We consolidate ruthlessly.

"Innovation" pages with no substance. If you can't point to a specific programme, publication, or outcome, the page is filler. Cut it.

Parallax effects and animation for the sake of it. Motion should guide attention, not perform. If your scroll animations are the most memorable thing about your site, your content has a problem.

These aren't style preferences. They're decisions rooted in what actually drives engagement, trust, and action on NGO websites — tested across the organisations we've worked with.

The real question behind all five

You're not buying a website. You're buying the system that will run your digital communications for the next two to three years.

Your partner's answers to these five questions tell you whether they understand that. Whether they've built for organisations that evolve, or just organisations that launch.

If you're not sure where your current site stands — whether it's infrastructure or just a deliverable — that's exactly what our Blueprint Audit is for. It's a structured diagnostic that maps where you are, what's working, and what needs to change before anyone opens a design tool.