Service / Processes & AI

Less repetitive work,
better decisions.

We help you improve your internal processes, connect the tools you already use and apply artificial intelligence only where it actually removes work. With your people involved from day one, because a tool nobody opens has improved nothing.

Process first,
tool second.

0

automations deployed before the audit. First we map the real process and measure the baseline of hours, cost and errors. A bad process automated is still a bad process, only more expensive and faster.

Method

The audit is contracted and delivered before touching any system

Where the real gap is

In almost any established company, production is already measured and the ERP has been running for years. The gap is in everything around them: supplier purchasing, sales, export, administration and document quality. That is where data is still typed twice, where judgment lives in the heads of three people who will retire one day, and where management consolidates by hand. That is the ground we work on.

What we do differently

We don’t replace your software. We connect what you already have.

How we help you

Map, connect, build. And make it stick.

Four ways we help, and one rule that orders them: first understand the process, then connect what you already have, and only then bring in AI. Getting your team to use it isn’t the last step: it decides whether the rest was worth anything.

01Know what to fix first

“I know we’re losing time, but I don’t know where to start or what’s worth touching.”

Before automating you need to know what you are automating. Half of it is usually unnecessary.

Interviews on the shop floor and in the office to document how work really happens, with its shortcuts and exceptions. A double-entry inventory: every piece of data someone types twice is a breakdown nobody has reported. Prioritisation by impact with hours, cost and error risk on the table, and a twelve-month roadmap. Change management is included, and here it is not a slide: a named owner for every pilot, the tool placed where people already work, and adoption measured in active users rather than deployments.

  • −Map of the real process, not the org chart
  • −Inventory of double entry and rework
  • −Prioritisation by impact and 12-month roadmap
  • −Change management and adoption measurement
02Connect what you have

“We have the tools, but they don’t talk to each other and someone copies data between them every day.”

We don’t replace your software. We connect what you have and remove the work in between.

ERP, MES, Microsoft 365, your CRM, your shop and the spreadsheets that hold up half the company. We build the layer that connects them so data is written once and travels on its own: APIs, server-side proxies so credentials and personal data are never exposed, synchronisations and scheduled processes. With one hard rule: every automation records what it did and warns when it fails. A silent automation is worse than none, because you have spent months trusting something that broke without a word.

  • −Integration with ERP, MES and Microsoft 365
  • −Secure proxies and GDPR by design
  • −Scheduled processes with logging and failure alerts
  • −Data migration and consolidation across systems
03Remove the repetitive work

“There’s work a person does by hand that a person shouldn’t be doing.”

Useful AI is boring AI: it removes repetitive work and leaves a trace of what it did.

Assistants that answer over your own documentation citing the exact source, with role-based permissions and without a single paragraph leaving your infrastructure. Automatic triage of what arrives by email, form or mobile, including voice notes and photos from the shop floor. Data extraction from delivery notes and invoices. And above all, governance: whoever proposes does not execute, the catalogue of actions is closed, reversible actions run on their own and irreversible ones wait for a person. It is the answer to the only question a board actually asks: what happens when it gets it wrong.

  • −Assistants over your own documents, citing the source
  • −Triage by text, voice or photo from mobile
  • −Documents into data: delivery notes, invoices and specs
  • −Governance: reversible runs alone, irreversible needs sign-off
04Build what doesn’t exist

“Nobody sells what we need, and we’re holding it together with a spreadsheet.”

When the tool you need doesn’t exist, you build it. You don’t force another spreadsheet.

Management applications, executive dashboards and digital records, with role-based permissions, deployed on your own infrastructure with data held in Europe. We do this because we do it for ourselves: our internal tool for project management, accounting and P&L is an application we built and use every day, not a product we resell. A dashboard nobody looks at is decoration, so they are designed with automatic alerts when something moves out of range.

  • −Management apps with role-based permissions
  • −Executive dashboards with automatic alerts
  • −Digital records and document traceability
  • −Deployed on your infrastructure, data in Europe

Who this is for

It depends on what you want to fix. Not on your size.

You don’t need to be a multinational or have an IT department. You need repeatable processes and someone with the authority to change them.

Industry and manufacturing

Production is measured. The rest lives in spreadsheets.

You have an ERP and perhaps an MES, but supplier purchasing, document traceability, custom orders and management consolidation still depend on spreadsheets and email.

Distribution and retail

Several systems that don’t talk to each other.

Shop, warehouse, invoicing and customer service in different tools, with someone copying data between them every day and errors that surface weeks later.

Professional services

Knowledge lives in people’s heads.

Case files, regulations and judgment spread across folders and veterans. When someone leaves or retires, the company loses something that was never written down.

When this is NOT for you

If you want a tool and already know which one.

If the decision is already made and it just needs installing, your integrator is cheaper. We come in when what’s missing is knowing what to fix and in what order.

Before buying a tool

Do you know how many times the same data is typed in your company?.

Let’s talk →

How we work

Four steps. The first one is short.

You don’t sign the whole transformation. You sign the audit, and from there decisions are made with data instead of intuition.

