A material study photographed in bright daylight. A monumental pleated wave of clear turquoise glass turns through a quarter circle, a polished pearl silver ribbon running along its crest, standing on a pale reflective floor that scatters light turquoise caustics. The left of the frame is empty pale mint.

Software for Canadian businesses

Machines do the work.People decide.

HUREAL builds the websites, platforms, mobile products, and agents a Canadian business runs on, and writes the line between the two into the build itself.

Every engagement is built in your own accounts, under your admin access, from the first commit. Nothing sits in a HUREAL account waiting to be handed over at the end. The terms of every HUREAL build

Book a discovery call Request a performance audit
How the work gets done
H1 candidates A. the boundary. The subhead carries the line.

The mechanism

How the work gets done,and who decides.

One exchange, at a parts counter, on an ordinary afternoon. It took eleven seconds and it stopped at the price.

Kevin, parts counter4:41 PM

Do we have fifty of the 3/4 inch brass elbows for the Barrie job?

HUREAL agent4:41 PM

Thirty two in Mississauga, twenty two in Brampton. I can hold fifty until Thursday.

Kevin, parts counter4:42 PM

Hold them and draft the purchase order. Dave sets the price.

HUREAL agent4:42 PM

Fifty held until Thursday. PO 4417 drafted against the Barrie job and sent to Dave for pricing.

Stopped at the price

Drafting the purchase order is the easy half. The half that matters is the agent checking its own work against the stock record and then handing the price to a person. Here is how both halves are built, in the order it happens.

01

Before any code

The scope, the price, and the date are agreed in writing before the first line of code. The document that says so is the first thing you receive, and it is the thing you hold us to.

02

In your accounts

The build runs in your own cloud accounts, under your admin access, from the first commit. Software you own from day one.

03

Agents with a line in them

Each agent is given a job and a boundary in writing: what it completes on its own, what it verifies before it hands over, and the person it hands to. Kevin's agent checked two branches, held the stock, and drafted a purchase order. Dave still sets the price.

Stock, scheduling, lookups, drafting, checking its own work against the record

Price, credit, hiring, the client relationship, anything with a signature

Nothing crosses this line without a person saying so.

What we make

Everything we build,in full.

Each one has its own page, with what is included, how it works, and what you end up with.

Every inquiry captured and handed over with its history attached.

  • Corporate and marketing websites

    Built around the decision your customer is actually making, and connected to whatever handles what happens next.

  • Content that scales

    Guides, catalogues and landing pages your marketing team publishes without waiting on a developer.

  • Content platforms and publishing

    Guides, catalogues, and knowledge bases, in a system your marketing team runs without a developer.

Websites and Platforms, in full
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.

Material study / Websites and Platforms

Most engagements start with one of these. They are built to connect, so the second one costs less than the first.

One of the eight, all the way down

An assistant answers the question.An agent finishes the job.

It books the meeting, updates the record, sends the confirmation, and tells you it is done. That difference is most of what we do. Agentic Operating Systems is one of the eight above. Here is the whole of it, at full size, before you click anything.

Scroll the drawing sideways to read it.

Ten steps, one of them yours. The gate is the largest object in the drawing, and the only dark one, because it is the largest object in the promise.

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, and it is never used because a section needed weight.

What you already run

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

Agentic Operating Systems, in full

A material study photographed in bright daylight. Dense layers of clear turquoise glass bend around a bright aperture, pearl silver inlay running between them, standing in a shallow film of water that ripples away to the left. The left of the frame is empty pale mint.

What ownership means

Built in your accounts. Yours from the first commit.

Not handed over at the end, because there is nothing to hand over. The domain, the code, the data, and the admin access were in your name before the first review.

HUREAL / Material studies

The product, not a picture of one

Both halves of that,on a screen.

Two surfaces from the system every engagement includes. The first is the cloud console in the first week of a build. The second is the agent console, where finished work waits for a person.

Cloud console, week one

your-company/production Region Canada, Toronto

People with access

The owner was set when the account was created and has not changed since.

3 people
  • YouOwner

    Everything. Billing, transfer, deletion, and every key.

    Owner
  • Your operations leadAdmin

    Deploys, logs, and environment settings. No billing, no transfer.

  • HUREALCollaborator

    Deploys, logs, and error reports. No billing, no transfer, no deletion.

