Lenses

Most tools organise around a dashboard or a chat window. A dashboard freezes one shape of one question. A chat window forgets. A Lens is neither: it is a written contract between a business concept and an analytical purpose, and it is the thing that gets reused.

What a Lens holds

A subject. The business concept it reasons about: customers, sites, assets, orders.

An intent, in plain language. What you are trying to understand. This governs everything that follows.

Indicators it chose itself. Given the intent, Nexyron selects the signals your data can actually support, rather than asking you to specify fields you would have to go and look up.

A feasibility judgement. Whether the population is large enough for the result to mean anything. A Lens that cannot answer says so instead of returning a confident number from too few subjects.

Its evidence. The series and aggregates behind every claim it makes, kept with the result.

Its output. A written report, a model you can score against, and reusable signals the next Lens can build on.

Why this is the unit

It survives. Ask a good question once and you keep it. Run it again next month against current data without rebuilding anything.

It explains itself. Because the evidence travels with the result, a Lens can be handed to someone who was not there when it ran, including an auditor.

It compounds. The signals one Lens establishes are available to the next. An analytics capability that gets better as you use it, rather than resetting with each request.

It is honest about its limits. The refusal to run on insufficient data is deliberate. It is what makes the results you do get worth acting on.

Typical Lenses

Churn and lapse risk. Revenue and demand forecasting. Utilisation monitoring. Delay and failure root cause. Conversion anomaly detection. Customer journey analysis.

Each is a subject plus a purpose, which is why the list is open-ended rather than a menu of built-in reports.