Coruve

Roadmap

What’s coming next

Coruve is an analyst, not a wall of dashboards — so what comes next is more analyst: better reasons, and proof that the fixes worked. This page lists only what is not built yet, and it puts no dates on work we have not started.

Next · the verified analyst

Plannedno date yet

What a fix would be worth

A finding gains a line saying what closing the gap it found would be worth a month — as a range, with the assumption printed in the same sentence, and nothing at all when the sample is too thin to say honestly.

Plannedno date yet

Proof that a fix worked

The Impact ledger already records every case you closed. What it cannot yet do is the arithmetic: measure the move against what that weekday would normally have brought, and print one number for the whole account — how many suggestions you acted on, and how many actually verified.

Plannedno date yet

Coruve does the digging first

Each night the top finding gets a short chain of follow-up checks — a bounded number of reads, every one shown with the numbers behind it — so the Brief arrives with the obvious questions already answered.

Plannedno date yet

One click from a finding to the thing it implies

The alert, the segment or the annotation a finding is clearly asking for, created from the finding itself and already filled in.

Plannedno date yet

Findings that name a cause

Tell Coruve when you deployed, or let the uptime monitor you already run send its incidents over, and a finding can say what happened just before the numbers moved. Signals in — Coruve will never page you.

Plannedno date yet

Which AI assistants reach your revenue

Coruve already separates AI-assisted visits from human ones. The next question is which of them end in an order — stated with the small-sample wording those numbers deserve.

Plannedno date yet

Findings ranked by what people actually act on

Which kinds of finding get used, and which get dismissed, nudging the order they appear in — by one step at most, with the method written down so you can check it.

Later · by request, not by date

Exploringon request

One Brief across all your sites

Today every property has its own Brief, which is the honest shape for most owners. One Brief that reads them all is written down and unbuilt — and it moves when enough people running several sites ask for it, not on a quarter we picked.

Exploringon request

Findings into the tools you already use

A webhook when a finding or an alert fires, so a case can land in your issue tracker or your chat. Coruve would send the signal and stop there — running your tracker is not our job.

Exploringon request

More than two segments side by side

Segment comparison ships today, capped at two at a time. Lifting that cap is a real request and nothing about it is decided yet.

Already shipped is on the changelog — this page only lists what isn’t built yet.

Missing something? Ask for it.

Tell us what you need and we reply the same day. If it fits what Coruve is — an analyst for your site, not a suite of tools bolted to it — it ships in up to 72 hours. Some things we deliberately don’t build, and that same reply will tell you which and why.

Request a feature

Build with an analyst that keeps getting sharper

Roadmap | Coruve