How to find a trustworthy web partner

Start with what you actually need

Before you talk to anyone, write down three things: who needs to use the site, what they need to do on it (call, donate, book, read), and whether you have content ready or still need help with copy and photos. A trustworthy partner will ask you these questions on the first call. Someone who jumps straight to "we'll send a quote" without understanding your situation is guessing — and you'll pay for the guess later.

Look for relevant experience — not just a pretty portfolio

A portfolio should show work that resembles what you need. If you're a local service business, look for other service businesses — not just SaaS landing pages or e-commerce stores you'll never run. If you're a nonprofit, look for mission-driven sites with donation paths, event pages, or volunteer forms. Years in the field matter, but so does variety: someone who's only ever cloned one template for every client has learned one trick, not how to solve your specific problem.

Ask how they built each site in the portfolio. Hand-coded, maintainable work is different from dragging blocks in a page builder. You don't need to understand the technical details — but they should be able to explain their choices in plain language.

Ask for references — and actually use them

A real web partner will connect you with past clients without hesitation. Not a list of anonymous five-star reviews on a third-party site — actual people you can email or call. Ask those references: Did the project finish on time? Could they update the site themselves afterward? Would they hire this person again? If a developer won't provide references, or only offers "NDA-protected" work they can't discuss, that's not confidentiality — it's a gap in their track record.

• —How long did the project take from kickoff to launch?
• —Were there surprises in the final bill?
• —Can you update content without calling the developer every time?
• —Is the site still working well a year later?

Understand what you'll own when it's done

You should own your website — the design, the content, the code, the domain. A trustworthy partner hands you the keys at launch: admin access, hosting credentials, documentation for how to update things. Lock-in is a business model for some agencies. They build on proprietary platforms, host on their servers, and charge monthly fees to change a phone number. That's not partnership — that's dependency.

Ask directly: \"If I stop working with you in two years, can I take this site somewhere else?\" The answer should be yes, without a complicated exit fee or a rebuild requirement.

Red flags that should stop the conversation

Some warning signs are obvious. Others hide behind polished sales pages. Here's what should make you pause — or walk away entirely.

Their entire portfolio is Squarespace (or Wix, or Weebly)

If every site they've built lives inside a page builder — especially if Squarespace is the only platform they know — you're not hiring a web developer. You're hiring someone to configure templates. That's fine for a very simple first site. It's a red flag if you're paying professional rates and expecting custom work, accessibility, performance, or a site you can grow beyond template limits. A serious developer can use builders when they fit; they shouldn't be the only tool in the box.

No references, or only vague testimonials

Stock quotes with first names and no business attached. Reviews that all sound the same. A refusal to connect you with a past client. Trust is earned through real relationships, not curated marketing copy.

They can't explain their process or pricing

"It depends" without ever getting specific. No written proposal. Hourly billing with no estimate. Surprise invoices for "additional rounds" that weren't mentioned upfront. You deserve a clear scope before you sign anything.

Everything looks like the same template

Identical layouts, stock photos, generic copy across every portfolio piece. If your site will look exactly like your competitor's — because they both got the same template — you're not getting design. You're getting assembly.

They dismiss accessibility, speed, or mobile

"We'll add that later" or "nobody really needs that." Later often means never. And the people who need accessible, fast, mobile-friendly sites are your customers — including the ones who leave quietly without telling you why.

You're always talking to a salesperson, never the person doing the work

Layers of account managers and project coordinators aren't inherently bad — but for a small business or nonprofit, you usually want direct access to the person writing code and making design decisions. Ask who you'll actually work with.

What a good first conversation sounds like

A trustworthy web partner listens more than they pitch. They ask about your audience, your timeline, your budget range, and what's frustrated you about your current site. They give a real opinion — not a script — and they're honest if they're not the right fit. They don't pressure you to sign this week. They follow up with a written proposal you can read on your own time and share with a board or business partner.

You don't need to become a technical expert to hire well. You need someone who respects your time, shows their work, connects you with people who've worked with them before, and builds something you can actually keep.