Pensa
Pensa is nexmin's interpretive engine: a junior analyst that holds longitudinal memory of the client, detects patterns across sessions and proposes lines of work grounded in your theoretical framework. It does not transcribe or summarise — that is Scriba's job. Pensa reasons over those data and connects them with the history.
Pensa works as a hypothesis layer over the clinical history Scriba has recorded. It retrieves context from months or years back via RAG (retrieval augmented generation) and crosses it with the current session: it spots subtle shifts in the discourse, contradictions across sessions, and moments where the client brushes against a pattern that has appeared before. Pensa's proposals always arrive as reviewable suggestions — never as closed conclusions. The boundary between observing and interpreting is sacred at nexmin: Scriba observes, Pensa interprets, and the clinician decides. Pensa adapts to each therapist's theoretical framework (humanistic, cognitive, systemic, integrative) by reading the organisation's context and the active protocols. Where Scriba asks "what was said?", Pensa asks "what does this mean within the whole process?". That is why they are two independent engines and not one: mixing them contaminates the data with premature hypotheses, and that is exactly what a humanistic therapist wants to avoid.
Inside nexmin
Pensa is native to nexmin — accessible from the client dashboard, the sandbox and the omnibar. Every conversation leaves a trace in CortexLedger so cost and model can be audited. Pensa is not sold as a separate service: it is the interpretive copilot of the workspace.
Related terms
Last updated: 2026-06-11