Authored on
Title

Choosing the Right Partner for Your Website

Subheader

The difference between a vendor and a partner shows up long before the contract is signed

Featured Image
adult man and woman gathered at a standing desk looking at a laptop together
Lead-in

I’ve responded to (more than) my share of RFPs, and I’ve inherited a lot of websites from firms that won the last one. The pattern I keep seeing has less to do with which firm gets selected than with what the client thought they were hiring in the first place.

Most public sector selections start with the wrong question. The question isn't “who’s the best web firm we can afford?” It’s “are we hiring a vendor, or are we hiring a partner?” The answer changes what you ask for, how you evaluate the responses, and what you should pay attention to in the first conversations.

A vendor sells you a website. You write a spec, they build to it, you sign off, they move on. The relationship has a clear beginning, a clear end, and a clear deliverable. A partner takes responsibility for whether the site keeps working, for the people you serve, over time. You define goals together, you make decisions together, and when something breaks two years in there's someone to call who remembers why you built it the way you did.

Both models exist in the market, and both call themselves the same things in their marketing. The job of your selection process is to figure out which one is actually sitting across the table from you.

The five factors below are how I’d do that. Each one is a way of testing whether a firm is set up to be a partner or set up to be a vendor — and whether they’re being honest with you about which one they are.

Sections
1. Real public sector experience

The most common mistake I see is choosing based on the size of a firm’s portfolio rather than the relevance of it.

Large firms with name recognition often win public sector contracts despite having little real focus on this kind of work. The day-to-day gets outsourced to developers unfamiliar with the constraints — Section 508, FERPA, state-specific procurement and security protocols, public records requirements, the whole shape of it. State agencies and universities end up with limited, low-priority products that still carry a premium price tag.

A partner who works in this space regularly doesn’t have to be told what the constraints are. They know that a modern design with visual complexity might look great in a portfolio, but the site has to load quickly, work for everyone, and be easy to understand for the broadest possible audience. That’s a different design instinct than what most commercial firms bring.

2. Security, accessibility as the starting point

Accessibility and security aren’t features. They’re legal obligations and basic professional responsibility. I’ve watched too many organizations scramble to retrofit accessibility after launch because the firm they hired treated WCAG conformance as something to address at the end.

A partner brings these up on day one. They have people on staff who know Section 508 and WCAG, can speak to privacy requirements like FERPA and HIPAA, and can explain how they align with NIST security guidelines and state-specific protocols. If the conversation gets uncomfortable around penetration testing, vulnerability assessments, or how they handle a disclosed CVE, that’s a red flag.

3. Proof, not promises

When you’re evaluating a proposal, you want to see evidence, not capabilities decks. The question isn’t whether they say their sites are accessible — it’s whether they can show you WCAG conformance reports or accessibility testing results from real launches.

A few questions that separate the two:

  • How many public sector sites have you launched in the last three years? — Recent matters. Standards and platforms shift.
  • Can I see an accessibility testing report from a recent project? — Real partners have these ready. 
  • What’s your track record meeting tight compliance deadlines? — Public sector work runs on fiscal years, legislative sessions, and audit cycles.
  • Walk me through a project where something went wrong. — How a firm handles trouble tells you more than how they handle success.

A vendor will talk a lot about what they can do. A partner shows you what they’ve already done.

digital tablet on a white surface showing the cover of the report on the screen
Dos and Don’ts for Creating Effective RFPs

Learn how to create clear, effective web project RFPs that attract qualified vendors and set your website redesign up for success. 

A public sector site has to work for everyone. A partner builds for that audience by default.
4. Straight talk

This is the one most articles about vendor selection miss. Communication isn’t about being responsive or “treating communication as a core competency.” It’s about whether the people you hire will tell you when something is a bad idea.

We’ve recommended against features clients were excited about. I’ve pushed back on requests from senior leaders that wouldn’t serve the public using the site. None of that is comfortable, but it’s the actual job. A vendor will build whatever you ask for, take the check, and move on. A partner has the relationship to disagree.

When you’re in the first conversations, listen for it. Do they push back on any of your assumptions? Do they ask why? Or do they just nod and ask when they can send a proposal?

5. A long-term mindset

A website isn’t a project — it’s a platform that has to keep working through staff turnover, administration changes, budget cycles, and a steady drip of new accessibility standards and security patches.

I’ve seen organizations get burned by firms that build a site, hand over the keys, and disappear. When something breaks two years in, there’s no one to call who remembers the context. You need a partner who views this as the beginning of a relationship. They should be talking about post-launch support, maintenance agreements, and how they’ll help you adapt as technology and regulations evolve.

A partner talks about the years after launch the same way they talk about the build. Ask about their client retention. Ask which public sector clients they’ve supported for five years or more. Ask how they handle urgent issues at 4 p.m. on a Friday. The answers will tell you whether you’re hiring someone for one project or starting a working relationship.

Decide before you go to market

Most vendor selection guides end with “trust your instincts.” Mine ends with the opposite: decide what you’re hiring before you go to market, then structure the process to find it.

If you want a partner, say so. Ask the specific questions, look for the specific evidence, and pay attention to which firms speak the language of a long relationship and which ones speak the language of a transaction. By the time you’re reading proposals, you should already know which one you’re looking at.

That’s the work we do at Electric Citizen. If it sounds like the kind of partner you're looking for, I’d love to talk.

About the Author

About the author

headshot of Dan

Dan Moriarty is the co-founder, CEO and chief strategist with Electric Citizen.

Meet the Team
Related Posts

Related Posts