Request a discovery call
  1. Home
  2. Insights

Insights

We publish whatwe would otherwise explain twice.

Plain answers to the questions that come up in every scoping conversation, written once and filed under each area we build in.

Every post answers one question a buyer actually asks. The answer is in the first eighty words, and the depth is under it.

Request a discovery call Start with an audit

Everything published

Filed by topic,newest first.

One topic for each area we build in. A post sits under exactly one of them, and every topic has an index of its own that a reader can subscribe to the same way they would a section of a newspaper.

The topics

One index per service, and nothing outside them.

There is no tag cloud and there are no categories that exist only here. A topic is one of the things HUREAL builds, so a reader who wants depth on a subject ends up on the page that sells it, and a reader who arrived at the page that sells it has one place to go for depth.

  • Websites and Platforms

    The site is the first thing a stranger judges and the system that catches what it brings in. What makes one work, what makes one expensive, and which of the two a redesign usually is.

  • E-commerce and Marketplaces

    Selling online stops being a storefront question the moment there are account prices, subscriptions, or a second seller. This index is about that moment and what it costs to arrive at it unprepared.

  • Web Applications and Portals

    The work a customer could do themselves at nine at night, and the arithmetic that decides whether building that is cheaper than answering the phone about it.

  • Mobile Products

    Most businesses need a better mobile website before they need an app. How to tell which one you are, and what changes about the build if the answer is the app.

  • Integrations and Data

    Two systems bridged by a person and a spreadsheet, and everybody knows which spreadsheet. What that costs to keep doing, and what it costs to stop.

  • Agentic Operating Systems

    Agents that finish work rather than answer questions, the line that decides what they are never allowed to do, and how a business tells the difference between a workflow and a wish.

  • Search and AI Visibility

    Being found by a search engine and being cited by an assistant are now two different jobs. Both, with the measurement and its date attached to every number.

  • Ongoing support

    What happens to a build after launch day, which is where most of its value is either kept or quietly lost.

Guides and long form assets are a later addition to this section and no route is published for them until one exists. A menu that promises a page that is not there is the fastest way to teach a reader that the rest of the menu might be aspirational too.

How this is published

Five kinds of post, and nothing outside them.

A post that does not fit one of these five is not written. The constraint is the quality mechanism: each type has a fixed structure and a fixed evidence requirement, and a piece that cannot meet the requirement is cut rather than softened.

The five post types
Type What it is What you can do with it
Measured read A measurement we ran, with the date it was run, the method written out, and the raw data published beside it. Check the number yourself, or run the same method against your own site.
Regulatory explainer One Canadian obligation, what it means for a website, what changes in the build, and what belongs to your counsel rather than to us. Arrive at your lawyer with the question already written correctly.
Decision guide The question a buyer asks at the shortlist moment. What drives the cost, what to ask a supplier, and what a bad answer sounds like. Brief any supplier, and tell whether the answer was any good.
Sector brief One sector: what the website has to do there, the objections that come up, and the systems it has to connect to. Skip the first meeting where somebody explains your own industry back to you.
Answer post One question, answered completely, in the words it was asked in. Read it in two minutes and stop looking.

Scroll the table sideways to read it.

Two parts of this are never automated, and they are the two that matter: which question gets answered, and whether the answer goes out. Both are a person's decision, and the second one is a signature in version control rather than a tick box in a tool. Research, drafting, checking and publishing are the parts a system can carry.

The standing rules

Four rules, and you can hold us to them.

True of every post published here

  1. It answers one question a real buyer asks: in the title, in the first eighty words, and then in full.
  2. It is about the work, never about a named company, ours or anyone else's.
  3. Every factual claim carries its source in the sentence it appears in. A claim that cannot be sourced is cut rather than softened.
  4. A post that could have been written about any company is deleted rather than published.

If a post breaks one of those, it is the kind of thing we would want to hear about. The contact page reaches a person.

Newsletter

New insights, by email.

Start with the problem you need to solve.

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

One process creates too much manual work.

Workflow Opportunity Sprint

We map it, then define what a connected system should do next.

Explore the Sprint

My website is underperforming.

Website Performance Audit

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

Explore the audit