A material study in bright daylight. A fan of clear turquoise glass blades opens from a low point and sweeps up to the right, crossed by a polished pearl silver ribbon, with a straight rank of upright glass fins standing behind it like a wall.
  1. Home
  2. Services
  3. Websites and platforms

One of the eight services

Websites andplatforms.

A website and platform build is the public face of a company and the system behind it: the pages a customer reads, and what handles the inquiry they leave.

The site does not stop at the form. Every inquiry arrives as a record with a source, an owner, and the time it came in.

Book a discovery call Request a performance audit

Know what you are building? Book a discovery call. Not sure where the problem is? Request the audit.

HUREAL / Material studies

Block 02

Soundslike this?

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

  2. We send people to the site before a meeting, and then explain it on the call.

  3. An inquiry arrives and somebody re-types it into the CRM.

  4. We have traffic, and nobody can say which pages produced revenue.

  5. Changing a page means emailing whoever built it, and waiting.

  6. We are hiring, and the engineers we want read the site before they reply.

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

If what you recognise is an order that has to be placed online, or an account that should be able to reorder without phoning, E-commerce and Marketplaces is the page for that.

Block 03

What this is,in plain language.

What happens today

Somebody is choosing a supplier. Three weeks before they contact anyone, at nine at night, they read four pages of your site on a phone. They form a view of how big the company is, how carefully it works, and whether it does the specific thing they need. Then they either send a message or they do not, and you never learn which it was.

The message that does arrive lands in an inbox. Somebody reads it in the morning, works out whose it is, and types the details into the customer record. Nothing about that is the site's fault or anybody's fault. It is what a site does when it was built as a document rather than as a system.

What happens after

The same person reads the same four pages. This time each page has one job, the next step is one step, and the thing they came to find out is on the page in the words they would have used.

The message becomes a record before it becomes an email: a source, an owner, the page it came from, and the time it arrived. The person who should answer it knows within a minute that it exists. A month later you can say which pages produced revenue, because that was wired in before launch rather than added after somebody asked.

A brochure describes the company. A platform does a job, and tells you whether it did it.

That is the whole difference, and every decision in the build follows from it. The structure comes from the decision your customer is making rather than from a page count. The design comes from the structure. The words come from what your sales team finds itself explaining on the phone. The measurement comes from the job. A site built the other way round, design first and job last, is a document with a contact form on it, and it can only ever be judged on whether people like the look of it.

Four things are built in from the first day rather than added at the end: the site is designed to the WCAG 2.2 AA standard and tested with a keyboard and a screen reader, it is measured on a mid-range phone on a cellular connection, every old URL is mapped to a new one before launch day, and your team holds admin access from the first commit.

Block 04

Who this is for,and who it is not for.

Where this pays for itself

  • Customers research before they buy. Professional services, construction and trades, manufacturing and distribution, healthcare, real estate, B2B services: anywhere the decision is made over weeks and mostly in private.
  • The company is entering somewhere new, a province, a region, a market, where nobody knows the name yet and the site is the only introduction.
  • Something changed: a rebrand, a merger, a new generation of leadership, a second division that the current site does not explain.
  • The same five questions come up on every first call, which means five answers are already written and are being delivered one conversation at a time.
  • You are competing for people as hard as you compete for customers, and the site is read by both.
  • There is something to publish: specifications, guides, a catalogue, a body of knowledge that a buyer would read if it existed in one place.
  • The inquiry has to land in a system, with a source and an owner, rather than in an inbox that somebody watches.

