- Customer
- Demo customer
- Order date
- 12 March 2024
- Items
- 4 desks
AI that moves work forward.
Agents that find information, process documents and carry out tasks in the systems you use.
With defined access and human oversight.
AI agent
What would you like to solve?
Find answers in your documents
Answers with sources and the right access.
See how
An internal assistant finds relevant passages in your procedures and documents. People can open the source and check the answer.
About AI knowledge searchProcess incoming requests
From a request to a clear next step.
See how
The agent gathers context, summarises the request and prepares a suggestion. You decide what can happen automatically.
Explore the workflowCheck before moving forward
Find missing details and discrepancies before approval.
See how
Checks reveal missing fields and conflicting information. The workflow stops when there is not enough evidence.
About security and responsibilityOne order. The whole workflow.
Follow an order from intake through human approval.
Order EX-1048
Awaiting clarification- Customer
- Demo customer
- Items
- 4 desks
- Delivery address
- Missing
- Order status
- Delivery requested
The order has arrived.
The demo customer requests delivery of four desks. No delivery address was provided.
See sources, tools and log
Sources in this example
- Order EX-1048 · 4 desks · delivery requested
- Demo customer · no saved delivery address
Simulated tools
Read order · read customer record · check required address · prepare draft · human approval · show follow-up
Your steps in the demo
No steps performed yet.
From first version to reliable operations.
- 01
A focused first version
We find one useful place to start.
- 02
Connected to your systems
We define data flow and the right access.
- 03
Tested with your team
We try, measure and improve.
- 04
Operations and development
We agree on ownership and next steps.
Products and services we operate
Which data do you need to start?
An overview of which documents, systems, and data types exist, who owns them, and who will use the solution. The actual data is shared only after access, storage, and controllership are agreed.
How is security handled?
Aprex clarifies data types, access, logging, providers, and human control points before production-near use. Sensitive data should not be sent uncritically to models or third parties. Read more on the security page and in the guide on privacy and GDPR in AI projects.
More questions about AI
Should we start with chatbot, RAG, or agent?
Start with the workflow, not the technology. If the problem is knowledge retrieval, RAG often fits. If the system must perform bounded actions, agent workflow may be right. If the goal is dialogue and guidance, a copilot may be enough. The guide on AI agent versus chatbot shows the practical difference.
What does an AI solution cost?
Scope drives the work: number of workflows, data sources, integrations, and approval needs. An internal assistant against one document base is different from agents across several systems with operations from day one. Aprex gives no fixed price without seeing the case; the guide on what an AI pilot costs explains what drives scope and what to send for a concrete assessment.
Can AI connect to existing systems?
Yes, when systems have APIs, databases, exports, webhooks, or other safe integration points. Integrations should be scoped during the pilot so risk and value are clear.
What should a pilot prove?
A pilot should prove one or more concrete effects: less manual work, fewer errors, faster case handling, better documentation, or better access to internal knowledge. The guide on what a 2-6 week AI pilot should include describes scope, measurement, and go/no-go.
What happens after the pilot?
The pilot ends with go or no-go based on measured results. On go, operations, further development, and ownership are agreed before the solution is extended. On no-go, the business keeps documented learning about what did not hold.
Can we start without clean data?
Often yes, if the scope stays narrow. The pilot can be limited to one data source that is good enough, while cleanup of the rest is planned in parallel. Aprex maps data quality early so the scope matches reality.
In depth: from data sources to operations
What is a practical AI solution?
A practical AI solution is connected to data, workflow, and responsibility. It can retrieve context, suggest actions, summarize documents, fill reports, answer internal questions, or trigger the next step in a process. Value appears when the solution works with the systems and routines the business already uses. That means the AI part rarely stands alone: around it you need integrations that open the right data sources, rules that bound what the system may do, and control points where humans approve before anything has consequences. Aprex designs solutions with a clear line between assistance (AI suggests, humans decide) and actions (the system executes within agreed bounds with full logging).
RAG and internal copilots
RAG connects language models to the company's own documents, routines, and data sources. Aprex can build internal assistants that answer with relevant context, link back to sources, and stay within agreed data boundaries. This fits knowledge work, support, operations, training, and documentation. A good RAG solution stands or falls on source quality: documents must be current, access-controlled, and structured enough for the right passage to be retrieved. Aprex therefore starts by mapping which sources exist, who owns them, and who should get answers from what, before the assistant itself is built. The solution should show its source evidence and flag when the sources do not support a reliable answer.
AI agents with control points
AI agents can perform bounded tasks when given clear rules and tools. They may draft content, update a CRM, check a form, notify the right person, or suggest the next action. Aprex designs agent workflows with logging, access control, and human approval where risk requires it. An agent should never get broad powers at the start: it gets one toolset, one area of responsibility, and a clear stop rule for anything it does not understand. Every run is logged with inputs, tool calls, and results, so errors can be traced and rules tightened. When the pilot shows stable behavior on real cases, responsibility can be extended step by step.
Document flow and automation
Many AI projects start with documents: reports, deviations, contracts, forms, meeting notes, or email. Aprex builds solutions that structure content, suggest text, extract fields, and pass information to the right systems without turning the whole process into a black box. Typically the flow is split into steps that can each be checked: collection, interpretation, suggestion, approval, and storage. Humans approve before drafts become official documents, and all versions are kept so it is always possible to see what AI suggested and what was actually sent. This gives the gains of automation without losing the line of responsibility.
Three concrete flows as illustration
Illustration 1: A case worker pastes in a customer request and gets a suggested reply based on internal routines, with references to the passages used. The worker edits and sends; the system learns which suggestions get accepted. Illustration 2: Photos and notes from a site visit are structured automatically into a report draft with checkpoints, gaps are flagged, and a professional approves before the report goes to the customer. Illustration 3: Incoming email is classified by type and urgency, routed to the right queue with a summary, while simple confirmations go out automatically and complex cases wait for human handling. These examples are illustrations, not descriptions of customer setups.
How we work, step by step
Step 1, mapping: Aprex walks through the workflow, data sources, users, and decision points. The deliverable is a description of one pilotable flow with clear scope, data boundaries, and measurable signs of value. Step 2, data foundation: Sources are gathered, access is clarified, and sensitive data is identified. Privacy, controllership, and minimization are agreed before production-near data is used. Step 3, prototype: A first version is built against real data types with source references, logging, and approval from day one. Step 4, evaluation: The prototype is tested with realistic questions and cases. Accuracy, time use, and error rates are assessed together with users, not just technically. Step 5, operate and improve: The solution is handed over with documentation, monitoring, and ownership, then improved against measured use before it is extended to more flows or user groups.
Typical systems and integration points
AI solutions rarely create value alone; they need context from the systems the business already uses. Typical categories are CRM and case tools for customer and case history, document storage and intranets for routines and templates, ERP and line-of-business systems for orders and master data, email and messaging for dialogue, and dashboards and reporting tools for figures. The technical interfaces are usually APIs, database connections, file and document APIs, and webhooks for events. Aprex scopes access to what the pilot needs, documents data types and storage locations, and builds so access can be tightened without rebuilding the solution.
When AI is the wrong choice
AI fits poorly where the answer must be identical every time without exception, where the data foundation is too thin or outdated to trust, or where the decision requires legal or professional responsibility that cannot be delegated to a system suggestion. It also fits poorly where the real problem is a messy process or missing data flow; then process and integrations should be cleaned up first. Aprex will say so when a request belongs in these categories, and suggest rules, better search, structured forms, or simpler automation instead. The goal is that the business ends up with the right solution, not necessarily an AI solution.
What would you like to get done?
Tell us where work gets held up. We will explore the options together.
