Stratelya Orchestra — AI practice

AI agents in production, inside your processes.

Orchestra is the operational and technical arm of Stratelya’s AI practice. We analyse a process, simplify it, connect your tools and put AI agents into service, with human sign-off, monitoring and measurement. The same building blocks run our own agents.

DIAGNOSTICTARGETAGENTSEVALUATIONPRODUCTIONMEASUREAI AGENTSILLUSTRATION · ONE DEPLOYMENT
ForExecutive teamsOperations leadersBusiness unit headsEurope · MENA · ASEAN
01 — Agents in service

The agents we run every day.

More than twenty agents run on our own processes today. Pick a domain: what each agent does, what triggers it, what stays human.

Continuous watch

In service

Reads over 500 news feeds, the global GDELT database and official registries, then matches each new publication against the companies followed.

Trigger
Continuous
Control
The client chooses the companies followed and its alert rules.

Alerts

In service

Sends the alert by e-mail, Slack or Microsoft Teams, with its source and date.

Trigger
Event
Control
Thresholds and channels set by the client.

Geopolitical watch

In service

Searches the last 24 hours for developments with business impact: sanctions, tariffs, conflicts, AI and data regulation, cyber incidents. Each item is tied to its source.

Trigger
Every 3 hours
Control
An item already known is not repeated.

Social signals

In testing

Scores posts from 1 to 10 for relevance and surfaces those that mention the companies followed.

Trigger
Continuous
Control
The sources followed are chosen by the team.

Public tenders

In testing

Collects French and European notices, qualifies them with a fixed grid and no AI, then analyses the notice and tender documents, citing pages.

Trigger
Daily
Control
Every external action goes through the approval queue.

Private tenders

In testing

Extracts the details of a tender received by e-mail, as a web page or as a document.

Trigger
Inbound e-mail
Control
Received content is treated as untrusted.
02 — Three steps

From a measured process to agents in production.

Each step produces reusable technical artefacts and ends with a decision point backed by your own measurements.

Measure the real process before choosing where an agent goes.

Work

  1. Interviews and on-the-job observation, task timing on a sample of real cases.
  2. Analysis of exports and history from your tools (CRM, ERP, ticketing) to measure volumes, lead times and process variants.
  3. BPMN 2.0 model of the current process: actors, tasks, decisions, exceptions, waiting times.
  4. Inventory of systems and data: sources, formats, quality, available APIs (REST, GraphQL, webhooks), exports, personal data involved.
  5. Qualification of each candidate task: volume, variability, share of human judgement, cost of an error, technical feasibility.
03 — Architecture

The stack, layer by layer.

For each layer: what we use in service and the market building blocks we are evaluating. The final choice is made at diagnostic, to fit your constraints.

Reference architecture
03 · Orchestrator

Sequences the agents’ tasks, schedules them, resumes them on failure.

In service

  • Trigger.dev: durable tasks, scheduling, waits, retries
  • Vercel Cron: simple scheduled tasks

Under evaluation

  • Temporal: durable execution for critical workflows at scale
  • LangGraph: stateful agent graphs with resume
  • Claude Agent SDK, OpenAI Agents SDK: tool-using agent loops
  • n8n: simple automations business teams can edit
  • A long task can wait without using compute.
  • A failed task is replayed without duplicating what was already done.

Safeguards

Every run is traced and reviewable.

Cross-cutting

Security

  • Separation and roles per organisation
  • Server-side secret management
  • Audit log of decisions
  • Model gateway (LiteLLM): centralised routing, quotas, logging
  • Input and output guardrails (NeMo Guardrails, Llama Guard)
  • Sovereign hosting (Scaleway, OVHcloud) or EU zones of the clouds (Azure, AWS Bedrock, Vertex AI)

Monitoring

  • Trace of every task
  • Log of every AI call and its cost
  • Cost overrun alerts
  • Langfuse: traces, costs and evaluations of agents
  • OpenTelemetry, GenAI conventions: standardised traces

