Judge understanding before visual taste
A portfolio should show craft, but the first conversation should show judgment. A useful partner asks who the customer is, what makes them choose, how they currently find the business, what proof exists, which action matters, and what the team can maintain after launch.
Ask the provider to restate the problem and recommend the first version. A strong answer may remove pages or features. If every discovery call produces the same package, the service is selling inventory rather than solving the business case.
Inspect one project deeply
Open a live website on phone and desktop. Test navigation, forms, loading, readability, focus, errors, and contact details. Ask what the original problem was, what changed during the project, who wrote the content, what the provider owned, what the client owned, and what happened after launch.
Look for tradeoffs rather than a flawless story. Experienced teams can explain why they used a template or custom system, what they postponed, and how they protected the important customer journey within budget.
- A relevant live site, not only screenshots
- Clear role in strategy, content, design, and development
- Evidence of launch testing and support
- An honest account of limitations
Make scope and ownership explicit
The proposal should list pages or page types, content responsibility, revision limits, mobile behavior, forms, integrations, accessibility, performance, search metadata, analytics, legal-content responsibility, hosting, licences, deployment, training, warranty, and maintenance. Ambiguity becomes surprise cost.
The business should own the domain and key accounts. Confirm access to hosting, analytics, search tools, design files, and code or a usable export. Document renewal dates and recovery access. Dependence may be acceptable, but it should be chosen with eyes open.
Choose the operating relationship
Some businesses need a fixed launch and rare changes. Others publish weekly, run campaigns, or depend on bookings and sales. Ask who will make updates, how requests are priced, what response time applies to a broken form, and how often performance is reviewed.
Do not choose by price alone or assume the largest agency is safest. Choose the team whose attention, skills, process, and support match the risk. A concise, complete proposal is more useful than a low headline number followed by add-ons.
- Named day-to-day contact
- Clear launch acceptance criteria
- Defined support and emergency route
- Known recurring costs
- Simple exit and handover path