Remove is enabled on our row, and it always is. Nothing here is held by a HUREAL login, so removing us changes who can reach the project and nothing else about it.

Agent console, an ordinary weekday

your-company/agent/approvals 4 waiting

Waiting for you

Finished, checked against the record, and not sent.

  • 03:41

    Quote drafted for a counter enquiry

    CheckedPriced from the current price list. Stock confirmed at two branches. Terms copied from the customer record.

  • 04:02

    Reply drafted to a website enquiry

    CheckedEvery sentence traced to a page on your own site. Nothing added from anywhere else.

  • 04:12

    Invoice prepared against work order 1180

    CheckedLine totals match the work order. Tax checked against the province on the record.

  • 04:15

    Refund requested, above the queue limit

    HeldOver the refund limit set on this queue. It stops here until a person decides.

    Held
Nothing crosses this line without a person saying so.

How an engagement runs

Five steps.You can stop after any of them.

Every one of them produces a document you own.

  1. 01

    Discovery call. Start with the scope, or start with the evidence.

    Book a discovery call if you know what you want built: a conversation with the people who own the outcome, followed by a written proposal. Request a performance audit if you want the evidence first.

    How long
    One call, then the written proposal. The audit is delivered in days to set business days.
    Your people
    The people who own the outcome.
    You end up with
    A written proposal with a scope, a price, and a timeline you can sign or walk away from, or the audit document, which is yours either way.
  2. 02

    Fixed scope, price, and timeline. Signed before any code.

    Not an hourly rate, not a range, and not a change order six weeks in. The number you sign is the number, and the things it does not include are listed next to the things it does.

    How long
    Set in the signed proposal.
    Your people
    One read of the document, and one conversation about what it excludes.
    You end up with
    A signed scope, price, and date, and a written list of what is not in it.
  3. 03

    Built in the open.

    Working software on a review schedule agreed at the start, not a reveal at the end. If something is going to be late, you hear it from us in the review, with the new date and the reason.

    The build runs in your own cloud accounts, under your admin access, from the first commit.

    How long
    Set in the signed proposal, with the review schedule agreed in it.
    Your people
    One reviewer at each 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

    Launched against a published checklist.

    The same fourteen checks every time, listed by name on this site rather than summarised as quality assurance. Speed on a mid range phone on a cellular connection, keyboard and screen reader, contrast and text sizing, reduced motion, every language read by a person who writes it, forms tested to the inbox and to the CRM, tracking end to end, redirects, structured data, crawler access for search engines and for AI crawlers, security, a restore actually performed, alerting pointing at a person, and your own team signed in to your own accounts before launch day.

    How long
    The checklist runs against the finished build. Fourteen checks, the same fourteen every time.
    Your people
    Your team signs in to your accounts and confirms admin access before launch day.
    You end up with
    A launch record against fourteen named checks, and the accounts already in your name.
  5. 05

    Run, monthly, cancellable.

    Improvement, monitoring, content, and reporting. Stop whenever you want. The system stays yours and keeps running.

    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 monthly report: what happened, what changed, what it produced, and what did not work.

What moves the price of a build: how many systems it connects to, how many languages are written natively, whether customers log in, and whether anything has to be migrated. What does not move it: how many pages you want.

Read the whole method, including the fourteen checks

The third door

An agent, answering as a business,from that business's own website.

Ask it the three things a buyer asks in the first ten minutes of every call, or give it a website and listen to it answer as that company.

Scripted demonstration. It runs inside this page, reaches no network, and sends nothing anywhere.

idle

    Answers are grounded in named sources. Anything the system cannot ground goes to a person.

    The full demonstration, and what each part of it can do yet

    Two doors

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

    Book a discovery call

    For when you know you are building something, or you know which process is costing you. A discovery call with the people who own the outcome. We map what the system takes over first, what stays with your people, what it connects to, and what it pays back. 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, compare it to two comparable companies in your market, and give you a prioritised plan with the arithmetic attached.

    Request a performance audit

    If neither of these is right for you, we will say so, and tell you what is.

    A material study photographed in bright daylight from a very low camera. A far fan of clear turquoise glass fins runs away to the right along a long silvery horizon, reflected in a pale sea glass floor. The left of the frame is empty pale mint sky and floor meeting at the horizon line.

    Software you own from day one.

    HUREAL / Material studies