Use Case Catalog

Twelve sub-categories. Over sixty concrete use cases. One predictive database underneath.

Browse by capability. Each use case shows the outcome, the demo that showcases it best, the Aito operator(s) it uses, and the vertical(s) where it commonly lives. The catalog is the index β€” for code examples and full query patterns, follow the "Read more" link into the docs. For the live application, follow the demo tag.

What is a predictive application? Read the architectural argument β†’

Building an agent? See the same operators in a live agent's toolbox, benchmarked β†’

Search
Vertical
Operator
Showing 63 use cases
analyze

Analyze

Pattern discovery, calibration, forecasting, segmentation. The decisions a user makes after seeing the data β€” and the patterns the data already contains.

Pattern Discovery

Co-occurrence, lift, persona-affinity, statistically discoverable AND predictive patterns. Find what's already in the data.

Pattern Explorer screenshot

Pattern Explorer

Co-purchase lift patterns, each shown only when its 95 % interval clears 1. In the generated PetNord data, dog dry food and dental treats go in the same basket 3.17Γ— more often than chance.

πŸ›’ E-commerce_relateE-commerceCross-vertical
Rule Mining screenshot

Rule Mining

AND-rules for GL code and approver, mined live with _relate from the fields known when an invoice arrives (vendor, category, vendor country, amount band), as rule candidates. A person promotes a candidate with sign-off and an audit-trail entry; the ERP demo can also dismiss one.

πŸ“‹ ERP🧾 Accounting_relateAccountingERP
Supplier Intelligence screenshot

Supplier Intelligence

Spend leaderboard plus delivery-risk discovery via _relate: which suppliers are over-represented among late deliveries, with the late rate and lift behind each, mined from the purchase history.

πŸ“‹ ERP_relate_searchERP
360 KPI Dashboard screenshot

360 KPI Dashboard

Pick a segment and every KPI arrives diagnosed: the rate, its root causes via _relate scoped to the segment, and the lever via _recommend, with the rate among customers who already have it.

πŸ€– Agent🐘 SQL🏒 Company AI_predict_relate_recommendCross-vertical
Market-Basket Rules screenshot

Market-Basket Rules

Directional A β†’ B basket rules with confidence, lift, and support, mined live by one _relate per anchor category. No precomputed rule table, no Apriori batch job.

πŸ›’ E-commerce_relateE-commerceCross-vertical
Override Mining screenshot

Override Mining

Every human correction is logged, and _relate over the override log surfaces the emerging patterns: which values people keep correcting to, and what drives the correction. Each pattern is a rule candidate.

🧾 Accounting_relate_searchAccountingCross-vertical
Confounder-Checked Root Cause screenshot

Confounder-Checked Root Cause

The distributor channel looks guilty for churn until climate is held fixed; conditioned, it drops out of the top drivers. A null-control card that finds no lever ships beside it, on purpose.

🐘 SQL_predict_relate_recommendCross-vertical
Exhaustive Driver Map screenshot

Exhaustive Driver Map

Every field Γ— value Γ— slice cell swept with relate() and ranked by how far its lift moves under conditioning: 827 cells from 18 statements. Interactions surface without anyone going looking for them.

🐘 SQL_relateCross-vertical
Prediction Over a Knowledge Graph screenshot

Prediction Over a Knowledge Graph

Accounts, contacts and deals are linked records, and one query reads the links both ways and predicts across them: an account's industry judged only by who works there, or a deal's odds from a fact that lives on its account, with $why naming the evidence.

🏒 Company AI_queryCross-vertical

Forecasting

Predicted quantities at query time. No separate forecasting model to maintain.

Demand Forecast

ERP: _estimate of units_sold per product from the season and last year's sales for the same month, measured on six held-out months against same-month-last-year and the trailing three-month average. E-commerce: _estimate of next month's units per SKU on Supply, seasonal category peaks via _relate on Patterns, and held-out accuracy via _evaluate on Model checks. No separate forecasting model.

