When the product is hard to explain, web design is an editing job
A great many organisations in Cambridge sell something that takes a paragraph to describe: an instrument, a licensing model, a research service, a platform that only makes sense to people in one discipline. For those businesses the visual surface is the least of the problem. The difficulty is deciding what a stranger needs to understand first, second and third, and refusing to say everything at once.
That is why the most valuable web design studios here behave more like editors than decorators. They will ask who the reader is, what they already know, and what they must believe before they will contact you. Then they will cut. A candidate who opens with colour palettes and closes without ever asking about your audience is proposing decoration, and decoration does not fix a page nobody can follow.
Information architecture before anything is drawn
Ask every candidate to produce the site structure before any web design is drawn: the page inventory, the grouping, the labels, and the route a first time visitor takes from arrival to enquiry. This costs a fraction of the design phase and it decides most of the outcome.
Labels deserve a fight. Technical organisations tend to name sections after their internal departments or after terminology that only insiders use, and visitors then hunt through a menu written in a private language. Insist that navigation labels are tested on somebody outside your field. If a bright person with no domain knowledge cannot guess what sits behind a word, the word is wrong, however accurate it is.
Evidence, references and the credibility layer
Buyers of technical products look for proof, and proof has a shape. Publications, method descriptions, specifications, named collaborators, data presented without exaggeration. These elements need proper web design rather than being pasted in at the end as an accessible list of links.
Ask how a candidate would present a specification table, a methodology page and a publication list, and whether those page types are inside the quoted scope. They are frequently excluded, then improvised, and they end up looking like the part of the site nobody cared about. For a research led organisation that is exactly the part visitors read most closely.
Test the prototype on people who are not you
A clickable prototype exists so that disagreements can be settled by watching somebody use it rather than by seniority. Even a handful of sessions with people resembling your real audience will tell you more than another internal review, and the findings are usually blunt: they did not see the button, they did not understand the section name, they expected pricing where there was none.
Agree in advance that testing happens before the visual work is signed off, not after launch when changes are expensive. Ask whether the studio runs sessions itself or expects you to arrange participants. Either is fine, but the answer belongs in the proposal rather than in an awkward conversation later.
The website will outlive the people who commissioned it
Teams change quickly in this market, spinouts change name, and a project that started with a founder writing the copy ends up in the hands of someone who joined afterwards. Web design that depends on its author being available is a liability in that environment.
Insist on written guidance: how the type scale works, when to use each page type, what the rules are for images, which patterns exist for tables, notices and forms. A short, clear document beats an elegant file nobody can interpret. Ask to see an example of this guidance from a previous project before you appoint anyone, because the quality varies enormously and almost nobody shows it unprompted.
Questions that surface how a studio actually thinks
- What would you remove from our current site first, and why?
- How do you decide what belongs on a landing page and what belongs deeper?
- Who writes the labels in the navigation, you or us?
- How would you present something complicated to a non specialist without dumbing it down?
- What guidance do we receive so a new colleague can add a page correctly?
The last question is worth pressing on. Guidance that exists only in the head of the person who drew the pages is guidance you will lose the moment they move on, which in this market happens often.
The first question is the sharpest tool you have. A studio that answers it with a genuine argument has already read your site. A studio that answers with a compliment has not.
Comparing web design agencies in Cambridge without a long procurement
Three candidates, one written brief, one deadline. Ask each for their reading of the problem in plain prose before any picture appears, because that paragraph is where the difference between studios becomes visible. Pretty web design work is common. Clear thinking about an unfamiliar subject is not.
Check as well who will be assigned. In a small market the senior name that attends the pitch is frequently spread across several accounts, and the person drawing your pages may be much less experienced. Ask for that split in writing, and ask how review works internally before anything reaches you.
The directory lists verified web design agencies with profiles you can read side by side, together with related specialists such as animation studios for explanatory work, public relations agencies and SEO agencies. When the shortlist is settled, request matched proposals so every studio answers identical questions. If the project also needs engineering, the listed software companies are the other half of that conversation.