Skip to content
Orchestron.

Service areas

All services
  • Product and platform engineering Full cycle build, MVPs, and application maintenance
  • AI, data, and hyper automation Agentic platforms, machine learning, data management
  • ERP solution services SAP, Salesforce, Oracle, ServiceNow, Microsoft
  • Integration and modernisation APIs and connectors for ERP, CRM, warehouse, ML pipelines
  • Security operations Next generation SOC, monitoring, incident response
  • Application operations Continuous application operations and enhancement
  • Infrastructure and network operations Cloud, data centres, networks, zero downtime migration
  • Digital workplace and service desk Multilingual L1, L2, and L3 support against service levels
Automated production line in a manufacturing plant AI in production Six deployments and the outcome each one produced.

Sectors

All sectors
  • Healthcare and pharma Patient facing services, records integration, applied AI
  • Public sector and infrastructure Citizen services, smart city, and major works programmes
  • Energy, utilities, and transport Smart grids, digital twin, predictive maintenance
  • Financial services Regulatory compliance, digital insurance, payment platforms
  • Manufacturing, fashion, and retail CAD, CAM, PLM, MES, ecommerce, and loyalty
  • Telco and media BSS and OSS, network operations, broadcasting platforms
Freight vehicle on a city expressway at dusk Customer service copilot Case study in logistics

Our work

  • Measured outcomes Six AI deployments and their results
  • Products and ventures Products launched with founders and partners
  • Customer service copilot Case study in logistics
  • Document classification Case study in commercial finance
  • Predictive maintenance Case study in heavy industrial
Overhead power transmission line crossing open farmland Products and ventures Products launched with founders and partners

Working with us

  • How we work Models, routes, and the path to a working pilot
  • Build. Operate. Transfer. The whitepaper on ownership without permanent dependency
  • Direct and partner delivery For clients directly, and inside consulting and integrator programmes
  • How an engagement starts Three steps from first contact to a clear decision
  • Collaboration models Project based, product and process team, delivery organisation
  • Routes to work together Vendor, technology partner, go to market partner
Team reviewing a delivery plan together Build. Operate. Transfer. We build a dedicated unit, run it to full performance, then transfer it to you.

Orchestron.

  • Corporate overview How the team is built and where we deliver
  • Offices Zagreb, Tirana, Chicago, and Riyadh
  • Governance How the firm is directed and held to account
  • Careers Open roles across our technology practices
  • Security and data protection How we handle confidentiality, access, and client data
Laptop running a development environment on a desk Careers Tell us what you build. A short description of your work is enough.
Contact

Case study

Document classification built on a real data audit

Commercial finance · Shows readiness

On this page

  • Context
  • Approach
  • Outcome
  • Principle

Context

The underwriting team of a commercial lender used several hours on document review for each application. The documents included financial statements, contracts, supplier agreements, and regulatory filings. Some were scanned PDFs of different quality, and some were native digital files. They were in many languages, and some had legacy formats. Earlier vendor proposals promised end-to-end automation, but they did not address the inconsistent source data.

Approach

Before we built anything, we did a six-week readiness assessment. The audit examined document quality, format consistency, classification taxonomy, and how documents moved through the team. The result was clear. Approximately 40% of new documents needed pre-processing or normalisation to make a classifier operate reliably.

We built the data preparation layer first. This layer had an optical character recognition (OCR) pipeline that we tuned for the actual document mix. It also had normalisation for the many less common formats, and a small human review step for ambiguous cases. After that, we built the classification model and trained it on the clean input.

Risk and compliance teams examined the audit findings before the model work started. As a result, the project was explainable from the start.

Outcome

  • 4× throughput on document review for each analyst.
  • Underwriters now use their time on cases that need judgement, such as covenant interpretation and risk assessment. They no longer use it on triage.
  • The data foundation is reusable. The same pre-processing layer now supplies two more AI workflows in adjacent operations of the lender.

Principle

Readiness. Without the data audit, the result is a fragile classifier and a project that fails on edge cases. The audit made the model viable in production. It also made the model explainable to risk and compliance teams. A regulated workflow must have both of these before it can use AI.

We show this case study with permission from the client, as an example only. Specific commercial details stay confidential. If you are a qualified counterparty, you can ask for these details under a non-disclosure agreement (NDA).

← Back to Orchestron. · More case studies · Discuss an opportunity

Orchestron.

Data, AI, and software delivery for business-critical systems.

Offices in Zagreb and Tirana. Representation in Chicago and Riyadh.

Site

  • Services
  • Industries and work
  • How we work
  • Whitepaper
  • Corporate overview
  • Products and ventures
  • Careers
  • Contact

Legal

  • Privacy Policy
  • Cookie Notice
  • Terms of Use
  • Security & Data Protection
  • Company Information

© Orchestronlab d.o.o. All rights reserved.