01

Process audit

Two or three weeks, fixed price. Interviews, map of the real process, inventory of systems and data, and a baseline measured in hours, cost and errors.

02

Prioritisation with management

A catalogue of cases ranked by hours freed and cost of error, with a twelve-month roadmap. Two pilots are chosen and their metric agreed before a line of code is written.

03

Pilots in production

Six to eight weeks. Delivered in production, not as a mock-up, with an internal owner and human control at the start. If the metric hasn’t moved in eight weeks, it stops.

04

Continuity and adoption

Maintenance of what is live, a new case every six to eight weeks, an executive dashboard and a monthly forty-five-minute steering meeting. What isn’t adopted gets retired, not dragged along.

What we measure

No baseline, no project. And without adoption, none either.

These are the indicators we set with you during the audit and measure against your own data, before and after each pilot.

Hours freed per week

People-time spent on the repetitive task before and after the pilot, measured on the same process.

Audit baseline

Times the same data is typed

Number of systems where the same value is entered by hand. Getting it from three down to one is usually worth more than any model.

Double-entry inventory

Real adoption

Weekly active users and share of reports or orders arriving through the new channel. A deployment is not an adoption.

The system’s own log

Errors and rework

Incidents, corrections and re-done orders before and after. It is the saving that never shows on an invoice but does show in the margin.

Logged incidents

We don’t publish improvement percentages from other clients: every process starts from a different baseline and a number without its context means nothing. Yours are set during the audit and measured on your data.

What you won’t find

What we DO NOT do.

In process and AI work it is easier to show a demo than to deliver something that survives in production. These are the limits that let us work with judgment, and saying them upfront avoids awkward meetings later.

  • ×

    We don’t automate what we can’t measure — without a baseline of hours, cost or errors before touching anything, there is no pilot. Faith doesn’t pay salaries.

  • ×

    Nor do we touch the machine — sensors, PLCs, control systems and in-line machine vision belong to your industrial integrator. We work the data layer that feeds them and reads from them.

  • ×

    Nor do we replace your ERP — if it works, it gets connected. Replacing a company’s core system is another project, another budget and probably another supplier.

  • ×

    Nor do we sign off what is regulatory — we can generate the documentation from your data, but whoever signs a CE marking, a declaration of performance or an environmental declaration is your engineer or your certifier.

  • ×

    Nor do we sell AI as fashion — if the process doesn’t need AI, we don’t add it. We charge for processes that work, not for technological adjectives.

  • ×

    Nor lock you in — month to month, full access to your accounts. You stay because it works.

  • ×

    Nor invent case studies — real accounts with real data before you sign anything.

Sectors

Is this for my business?.

It depends on what you want to build.

We work with businesses that no longer want to improvise. That seek direction, not just execution.

EDP
Eleia Energía
Flame Analytics
Fotocasa
Santillana
Viacore
ULMA
Esnova
Ferrovial
Helvetia
ITC
Neodoc

A shared goal:
making every decision count.

Frequently asked questions

What our clients ask us.

Isn’t this what my IT person or ERP integrator already does?

They complement each other rather than overlap. Your integrator maintains and extends the system they sold, and your IT person keeps the infrastructure running. Neither has the mandate to sit down with purchasing, sales and administration to ask why the same delivery note is typed three times. That is process consulting work, and it ends in a map and a roadmap that they, we, or both can then execute.

Where do we start if we have never automated anything?

With the process that burns the most hours and whose result can be measured, which is almost never the one that looks most technological. In practice it is usually incoming orders or enquiries, the paperwork that goes with each shipment, and consolidating data for management. What we never recommend is starting with a conversational assistant: it is the most impressive thing to demo and the last thing you should build.

What happens when the AI gets it wrong?

It is handled by design, not by trust. Whatever the AI does on its own is always reversible, and its catalogue of actions is closed: it cannot execute anything not on the list. Anything irreversible, such as sending something to a customer, changing stock or signing a document, stops and waits for a person to approve it. Every action is logged, so you can always reconstruct what happened and undo it.

What if my team doesn’t use it?

It is the real risk in these projects, well above the technical one, which is why change management is included rather than sold as an extra. We work with three rules: the tool goes where people already work and is never one more screen to open, every pilot has a named internal owner, and what gets measured is adoption rather than deployment. If people aren’t using it after eight weeks, it is retired. Dragging dead tools along is exactly what makes nobody believe in the next one.

How much does it cost and how long does it take?

The first conversation is free and you leave it knowing whether we think there is a case. What is fixed-price is the process audit that follows: two or three weeks, and the report is yours whether you continue with us or not. Pilots are quoted one by one with the metric already agreed, and usually run six to eight weeks each. Continuity is a monthly fee with no lock-in. Before the audit we don’t give a number, because it would be made up.

BLOG

Latest articles.

View all articles →

Let's talk about your business.

The first step is a conversation.

No strings attached, no smoke.

✓We respond within 24 hours
✓No sales pitch. Just strategy.
✓First conversation free, no commitment