A material study photographed in bright daylight. A tall radial fan of clear turquoise glass fins opens like a wheel on the right of the frame, a polished pearl silver ribbon curving down out of its centre and along a pale reflective floor. The left of the frame is empty pale mint.
  1. Home
  2. Services
  3. Agentic Operating Systems
  4. The three modules

Part of Agentic Operating Systems

Three modules,sold inside a build.

A module is a fixed piece of an agentic operating system, with a scope that does not move and a price that is fixed in the signed scope. It is a line on a project, not a product on a shelf.

Each one has a fixed scope, so its price is a commitment written into the signed scope. If delivery runs over, that is ours to absorb.

Book a discovery call Hear one working first

Ready to scope a build? Book a discovery call. Want to hear what one of these actually sounds like before you speak to anybody? Open the demonstration.

HUREAL / Material studies

Block 01

What these are,and what they are not.

Three modules. Each one has a fixed scope written down before anything is built, a price that does not move, and an owner at the end of it who is you. They are bought as part of a build, which is the only arrangement in which they are worth buying.

What a module is

A defined piece of work inside a project: one job, done end to end, with the boundary written before the first line of code. It runs in your own cloud accounts under your admin access, it is yours the day it ships, and the vendor keys are in your name.

The price is the commitment. A fixed scope is what makes a fixed price honest, and the two are written into the same signed document or not at all.

What a module is not

It is not a subscription, not a seat, and not a tier. There is no catalogue to browse, no add to cart, no free trial, and no monthly agent price list, because a monthly agent price list would contradict the promise made on every other page of this site: fixed scope, fixed price, fixed timeline, agreed before any code.

It is also not a product you can buy on its own. A module with no build under it is a worse version of something you can already buy configured, which is the subject of block 06.

There is no marketplace. There is no shelf.

What there is instead is a short list of things an agent can do well when it is standing inside a system we built, and one rule that decides whether your case is one of them. Everything below is that list and that rule.

The three, at a glance

Two fixed-scope modules, and one that comes with the build.

Each one is priced per build and inside the build, in the signed scope. Having HUREAL run and tune Follow-Up or Front Desk afterwards is optional, sits under Care and Optimization, is declinable, and is cancellable.

  • Follow-Up Fixed scope

    Quotes and inquiries acknowledged in minutes and chased on a schedule you set, until somebody answers or asks you to stop. Optionally run by us afterwards.

  • Front Desk Fixed scope

    Your phone answered by something that can look the answer up in the system we built for you. Sold only when it passes the rule below. Optionally run by us afterwards.

  • Site Answer Included with every build

    Your site answering a real question out of your own pages, with the source shown, and part of every website build rather than an extra.

How every price on this site is set Hear one working

Block 02

One question decideswhether we sell you one.

It is asked out loud on the call, before scope and before price, and the answer is allowed to end the conversation. Publishing it here means you can answer it yourself tonight and save the call.

The rule

Asked on the call, and published here so you can answer it without one

Does this agent need to read or write something only a system we built can reach?

If the answer is yes

  • It needs the order record, the account price, the booking calendar, the portal entry or the document set that exists because we built the thing holding it.
  • We sell it, as a fixed-scope module of that build, priced in the signed scope, delivered inside the project rather than beside it.
  • You own it. The module, its configuration and its data sit in your accounts under your admin access from the first commit, so there is nothing to hand over at the end.
  • Nobody else can do this at any price, which is the only honest reason to buy it from us rather than from a product.

If the answer is no

  • We do not sell it, and that is not a negotiating position. It holds when the client is keen, when the budget is there, and when the work would have been easy.
  • You want the phone answered and nothing looked up. That is a solved category with good products in it, and block 06 says so plainly and tells you what to go and buy.
  • You want one rule fired on one trigger. That is automation. It costs less than anything we would build, it will not drift, and it is usually configured rather than made.
  • You want outbound calls made. That one is a refusal rather than a referral, and it is also in block 06.

The rule has to survive a client who wants to buy, which is the only condition under which a rule means anything.

