ENNL
Book a call

Services / Operations software

Operations software that fits how you work.

Bespoke operational systems for planning, orders, inventory and transport, with AI built in. You own the code and the data.

Book a callAll services

01 / Problems

Problems we solve

These are the situations that bring operations teams to us. This page does not cover data platforms or standalone AI models, which have their own pages.

  • The real process lives in spreadsheetsPlanning, stock and orders run on files and mailboxes that one or two people understand, and every handover loses something.
  • A package that almost fitsStandard software forces your process into its shape, and the last twenty per cent is done by hand next to it.
  • The ERP does not reach the shop floorYour ERP holds the records, but the daily decisions, exceptions and checks happen outside it, in tools that do not talk to it.
  • Manual work that AI could takeReading e-mails, checking documents and proposing a plan are repetitive, yet no tool you own can do them with a person in control.

02 / What we build

Modules around your operation

We start with the process that hurts most and add modules from there. The list below shows typical areas, not a fixed product.

  • Planning and schedulingA planning board with your own rules, warnings when a plan breaks them, and AI proposals that a planner accepts or changes.
  • Order handlingOrders from mailboxes, portals and EDI become structured orders, checked against your rules and passed on to your ERP.
  • Inventory and warehouseStock positions, locations, receipts and replenishment signals, kept in sync with the systems that already hold the master data.
  • Transport and dispatchTrips, assignments, status updates and proof of delivery, with the paperwork attached to the order it belongs to.
  • Quality and inspectionChecks, findings and corrective actions recorded once, reportable per batch, site or customer.
  • Field service and work ordersWork orders, parts, hours and reports from the field, with the office view and the mobile view built on the same data.
Today's worklistIllustration
  • Order from e-mailDone

    Customer order read, every line checked against the price list and sent to the ERP.

  • PlanningPlanner decides

    Truck 4 goes over its driving time on Thursday. Proposal: move two stops to truck 7.

  • StockReview

    An item is below its reorder level in warehouse B. A purchase proposal is ready.

  • ERP linkIn sync

    Stock and order status updated in your ERP.

What we automate

What we automate, in practice

Eight routine tasks from logistics, wholesale and manufacturing. Pick one to see what the screen looks like on a normal morning.

NexOps workspaceOrder intaketoday · 10:42Demo data
  • planning@demo-shipper.exampleNewTransport order Mon 16/6, PDF attached10:41PDF
  • dispatch@demo-carrier.examplePickup confirmed for Friday09:58
  • office@demo-supplier.exampleDelivery note 774009:12

Transport order Mon 16/6, PDF attached

planning@demo-shipper.example → orders@demo-company.example · 10:41

transport-order-16-6.pdf

Hello, please find our order for Monday attached.

Ref: TO-88213

Pickup: Venlo

Delivery: Barendrecht

Date: Mon 16/6, 07:00

Load: 2 × 33 pallets

Rate: €1,240.00

Kind regards, the planning desk

Draft order

ORD-2031

DraftReadingTo checkSent to ERP
Customer ref
TO-88213
Pickup
Venlo
Delivery
Barendrecht
Date
Mon 16/6, 07:00
Load
2 × 33 pallets
Rate
€1,240.00Differs from price agreement (€1,185.00)

Approved by planner

Activity

  1. E-mail received
  2. 6 fields read from the PDF
  3. Rate differs from the price agreement
  4. Approved by planner
  5. Sent to the ERP

The rate differs from the price agreement, so the planner decides. Nothing reaches the ERP without approval.

03 / Integrations

Connected to the systems you already use

Dutch operations run on a handful of well-known systems. We build integrations with them, so the new software reads from and writes back to your records instead of creating a second version of the truth.

  1. Mailboxes, portals, EDIWhere the work arrives
  2. Your operations softwarePlanning, orders, stock, transport
  3. ERP and accountingStays the system of record

Accounting and ERP

  • Exact
  • AFAS
  • Twinfield
  • SAP
  • Microsoft Dynamics

Ports and logistics

  • Portbase, where it is relevant to your flows
  • EDI and customer portals
  • Telematics and on-board data through their APIs