You probably do not need this if

  • It is five pages, nothing logs in, nothing connects, and nothing gets published on a schedule. A template on a page builder does that well, does it next week, and costs a fraction. Block 11 runs that comparison in full and it goes against us.
  • The pages already convert and nobody arrives. Rebuilding a site that is working is an expensive way to solve a traffic problem. The work is Search and AI Visibility, and it costs less.
  • Nobody will own the site after launch. A site is a publishing commitment. The best build in the country goes quiet in a year without a person whose job includes it, and a subscription product keeps working without one.
  • The content does not exist and the date cannot move. Content is the single most common reason a build runs late. Where the launch is fixed and the material is not written, the honest sequence is the template now and the platform next year.
  • The requirement is that it should look more modern. That is a real requirement and a legitimate one. It is usually a smaller job than a platform: a design system and a set of templates on what you already run. We will say so on the discovery call, before anything is scoped.

Where a page builder is the right answer, we will say so, and we will not quote you for a platform.

Block 05

What itincludes.

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.

Websites and platforms, the capability table
Capability What it does What it changes
Before anything is designedStrategy and architecture
The job of the site The decision your customer is making, the audiences, the conversion goals, and how the business will know it worked, agreed on the discovery call and written into the proposal. You find out what the site is for before you pay to design it.
Architecture and wireframes Sitemap, page-by-page purpose, and content-first wireframes, approved before anyone chooses a colour. The structure is argued once, while changing it is still free.
The measurement plan Which pages are supposed to produce what, agreed in advance and wired before launch rather than after somebody asks. "Did it work" has an answer instead of an opinion.
Corporate and marketing websites Sub-service
The design system Type, colour, spacing, components and their states, built as a system rather than as a set of pages. The second page costs a fraction of the first, and the fortieth still matches.
Page templates Services, locations, people, projects, careers, legal, and the templates your team will need next year. New pages get published, not commissioned.
The words Written from your material, your people, and the questions your sales team already answers. You review every one. The page says what a good first call says.
The content management system Your content types, your approval flow, previews, scheduling and roles, with your team trained before launch day. A change takes an afternoon and no developer.
Multilingual websites Sub-service
Native authoring per language Each language written by a person who writes it, from one brief, with its own question research rather than a translated keyword list. Customers read something a person would have written.
Per-language structure A content model where each language is a version rather than a field, with its own URLs, sitemaps, hreflang and structured data, and switching that keeps the reader on the page they were on. Each market can rank on its own terms instead of competing with itself.
Content platforms and publishing systems Sub-service
The content model and the workflow Guides, articles, specifications, cases, questions, glossary and documents, with draft, review, approve, schedule, publish and expire. Publishing stops depending on whoever is least busy that week.
Topic architecture Pillar pages, clusters, and the internal linking between them, marked up so an answer can be lifted cleanly by a search engine or an assistant. Each new piece makes the last one stronger instead of competing with it.
What every build carriesWhatever else is in the scope
Forms, routing and the CRM Every form, chat and booking becomes a record with a source, an owner and the time it arrived, with an acknowledgement the customer actually receives. The inquiry has an owner within a minute, not within a morning.
Accessibility and performance Designed to the WCAG 2.2 AA standard, tested with a keyboard and a screen reader, and measured on a mid-range phone on a cellular connection. The site works for the customer who is not on office wifi.
Migration and redirects Every old URL mapped to a new one before launch day, with the internal links updated to match. A new site does not cost you the traffic the old one earned.
Search foundations Structure, internal linking, structured data, sitemaps, and crawler access for search engines and for AI crawlers. The site can be found, and it can be quoted.

Scroll the table sideways to read it.

What comes with every build of this kind

Site Answer, included in the scope of every build.

Your site answering a real question from your own documents, with the source shown, so a visitor who would have sent a message gets the answer instead. It is one of the three fixed-scope modules, and it is part of every Websites and Platforms build rather than an extra beside it. The signed scope says so in writing.

  • Site Answer Included with every build of this kind

    Your site answers a real question from your own documents, with the source shown, and hands over anything it cannot ground.

See the three modules Hear one working

Block 06

How itworks.

A search to a reply in seven steps. The point of the drawing is the right hand end: the site does not stop at the form.

Scroll the drawing sideways to read it.

