Look beyond the screenshot
A portfolio image can show visual direction, but it cannot prove how the live site works. Open the website on a phone and desktop. Try the main task: find a service, understand the price basis, make a booking, browse products or contact the business. Check whether the navigation, text size, forms and calls to action remain usable at different widths.
Ask what work the agency completed and what was supplied by the client or another vendor. A project link may represent design, development, maintenance or only one part of the work. Understanding the scope helps you compare relevant experience rather than assuming every visible element was created by one team.
Check fit with your own customer and business model
A freight company, bakery, veterinary clinic and vehicle dealership have different customer questions and transactions. Look for examples that show the type of task your customers need to complete, even if the industry is not identical. Ask how the design decisions would change for your audience, content volume, integrations and internal editing needs.
GrowBiz’s public portfolio includes freight, business supplies, retail, bakery, home services, veterinary and automotive websites. These links are examples of delivered website projects; no traffic or sales outcomes are implied.
Ask about accessibility, content and technical handover
Ask how the team checks keyboard navigation, form labels, contrast, headings, image alternatives and mobile interactions. Automated tools can catch some issues, but a review should also consider how a person uses the site. Confirm that the page structure, metadata, redirects and analytics are included only to the degree stated in the proposal.
Check who owns the domain, hosting, design files, content and analytics after launch. Ask whether you can update basic information without paying for every small change and what support costs after the included period. A responsible project scope states the handover process and recurring costs before work begins.
Request a project explanation, not a fabricated case study
For a project that resembles yours, ask the provider to explain the initial requirement, constraints, decisions and approved deliverables. If performance data is offered, request the source, date range, property and measurement definition. A screenshot with no context should not be treated as proof that a website generated a particular result.
Ask permission before contacting a client reference. A public website link does not authorize an agency to disclose private project information, customer feedback or analytics. A clear answer about what can and cannot be shared is more trustworthy than a dramatic number with no source.
Compare the portfolio with the written proposal
Choose a small set of criteria and apply them to each candidate: quality on mobile, clarity of messaging, fit to your industry, demonstrated scope, accessibility approach, ownership and ongoing support. Then compare the proposal’s pages, timeline, revisions and cost. The portfolio can help you ask better questions; it cannot replace a clear contract.
GrowBiz’s portfolio page, website design service and pricing page provide starting points for a project discussion. Final work should be scoped to the customer task and requirements rather than copied from another company’s site.
Practical checklist
- Open live project links on mobile and test the main task.
- Confirm what the agency did on each portfolio project.
- Ask for sourced evidence before accepting performance claims.
- Match portfolio evidence to a written scope and ownership plan.
In short
A portfolio is a starting point for questions about fit and execution. Screenshots alone do not prove rankings, sales or conversion outcomes.
This article is general educational information, not legal, privacy, cybersecurity or financial advice. Confirm requirements for your situation with a qualified professional.