Why the rule is drawn there and not somewhere more convenient. An agent that only needs to hear a caller and take a message is a product you can buy, configured, this afternoon. We would be selling you a more expensive version of it, and the only thing we would be adding is our invoice. An agent that has to look up whether your order shipped, quote from your account price book, or write into the portal your customers log into is a different object: it needs the system, and the system is the part we built. That is where we are the right supplier, and it is the only place we claim to be.

Module 01

Follow-Up.Nothing you quoted goes quiet.

Every inquiry and every quote you send is acknowledged within minutes, referencing what was actually asked, and then followed up on a schedule you set until the person answers or tells you to stop. Chasing is the single most expensive thing a busy office forgets to do, and it is the smallest thing worth handing over first.

What the module does

  • Watches the inbox and the site formsand acknowledges every inquiry within minutes, in your words
  • Creates the record in your CRMwith the source, the owner and the time it arrived
  • Drafts the follow-ups on your scheduleand sends them, or holds them for approval, whichever you chose
  • Stops the moment there is a replyor an opt out, on the same day, without being asked
  • Reports weekly on what is still outstandingso the list of unanswered quotes is a document rather than a worry

What stays with your people

  • The priceit never negotiates and never discounts
  • The dateit never commits your company to one
  • The judgement callanything it cannot ground in your own documents is handed over, not guessed at
  • The relationshipit chases a quote, it does not run an account
Who it is for. Anyone who sends quotes with nobody chasing them, which is most trades, distribution and professional services offices in a busy month. What you provide. Mailbox access or a forwarding address, the quote template, the three facts that belong in a follow-up, your opt out list, and one decision: approve first, or send automatically. What it is delivered in. 5 to 8 business days, where the real work is the CRM connection and the consent audit rather than the writing. The consent part is not optional. Canada's anti-spam law applies to every message this module sends: consent on file, your identification in the message, and a working unsubscribe in all of them. That is a product requirement here, not a setting somebody remembers to switch on. What it is and what your counsel should be asked is a question for them, not for us. Price. Fixed, as a line in the signed scope of the build it sits inside, owned by you and running on your accounts. Optionally, HUREAL runs and tunes it afterwards, under Care and Optimization, declinable and cancellable.

Module 02

Front Desk.It answers, and it can look things up.

It answers your phone, identifies the caller, finds the thing they are asking about in the system we built for you, books into the real calendar, and escalates anything ambiguous to a named person. An answering service cannot do the middle part of that sentence, at any price, because it does not have your system.

What the module does

  • Answers, and says in its first sentence that it is automatedevery time, to every caller, with no setting to turn that off
  • Identifies the caller and finds their recordin the system we built, not in a summary of it
  • Looks up the thing they called aboutorder status, an account price, a booking, a portal entry
  • Books into the real calendarthe one your people are already looking at
  • Escalates anything ambiguous to a named personand the escalation is in the log with its reason

What stays with your people

  • Quoting a priceit does not, in any circumstance
  • Promising a dateit does not commit your company to anything
  • Anything about a balanceaccount and payment conversations go to a person
  • Clinical, legal or financial advicenever, regardless of how the question is phrased
  • Calling anybodythe module is inbound only. See block 06
Who it is for. A HUREAL build client whose phone rings for things the system we built already knows the answer to. If that sentence does not describe you, this module is not for sale, and block 06 is the honest version of why. What you provide. A number to forward, the business facts, an escalation number, and the system access, which by construction we already have. What it is delivered in. 3 to 5 business days on top of the build, plus a supervised first week in which every transcript is read by a person. Recording. Transcript only. No audio is retained, which removes most of the question rather than answering it cleverly. Price. Fixed, as a line in the signed scope of the build it sits inside, owned by you. Optionally, HUREAL runs it afterwards, under Care and Optimization.

The published limit on this module

HUREAL does not yet put a voice agent in a clinic. Doing it properly needs Canadian region infrastructure and a health information posture that we have not built, and the vendor stack underneath has no documented data residency option we would be willing to put a patient call through.

Back office work that touches no health information is a different question and we will happily scope that one. When the clinic route is genuinely ready, this paragraph changes. Until then it is a limit rather than a hedge, and it is here so you meet it on this page instead of three weeks into a procurement.

Module 03

Site Answer.Included with every website build.