Seven steps, and the last three are the ones most sites do not draw at all.

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, and you can name where from.

    A search, a referral, an ad. Every arrival carries its source with it from the first click, and the source stays attached to the record at the other end. That one decision is what makes the rest of this drawing measurable rather than anecdotal.

  2. One page, one job.

    The page they land on is about the thing they searched for, and it is trying to do one thing. A page with four jobs does none of them, and it is the single most common reason a site with traffic produces nothing.

  3. The next step is one step.

    A quote, a call, a slot. Not a menu of ways to get in touch. The page asks for the next thing a person in that situation would actually be ready to do.

  4. The form asks only for what you need.

    Every field is a reason to leave. What you ask for is what your team genuinely needs to reply well, and nothing that is being collected because a form template had it.

  5. It becomes a record before it becomes an email.

    Into your CRM with the source, the owner and the date. Not a notification somebody has to notice, and not a copy of an inbox. If the record is not created, the inquiry did not happen, and that is the point of drawing it this way.

  6. A person replies.

    Here is the line on this service, and it is a short one: the site never replies to a customer in your name. It captures, it records, it routes and it acknowledges receipt. The answer is written by your person, the same day, in your words.

  7. What happened is logged, and it changes the page next month.

    Which pages produced records, which produced records worth having, and which produced nothing. That loop back to the top of the drawing is the whole reason the measurement plan is in the scope rather than in a later phase.

Every check this build passes before it goes live is published by name. Fourteen of them, written out rather than summarised as quality assurance. Read them before you hire anybody, and hold whoever you hire to them.

Read the fourteen checks

Block 07

What youend up with.

  • The strategy document

    The job, the audiences, the decision your customer is making, the conversion goals and the measurement plan, in writing, from phase one.

  • The architecture

    Sitemap, page-by-page purpose, and the content-first wireframes you approved before any visual design existed.

  • The design system and component library

    So the next page costs a fraction of the first and still looks like the company.

  • The live site, in your accounts

    Hosting, domain, repository and analytics in your name, under your admin, from the first commit.

  • The content management system

    Your content types, your approval flow, your roles, with your team trained on it before launch day and not after.

  • The words

    Written from your material, reviewed by you, and yours to change without asking anyone.

  • The measurement

    Analytics, conversion tracking and a report that answers which pages produce revenue.

  • The redirect map

    Every old URL pointed at its new home, with the internal links updated to match.

  • The launch record

    The fourteen published checks, run in full, with the result of each one written down.

  • The documentation and the training

    Written for a developer who has never met us, and a session for the people who will run it.

V3. The inquiry, as it lands

your-company/crm/inquiry Tuesday, 14:06

What the form actually produced

One record. Six facts. None of them typed by a person.

  • Source

    Organic search, the phrase they searched, the page they landed on.

  • Page

    The one they were reading when they decided to write to you.

  • Owner

    Assigned by your routing rule, to a person, not to a shared inbox.

  • Arrived

    14:06. The clock on the reply starts here and it is visible.

  • Asked

    What they typed, unedited, in the language they typed it in.

  • Acknowledged

    14:06. An automatic acknowledgement that refers to what they asked, and promises a person rather than a brochure.

    The only one it sends
The acknowledgement is the only message this system ever sends a customer on its own, and it says a person is coming. That is the line on this service, drawn in the one place a visitor can check it: submit the form on this page and watch what arrives.

On every HUREAL engagement, whichever of the eight it is

  1. A written scope with a fixed price and a timeline, before any code.
  2. The working build, reviewed at every phase, in your own accounts.
  3. Full ownership of the code, the content and the data, with admin access from day one.
  4. A named contact who is accountable for the work.

Block 08

How anengagement runs.