Solid line: in service at Stratelya. Dashed: market building blocks under evaluation, not used yet.

At a client, we reuse these building blocks or connect to its tools through their APIs. The choice of models, orchestrator and hosting is made at diagnostic.

04 — Agent engineering

The patterns that make an agent reliable.

A useful agent is an engineering problem first, not a prompt. These are the patterns we apply, the problem each one solves and its status with us.

01In service

Structured outputs

Problem
Free text does not fit into an information system.
Answer
JSON schema imposed on the model and validated on receipt. Non-conforming output is rejected, retried or escalated.
02In service

Writer and reviewer

Problem
A model is poor at spotting its own errors.
Answer
A second agent, with its own instructions, checks every figure and citation against the sources.
03In service

Committee and arbitration

Problem
A single perspective misses risks.
Answer
Specialised agents analyse in parallel; one agent arbitrates and makes disagreements explicit.
04In service

Computation outside the model

Problem
A language model gets calculations and fixed rules wrong.
Answer
Scores, calculations and business rules in deterministic code. The model explains; it does not compute.
05In service

Routing by task

Problem
The strongest model everywhere costs too much and answers too slowly.
Answer
A fast model to extract and classify, a strong model to analyse; the choice is set per task.
06In service

Untrusted content isolated

Problem
An e-mail or document can carry malicious instructions (indirect injection).
Answer
External content is framed as data. The agent reading it has no action tool.
07In service

Durable execution

Problem
A real process lasts hours or days and fails along the way.
Answer
Persistent workflow, idempotent retries, waiting without using compute.
08In service

Budget per organisation

Problem
An agent loop can blow up the bill.
Answer
Cap reserved before each call, actual cost recorded, overrun alert.
09In service

Versioned instructions

Problem
An instruction change can degrade quality without anyone noticing.
Answer
Every version is kept, with rollback available.
10Under evaluation

Cited document search (RAG)

Problem
The model does not know your internal documents.
Answer
Vector index of your documents; relevant passages are given to the model with their reference, and the answer cites them.
11Under evaluation

Instruction caching

Problem
Long instructions are billed again on every call.
Answer
Provider-side caching of the stable parts of the instructions.
12Under evaluation

Batch processing

Problem
Non-urgent work pays the real-time price.
Answer
Providers’ batch APIs for volumes that can wait.
13Under evaluation

Continuous evaluation

Problem
A model change can break an agent that worked.
Answer
Test set replayed automatically on every change of model, instructions or tool.

Which level of autonomy for which task

We set the autonomy of each task on two criteria: the cost of an error and whether it can be undone.

Cheap errorCostly errorReversibleIrreversible
Level 1

Assistant

The agent analyses and recommends; a person decides and acts.

Examples
  • Prices and contractual commitments
  • Payments
  • Decisions about people
Control

Human decision and execution.

05 — Evaluation and security

Measure before deploying, protect before opening.

Pilot evaluation protocol

  1. Test set built from your real, anonymised cases, with the expected answer.
  2. Acceptance thresholds agreed with you before the pilot.
  3. Shadow mode: the agent proposes, nothing is executed, and we compare with what your teams did.
  4. Production only once the thresholds are met.

What we measure

Accuracy
Field by field for extractions, answer by answer for analyses.
Valid citations
Share of statements whose source exists and says what is written.
Human rework
Share of outputs corrected or redone by your teams.
Critical errors
Errors with binding consequences: the target is zero.
End-to-end lead time
From case intake to usable result.
Cost per case
AI calls and infrastructure, per case processed.

Threats and countermeasures