It answers questions on your website using only what is on your website, shows the page each answer came from, and hands over to a person the moment it does not know. It ships with every Websites and Platforms build, as part of the build's scope.

What the module does

  • Answers out of your own pagesand shows which page, in the answer, every time
  • Says that it does not knowwhen it does not, rather than producing something plausible
  • Hands over to a personwith what was asked, so nobody has to ask again
  • Reports weekly on what it could not answerwhich is the most useful content plan a company will ever be handed

What stays with your people

  • Anything not on the siteit does not improvise, extrapolate or fill a gap
  • Price, availability and commitmentsunless the page it reads already says so in public
  • Deciding what goes on the site nextthe report tells you what people asked, you decide what to answer
Why it is part of the build. It costs very little to run, it makes the build more valuable, and selling it as a separate line would be charging for the cheapest part of the work. It is also the one module on this page a visitor can verify for themselves by using it. What you provide. A site with the answers actually on it. Where the answer is not written down anywhere, the first useful project is writing it down, and that is a content job rather than an agent job.

Block 06

What we will notsell you.

Two things, published here rather than explained on a call. Both of them are revenue we could take and choose not to, and both hold when the client is keen and the budget is real.

Outbound calling agents

We do not build agents that telephone people who did not ask to be telephoned. Not as a module, not quietly inside a larger build, and not as a favour to a good client.

Outbound solicitation by telephone sits inside Canada's unsolicited telecommunications rules, and an agent dialling strangers on your behalf puts your company inside that regime rather than ours. We are not interested in becoming good at it, we will not be the reason it happens to your brand, and there is no price at which we would take the work.

Inbound is a different thing entirely, and Front Desk is inbound only by construction rather than by policy.

A standalone receptionist

If all you need is the phone answered, you do not need us.

There are several good Canadian products that do exactly this. They are self serve, they are configured in an afternoon, several of them store their data in Canadian regions and handle French, and they are sold as an inexpensive monthly subscription. Read the current price on the product's own page before you buy.

We would be selling you a more expensive version of something that already exists and already works. The only thing we would be adding is our invoice. Buy one of those instead. If it would help to have the shortlist, ask on a call and you will get it.

Why both of these are on the page rather than in a drawer

Each refusal costs us money we could have taken, and that is the entire reason they are worth publishing. A company that will not tell you when to buy from somebody else is a company you cannot trust when it tells you to buy from it.

The rule in block 02 is the same instrument pointed at the same problem. If the agent does not need the system, the agent does not need us, and we would rather you found that out on a page at eleven at night than four weeks into a procurement.

Two more things were considered and deferred rather than refused, which is a different verdict and is recorded as one: a booking module for clinics, which needs the infrastructure named in block 04, and a tender watching module for construction, whose demand we have not yet tested on real buyers. Neither is sold, and neither is promised.

Block 07

How they are governed,and what stays human.

Every module is a slice of the same drawing, and the largest object in it is the line, because the line is the largest object in the promise. What a module may do unattended is a written decision made before the build, not a setting somebody changed on a Friday.

Scroll the drawing sideways to read it.

The whole service, drawn. A module is one lane of it, and the gate is the same gate.

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. The boundary is written before anything is built.

    What the module takes over and what stays with your people is a document, agreed and signed before the first commit. Nobody discovers the boundary after launch, because the boundary is a deliverable rather than a behaviour.

  2. Every module has a list of things it may never do.

    Role, tools, limits and escalation rules, per module, in writing. The lists in blocks 03, 04 and 05 are the published versions of exactly that document, which is why they read as flatly as they do.

  3. Anything sensitive waits at the line.

    The gate is one line with one opening and a person standing in it. Nothing crosses because a model sounded confident, and nothing crosses on a timer. You release it, or you do not.

  4. An answer that cannot be grounded is handed over.

    Answers come from your documents, your records and your price list, with the source shown. Where the module cannot ground an answer in one of those it marks it and gives it to a person, and the handover is in the log.

  5. Everything it did, and why, is written down for a person to read.

    The audit trail is plain language, exportable, and kept whether or not anything went out. Two of the most useful entries in any log are the two where the system declined to act.