Five phases. You can stop after any of them, and every one produces a document you own.

  1. 01

    Discovery call

    A discovery call with the people who own the outcome. We agree the job the site has to do, who it is for, the decision they are making, what it connects to, and how you will know it worked.

    How long
    One call. The written proposal follows it.
    Your people
    Whoever owns the outcome, plus whoever knows what sales gets asked.
    You end up with
    A written proposal: a scope, a price and a timeline you can sign or walk away from. Yours either way.
  2. 02

    Design

    Structure before surface. Sitemap, page-by-page purpose and content-first wireframes first, approved while they are still cheap to change, then the design system, then the templates that carry the argument.

    How long
    Set in the signed proposal.
    Your people
    One approver for the structure and one for the design.
    You end up with
    The architecture, the design system, and the key templates, each reviewed against the strategy.
  3. 03

    Build

    Templates, content, languages, integrations and tracking, in your own accounts under your admin access from the first commit. Working software at every review, not a reveal at the end.

    How long
    Set in the signed proposal, with the review schedule agreed in it.
    Your people
    One reviewer per review, plus whoever owns the systems being connected.
    You end up with
    Working software at every review, in your accounts from the first one.
  4. 04

    Launch

    The redirect map first, then the same fourteen published checks every HUREAL build passes, then go live and switch the measurement on.

    How long
    The checklist, the migration and the go-live, on the dates agreed in the proposal.
    Your people
    Whoever signs off the content, plus an admin sign-in before launch day.
    You end up with
    A launch record against fourteen named checks, and a redirect map you can audit.
  5. 05

    Run

    Improvement, content, monitoring and reporting. What changes next month comes from what the measurement said, not from a list somebody wrote in January. Monthly, and cancellable.

    How long
    Monthly, for as long as you want it. Cancellable at any time.
    Your people
    One read of the monthly report and one call to pick what changes next.
    You end up with
    A written report: what the site produced, what changed, and what did not work.

What makes it longer: how much of the content has to be written from scratch, how many systems it connects to, how many languages are authored natively, whether customers log in, and whether anything has to be migrated. What does not make it longer: how many pages you want. Twenty service pages on one template is a smaller job than five pages that are each unique.

Read the whole method, including the fourteen launch checks

Block 09

What itconnects 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 its source, its owner and its arrival time.

    Salesforce, HubSpot, Zoho, Dynamics

  • Marketing and email

    Where a subscriber, a nurture sequence and a consent record live.

    Mailchimp, Klaviyo, HubSpot, Campaign Monitor

  • Analytics and tag management

    Where the click becomes a number you can act on, including server-side where the browser cannot be trusted.

    GA4, Google Tag Manager, server-side tagging

  • Booking and scheduling

    Where a slot is held, moved or released by somebody who did not phone.

    Calendly, Acuity, an in-house dispatch board

  • Hiring and careers

    Where an application goes when the site is also a recruiting surface.

    Workable, Greenhouse, BambooHR

  • ERP and product data

    Where price, stock and specification are actually true, for the pages that show any of them.

    NetSuite, SAP, Sage, a product information system

  • Payments

    Where a deposit, a fee or a registration is taken on the site itself.

    Moneris, Stripe, Square, Interac e-Transfer

  • Search and crawler tools

    Where you verify that a search engine and an AI crawler can reach and read the site.

    Google Search Console, Bing Webmaster Tools

  • Your industry system

    The one system that runs your trade, which is usually the one that matters most and the one nobody else connects to.

    estimating, practice management, property management, dealer systems

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.

Block 10

What we do,and what we will not do.

What we do

  • Name the price before the workFixed scope, fixed price, fixed timeline, signed before any code is written.
  • Start from the jobThe structure comes from the decision your customer is making, never from a page count.
  • Write the wordsFrom your material and your people, with you reviewing every one of them.
  • Build it as a systemA design system and templates, so the fortieth page still looks like the first.
  • Test what we claimKeyboard, screen reader, contrast, reduced motion, and a mid-range phone on a cellular connection.
  • Put it in your accountsHosting, domain, repository and analytics in your name, with your admin access from the first commit.
  • Say when it is smallerWhere a page builder or a configured platform does the job, that is the recommendation, and it is free.

