Request a discovery call
  1. Home
  2. What we build
  3. Digital Experience
  4. Websites and Platforms
  5. Corporate and marketing websites

Part of Websites and Platforms

Corporate and marketingwebsites.

A corporate website is the public face of an established company, built around the decision a customer is actually making, and connected to the systems that handle what happens next. Corporate website design and development is one of four services under Websites and Platforms.

A site that starts from a job rather than from a page count, and a way to tell whether it did it.

Request a discovery call Start with an audit

In your words

Soundslike this?

  1. Our sales team answers the same five questions on every first call.

  2. The site was built for the company we were four years ago.

  3. An inquiry arrives and nobody is sure whose it is until somebody claims it.

  4. We cannot change a page without booking a developer.

  5. We are on the shortlist against firms nobody has heard of, and we look the same as they do.

  6. We are hiring hard, and the careers page is a form and a paragraph.

  7. We have analytics, and none of us can say which pages produce work.

If the pages already do their job and the problem is that nobody finds them, the page for that is Search and AI Visibility.

In plain language

A website with a job, and a way to tell.

We build a corporate site as infrastructure rather than as a document. It starts from a job: what the site has to make happen, for whom, and how the business will know it happened. The structure comes from the customer's decision, the design comes from the structure, and the words come from what your sales team finds itself explaining.

A brochure describes the company. A corporate site answers the decision.

It also means the site does not end at the contact form. An inquiry becomes a record with a source, an owner and a timestamp, and the person who should answer it knows within a minute that it exists. Everything after the form is the half of the job most sites leave to a person and an inbox.

Templates carry the weight. Services, locations, people, projects, careers and legal each get a template rather than a page, so the twentieth service page costs a fraction of the first and still looks like it belongs.

When this is not the answer. If the business sells online rather than explaining itself, the storefront is the project and the corporate site is the smaller half of it: start at E-commerce platforms.

If the pages are sound and the problem is that the same requests keep arriving in somebody's inbox, a customer portal removes the request instead of handling it faster.

The capability table

What corporate website design and development includes.

Fifteen capabilities, what each one does in plain words, and what it changes for the business. Nothing here is a category name standing in for work.

Corporate and marketing websites, the capability table
Capability What it does What it changes
Before any designStrategy and structure
Audience and job definition What the site has to make happen, for whom, and how you will know it happened. The scope stops being a page count and starts being an outcome.
The customer's decision path The order a buyer actually researches in, mapped from what your team gets asked. A page exists because a decision needs it, not because a competitor has one.
Content first wireframes Structure and real words, reviewed before any visual design exists. You approve the argument before anyone chooses a colour.
The competitive picture What your buyer sees in their own browser when they build a shortlist. You find out what you are compared against while it is still cheap to respond.
The buildDesign, content and templates
A design system Components and rules rather than a set of pages. The next page costs a fraction of the first.
Page templates Services, locations, people, projects, careers and legal. A new office or a new service is an entry, not a project.
Copywriting Authored from your material, your people, and the questions your sales team already answers. The site explains what is currently explained on the phone.
A content management system Built to your content types and your approval flow. Your marketing team publishes without booking a developer.
What happens after the formWhere most sites stop
Forms, routing and acknowledgement Every inquiry becomes a record with a source, an owner and the time it arrived. Nobody discovers on Friday that Tuesday's inquiry was nobody's.
The CRM connection The record lands where your sales process already lives. The site stops being a separate system with its own inbox.
Analytics and conversion tracking Reporting built around which pages produce work. You can answer the question the board asks.
Before it goes liveThe checks, run in full
Technical search foundation Structure, internal linking, structured data, sitemaps and crawler access. Search engines and assistants read the site the way a person does.
Accessibility Designed to WCAG 2.2 AA and tested with a keyboard and a screen reader. The result is a measurement rather than a claim.
A performance budget Tested on a mid range phone on a cellular connection. The site is fast where your buyer actually reads it.
Migration and redirect mapping Every existing URL mapped before the old site comes down. The rankings you already have survive the move.

Scroll the table sideways to read it.

How it works

A search to a reply, in seven steps.

The parent's drawing, read from the left. This page is about everything before the line: how somebody arrives, what the page asks of them, and what happens to the record they leave behind.

Scroll the drawing sideways to read it.

Seven steps, one of them yours. The point of the drawing is the right hand end: the site does not stop at the form.

What the system does

The work, the path it takes, and everything HUREAL builds. It never means anything else.

What stays with a person