The risks specific to language-model applications, per the OWASP Top 10 for LLM Applications, and the countermeasure we apply.

  • LLM01
    Prompt injectionExternal content isolated as data; the agents reading it have no action tool.
  • LLM02
    Sensitive information disclosureSeparation by organisation enforced in the database; data minimised in instructions.
  • LLM05
    Improper output handlingOutputs validated against a schema, never executed or displayed as raw HTML.
  • LLM06
    Excessive agencyTools limited to the agent’s scope; approval queue for every external action.
  • LLM09
    MisinformationMandatory citations, rereading by a second agent, unsourced figures removed.
  • LLM10
    Unbounded consumptionBudget caps, cost recorded per call, overrun alerts.

Compliance: each use is classified under the AI Act from the diagnostic; personal data processing is minimised and retention periods set, in line with the GDPR.

06 — Company map

Your company, function by function.

Pick a function to see a concrete example: the process before and after, the tasks handed to agents, the responsibilities that stay human, the connected tools and the deliverables.

Illustrative example
Sales

From incoming request to commercial proposal

Before

  1. Request arrives by e-mail, forwarded by hand
  2. Client information searched across several tools
  3. Proposal written from an old document
  4. Follow-ups tracked in a spreadsheet

After

  1. Request captured and qualified in the CRM
  2. Client context sheet prepared
  3. Draft proposal built on your templates
  4. Follow-ups scheduled, approved by the account owner

Tasks handed to agents

  • Read, classify and log the request
  • Gather the client history
  • Prepare the draft proposal
  • Suggest a follow-up schedule

Human responsibilities

  • Qualify the opportunity
  • Set price and terms
  • Review, approve and send
  • Own the client relationship

Connected tools

  • CRM
  • E-mail
  • Office suite
  • Template library

Tool categories: actual connections depend on your environment and are confirmed during the diagnostic.

Deliverables

  • Complete opportunity record
  • Proposal ready for review
  • Up-to-date pipeline tracking

These examples illustrate the approach. They are neither client references nor achieved results: each process is analysed from how your company really works.

07 — Walkthrough

Agents at work, from request to proposal.

A complete journey: a client need comes in, agents prepare, your teams sign off. No real events are published for this journey: this walkthrough is a simulation.

Simulation · illustrative journey
  1. 01IntakeAgentNext
  2. 02ContextAgentNext
  3. 03QualificationHuman sign-offNext
  4. 04DraftingAgentNext
  5. 05PricingHuman sign-offNext
  6. 06Send and follow-upHuman sign-offNext

Start the simulation to follow the journey step by step.

Simulation: no client data, no real events. Agent names and contents are examples.

08 — What is available

Available, illustrative, tailored.

So you know exactly what you are buying, we separate what Stratelya delivers today, what this page illustrates and what gets built for you.

Available

What we deliver today

  • Process diagnostic and mapping
  • Process redesign and simplification
  • Design and commissioning of AI agents on a pilot scope
  • Team support and change management
  • Before / after measurement on indicators agreed together
Illustrative

What this page shows

  • The function map and its examples
  • The sales journey walkthrough
  • Agent, task and deliverable names

They illustrate the approach: they are neither client references nor results.

Tailored

What depends on your environment

  • Connections to your tools, depending on their access and interfaces
  • Agents specific to your business and your rules
  • Sign-off circuits and security rules
  • Data processing and hosting to your requirements
  • Result indicators
09 — Principles

Useful agents, under human control.

AGENT PREPARESOWNERHUMAN DECISIONAUDIT TRAILMEASUREADJUSTMENTAGENT PREPARESOWNERHUMAN DECISIONAUDIT TRAILMEASUREADJUSTMENT
Hover or select a principle
Ownership

One owner per agent

Every agent has an owner in your teams, a written scope and operating rules.

Decision

Binding decisions stay human

Prices, commitments, choices about people, payments: the agent prepares, a person decides.

Data

Your data stays under control

Access limited to what is strictly needed, agent actions logged and reviewable.

Measurement

Measure before scaling

Nothing is rolled out more widely without measurement on the pilot and your decision.

Let’s talk

Let’s find your first process to transform.

A first conversation to find the process where effort is lost the most. We start from how your company really works, not from a sales demo.