Job 05 · Get answers without an analyst

Ask your store a question.

“What sold best last week? Why did revenue dip on Tuesday?” Plain language in, plain language out — with the working shown and the action one approval away.

Lumnya consoleconfirm-gated

Today, without it

Ten dashboards, no answers.

Analytics tells you what happened. The why — and the what-now — is still homework.

A number moved and nobody can say which driver moved it
The report you need is three exports and a pivot table away
Insight on Monday, action on Thursday, relevance gone by then
Charts that describe the problem instead of proposing the fix
Questions you don't ask because asking them costs an hour

Ask in plain language

The dashboard answers back.

Lumnya reads your live store data and answers the question you actually asked — no query language, no chart-building, no waiting for someone to run it.

It shows its work

An answer you can check.

Revenue Detective decomposes a move into quantified drivers — volume, basket size, refunds, mix — so “sales dropped” becomes a list of reasons with numbers next to them. Every specialist attaches its reasoning to what it reports.

Lumnyafresh snapshot

From answer to action

Then tell it to fix the thing.

Prices down to the right variant, refunds, discount codes, customer emails, settings, triggers and FAQ — you ask, Lumnya shows you the exact change first, and nothing happens until you approve it.

multi-model engine

routine work → fast modelsrevenue-critical moments → stronger modelshigh-stakes reasoning → frontier models

router · reads the intent

Fast model

routine work

    Stronger model

    checkout · cancellation · returns

      Send one

      How it runs

      Four steps, no project plan.

      The honest edges

      What it won't do

      An honest read on the analysis you get.

      Change a price, issue a refund or email a customer without your approval
      Answer from data it doesn't have — it tells you what's missing instead
      Pretend to a certainty it can't support
      Reach outside your store's own isolated data to answer you
      Make silent changes — every action is logged with what changed

      Why it matters

      Not a chart. An answer, and then a fix.

      The gap between knowing and doing is where most stores lose the week.

      Straight answers

      Questions merchants ask about this one.

      No. It reads live store data to answer, and it can act on what it finds — price edits down to the variant, refunds, discount codes, emails, settings — with every consequential action previewed and confirm-gated.

      It tells you what it doesn't have rather than filling the gap with something plausible. Low confidence surfaces as low confidence.

      Your store's own isolated data. Nothing is pooled across merchants, and your data isn't used to train foundation models.

      Private beta

      Hand over this job first.

      Join the private beta and be first in line when Lumnya opens to your store.