Back office automation

Your systems each do their job. The work between them is done by people.

That work sets the pace at which you can take on customers, and it depends on the few people you can least afford to lose. We map where it happens and automate it, so taking on more customers stops meaning taking on more people.

Our clients are mid-market manufacturers, distributors, and value-add businesses.

What does back office automation involve?

Back office automation removes the repetitive handoffs that carry data between systems and teams: order processing, stock updates, invoice flows, customer onboarding, compliance checks, lead routing. We map how work moves through your operation, find the handoffs that cost the most time and cause the most errors, then automate them across systems rather than inside any single one. Most of that work happens between an ERP, a commerce platform, a CRM, and the tools around them, and much of it has nothing to do with a webshop.

Four things we hear

The only way we know how to grow is to hire another person.

That is the ceiling, and it is worth knowing exactly where it falls before hiring against it. The work that limits capacity is rarely spread evenly. It concentrates in a handful of steps, and mapping the process is what makes them visible.

One person knows how the exceptions are handled.

Most businesses like yours have that person, and they are usually the reason the operation works. Mapping the process turns what they know into something the business owns, and that serves them as much as it serves you. The judgment stays with them, and the repetition stops being theirs.

We bought software for this, and the typing moved somewhere else.

A tool automates what happens inside its own boundary, and the manual work collects at the edges: the export, the re-entry, the correction. That is an argument for buying one after the process is on paper, and not before.

The customer finds the mistake before we do.

That happens when the check that would have caught the error is the same manual step that produced it. Automating the step is also the opportunity to build the check into it, which is why the two are worth doing together.

‍

Six places the manual work shows up

Order processing

Orders arrive by email, phone, or portal, and someone types them into the ERP.

Stock and pricing updates

Figures are right in one system and a day old in the next.

Invoice flows

An invoice waits for a person to match it against a delivery note.

Customer onboarding

Documents are collected, checked, and filed by hand, one customer at a time.

Compliance checks

Verification that has to happen, has to be evidenced, and currently runs on someone's attention.

Lead routing

An inquiry sits in a shared inbox until somebody notices and passes it on.

‍

Each step looks small. Together they decide how much new work the business can take on, and they hand that decision to whoever happens to be handling the exceptions.

If the goal is for your customers to handle these steps themselves, that is portal work.

Why back office automation tools rarely settle it

Most automation software works inside one system. It will automate a sequence within your ERP or your marketing platform, and that is genuinely useful. The expensive handoffs fall between systems: between the shop and the ERP, between the ERP and the finance tools, between a compliance check and the person who has to act on its result. A single vendor rarely sees those, because they fall outside the product. Our recommendation follows the process rather than a product we happen to support.

Automating a process nobody has examined only makes that process faster. If it carries a workaround someone invented years ago to get past a limitation that no longer exists, automation locks the workaround in and repeats it at speed. Automation without understanding scales mistakes, so the mapping comes first.

Some systems cannot exchange the data an automation would depend on, and that is a connection problem before it is an automation one.

Integration & Optimization →

How we decide what to automate

In this work, the build is usually the short part. Once a process exists on paper, with every variation and decision point named, writing the software that runs it is comparatively quick. At OurWorkPlace, the mapping ran first, in workshops on the client's own site, and the onboarding was then built in a single pass. We treat the mapping as the part that carries the risk, which is why it gets the attention.

Mapping the operation

What happens, in what order, who decides what, and which parts exist only in someone's experience. For many clients, that map is the first time the whole process has been visible in one place, and it often answers the question of where to start.

Deciding what gets built

Three questions do the work here. Can the task be defined clearly enough that it will be carried out the same way every time? Do we understand the edge cases well enough to handle them, or to catch them and pass them to a person? Where do people stay in the loop, and what do they see when something needs a decision? Work that fails the second question needs the process settled before anything is built, and we will say so, including when that means less work for us.

Building in steps

