About HUREAL
We build the softwarebusinesses run on.
HUREAL designs, builds, and runs the software a business operates on, from the website and the platform behind it to agentic systems that carry a whole process to the end.
The first thing HUREAL built was HUREAL. This site is held to the same published launch checklist every client build is held to, and the measurements are published.
HUREAL / Material studies
The company
It started with a conditionrather than an ambition.
HUREAL is a Canadian company. It designs, builds, and runs the software a business operates on, from the website and the platform behind it to agentic systems that carry a whole process to the end.
A company has no business selling this work until it has done it for itself.
So the first thing HUREAL built was HUREAL. This site passes the same published launch checklist every client build passes, and the results are published. Test it on a phone. Tab through it with no mouse. It is the only sample there is.
The founding team leads the work and stays accountable for it. An AI workforce carries much of the execution, through quality gates every deliverable passes before anyone sees it. That is not a flourish. It is why one fixed price, agreed before any code, buys depth that usually arrives on an hourly rate.
A client ends up holding all of it. The domain, the accounts, the code, the content, the data, admin access from day one, and documentation written for a developer who has never met us. If they leave, nothing has to be handed back.
How the work is produced
An AI workforce,with a line in it.
A large part of the production work, drafting, generation, checking and testing, is done by systems HUREAL built and runs. What comes out of them is not a deliverable until a person has taken it. The boundary is the same one we build into a client's system, drawn here against ourselves.
What the workforce carries
- DraftingFirst versions of copy, markup, structured data, queries and tests, produced against a written brief rather than against a mood.
- GenerationArtwork, diagrams and variants, produced to a written specification with the specification kept beside the output.
- CheckingContrast, heading structure, link targets, alt text, spelling, and the build rules this site is made of, run again on every change.
- RepetitionThe same check on every page, every time. This is the part people stop doing properly somewhere around page forty.
- ResearchReading source material and extracting what it actually says, with the source kept attached to the sentence it produced.
What stays with a person
- The scopeWhat is being built, what it costs, and when. Agreed in writing, signed, before any code.
- The judgementWhich of three defensible options is right for your business. No gate scores that, and no gate is asked to.
- The claimEvery sentence that asserts something about you or about us. Nothing about a client is written by a system and shipped unread.
- The gate itselfA gate produces a measurement. A person decides what to do about the measurement, including deciding it does not matter.
- The relationshipThe call that matters is made by the people accountable for the work, never by a system.
That is why the production model is a statement about cost structure rather than a slogan. The execution is carried; the decisions are not delegated. A company with sixty billable people cannot adopt it without dismantling how it earns, which is the only reason it is worth writing down.
What this does not mean. It does not mean nobody reads the work. Nothing on this site and nothing in a deliverable goes out unread, and the people who scoped your project are the ones who sign it off. It also does not mean you ever talk to a system instead of to a person. The systems are how the work gets made. They are not who you deal with.
Published in advance
What HUREALwill not do.
Published here rather than discovered on a call. Each one of these costs us work, which is the only reason any of them is worth reading.
-
Certify compliance
HUREAL designs to a standard, tests against it, and documents what was built. The determination belongs to your counsel or your privacy officer, and a vendor offering to make it for them is offering something they do not have.
-
Guarantee a ranking or a result
Nobody controls a search engine or an assistant. What is published is the method and the monthly measurement, including the months where something did not work.
-
Build a system with no person in it
Every system HUREAL builds has a gate in it. If removing the gate is the requirement, HUREAL is not the right builder, and you hear that on the first call rather than in week six.
-
Discount to close
The scope changes or the price does not. A price that moves under pressure was not a real price, and both sides know it at the moment it moves.
-
Sell the larger thing
Where the answer is smaller than the project you asked about, that is the answer you get. Most businesses need a better website before they need an app, and we will say so and build the website.
-
Hold your passwords
Accounts are opened in your name, admin access is yours from day one, and nothing sits in a HUREAL login waiting to be handed over at the end.
A company that publishes what it refuses has told you more about its judgement than any description of itself could, and it is a great deal harder to take back.
Questions people actually ask
The answersbefore the call.
-
Who are HUREAL?
A Canadian company that designs, builds, and runs websites, digital platforms, mobile products, and agentic systems for Canadian businesses. The founding team leads the work, an AI workforce does much of the execution, and every deliverable passes quality gates before it reaches you.
-
What does "an AI workforce does much of the execution" actually mean?
It means a large part of the production work, drafting, generation, checking, and testing, is done by systems we built and run, supervised by the people who scoped your project. It is why we can carry the depth of work we do at the price we do. Every deliverable passes the same gates before it reaches you, and the people who scoped your project are accountable for it either way.
-
How do you price work?
Fixed scope, price, and timeline, agreed before any code is written. Not hourly, and not a range that moves once work starts. Every price is set after the discovery call and given in the signed proposal, because an honest number needs the scope.
-
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. Not how many pages you want.
-
What if we already have a developer or an agency?
Keep them. We work alongside in-house and external teams, and we write down who owns what so nothing sits in the gap. We are usually brought in for the strategy, the platform, the connections, and the measurement.
-
Can you work on a site or system you did not build?
Yes. That is what the performance audit is for, and improvement work on an existing system is a normal engagement. Where the honest answer is that rebuilding costs less than repairing, we will show you the arithmetic rather than assert it.
-
Do you do accessibility and privacy work?
We design for the WCAG 2.2 AA standard and test against it, and we design privacy, consent, and data handling into the build. We document what we built so your counsel or privacy officer can make the determination. We do not make that determination for them, and we would be cautious about a vendor who offered to.
-
Do you write French, or translate it?
Write it. A French page is authored by a person who writes French, from the same brief, with its own question research. Translation is not a substitute and Quebec customers can tell.
-
How fast can you start?
It depends on what is already scoped, and current availability is the honest answer we will give you on the call rather than a number on a page that goes stale.
-
What happens if we stop working with you?
Nothing has to be handed over, because you already hold all of it. The domain, the accounts, the code, the content, and the data are yours, admin access has been yours since day one, and we do a final documentation pass so whoever picks it up next starts informed.
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. Afterwards you get a written proposal: a scope, a price, and a timeline you can sign or walk away from.
Book a discovery callRequest 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 auditKnow 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? We publish what we would otherwise explain twice: plain answers to the questions that come up in every scoping conversation. There is no sales email attached to any of it.
Read the InsightsWhat 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.
Software you own from day one.
Admin access from day one, not at handover.
HUREAL / Material studies