Working with the agent
Insights
An insight is a dated, sourced observation about your store. It is what the agents write before anything becomes a job.
An insight answers one question: what is true about this store right now that was not obvious before?
It is not a task. It has no owner and no estimate. Some insights never become anything — they exist so that the next finding has context.
Anatomy of an insight
| Field | What it holds |
|---|---|
| Title | One sentence, in plain language |
| Source | Shopify, GA4, Click Context or Klaviyo |
| Evidence | The numbers behind the claim, with the date range and the sample size |
| Severity | How badly it appears to hurt |
| Date | When the agent observed it |
Every insight names its source. If a claim rests on 40 sessions, the insight says so, and HI Engine ranks it below anything better supported.
Where they come from
Agents run on a schedule against each connected source. Each agent looks for a different class of problem:
- Shopify — catalogue gaps, thin product pages, collections that receive traffic and convert poorly, theme issues.
- GA4 — a segment that stopped converting, a channel that changed shape, a funnel step that lost volume.
- Click Context — an element people fight with, a section nobody scrolls to, a form field people abandon, a script that throws errors.
- Klaviyo — a flow or campaign whose performance moved.
Reading them well
Two habits save time.
Split before you conclude. A store-wide conversion rate of 1.3% can be 2.0% on mobile and near zero on desktop. The second fact is the story. Insights that matter usually name a segment.
Check the sample. Two groups of visitors rarely convert at the same rate even when nothing separates them, and the smaller the sample, the more of that everyday variation looks like a real difference. HI Engine says when a difference is not statistically significant, and ranks it as a hypothesis instead of a finding.
Insights are not a queue
You do not have to clear them. Old insights stay for context and get archived when they go stale. The list you act on is Ideas.
From insight to idea
An insight becomes an idea when three things are true:
- It points at something you can change.
- The change fits on one surface — one page type, one section, one flow.
- There is enough evidence to size the change.
The agent then writes the idea, attaches the evidence, and scores it. See Ideas.
Connect Slack
HI Engine sets up a Slack channel for your store. New ideas, finished builds and test results arrive there, and you can ask the agent questions in-thread.
Ideas
An idea is one proposed change, on one surface, with evidence and an estimated monthly impact. The Ideas board is the list you actually decide on.