Skip to content
Orvenant
Orvenant

Website design

A website that makes the next step clear.

Website design that helps people understand your business, find the right service and get in touch. Start with customer journeys, then build a visual system your team can use.

A website should answer the questions behind the visit.

People arrive with different jobs to do. Some are checking whether you understand their problem. Others need to compare an option, see how delivery works or find a direct way to talk. We start by identifying those journeys and the information each one needs. That gives the design a purpose beyond a visual refresh: the right page, in a sensible order, with a clear next step. If the offer itself is unclear, we work through that before drawing polished screens.

What goes into a useful design system.

The proposal names the pages, states and handover materials in scope. These are the decisions we make together before a design becomes a build.

Information architecture

We map audiences, questions and page relationships, then test labels and navigation against the words customers use. Key paths include service discovery, comparison, evidence and contact. The result is a page map and wireframes that the content and development teams can review before visual design begins.

Content-led layouts

Headings, explanatory copy, media and actions are planned as one experience. We decide where detail helps a buyer and where it gets in the way. Long-form pages, overview pages and contact journeys can share a visual language without forcing every page into the same template.

Reusable interface rules

We define typography, spacing, color, components and interaction states for desktop and mobile. Navigation, forms, errors, keyboard focus and reduced-motion behavior are included in the design review so the built experience is as clear as the static screens.

Explore Reusable interface rules

Decisions worth making before production.

A design cannot supply missing facts. We agree who approves service claims, what proof may be shown, which languages are ready, who supplies photography and which enquiries should reach your team. Search visibility starts with useful, well-organized information; metadata and structured data support that work but cannot replace it. If you are replacing an existing site, we also review URL changes and redirects before the new navigation is locked.

Review the experience in the browser.

We review important journeys at real screen widths, with realistic content lengths and the input methods people actually use. This catches cramped copy, hidden controls and confusing interactions early. Feedback is recorded against the agreed goals, so a change to one page does not quietly make the rest of the site inconsistent. We can pair design with implementation, or provide a documented design handoff to your development team.

Know what you will own at handover.

The final handover is defined in the proposal: source designs, component behavior, page specifications and agreed media requirements. If Orvenant also builds the site, we check the implemented pages against the approved experience before launch. Content writing, brand development, photography, licensing and ongoing optimization are separate scope choices, discussed before work starts rather than assumed afterward.

Some of the teams we have worked with.

Across talent, fitness, mobility, payments and local commerce.
RandstadClassPassVeezuRushpaySupport Black Owned

Questions before we start.

Do we need finished copy before design starts?

You need a clear offer, the main audience questions and someone who can approve factual claims. We can plan the content structure before every sentence is final, but the design should be reviewed with realistic copy before development. If you need writing as part of the project, we agree that scope explicitly.

Can our existing brand and CMS be retained?

Often, yes. We first review the brand assets, editorial workflow and technical constraints. A visual system can work within an existing brand, and a design can be prepared for an existing CMS. If either system prevents a useful result, we explain the tradeoff before recommending replacement.

What happens if we are also changing our site structure?

We inventory important pages and URLs, decide what to keep or consolidate and plan redirects for moved content. Search performance is not guaranteed, but the migration should be treated as part of the project rather than a final technical task. See our website redesign and migration service for the wider cutover process.

A DIRECT CONVERSATION

Bring us the problem. We’ll work through the next step.

Share what exists today and what you want to change. We can discuss the scope, dependencies and a practical way forward.

Privacy settings

Optional Google Analytics measures page visits and contact-option use. Rejecting keeps Analytics off. Accepting allows analytics cookies. Advertising features stay off, and enquiry contents and contact details are not sent to Analytics.

Withdrawing stops future collection and removes this site’s accessible Analytics cookies. It does not erase information already received by Google. Privacy notice · Cookie notice