Product update2 min read

Making growth simpler

How we rebuilt Avara around three questions — what should I improve, what is being done about it, and is it working — and moved everything else out of the way.

StatusIn development

Earlier versions of Avara were organized around how Avara works inside: intelligence, strategy, actions, activity, integrations, autonomy, diagnostics. Every one of those screens was accurate. Together they asked a person to understand our architecture before they could answer a simple question about their own website.

So we rebuilt the product around the questions people actually bring to it.

Three questions

  1. What should I improve? — _Overview_ and _Opportunities_
  2. What is being done about it? — _Work_
  3. Is it working? — _Results_

_Ask Avara_ answers follow-up questions from Avara's own records, with links to them. Everything else — the detailed intelligence, every finding, strategy versions, the full activity log, integrations, coding-agent access, autonomy and diagnostics — moved under _Settings_, and is reached in context from the record that needs it. Nothing was deleted; it simply stopped competing for attention.

The sidebar went from nine entries to six.

One next step

The Overview now leads with a single recommended next step, chosen in a fixed order: fix what is blocked or failed verification first, then review work waiting for your approval, then hand approved work to a coding agent, and so on. It is always a link into the exact record that needs you.

One shared picture

The most important change is one you should never notice. Overview, Opportunities, Work, Results and Ask Avara now all read the same view of a website's state, built from stored records only. No page counts or labels things its own way, so the number of items waiting for you is the same number everywhere — which, before this change, it was not always.

Work moves through stages that say who has to act next:

  • Needs your review — Avara prepared it and needs your decision.
  • Waiting for agent — approved, waiting for a connected coding agent.
  • In progress — an agent has taken it on.
  • Awaiting verification — reported done; Avara is checking the live site.
  • Verified — Avara saw the change on the live site itself.

A report from an agent is never shown as verification. Verified work then waits for performance data before Avara says anything about results.

Where this stands

This restructuring is complete in the codebase and covered by our test suite, and it has been exercised end to end on a test website. Avara is in closed beta, and we have not yet verified it with beta customers, so we describe it here as in development.