πŸ“‹ ERPπŸ›’ E-commerce_estimate_relate_evaluateERPE-commerce
Project Success Probability screenshot

Project Success Probability

For every active project, _predict of six outcomes (makes money, team stays happy, customer stays happy, lands on time, the thing works, opens a door) and a combined reading from outcome_score, plus the properties of the work that move each outcome across completed projects from _relate, so the portfolio review starts from the projects most at risk.

πŸ“‹ ERP_predict_relateERP
Opportunity Scoring screenshot

Opportunity Scoring

A deal sheet from your own history: win odds with $why, effort in person-days, and reference projects, the numbers an LLM or a gut call would otherwise invent.

πŸ€– Agent_predict_estimateCross-vertical
Utilization Forecast screenshot

Utilization Forecast

Per-consultant load from active assignments, next to each person's historical norm and the share on projects at risk, plus _predict of the role and allocation_pct a person typically takes on a given project type. Capacity planning without a separate forecasting model.

πŸ“‹ ERP_predict_searchERP
Price Estimation screenshot

Price Estimation

Fair-price band per SKU from its realised prices with outliers flagged, and _estimate of units, revenue and profit at a candidate list price, answered only within the prices the product has sold at.

πŸ›’ E-commerce_estimate_predictERPE-commerce
Stockout & Overstock Risk screenshot

Stockout & Overstock Risk

Stock and lead times checked against next month's predicted demand for every SKU: a reorder queue ranked by revenue at risk, and the overstock that ties up capital.

πŸ›’ E-commerce_estimate_predict_searchE-commerceERP
Revenue Outlook screenshot

Revenue Outlook

Scheduled revenue per month next to predicted revenue, from _predict of on-time and on-budget delivery for every active project, with $why behind each.

πŸ“‹ ERP_predict_searchERP
Pipeline Close Likelihood screenshot

Pipeline Close Likelihood

Every open deal carries a probability of closing, learned from the deals that closed before and shown beside the rep's own typed-in probability, so the deals where the two disagree stand out.

🏒 Company AI_predict_queryCross-vertical
assist

Assist

Search, recommendations, smart forms, conversational. The human stays in control; the system boosts speed and accuracy.

Recommendations

Cross-sell, similar items, bought-together, for-you. All from the same _recommend operator.

Bought Together screenshot

Bought Together

Cross-sell ranked by co-purchase lift: category pairs on Patterns, and per product "often in the same basket" in the Shop. Mined live from order data β€” not from a curated rule.

πŸ›’ E-commerce_relateE-commerce
For You screenshot

For You

Personalized tile rankings per shopper. Same query, different per customer: _recommend with the household's pets, the month, the cart and the shopper's own history as context.

πŸ›’ E-commerce_recommend_predictE-commerce
Win-back Ranking screenshot

Win-back Ranking

At-risk customers ranked by the spend at stake, each with the offer and the action that bring the most back after their cost. Drives outreach prioritization with an expected return per customer.

πŸ›’ E-commerce_recommend_predict_estimateE-commerce
Next Best Outreach screenshot

Next Best Outreach

_recommend the channel and angle that most likely books the meeting for this buyer, with the predicted meeting rate attached. Optimisation, not description.

πŸ€– Agent_recommendCross-vertical
Cart Completion screenshot

Cart Completion

Given what is already in the basket, the products this shopper is most likely to add: the Shop's "Picked for you" re-ranks with _recommend, with the cart's categories as context, as items go in.

πŸ›’ E-commerce_recommendE-commerce

B2B Cross-Sell

Pick a product and get what is bought with it: _relate over past order baskets ranks the products that co-occur with it by lift, with the counts behind each pair.

πŸ“‹ ERP_relateERP

Conversational

Natural language interfaces and agent stacks backed by predictions, not by an LLM-only stack.

Agent Toolbox screenshot

Agent Toolbox

Give an LLM agent Aito ops as tools: it predicts win odds, estimates effort, queries references, recommends the outreach that books the meeting, then drafts an action that waits for a person to approve it. Grounded numbers an LLM can't invent.

