Ask how they would approach your specific problem.
Describe the audience, the offer and what is not working today. Listen for questions about customer decisions, content, operations and the desired action. A useful conversation should produce a clearer understanding of the project, even before the visual direction has been chosen.
Ask the provider to explain a tradeoff. For example, what would they launch first if the schedule were constrained, or when would they recommend a service page instead of another city page? Their reasoning tells you more than an assurance that every requested feature is easy.
Read the portfolio as evidence.
Ask which parts of a displayed project the team actually completed. Design, development, content and ongoing marketing may have been handled by different people. A clear account of responsibility helps you understand whether the example demonstrates the capability you need.
For performance claims, ask what was measured, over what period and with what limitations. A screenshot of traffic alone cannot establish why a result occurred. Concepts should be labelled as concepts, and client work should be represented with permission and accurate context.
Make the scope concrete before comparing prices.
Check who supplies the copy, images, legal or policy text and approvals. Ask how many design and content review stages are included, what happens when the brief changes and which integrations require existing accounts or separate subscriptions.
For search and lead generation, ask for deliverables rather than broad promises. A proposal might include page planning, crawlable content, metadata, analytics setup and a tested enquiry workflow. No provider can guarantee a particular organic ranking or an AI system’s recommendation.
Understand the working relationship.
Agree on the project contact, review process and responsibilities on both sides. A realistic schedule accounts for content collection and approvals, not just design and coding. If several people in your organisation provide feedback, choose one person to consolidate it.
Ask how issues are handled when a decision is unclear or a dependency is delayed. Written milestones, visible decisions and a clear change process make the relationship easier to manage than relying on informal assurances throughout the project.
Check what you receive at the end.
Clarify account ownership, source or export access, content rights and the ongoing support arrangement. Confirm how a routine edit is made, where enquiries appear and who can see analytics. Access should be documented without sharing passwords in ordinary messages or public files.
Ask the provider to demonstrate the finished customer journey before launch. A visitor should be able to understand the offer, complete the intended action and receive an accurate confirmation. The handover should explain how the business continues operating that journey after the project team steps back.
Your planning checklist
- Use the same brief and comparison questions for each provider.
- Verify portfolio responsibility and the basis of result claims.
- Clarify content, integrations, reviews and change handling.
- Confirm ownership, access and the ongoing support scope.
Common questions
Should we choose a provider based on a similar-looking portfolio?
A relevant visual direction is useful, but also assess how the work solved a business problem and what the provider actually delivered. The best fit needs to understand your content, customer journey and operational requirements.
What is a reasonable expectation for SEO in a website proposal?
Look for defined work such as search intent planning, technical accessibility, useful content, metadata and measurement. Ranking guarantees are not a substitute for those deliverables, and ongoing content or promotion work should be scoped separately when required.
Sources & further reading
References for the planning context. No relationship with the organizations listed is implied.