What we will not do

  • Quote a platform for a brochureWhere five pages and a contact form is the requirement, a custom build is us charging you for craft you do not need.
  • Certify your complianceWe design to the standard, test against it, and document what we built. The determination belongs to your counsel or your privacy officer.
  • Launch a rebuild without the redirect mapA page that ranks and then disappears takes its traffic with it. If the map is not finished, the launch moves.
  • Publish a number about your business we did not measureNo invented percentages on your site, in your deck, or in ours.
  • Build something only we can maintainMainstream technology, documented for a developer who has never met us. Being difficult to replace is not a business model we are interested in.
  • Hold your passwordsAccounts are opened in your name and we work under our own access, which you can revoke.
  • Send anything to your customers from a system you have not signed offNot a form acknowledgement, not an automated reply, not a newsletter.

Every one of those is in the scope document before you sign it, which is the only place a commitment is worth anything. The recommendation to buy less is the one that costs us money, and it is the one we would ask you to test us on first: bring us a project where the answer is a template, and see what we say.

Block 11

A template, a configured platform,or a built one.

Three ways to have a website, and they are not three tiers of the same product. They cost different amounts, they fail differently, and the cheapest one is genuinely the right answer for a lot of companies.

The three approaches, on ten deciding factors
Deciding factor A template on a page builderSubscribed A configured platformConfigured A platform built to the jobBuilt
What you are buying A theme, and a monthly subscription to the tool that runs it. A mainstream content system, set up and themed by a developer. A structure, a design system and a build shaped to one company's job.
Cost to start Lowest, by a wide margin. Middle. Most of it is configuration and content. Highest. It is a build.
Cost to keep A subscription, and it rises when you add features. Hosting, plus a developer for the parts the theme did not plan for. Hosting, plus the monthly arrangement if you want one. Both declinable.
Time to the first live page Days. Weeks. Longest, because the structure is agreed before anything is designed.
Where the structure comes from The theme decided it before you arrived. The theme, adjusted where it can be. The decision your customer is making.
A page type nobody planned for Fit it to an existing block, or do without. A developer, and sometimes a plugin. It is a template, and the next one like it is cheaper.
Speed on a mid-range phone Whatever the theme ships with. Often heavy, and not yours to fix. Improvable, within the limits of the theme. A budget agreed in the scope and measured before launch.
Accessibility Whatever the theme ships with, and it is rarely tested. Improvable, and often improved after somebody reports a barrier. Designed to WCAG 2.2 AA, tested with a keyboard and a screen reader, recorded in the launch checklist.
Connecting to your CRM, ERP or booking system A built-in connector if one exists, and a workaround if not. A plugin, which somebody has to keep current. Built, validated during scoping, confirmed in writing before signature.
A second language, authored rather than translated A translation layer bolted on the side. Possible, and usually a field on the English page. Each language a first-class version, with its own URLs, research and structured data.
When it is the right answer Five pages, no logins, no connections, nobody publishing on a schedule, and a date that cannot move. A content site with a familiar shape, a competent developer to hand, and no unusual requirements. The site has a job, it has to connect to something, and somebody will own it after launch.

The verdict, including where it goes against us

If the site is five pages, nothing logs in, nothing connects and nobody is going to publish on a schedule, buy the template. It will be live next week, it costs a fraction of anything we would build, and a platform would be us selling you craft the job does not need. We will tell you that on the discovery call, before anything is built.

If nobody on your side will own the site after launch, the subscription is the better buy. This one is uncomfortable and it is true. A subscription product keeps working without an owner, because somebody else is maintaining it. A platform built for one company needs a person whose job includes it, and where that person does not exist the site is quietly out of date in a year and the money is gone. The question is not whether you can afford the build. It is whether anyone is going to feed it.

