How it works

Signal to sign-off, step by step

The same four-step loop runs everything aiRA does — signal, plan, ask, execute. Here it is, with nothing hidden.

01Signal

A movement in your data starts the loop

aiRA reads your systems of record continuously — loyalty engine, CDP, commerce, campaign manager. When a metric drifts from its baseline, the drift becomes a signal. Sized, sourced, timestamped.

What your team seesOne card: the metric, the delta, and every system the signal was read from.

01 · signal feed · fictional
TUE 09:12 · SIGNAL DETECTED
Repeat purchases are slipping in the North region
Repeat rate 41.8% → 36.2%−5.6pp over six weeks

The dip concentrates in two store clusters and one loyalty tier — 38,400 members.

Loyalty engine CDP Commerce & POS Data warehouse
02Plan

The signal becomes a plan you can read

aiRA drafts the response: who to reach, what each cohort gets, what to expect. Every line carries its own projection. No black box — the plan reads like a brief, not a log file.

What your team seesThe full draft — each play, its audience, its offer, and the effect it expects.

02 · plan draft · fictional
Retain agent Win-back offer for the 38,400 slipping members, split by tier expect +2.1pp repeat
Convert agent Bonus-points offer for the two affected store clusters expect +1.4pp repeat
Retain agent Hold-out group set aside so the lift can be measured clean baseline
Your rule — offers above a 12% discount wait for approval
03Ask

Your thresholds decide what ships and what waits

The thresholds are yours to set — discount caps, audience limits, spend ceilings, compliance routing. Inside them, aiRA executes freely. Anything that crosses one waits, with the threshold named and the reason stated, until a person decides.

What your team seesThe approval queue — routine actions recorded, the exception held with its reason.

03 · approval ledger · fictional
Segment rebuild — five lifecycle cohorts refreshed Recorded
Offer copy variants drafted for review Recorded
16% discount proposed for the slipping tier Crosses your 12% discount cap — held until you decide Waiting for you
Send-window check — inside the audience limit you set Recorded
04Execute

The approved plan runs in your systems

After sign-off, aiRA configures the work in the stack you already run — offer engine, campaign manager, messaging channels — and pushes it live. Then it measures the result against its own projection and reports back.

What your team seesThe outcome, read against a hold-out: what ran, what moved, what it was worth.

04 · outcome report · fictional
Weeks 1–6 · after your sign-off
Win-back cohort — repeat rate40.9%
Hold-out group — repeat rate36.4%
  • 2 offers configured and pushed to the offer engine
  • Every send logged against the plan your team approved

+4.5pp repeat rate over the hold-out — the slip recovered in six weeks.

Inside step 04

One path from plan to production

Every approved plan takes the same route into your systems. Three rungs, no side doors, no manual re-entry.

  • //01Structured plan
  • //02Your sign-off
  • //03Automated execution in your systems

99.9% execution accuracy across 90+ partner organisations — 8,000+ offers at year-start, 200+ monthly thereafter.

What gets recorded

Every action, on the record

Every action lands in the audit trail — automatic or approved. Who set it in motion, what it touched, when it ran, and the rule it ran under. Nothing executes off the books.

Exceptions carry more: the threshold they crossed, the reason they were held, and the decision a person made. Held work stays held until someone says otherwise.

How we handle security →

Try it

Click through it yourself

The homepage demo runs this exact loop on a fictional brand — your clicks drive every step.