The line, its single opening, and the plate standing in it. On a light board it is the one dark plate.

What you already run

Present, named, and not for sale. The lowest contrast on the board, deliberately.

  1. They arrive from somewhere, and the page knows which.

    Search, a referral and an ad are three different states of mind arriving at one page. The page does not change for each of them, but the reporting does, because the thing you want to know next month is which of the three produced work.

  2. One page, one job.

    A page that offers four things gets chosen for none of them. The job is decided in strategy, written into the template, and it is the reason the page exists at all.

  3. The next step is smaller than the sale.

    A quote, a call or a slot. The step is sized to the decision the visitor is actually ready to make, which is almost never signing.

  4. The form asks for what you will use.

    Every field is there because somebody downstream needs it. Fields that exist because the old form had them are the cheapest conversion you will ever recover.

  5. It becomes a record, and then it is somebody's.

    Source, owner and the time it arrived, in your CRM rather than in ours. What goes out is logged, and what was logged is what tells you which page to change next month.

The template is the point. A page built on a system costs a fraction of one built on its own, and the difference compounds every time you add an office, a service or a person.

Read the method

The deliverables

What you end up with.

  • A live site in your accounts

    On infrastructure in your own accounts. How ownership works

  • A design system and component library

    So the next page costs a fraction of the first and cannot drift from the rest.

  • Templates for the pages that repeat

    Services, locations, people, projects, careers and legal, each with a content model behind it.

  • A CMS your team publishes in

    Built to your content types and your approval flow, trained before launch rather than handed over after it.

  • Every inquiry in your CRM

    With its source, its owner and the time it arrived.

  • Analytics that answer which pages produce work

    Set up around the questions your leadership actually asks.

  • The strategy document

    The job, the audience, the decision path and the measurement plan, in writing.

  • The launch checklist results

    Fourteen named checks, run in full, with what each one returned.

  • The redirect map

    Every old URL and where it now points, so the move is auditable a year later.

What is not on this list. The second language. A site authored per language is a different scope and a different set of decisions, and it is on Multilingual websites. So is the publishing programme that fills a site with guides and answers, which is Content platforms.

By category

What a corporate site connects to.

By category, because the category is the question. The first real objection is whether this works with what you already run, and the honest answer is a list plus a qualifier, not a wall of logos.

  • CRM

    Where the inquiry becomes a record with a source, an owner and a date.

    Salesforce, HubSpot, Zoho, Dynamics

  • Marketing automation

    Where a follow up sequence and a newsletter live.

    Mailchimp, Klaviyo, HubSpot, Campaign Monitor

  • Analytics and tag management

    Where the question of which pages produce work is answered.

    Google Analytics, Google Tag Manager, server side tagging

  • Applicant tracking

    Where a careers page has to send an application.

    Workday, BambooHR, Lever, an in house board

  • Accounting and ERP

    Where a price, a stock figure or an account is true.

    QuickBooks, Sage, NetSuite, SAP

  • Document and asset storage

    Where the specifications, drawings and certificates a page links to actually live.

    SharePoint, Google Drive, Dropbox

  • Your industry system

    The one system that runs your trade, which is usually the one that matters most and the one that is hardest to connect.

    estimating, dispatch, practice management, property management

Every connection is validated by HUREAL's engineers during scoping and confirmed in writing before signature. Where a system genuinely cannot be connected, you hear it during discovery rather than during the build, and the scope is drawn around it instead of making a platform migration the price of entry.

Asked and answered

Questions people actually ask.

  • Who writes the content?

    We do, from your material, your people, and the questions your sales team already answers. You review every word. If you have a writer you like, we work with them and provide the structure and the brief.

  • Can our marketing team change it afterwards without a developer?

    Yes, and that is a design requirement rather than a feature. The content model is built around your actual content types and your approval flow, and your team is trained on it before launch rather than handed a manual after it.

  • What happens to our search rankings when we move?

    Every existing URL is mapped to its new home before the old site comes down, and the map is a document you keep. Pages that already earn traffic are identified first, so the new structure is drawn around them rather than around a new menu.

  • What does it cost?

    The price is set after the discovery call and written into the proposal you sign. How scope and price are set

Three pages next to this one

Where this sits.

Two ways to start from here.

I know what I need to build.

Discovery call

A free conversation, then a written proposal with scope, price, and timing.

Request a discovery call

My website is underperforming.

Website Performance Audit

A written report and a prioritized plan of what to fix first.

Explore the audit

A website with a job, and a way to tell whether it did it.