Each change goes live on its own and is measured against the time it was meant to save. We standardize the parts that work the same everywhere, and build custom only for what makes your business genuinely different. When something is unclear, we come back with two options and the reasoning behind each, and you either choose one or propose a third.

Handing it over

It runs on your own systems and it is documented: that is what leaves you free from vendor lock-in.

Mapping an operation wider than one process is the work of a discovery engagement.

Systems Architecture & Discovery →

What we have automated

Our Workplace

Our Workplace

AML compliance onboarding, automated end-to-end in three months.

A virtual address provider whose owner read and judged every new customer's identity documents himself. Verification, payment, signature, and address lookup now run inside one flow that branches by type of customer. Incoming post is sorted on the same platform by an AI-powered document processor, and forwarding an item now takes two manual actions instead of five.

Tisch Scientific

Tisch Scientific

Real-time stock between Magento and the customer portal.

The figure a customer sees is the figure in the warehouse. Around it, we automated rules the team had been applying by hand: which payment methods and categories are open to which type of customer, whether an account is active or suspended, and the reminders that follow an abandoned order.

Aminoverse

Aminoverse

Product data and leads routed automatically between platform and Odoo.

Aminoverse sells enzyme kits and offers custom research services through one headless platform, with a separate path through the site for each kind of buyer. Product data stays in step between the platform and Odoo, and a research inquiry reaches the right person with a consultation bookable through Calendly.

‍

Talk to us about the process that is costing you the most.

Book a meeting →

What we work with

We build against what already runs in your business. ERP is usually one node rather than the whole picture, so the work reaches the CRM, the commerce platform, fulfillment, and the compliance tools around them.

ERP

Microsoft Business Central, Odoo

Commerce

Magento, Shopware, Shopify

Connecting layer

Middleware and integration platforms if they fit, direct API work if they do not

What changes

The measurable part is time, and most of it comes back to the people who were holding the process together. The part that shows later is that the process now exists outside them, so a resignation or a long absence carries less operational risk than it used to.

Each change is checked against what it was supposed to save, so the case for the next one is made with your own figures instead of ours. The map that made the first automation possible is the same map the next one starts from.

Where we fit, and where we do not

We automate business processes where they cross systems, run often, and hold an experienced person in place. A process that is simple, runs end to end in one system, and happens a few times a month is better served by a specialist tool or your existing supplier, and you will hear that from us on the first call.

We have told clients to rework the plan before starting a build they were ready to pay for. That call is easier to make early, which is the argument for having the conversation before the budget is committed.

FAQ

What is back office automation?

The automation of the internal work that keeps a business running: order processing, stock and pricing updates, invoicing, onboarding and compliance checks. Business process automation services describe the same work in broader terms. What matters in practice is whether the automation stays inside one system or connects several.

Which processes should a business automate first?

The ones that are repetitive, well understood, and held together by a person whose time is expensive. Volume alone is a poor guide, and a process nobody can describe end to end is a poor first candidate, however much time it consumes.

Should we buy a tool instead, and what are the best back office automation tools?

Sometimes a tool is the right answer, and if it is, we will tell you so. Which one depends on what already runs in the business, so the question tends to arrive one step early: a shortlist is quick to draw up and hard to judge until you can see the whole process at once. The test for any option on it is which handoffs it removes by name, which ones it relocates to its edges, and what happens to it when the rules change.

Should we outsource the work instead?

Outsourcing buys capacity quickly, without a project, and it suits work that is genuinely irregular, so for some businesses it is the right call. What it leaves untouched is the process itself, and the dependency moves rather than ending, from one person in your building to a supplier whose staff turnover becomes your risk. The practical test is repetition, because repetition is what lets a one-time build pay for itself, while paying by the hour does not.

Do we have to replace our ERP first?

In most cases, the ERP can stay where it is, and the assumption is worth checking before it turns into a replatforming budget, because an aging system gets blamed for problems the handoffs around it are creating. Our preference is to stabilize what is there and build on top rather than force a platform move. Replacing it becomes the right call when it cannot expose its own data, when it holds a rule nobody can change, or when support for it is ending.