Choosing a web partner is one of the higher-stakes decisions a mission-driven organization makes – not because websites are expensive, though they are, but because the consequences of the wrong choice compound long after the project ends.
These are not rare outcomes. They are the most common ones. The questions below are designed to surface them before they become your organization’s experience.
Experience with your type of organization matters more than general portfolio quality. A web partner who has built for museums, nonprofits, or cultural institutions understands the accountability structures, the stakeholder dynamics, and the institutional voice requirements that general commercial work does not prepare someone for. Ask specifically what organizations they have served in your sector and what the websites they built needed to accomplish.
Platform expertise determines what your organization inherits. A WordPress or Drupal build is only as sound as the person who built it. Ask directly which platforms they work in, what their depth of experience is with each, and whether they will document the architecture so your team – or a future partner – can work with it without starting over.
Process clarity reveals how much the partnership will cost you in staff time and attention.
A web partner who cannot explain their process clearly:
Ask for a written process overview before any agreement is signed.
Eight questions worth asking directly
Can you show me your portfolio and describe your specific role in each project? Portfolios show outcomes. The question behind the portfolio is whether this person led the thinking or executed someone else’s decisions.
What types of organizations do you typically work with? Every capable web partner has a context where they do their best work. An honest answer tells you whether your organization fits that context.
How do you handle a situation where the project scope changes after work has begun? Scope changes are inevitable. How a partner handles them reveals whether the relationship will stay functional under pressure.
What does your communication process look like from start to launch? You should know what to expect at every stage – not learn it as you go.
How do you approach security, performance, and accessibility? These are not optional considerations for institutional websites. A partner who treats them as afterthoughts is a partner who will leave you with problems you did not anticipate.
Do you provide a development link so we can review progress before launch? Any partner who presents finished work without interim review opportunities is removing your ability to course-correct when it is still inexpensive to do so.
What documentation do you deliver at the end of the project? The handoff is where most web partnerships fail. Documentation of the architecture, the content types, the access credentials, and the maintenance requirements determines whether your organization owns what was built or depends on the builder indefinitely.
What is your estimated timeline and investment for a project like ours? Ask this after all other questions have been answered.
What a completed project should deliver
Beyond the website itself, a well-run project should produce three categories of deliverable.
Design documentation: wireframes, style guide, typography system, image assets, gives your team the materials to maintain visual consistency after launch.
Project documentation: the signed agreement, access credentials, content architecture, database relationships, and theme file structure, gives your organization the institutional knowledge to manage the site independently.
The live website with full administrative access: not partial access, not access contingent on a continued relationship, is the baseline expectation. You commissioned it. You own it.
If a prospective partner is reluctant to commit to any of these, that reluctance is itself meaningful information.
Focus on what is visible: navigation clarity, mobile responsiveness, and whether the site communicates the organization’s purpose clearly. Ask the partner to walk you through a project: what the organization needed and what decisions were made. A partner who can explain their reasoning led the thinking, not just the execution.
Prioritizing price over fit. The lowest proposal rarely reflects the lowest total cost, it typically means limited experience, limited scope, or margin recovered through change orders. For organizations accountable to boards and funders, a failed project costs far more than the difference between proposals.
Only if you have a clearly defined scope and multiple qualified candidates. For most organizations, the more useful first step is a direct conversation with a partner whose existing work reflects your sector. Clarity about what the project needs to accomplish should come before any evaluation process begins.
Frances Naty Go is the founder of Goldlilys Media, where she helps mission-driven organizations turn their websites into clear, durable systems that support meaningful work over time. She works with museums, nonprofits, health and wellness brands, higher education, life sciences, travel organizations, and expert-led businesses.
With a background in Computer Science from UC San Diego, Frances brings a thoughtful, strategic approach to building digital experiences that educate, orient, and build trust, without unnecessary complexity.
Questions first? Start a conversation