πŸ€– Agent_predict_estimate_query_recommendCross-vertical
Agent Tool Shortlisting screenshot

Agent Tool Shortlisting

Shortlist the tools an agent should consider with one calibrated _predict over its own call history, and hand the LLM ~17Γ— fewer prompt tokens for its pick.

πŸ€– Agent_predictCross-vertical
AI Assistant screenshot

AI Assistant

Conversational shopping or support interface backed by predicted product/answer rankings. The LLM frames; the predictive database decides.

πŸ› Grocery_recommend_query_predictCross-vertical
Question Answering screenshot

Question Answering

Predict canonical answers from a prompt corpus. Question-shaped input, predicted-answer output, calibrated confidence to decide auto-vs-route-to-human.

πŸ› Grocery_predict_queryCross-vertical
Help Drawer screenshot

Help Drawer

In-app help articles ranked by _recommend against click history (CTR-ranked, like product recommendations). Users see what other users on the same page clicked.

🧾 Accounting_recommendCross-vertical
Company AI Copilot screenshot

Company AI Copilot

A chat agent over one linked customer view: it reads KPIs, diagnoses them with $why and _relate, recommends the lever, and drafts a play that waits for a human to approve it.

πŸ€– Agent_predict_relate_recommend_query_estimateCross-vertical
automate

Automate

Categorization, routing, anomaly detection, multi-field prediction, optimization. Calibrated confidence decides what auto-processes and what routes to human review.

Categorization & Routing

The decisions where the user picks from a menu and the right pick is statistically determined by surrounding fields.

PO Queue Routing screenshot

PO Queue Routing

Every purchase order arrives with predicted account code, cost center, and approver, sorted into Rule, Aito and Review rows; the coding on Rule and Aito rows can be accepted in bulk.

πŸ“‹ ERP_predictERP
GL Coding screenshot

GL Coding

Predicted GL code and approver per invoice with $why factor decomposition. The core of predictive AP.

🧾 Accounting_predictAccountingERP
Ticket Classification screenshot

Ticket Classification

Auto-route tickets via _predict on description. Confidence-tiered β€” high auto-routes, mid suggests, low routes to manual.

πŸ› Grocery_predictCross-vertical
Confidence-Gated Handoff screenshot

Confidence-Gated Handoff

Calibrated confidence as governance: high $p auto-resolves, a borderline read goes to the LLM with Aito's shortlist, a low one goes to a human with the tentative answer attached, and sensitive intents are gated regardless. The number decides who acts.

πŸ€– Agent_predictCross-vertical
Tag Prediction screenshot

Tag Prediction

Auto-classify content (products, tickets, documents) into a multi-label taxonomy. Saves manual labeling effort with calibrated confidence per tag.

πŸ› Grocery_predictCross-vertical
Approver Routing screenshot

Approver Routing

Predict the right approver from invoice or PO content. Same pattern as GL coding, applied to the person dimension instead of the account dimension.

πŸ“‹ ERP🧾 Accounting_predictAccountingERP
Payment Matching screenshot

Payment Matching

Each bank transaction matched to the open invoice it pays. A payment that quotes an open invoice's reference is matched by plain lookup; the rest go to _predict of invoice_id across the link from bank transactions to invoices, with $why showing which name, description, and amount tokens carried the match.

🧾 Accounting_predict_searchAccounting
Invoice Line Matching screenshot

Invoice Line Matching

Supplier invoice lines matched to the catalog SKU they refer to: _predict of sku across the link to products returns a ranked shortlist with reasons, scored live against held-out truth.

πŸ“‹ ERP_predict_searchERPAccounting
Ticket Resolution: Predict vs LLM screenshot

Ticket Resolution: Predict vs LLM

The same support ticket resolved by two engines side by side: two _predict calls for the intent and its parameter, with $p and $why, against a live LLM call, with latency and tokens measured on every run.

πŸ€– Agent_predictCross-vertical