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 ranked by statistical significance. Dog dry-food cross-sells to dental treats at 2.72Γ— in the PetNord fixture.

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

Rule Mining

Statistical patterns (category=telecom & gl_code=6200 β†’ approver=Timo, 15.8Γ— lift) mined live with _relate as rule candidates. In the ERP demo each candidate is promoted with sign-off and an audit-trail entry, or dismissed.

πŸ“‹ 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_relateERP
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 that moves it via _recommend with projected lift.

πŸ€– 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_relate_queryE-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: _predict units_sold blended with seasonality factors from same-month historical data. E-commerce: _estimate of next month's units for the top movers, seasonal category peaks via _relate, and held-out accuracy via _evaluate. No separate forecasting model.

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

Project Success Probability

A calibrated P(success) for every active project from _predict, and the people and project fields that move the success rate 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 via _predict allocation_pct. Capacity planning that respects role and project mix without a separate forecasting model.

πŸ“‹ ERP_predictERP
Price Estimation screenshot

Price Estimation

Fair-price band per SKU from its price history with outliers flagged, and _estimate of units sold at a candidate price.

πŸ›’ E-commerce_estimate_relateERPE-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 calibrated probability of closing, so the pipeline is weighted by P(won) instead of summed and each stage shows its predicted win rate, learned from the deals that closed before.

🏒 Company AI_predict_queryCross-vertical
assist

Assist

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

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 a confidence-gated action. 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. Holds as the catalog grows, and hands the LLM ~16Γ— fewer tokens for the same 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 read what other users with similar queries 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 β€” three confidence tiers, bulk-approve for rule-matched rows.

πŸ“‹ ERP_predictERP
GL Coding screenshot

GL Coding

Predicted GL code, approver, payment method, cost center 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 is handed 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: _predict of invoice_id across the link from bank transactions to invoices, with $why showing which reference, name, 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