Skip to content
Customer analysis

Customer analysis

Agent: the customer analysis (customer_analysis), run from the Customer analysis card on Why (/simulate?tab=knowledge&card=customers). The old /market_diligence address redirects to that card (owner, 2026-10-31).

What it does

It analyses your shipper and consignee business accounts from your own records and suggests re-pricing, service-level and account reviews for a person to decide. Its jobs:

  • Cost to serve and margin. Activity-based cost to serve per account: transport, warehousing, handling, order processing, returns and other costs, as your records state them, with the margin on the orders that state both revenue and a cost.
  • Service. OTIF (on time and in full) per account.
  • Claims and disputes. Claim and dispute rates per account.
  • Payment behaviour. Days from invoice to payment, weighted by amount, and open receivables.
  • Concentration. Each account’s share of revenue, the top-three share and the Herfindahl-Hirschman index.
  • Churn signals. Order volume falling, no recent orders, service levels falling and disputes rising, each with the figures behind it.

What it reads

Your own account records: one row per order, with the account, its type, dates, revenue, activity costs, delivery outcome, claims, disputes and invoice and payment dates. A connection is marked as account records by the operator. No public data is used.

What it produces

  • Per-account figures, with the number of rows behind each.
  • Concentration figures and flags.
  • Recommended actions, each naming who decides: re-pricing (Commercial Pricing Manager), service-level and account reviews (Account Manager), payment terms (Credit Controller), concentration (Commercial Director).
  • On request, a short written summary. It phrases the figures above and adds none.

Human oversight

  • Every recommended action is a draft. Sending one for approval puts it in the approval queue, where a named person approves or rejects it.
  • FACE does not change a price, send a notice or close an account.

Model

The figures and the recommended actions are fixed arithmetic over your records. No model computes them.

The optional summary uses the general reasoning tier.

Where it runs and data handling

On the deployment’s own model plane: Runink’s shared machines on a Trial, your own cloud on Cloud and your own servers on On-premises. No outside AI service is called on any plan, and nothing leaves the deployment. See Facts shared by every card.

Guardrails

  • Business accounts only. Rows that describe an individual or a consumer are excluded and counted, never analysed.
  • Refuses to profile or track an individual person.
  • Refuses to price or segment by protected characteristics.
  • Refuses to inflate, hide or adjust cost to serve, margin, OTIF or payment figures.
  • Recommends only. It does not send notices or terminate contracts.

How to read its results

  • Cost to serve is what your rows state. Overheads your records do not allocate to orders are not in it, and a missing cost is never treated as zero.
  • A churn signal is a pattern in your records, not a prediction that an account will leave.
  • Days to pay is measured over paid invoices only.
  • Concentration is computed in the currency with the most revenue; accounts in other currencies are not added to it.

Thresholds

There are no built-in thresholds. Each is a target set for a deployment, or for your organisation by an admin under Admin → Public registries & market data. Until a target is set, the figure it would judge is shown as measured, no signal or review is raised on it, and the result names it as having no target. Every result shows the thresholds it applied.

ThresholdDefault
OTIF below which a service-level review is suggestedNo target set
Days to pay above which a payment-terms review is suggestedNo target set
One account’s share of revenue above which concentration is flaggedNo target set
Claim rate above which an account review is suggestedNo target set
Recent orders as a share of the prior window, at or below which “order volume fell”No target set
Days since the last order, as a multiple of the account’s median gap, above which “no recent orders”No target set
OTIF drop in points at or above which “service level fell”No target set
Disputed share of recent orders at or above which “disputes rising”No target set

Revenue concentration is also flagged when its Herfindahl-Hirschman index is above 1,800, the level the 2023 US DOJ and FTC Merger Guidelines call highly concentrated. That is a market measure, applied here to your revenue shares, and the flag says so.