Knowledge lives in documents
Contracts, procedures and instructions are scattered, and the answer depends on who remembers where to look.
Private AI for businesses
I implement AI assistants for documents, complaints, service and customer support. The solution can run locally, in a European cloud or through a secure API, with access control, cited sources and human approval.
Service and B2B companies · Kraków and Poland. The first step is one process, not buying a server.
Where companies get stuck
The value comes from connecting company knowledge to real work. A chatbot without sources, permissions and measurement soon becomes another place to check by hand.
Contracts, procedures and instructions are scattered, and the answer depends on who remembers where to look.
The team spends time reconstructing answers instead of handling work that needs experience.
Permissions, retention, logs and rules of use matter more than the model name.
Local model, European cloud or ready API? It depends on data, quality and total task cost.
Concrete use cases
A good first project has repeatable input, an existing source of truth and a person who can evaluate the result.
AI collects case data, checks completeness, finds the procedure and prepares a response for approval.
An employee asks about instructions, contracts, pricing or policies and gets an answer with its source.
The system classifies the problem, proposes diagnostic steps and routes a difficult case to the right person.
The assistant prepares a reply from the offer, customer history and current commercial terms.
A new team member finds procedures faster and knows when a manager must decide.
The model extracts agreed fields, structures the case and starts a deterministic process step.
Working proof of concept
The PoC runs locally on a Mac and uses fictional cases with photos. The model prepares a summary and draft, while a separate rules engine checks the order number, required evidence, a PLN 200 limit and the user's role.
This is a process demonstrator, not a client deployment. A pilot uses an agreed sample of real cases and measures quality, time and cost.
Four ways to work together
You can order the audit, the pilot or the full integration. Scope and cost follow the process review.
01 / I do not know where to start
I review one concrete process, its knowledge sources, systems and constraints. I compare changing the process, buying a tool, using an API and running a model privately.
The result may be a decision not to build anything.
Ask about this service02 / I want to test one case
I build a small, measurable prototype over legally shared documents. Answers show their sources, respect permissions and hand uncertain cases to a person.
A pilot does not pretend to be a finished product or an automatic decision.
Ask about this service03 / The pilot works, now connect it
I connect the assistant to email, storage, CRM, SharePoint or another system. I add roles, operation logs, error handling and approval for consequential actions.
Provider dependencies and limits are clear before work starts.
Ask about this service04 / I have a system to maintain
I monitor answer quality, availability, cost and changes in the knowledge base. I update rules and models when measurement shows a real need.
Care is a separate service, not a hidden subscription.
Ask about this serviceArchitecture choice
I compare quality, data classes, volume, required latency and total operating cost. For many small businesses, a hybrid design works best: documents, permissions and rules stay local while only minimal, redacted context reaches the model.
Ask for an architecture comparisonWhat private means
Data: Local or in a European cloud, depending on requirements and cost.
Sources: Answers point to the document and passage behind them.
Access: Users see only what they are allowed to see.
Human: Critical actions and uncertain answers go to approval.
Measurement: We test real questions, errors, latency and task cost.
Handover: Code, configuration, logs and instructions stay with you within the agreed scope.
First project
We do not start with a model. We start with a question that costs time or causes errors today.
Using legally shared material, we define what the system can see and what a good result looks like.
We test a local model, a European cloud and ready APIs. Local does not always mean cheaper.
You get the pilot result, tests and the cost of keeping it running. We can continue, change direction or stop.
Questions before the first implementation
Start with the problem
Describe where time disappears today. To start, you only need the process, never passwords, API keys or customer data.