A built platform earns its cost in a narrow place, and it is worth naming exactly: the site has a job somebody can state in a sentence, it has to connect to at least one system you already run, there is enough content or enough publishing ahead that templates pay for themselves, and somebody owns it on Monday. That is the whole case. The discovery call is where we find out whether your project is in it, and we would rather find out there than in month three.

Block 12

What a Canadian buildhas to be designed around.

A public website is the surface a regulator, a customer and a procurement officer can all reach without asking anyone's permission. These are the requirements this service is designed around, and the line between what we build and what your counsel decides.

  • AccessibilityWCAG 2.2 AA, plus AODA and the provincial equivalents, and the Accessible Canada Act where it applies

    What we design forEvery path completed with a keyboard and no mouse, every page read end to end by a screen reader, contrast and text sizing checked on the surface we shipped rather than in the design file, reduced motion honoured with a still version that still communicates, and forms whose errors are readable and recoverable.

    What we document for your counselThe test results per template, the standard tested against, and the date. So a barrier report can be answered with a measurement, and so a procurement questionnaire can be answered from a document instead of from memory.

  • PrivacyPIPEDA, Quebec's Law 25, and the provincial private-sector statutes where they apply

    What we design forA stated purpose for every piece of data the site collects, the smallest set of fields that does the job, consent captured before analytics and marketing scripts run rather than after, retention set per record type rather than left at a default, and a cookie preference surface that actually changes what loads.

    What we document for your counselWhat the site collects, where it is stored, which processors see it, who internally can reach it, and how long it is kept.

  • LanguageQuebec's Charter of the French Language, where the business operates there

    What we design forPer-language authoring as a first design decision rather than a translation pass at the end, which means the content model, the layout, the URLs and the search research are built for it from the start. Customer-facing text is authored per language, including the forms, the error messages and the automated acknowledgement.

    What we document for your counselWhich surfaces are authored per language and which are not yet, so the gap is a list somebody owns rather than a surprise.

  • Electronic messagesCASL, for anything the site sends or subscribes somebody to

    What we design forConsent and its basis recorded against the record at the moment it is given, no pre-ticked boxes, an unsubscribe that works in one action, and the identification and contact information the legislation asks to be present in a commercial message.

    What we document for your counselThe consent basis per subscriber and the send log, which is the evidence the legislation asks you to be able to produce.

  • Where the data livesAnd which processor sees it

    What we design forThe hosting region, the form processor, the analytics processor and the email processor named in the scope before the build, chosen rather than inherited from whatever a vendor defaults to.

    What we document for your counselEach processor, what it sees, the region it sees it in, and what changes if you move region later.

HUREAL designs to a standard, tests against it, and documents what was built. The determination is your counsel's or your privacy officer's to make, and a vendor offering to make it for them is offering something they do not have. Our own conformance target and how to report a barrier are on the accessibility page.

Block 13

