Skip to main content
Use cases, not features. Whatever the business problem, it takes one of three shapes: an agent, an agentic workflow, or a full-stack portal. Start from the shape that fits, then combine them. Most enterprises start on SaaS for speed and move to self-hosted when criticality or sovereignty require it.
Every example below comes with a prompt. Connect the Prisme.ai MCP to VS Code, paste the prompt into Claude Code, GitHub Copilot, or Codex (and use the starter SPA for portals), then review and version in Git.

Agents

Talk to it, it acts. A conversational agent that reasons over your knowledge, calls tools, and acts on your systems.
Agents: people ask through Chat, Store, Teams, or a website embed; the agent (LLM routed across providers, skills via tools and MCP, knowledge via RAG and memory) reads and writes to your systems via connectors and MCP; governed and traceable, with answers sourced and human approval on sensitive actions.
A secure, multi-LLM assistant for daily work, grounded on internal content, no data leakage.
Instant, sourced answers on leave, payroll, and mobility.
Real-time, cited answer suggestions for support agents.
The agent gathers data across CRM, news, and your systems, and prepares the meeting and the pitch.
Query your warehouse in plain language and get exact figures.

Agentic workflows

Headless automation. A process that runs on its own (endpoint, event, or schedule), calls agents where judgment is needed, and acts on your systems. No UI required.
Agentic workflows: triggered by an endpoint, an event, or a schedule; the workflow runs steps and conditions, calls agents where judgment helps, and asks for human approval on sensitive steps; it updates CRM, ERP, and ticketing, generates reports, and notifies; governed and traceable end to end by correlation ID.
Monitor the ledger, detect anomalies, propose corrective entries for approval.
After a meeting, draft the CRM notes, update SAP, refresh Power BI.
Match invoices to purchase orders, flag exceptions, route approvals.
Resolve tickets end to end with policy-based fixes.
Assemble an AI Act or DORA dossier from evidence.
Triage SIEM/EDR alerts and propose containment for approval.
Extract fields from documents, validate, and route.

Agentic portals (full-stack)

The highest-value shape: a React front-end, agents, and workflows in one custom portal that replaces a patchwork of siloed tools, connected to your systems and governed.
Custom portals: your systems and data connect via connectors and MCP into a portal built in Builder (React front-end, agentic workflows, agents, Knowledges and Collections), delivered to your channels, governed and traceable, deployed on SaaS or self-hosted.
A React front-end over your CRM, with agents that draft, summarize, and update records.
Ticket queue with agent triage and resolution, connected to your service desk.
Usage map, regulatory watch agent, and audit-ready reporting in one place.
Onboarding, scoring, and contract-risk agents over your procurement systems.
One front-end over apps that do not talk to each other, with workflows replacing manual copy-paste.
Aggregate alerts, enrich with agents, drive response on approval.
Connect entities across your data and let agents navigate and answer over the graph.
The prospecting brief and the post-meeting updates, in one UI.
Stand a portal up fast for an event or a crisis cell, retire it when done.

Custom portals & apps

The full theme: one pattern, many portals, plus the economics that make it pay off.

One need, three shapes

The same business need can take any of the three shapes. A Sales assistant can be an agent (prepare the prospecting brief), an agentic workflow (update CRM, SAP, and Power BI after each meeting), or a full portal (a sales cockpit that does both, with a UI). You pick the shape per use case, on the same governed foundation.

By sector

Regulated industries most often deploy self-hosted, for data residency and sovereignty.

Next steps

Adoption & Governance

Frame and prioritize your first use cases

Builder

The tool every one of these use cases is built with