Ask what the supplier actually delivered
Identify whether the work included design, development, content or only one part of the site. The current live website may have changed since delivery. Ask which features and decisions belong to the project being presented, and avoid treating every visible element as the supplier’s work. A credible explanation of constraints is more useful than an unexplained gallery of attractive screens.
Look beyond a matching industry
A website from your sector may still solve a different customer problem. A relevant example might instead share complex inquiries, multilingual content or frequent editing. Review one comparable task on a phone and ask how the agency would adapt the approach to your situation. Do not infer conversion gains or search rankings from appearance alone.
A practical check before you buy
Select one project and one task similar to yours. Ask for the original brief, the delivered scope and an explanation of how the task was checked. Accept anonymised process evidence where client confidentiality limits disclosure.
| Decision | What to consider | What to check |
|---|---|---|
| Visual fit | Actual delivered pages | Review current and original scope |
| Functional fit | Comparable customer task | Try the complete journey |
| Claimed results | Defined evidence | Check period and attribution |
An illustrative business scenario
A US industrial supplier can assess a different B2B project for specification handling and inquiry routing rather than choosing by industry imagery alone.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.