When reading design cases, do not stop at the visual impression. A sounder approach is to check four layers: which business difficulty the site addresses, which measures were used, whether the features can actually be operated, and whether the results can be traced to a source. Appearance reflects only part of the capability. Whether a vendor can take on your needs depends on how it handles real problems.
During proposal comparisons, decision makers often open several portfolios at once. Because the showcased work has been selected, surface quality often looks similar. The sections below set out a practical way to evaluate cases and use four real projects to show how to break them down.
Why visuals are not enough
Screenshots mostly show visual direction. What you need to judge is whether the team can handle your operating process. Three gaps show up often in practice:
- A polished brand site does not mean the system is mature: A refined corporate site does not guarantee that membership, inquiry, or order flows are equally reliable.
- A well-known client does not mean full ownership: Sometimes only one campaign page was delivered, not the whole site.
- The people behind an old case may be gone: Those who built that project will not necessarily take yours.
When reviewing work, move past appearance and ask what was actually solved. If you are still comparing types of providers, first clarify whether you need a brand site, transaction features, or a process system.
Four keys for judging work
The table below can be used directly against a portfolio. The first four rows are the main criteria; scope and timing add further checks. Only cases that state concrete substance are worth using as references.
| Criterion | Question to ask | Stronger case | Caution |
|---|---|---|---|
| Problem | What did the site originally need to handle? | It names a concrete process or business difficulty | It only says the brand image was strengthened |
| Approach | Why was this approach chosen? | The approach maps to the problem | It only lists design styles |
| Features | Can they actually be used? | The site is still online and features can be tried | Only screenshots or video are shown |
| Results | What actually changed? | There is a source, or the before-and-after change is explained | Only adjectives or unsourced numbers |
| Scope | Which parts did the vendor own? | Planning, design, and development scope are stated clearly | Only the client name and logo appear |
| Timing | When was the work completed? | Launch date and current status can be explained | No year is shown, and the site can no longer be opened |
Four checks before trusting numbers
Result figures are attractive and also easy to misread. A rise in inquiries may come from a redesign, or from extra advertising in the same period. When you see numbers, clarify these points first:
- Where does the evidence come from? Client feedback, analytics tools, or backend records are all acceptable, but the source must be stated clearly.
- Which period is being compared? Peak and off-peak seasons differ, so a direct comparison can inflate the result.
- What else happened at the same time? Advertising, exhibitions, or a new product launch can all affect the outcome.
- Does it fit your situation? Results from export manufacturing may not apply to a local service business.
A lack of numbers does not make a case useless. Many clients cannot publish performance figures. In that situation, look at whether the process changed, for example from phone handling to completion online. A qualitative account that clearly describes the before-and-after difference is often more useful than a percentage with no source.
Project one: English catalog
Original difficulty: Products spanned several series, and buyers were mostly overseas engineers and purchasers, yet overseas inquiries were under ten a month before launch.
Measures taken:
- Present a full English product catalog with a clear category structure
- Add specification search so engineers do not have to browse page by page
- Provide electrical specs, dimension drawings, and PDF technical documents on product pages
What changed: According to client feedback, overseas inquiries rose to more than fifty a month.
What this case shows: Buyers needed specifications, not brand copy, so the focus was on finding products and downloading documents. When planning a business-to-business site, ask first how specification data will be organized.
Project two: orders and ERP
Original difficulty: Orders and sales opportunities from global clients were scattered across different processes. Orders had to be entered manually into the enterprise system, and regional sales progress was hard to track.
Measures taken:
- Integrate international payments so clients can order in multiple currencies
- Manage sales organizations and opportunities across region, country, and area
- Sync orders both ways with the enterprise system to reduce manual entry
What changed: Orders no longer need manual entry, and sales opportunities can be tracked end to end.
What this case shows: System cases should be judged by how data moves. Ask where data comes from and what happens when sync fails. That reveals capability better than screens do.
Project three: member booking
Original difficulty: Member management and venue booking relied on phone calls. Peak periods often caused double bookings, and members had to call back repeatedly to confirm slots.
Measures taken:
- Members choose date, time slot, and headcount online; the system checks conflicts before sending confirmation
- Venue, lodging, and dining bookings sit on one platform
- The backend centrally manages member data, booking reports, and announcements
What changed: Members can check slots and book online without calling to schedule.
What this case shows: The hard part of a booking system is exceptions. Ask how clashes, cancellations, and waitlists are handled, and request a live demonstration.
Project four: society platform
Original difficulty: Members were spread across locations, and dues payment, event and annual-meeting registration, and guidance documents all needed one online entry point.
Measures taken:
- After login, members can check dues and use a dedicated learning area
- Academic events and the annual meeting can be registered and paid for by card online
- Guidance documents, health information, and announcements are updated by the society itself
What changed: Dues lookup, annual-meeting registration, and card payment can all be completed online.
What this case shows: This kind of site needs ongoing maintenance after launch, so confirm that the client can update content. Ask to see the backend as well as the front end.
Five questions for vendors
After reviewing the portfolio, pick the case closest to yours and ask directly:
- What problem did this project originally need to solve?
- Which parts did your company own, and was any work outsourced?
- Can the front end and backend be operated on site?
- What is the source of the result figures, and which period was compared?
- If this were our requirement, what would be different?
The fifth question is especially useful. A vendor that can answer it specifically has usually started to understand your problem. Before signing, also confirm maintenance, acceptance criteria, and later support.
Strong cases explain solutions
The point of reviewing cases is to judge whether the other party can handle your difficulty. Keep three points in mind:
- Start with the problem and the approach: The screen is only the result. Confirm that the approach matches the real difficulty.
- Operate the features yourself: Review both front end and backend. Cases with only screenshots have limited value.
- Ask for the source of results: Numbers are useful only with a source. A clearly explained process change is valuable too.
If the basics are still unclear, first define the site goal, the users, and the required features, then compare the work. When several cases are already in hand and the choice is still hard, write the requirements down and check them item by item. That usually gives direction faster than browsing screens again and again.