Collaboration and identity

  • Microsoft 365 mailboxes and calendars
  • Microsoft Entra ID sign-in and roles
  • Your own APIs and webhooks

These are products of their own vendors. We build integrations through the interfaces they offer; we are not a partner or reseller of them. What is possible depends on your licence and version, and we confirm it in discovery.

04 / Phases

Phased delivery, live early

You see working software in production before the whole system exists. Scope and plan follow a first conversation.

  1. Discovery

    We map the process, the systems and the exceptions with the people who do the work. The result is a written scope, a clickable design and a plan for the first module.

  2. First module in production

    One module goes live in your environment, with sign-in, roles, integrations, tests and a deployment pipeline. Real use shows what to change before more is built.

  3. Extend

    Further modules and integrations follow in the order that pays off most. Each phase ends in a release you can use, and you decide whether to continue.

05 / Sectors

Where we typically start

The processes differ by sector. These are the starting points we see most often, not claims about specific clients.

  • Logistics and transportOrder intake, planning, status and proof of delivery in one place.
  • Customs and portsDocument checks before a declaration, status per shipment and chasing of missing paperwork.
  • Trade and wholesaleOrder handling, stock signals and matching of supplier documents to purchase orders.
  • FoodBatch and quality records, planning that respects shelf life and structured handling of complaints.
  • ConstructionWork orders, subcontractor documents and site reports tied to the project.
  • ManufacturingProduction planning, quality checks and maintenance requests on a single data model.

06 / Ownership

You own the code and the data

Operations software becomes part of how you run the business, so you should be able to keep it, move it and change it.

  • The code lives in your repositories, with the documentation and the deployment pipelines
  • It runs in your Azure tenant or in another EU environment you choose, with private networking and secrets in a vault
  • Access follows your identity groups, with least privilege and an audit trail
  • It is built on open source and standard components, so another team can take it over
  • Your data stays in your environment, and we do not send it to external AI services without your written agreement
  • A handover with documentation and knowledge transfer, whether or not you keep us on afterwards

Run and evolve

After go-live, we stay on

Software that people depend on needs an owner on call. If you want one, we keep running and improving what we built, under a written agreement. It is optional: the code and the documentation are yours, so your own team can take over at any time.

  • MonitoringHealth, errors, queues and the quality of AI output are watched, so a problem is seen before your team reports it.
  • UpdatesDependencies, security patches and model or framework changes are applied and tested through the same pipelines as the first release.
  • Small changesNew fields, rules, reports and integrations are added in small releases, in the order your team decides.
  • Support and incidentsA named channel for questions and incidents, with the cover hours that fit how your operation runs.
  • Review and roadmapA regular review of use, quality and open requests, ending in what to build next.

About the service level agreement

The service level agreement is written per client: cover hours, how an issue is classified and how fast we respond. We do not publish standard response times, because they depend on the system and on what your operation needs.

Ask about run and evolve

FAQ

Questions about this service

Do you replace our ERP?

Not by default. Most often we build the operational layer beside it and connect it, so the ERP stays the system of record. Replacing an ERP is a larger decision that we only take on when the discovery shows it is the right one.

Why build instead of buy a package?

A package is the right answer when your process fits it. We build when the process is what sets you apart, when you run on spreadsheets next to a package, or when you want AI inside the workflow and control over the result. We tell you honestly if buying is the better choice.

Which systems can you connect to?

We build integrations with systems such as Exact, AFAS, Twinfield, SAP and Microsoft Dynamics, with Portbase where it is relevant, and with mailboxes, EDI and APIs. We confirm what the interfaces allow in discovery.

How is the work priced?

Each phase is scoped and quoted after a first conversation. We do not publish prices, because they depend on the processes and systems involved.

Who owns the software afterwards?

You do. The code is in your repositories, it runs in your environment and it is documented. Run and evolve is optional.

Do you have references for this?

Our delivered work is listed on the work page, mostly data and AI platforms for logistics, public and industrial organisations. Where a reference fits your question, we show it on a call.

Next step

Which process should come first?

Tell us where the daily work is manual or scattered. We tell you which process bespoke software fits and what the first module is.

Book a callSend a messageor email info@nexops.nl directly

Currently accepting projects for Q4 2026