Method

How does Hevaris work?

Every piece of work follows the same seven steps, from gathering facts to a single report at the end. Work is done with AI tools, and a person checks every claim against facts the client can support.

Last updated

The seven steps

  1. Facts first, with a written do-not list

    Before anything is built, the facts are gathered and a written do-not list is agreed: the claims, words and promises the work must never contain.

  2. Prompts reviewed before a build session

    The instructions for each build session are read and checked before the session starts.

  3. Diffs and screenshots reviewed before every commit

    Every change is checked line by line, and in the browser, before it is saved to the site history.

  4. One commit per task

    Each task is saved on its own, so any single change can be read, questioned or reversed without disturbing the rest.

  5. High-risk pages held for review

    Pages that make claims about price, scope or outcomes are held back from publication until they have been reviewed.

  6. One consolidated report per batch

    Each batch of work ends with a single report: what changed, what is unresolved and what needs a decision.

  7. Contradictions surfaced, not silently overwritten

    When two sources disagree, the disagreement is reported for a decision. Neither version is quietly chosen.

What does this mean for me?

A claim only goes on a page if you can support it. Where we cannot check something, it is marked for you to confirm rather than filled in. See what we don't take for the work we decline, and SEO & AI-search audits for what we do offer.