Ask what commercial problem the site will solve
A page count and feature list are not a useful brief on their own. A strong agency should ask which audiences matter, what currently blocks action, how leads are qualified and what would make the investment commercially successful.
Listen for a clear link between business goals, content, user journeys and measurement. If the conversation remains entirely visual, the finished site may look fresh without changing performance.
Inspect the thinking behind the portfolio
A gallery proves taste. A case study should also explain the problem, constraints, decision-making and role of the agency. Ask which parts were strategy, design, development, copy, SEO and client-supplied work.
Look at the live mobile experience, not only a desktop mockup inside a laptop frame. Navigation, content density, forms and commerce controls reveal whether responsive design was treated as a real product requirement.
- Review comparable complexity, not only comparable industries
- Open live work on mobile
- Ask who actually completed each discipline
- Request a clear definition of success
Understand the operating model
Find out who will lead the work after the pitch, how feedback is handled and where responsibility changes hands. Too many handovers can dilute the original commercial insight; too little specialist depth can create technical risk.
The best fit is usually the team whose process matches the organisation’s decision speed, internal capability and appetite for collaboration—not automatically the largest or least expensive supplier.
Make SEO and post-launch ownership explicit
Confirm who owns keyword research, URL architecture, redirects, metadata, schema, analytics and launch monitoring. Also confirm who controls the source code, design files, domains and third-party accounts after handover.
A useful proposal describes the system being created, the evidence required from the client, the acceptance criteria and what happens after the first release.