A foundation for your enterprise AI

Your AI. Your way.

We bring working capabilities, tested approaches and a solid foundation. Together, we build a solution for your business.

The shared groundwork is already in place. With you, we solve what is specific to your business.

Your data and systems
SharePointMicrosoft 365Czech data boxesYour ERPScans and photos
we pick what fits
AI//BRO capabilities
Company knowledge with citationsOCRAgentsAutomationsAPI connectors
we integrate and operate
A result in your work
Answer with sourcesWord reportTable recordBrief for a colleague
Illustrative scenario. Your goal determines the scope.
From input to useful work

From your data to a useful result

Three examples of how the existing capabilities work together. An input, a few readable steps, a tangible output.

Find the answer. Check the source. Create the output.

Available
Input
Supplier agreement.pdf
Framework agreement, 14 pages, article 11 Termination.
Internal purchasing policy.docx
Chapter 4 Deadlines and responsibilities.
Question: “What notice periods apply to these suppliers?”
Work
  1. Read both documents and split them into passages.
  2. Find the clauses on termination and notice periods.
  3. Compare the agreement’s terms with the policy.
  4. Prepare a short answer and a Word report.
Output
The framework agreement’s notice period is 3 months to the end of a calendar month [1]. The policy requires internal approval 30 days before notice is served [2].
[1] Supplier agreement, art. 11.2 · [2] Purchasing policy, ch. 4.3
DOCXNotice periods overview.docx
Report with numbered sources
Capabilities involved Company knowledgeCitationsAgents for multi-step workExcel, Word, PowerPoint and PDF

Illustrative scenario. Citations and automated review help inspection; they do not guarantee factual or legal correctness.

From an email attachment to a structured record.

Available
Input
Shared M365 mailbox · receipts@company.example
New message with attachment receipt-0412.jpg
Beran Stationery Ltd.
12 Oct 2026 · 14:08
Total 1,248.00 CZK
Work
  1. Receive the message from the shared mailbox.
  2. Extract fields from the receipt photo (OCR).
  3. Apply the configured company procedure.
  4. Write to a table, or call a permitted API.
Output
SupplierDateAmountCurrency
Beran Stationery Ltd.12 Oct 20261,248.00CZK
Example integration
Expense created in the time-tracking system · API response: 201 Created
Capabilities involved Microsoft 365Scans and photosCompany procedures and templatesAutomationsAPI connectors

Illustrative scenario. Payment approval stays with people; the solution performs no financial authorisation.

Czech data boxes as part of your business process.

Available

Connect Czech data boxes to your business processes. Turn messages and attachments into clear input for the next step.

Input
Data box message · Request for additional documents
Sender: Lipová Municipal Office (illustrative)
Attachment: request-2026-0917.pdf · 2 pages
Work
  1. Receive the message and attachment from the data box.
  2. Summarise the content and the documents requested.
  3. Prepare a clear brief for the next step.
  4. Hand it to the responsible colleague.
Output
Brief for: Jana Vlková, operations
The office requests two more documents for application no. 2026/0917: a register extract and proof of fee payment. The attachment states a deadline that needs to be verified.
Capabilities involved Czech data boxesCompany knowledgeAgents for multi-step work

Illustrative scenario. Sending messages, calculating legal deadlines and delivery tracking are not part of this scenario.

Architecture

One approach. Put together your way.

Users, identity, models and your business systems stay the same in both arrangements. The only difference is how many roles the integrated AI//BRO covers and how many we compose from your tools.

All together. AI//BRO as an integrated foundation, adapted to your operation.

Users
Personal assistanttopics, chat, feedback
Automated tasksschedule, webhook, mail
Your identity
Entra ID sign-inroles and service identities
AI//BRO · integrated foundation
Interface and topicschat, agent jobs, feedback
Agents, automations and chained stepsrun state, user questions, history
Procedures and agent definitionsversions, templates, explicit updates
Model and tool accessmodel providers, MCP client, OpenAPI operations
Roles, audit, limits and costsactivity records, spending overview
Knowledge and sourcesingest, search, citations, OCR, transcripts
Language models
Azure OpenAI · OpenAI · Bedrock · Geminioutside your deployment boundary
Local Ollamainside your environment
Business systems
SharePoint, M365, file storage
Czech data boxes
Your ERP and CRMintegration tailored to your environment
Gmail, IMAPpersonal inbox rules and results
Personal authorisation today. Personal M365 connections work within the signed-in user’s permissions.

Your way. We select the parts you need and build around your tools — from Git to gateways.

Users
Personal assistantyour chat or portal
Web, chat, feedback
Orchestration
Git repositoryagents, processes, workflows
Orchestratorstate and escalation
Authentication
Your identityusers and services, identity propagation
Gateway · composed for you
LLM gatewaymodel calls
Traffic gatewaytool calls
Tool cataloguediscovery
AI//BRO capabilities and principleswhere they fit: agents, knowledge, connectors
audit, limits, spending visibility
Language models
Providers of your choice
Tools and business systems
MCP serversadapters for selected systems
ERP · CRM
DMS, records
Knowledge base, policies, wiki
OBO in your tailored solution. The user’s identity flows all the way to the target system.
Existing AI//BRO capability Your existing system Composed and integrated for you Planned
Scope

We use what fits your needs

Some solutions use the whole AI//BRO foundation. Others use selected capabilities or build on your tools using proven principles. Your goal determines the scope.

All together.

AI//BRO as an integrated foundation, adapted to your operation.

Personal authorisation today.

Your way.

We select the parts you need and build around your tools — from Git to gateways.

OBO in your tailored solution.

We use existing capabilities, tested approaches or both. Together, we define the architecture, integrations and operation.

Operation and control

You know where things run and who can access what

Your environment

Deployed with Compose or Helm in your environment, with your branding.

Model choice

Azure OpenAI, OpenAI, Bedrock, Gemini or local Ollama. Data sent to a cloud model leaves your deployment boundary — we say so openly.

Roles, audit and costs

Access rules, activity records and model cost tracking within the configured retention.

Isolated calculations

Scripts run in an isolated sandbox, separately from API and MCP calls, which go through the backend.

Working together

We start with one real process

01

Understand

We pick one real process and its owner. We look at the data, systems and desired outcome.

02

Select

We compare your existing tools, reusable capabilities and the integration work required.

03

Verify on your data

We choose one process and verify the result with your data. We assess processing time, corrections needed and source traceability.

04

Integrate and operate

The design also defines who operates, maintains and takes over the solution.

Getting started

What shall we start with?

Bring a concrete use case. Together, we will look at the data, systems and desired outcome and choose a useful first step.

Let's discuss your use case

No subscription, no checkout. We agree on a first process and what we will observe.