Questions peopleactually ask.

  • How long does it take?

    The timeline is fixed in the scope you sign before any code is written, so the honest answer for your project comes in the written proposal after the discovery call. What moves it is content and integrations. What does not move it is page count: twenty service pages on one template is a smaller job than five pages that are each unique.

  • Who writes the content?

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

  • 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, in every language you publish, and your team is trained on it before launch day rather than sent a document after it.

  • What moves the price of a build?

    How many systems it connects to, how many languages are authored natively, whether customers log in, and whether anything has to be migrated. Not how many pages you want. The full list of what moves a price, and in which direction, is published on the pricing page.

  • Will we lose our rankings when we move?

    Not if the redirect map is done properly, and it is a named step in the launch phase rather than a task somebody remembers. Every old URL points at its new home, internal links are updated to match, and the map is a deliverable you can audit. A rebuild that skips it is the fastest way to lose traffic you already had.

  • Do we have to move off our current content system?

    Often not. The system holds the content and the templates decide what a visitor experiences, so in a lot of projects the sensible scope is new structure, design and templates on what you already run. If a move really is warranted, you get the reasoning in writing before you decide.

  • What does it cost?

    The build price is set after the discovery call and sent in a written proposal, because an honest number needs the scope. Fixed scope, fixed price, fixed timeline, agreed before any code. Not hourly, and not a range that moves once work starts.

  • How do we check that you can actually do this?

    Four ways, all of them before you sign anything. The method is published phase by phase. The fourteen launch checks are published by name. This page is the sample: open it on a mid-range phone, tab through it with a keyboard, turn on reduced motion. And phase one produces a written scope, price and timeline that is yours whether or not you continue.

  • Who owns the site, the domain and the content?

    You do, all of it, from the first commit rather than at handover. Hosting, domain, repository and analytics are in your accounts under your admin access, and we do not hold your passwords. If you stop working with us, nothing has to be handed back.

  • What happens after launch?

    A monthly arrangement if you want one: improvement, content, monitoring and reporting, with what changes next decided by what the measurement said. It is cancellable, and the site stays yours and keeps running either way.

  • Can we launch in English and add French later?

    Yes, and it costs less that way than retrofitting a translated layer, because the structure is built for a second language from day one. Adding it becomes authoring and review rather than a rebuild. Whether waiting is a good idea for your market is a different question and we will answer it honestly.

  • We already have a marketing agency. Does that work?

    Yes, and it is common. We are usually brought in for the strategy, the platform, the connections and the measurement, and we write down who owns what so nothing sits in the gap. Keep the people who know your market.

Block 14

Three servicesnext to this one.

Block 15

Where thismatters most.

Four sectors, and the reason in each

  • Construction and trades

    The site is read twice and by two different people: by a client checking whether you are the size of company that can carry their job, and by the crew you are trying to hire. Both decide in about four seconds, and they are looking for opposite things.

  • Manufacturing and distribution

    Buyers research specifications for weeks before anyone picks up a phone. Whatever is not on the site gets asked on the call, and whatever is not on the site and not on the call gets assumed.

  • Professional services

    The site is the first meeting, and it happens without you. What a firm publishes about how it works is the only evidence a prospect has before they choose whose number to dial.

  • Real estate and property

    Listings, availability and documents change faster than anybody can maintain by hand, and the site is judged on whether what it shows is true today.

Read on this topic

Every article about this service lives under one index, so a reader who wants depth has one place to go rather than a tag cloud.

The websites and platforms index

Everything we have published on this

Block 16

Two ways to start.Both end with a document you own.

Book a discovery call

For when you know you are building something. A discovery call with the people who own the outcome. We agree the job the site has to do, who it is for, the decision they are making, what it connects to, and how you will know it worked. Afterwards you get a written proposal: a scope, a price and a timeline you can sign or walk away from.

Book a discovery call

Request a performance audit

For when you want the evidence before the decision. We look at what you have against the job you want it to do, and give you a prioritised plan with the arithmetic attached. The document is yours either way.

Request a performance audit

Know what you are building? Book a discovery call. Not sure where the problem is? Request the audit. If neither is right for you, we will say so, and tell you what is.

Not ready for either? Talk to the demonstration in your browser for three minutes, or paste your own address and hear it answer as your business. No form and no booking, and the transcript arrives by email a minute later.

Hear it work

What every HUREAL engagement commits to, in writing

  • A fixed scope, price and timeline, agreed before any code is written.
  • A working build, reviewed at every phase, running in your own accounts.
  • Full ownership of the code, the content and the data, with admin access from day one.
  • A named contact who is accountable for the work.
A material study photographed in bright daylight. A tall fan of clear turquoise glass fins rises on the right of the frame with a polished pearl silver ribbon curving through it, standing in a shallow film of still water. The left of the frame is empty pale mint.

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

HUREAL / Material studies