True of all three modules, on every engagement

  1. It runs in your own cloud accounts, under your admin access, from the first commit.
  2. The limits are yours to tighten without asking us.
  3. The off switch works without calling us, and it is tested before launch day rather than configured and assumed.
  4. What is held, where, by which processor and for how long is documented for your privacy officer.
  5. Your data is not used to train a model, and that sits in the contract rather than only on this page.
  6. A named person is accountable for it, and alerts point at them rather than at a shared inbox.

Block 08

What happenswhen one gets it wrong.

It will. The interesting question is not whether a system makes a mistake, it is where the mistake lands, how quickly it is found, and who is holding it when it is. Three mechanisms answer those three, and all three are in the scope rather than in the sales conversation.

01

It runs in shadow first

The module does the work alongside your people, who see everything and approve everything, until the output is trusted. The wrong answers happen in the period where they cost nothing, which is the only period in which a wrong answer is useful.

02

Sensitive work waits at the gate

Anything that leaves the building, commits you, or touches money waits for a person in a queue that person actually works in. A mistake caught at the gate is a draft somebody deleted rather than an email a customer received.

03

Everything is in a log a person can read

Written for a person rather than for an engineer, exportable, and kept whether or not anything went out. A mistake is findable instead of mysterious, which is the difference between fixing it this afternoon and arguing about it for a week.

And if it is worse than that, you stop it. The off switch works without calling us and it is tested before launch day. The run arrangement, where you have one, is monthly and cancellable, and the module, its configuration and its data stay in your accounts and keep working either way. Accountability is a name, not a mailbox. Monitoring for drift and for performance runs after launch, and the alert points at a person who is answerable for the module rather than at a shared inbox nobody owns.

Questions

Questions peopleactually ask.

  • Can I buy a module without a build?

    No. A module needs to reach something only a system we built can reach, and with no build there is nothing for it to reach. What you would be buying is a worse version of a product that already exists, so we would rather point you at that product. Site Answer is the exception in one direction only: it is included with a website build, never sold on its own.

  • Is there a monthly price for an agent?

    No, and there will not be one. The module is a fixed-scope line item in a build. Having us run and tune it afterwards is optional, sits under Care and Optimization with its own signed scope, and is declinable and cancellable. A monthly agent price list would contradict the promise on every other page of this site.

  • Why will you not sell me an AI receptionist?

    Because good ones already exist, they are self serve, and they are sold as an inexpensive monthly subscription. If the phone just needs answering, buy one of those. We are the right supplier only when the agent has to look something up in the system we built for you, which is a thing a standalone product cannot do at any price.

  • Will you build an agent that makes outbound calls?

    No, at any price. Outbound telephone solicitation sits inside Canada's unsolicited telecommunications rules, and an agent dialling strangers on your behalf puts your company inside that regime. Front Desk is inbound only by construction rather than by policy, so there is no setting to change.

  • Who owns the module, the configuration and the data?

    You do. It runs in your own cloud accounts under your admin access from the first commit, so there is nothing to hand over at the end. The vendor accounts are opened in your name, we do not hold your passwords, and your data is not used to train a model.

  • What does the price actually cover, and what happens if it runs over?

    The scope written down before the build starts, delivered. If delivery runs over, HUREAL absorbs it, which is what makes the price in the signed scope a commitment rather than an estimate. Anything outside the written scope is a change to the scope with its own price, agreed before the work, never a surprise on the invoice.

  • Does the caller know they are talking to software?

    Yes. Front Desk states that it is automated in its first sentence, to every caller, and there is no setting to turn that off. It never claims to be a person, and it never gives clinical, legal or financial advice regardless of how the question is phrased.

  • Can we try one before committing to anything?

    Yes, and no form or booking is involved. The demonstration runs in your browser, you can talk to it, and you can paste your own address and hear it answer as your business. It is the shortest honest version of what these modules do.

Block 09

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

Book a discovery call

For when you know which process is costing you. A discovery call with the people who own the outcome. We map the workflow, ask the qualification question out loud, agree what a module would take over and what stays with your people, and work out 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, 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 the honest answer is that you do not need us, we will say so, and tell you what to buy instead.

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.

Work that finishes, inside limits you set.

HUREAL / Material studies