Four revealing questions
- Whose name are the hosting and domain in? Should be yours.
- What happens if we want to leave? Should be straightforward.
- How are updates handled after launch? Should have a real answer.
- Can we see a site you built two years ago? Reveals how they age.
The fourth is the most useful and the least asked. Anyone can show you a site launched last month; the ones from two years ago show whether the work lasts.
What to look for in their work
- Sites that load quickly on a phone
- Sensible structure rather than everything as a page
- Content that has clearly been updated by the client since
- Forms that work — try one
Warning signs
- Hosting held in their name as standard
- No mention of updates or maintenance
- A quote with no scope detail
- Reluctance to give client references
- Everything built with the same multipurpose theme
Get the scope in writing
| Should specify | Why |
|---|---|
| Page templates and count | The main driver of effort |
| Who writes the content | The most common overrun |
| What functionality is included | Prevents assumption gaps |
| Revision rounds | Prevents endless iteration |
| What happens after launch | Support and maintenance terms |
Reference calls are worth the time
Ask a past client two things: did it come in on time and budget, and what happened when something broke afterwards.
Those two answers are more informative than any portfolio.