Arc Agent SystemsArc Agent Systems
Book a call

Client results · logistics

A manual back office, rebuilt while it kept trading.

A cross-border parcel logistics operator came to us with a website and almost nothing behind it. Six months later the same team was serving nearly four times as many customers.

300 → 1,150+

Registered customers

10

Manual processes rebuilt

~150

Reviewed leads per week

0

Extra operations staff

The situation

Everything behind the website was a person, a mailbox and a spreadsheet.

The operator gives businesses and consumers in one jurisdiction a delivery address in a neighbouring one, receives their parcels, and holds them for collection. It is a simple, high-volume service. All of the commercial value is in how smoothly the operation runs.

It was running entirely by hand. Enquiries were read and answered one at a time. Customer details were retyped into a spreadsheet. A member of staff worked out each customer's reference and emailed it to them. Somebody noticed a parcel had arrived and wrote to tell the customer. Invoices were assembled per transaction. And the only way to know how the business was doing was to count rows.

None of this was anyone's fault. It is what every growing operation looks like just before it stops scaling.

What that cost them

Step

How it was handled

What it cost

Customer enquiry

Read and answered individually by hand

Several hours daily; slow replies; enquiries lost in a busy inbox

Customer registration

Details retyped into a spreadsheet

Transcription errors, duplicates, no single customer view

Issuing a customer reference

Worked out and sent by a person

A customer could not use the service until someone got to it

Parcel arrival

Noticed by staff, then emailed

Missed notifications, and a steady stream of “has it arrived yet?”

Collection

Manual lookup and confirmation

Counter queues; risk of handing over the wrong parcel

Invoices and receipts

Assembled by hand per transaction

Slow, inconsistent, VAT errors, billing disputes

Knowing how the business was doing

Counting rows in a spreadsheet

No live view; decisions made on stale figures

System problems

Reported in a messaging app

Lost in chat threads, with no owner and no date

New business

Word of mouth

No pipeline, nothing measured

What we built

Ten systems, delivered in stages, in production.

Nothing was switched off and rebuilt. Each layer went live alongside the existing process, was verified, and then took over.

01

Front door

Registration and instant customer reference

The website now feeds a registration flow that creates the customer record and issues a unique reference automatically. A customer can register and start shipping the same minute, with nobody in the loop.

02

Source of truth

Central database and operations dashboard

One source of truth for customers, parcels and transactions, with a staff application covering the working day. Historical data was cleaned and migrated in staged batches.

03

Outbound

Event-triggered parcel notifications

Despatch, arrival and collection notices are generated from events recorded in the system. The customer is told before they think to ask — which is what makes the inbound question disappear rather than simply move somewhere else.

04

Counter

Reference and QR-based collection

Arrivals and collections are processed against the customer reference or a QR scan with on-screen confirmation. Matching a parcel to a person stopped being a judgement call at a busy counter.

05

Money

Automated invoices and receipts

Branded documents generated from the transaction record, with VAT handled correctly including zero-rated lines. Totals are entered as the customer sees them and the system derives the rest.

06

Intelligence

An assistant the owner can talk to

A voice-enabled assistant that answers questions about the business in plain English, computed from the live database. The assistant interprets the question; the application produces the number. The model has no mechanism by which it can invent one.

See it running

The assistant, on live data

The owner asks a question in plain English. The application computes the answer from the database - the model has no way to produce a number of its own.
Open the demo in a new tab →

07

Continuity

In-app support and ticketing

Staff report an issue from inside the application. Priority is derived from two plain-English questions rather than asking non-technical staff to rank severity. Each report becomes a referenced ticket with a working-day due date.

08

Pipeline

Lead sourcing and outreach

An end-to-end pipeline from sourcing through enrichment and fit scoring to human review and paced, compliant sending. Around 150 reviewed leads a week, every one confirmed by a person before it goes.

09

Pipeline

Weekly content, screened and approved

Draft posts screened automatically against a restricted-phrase list before any person sees them, then approved in two stages. On a cross-border service, wording around customs and duty carries real exposure; the check enforces it rather than relying on someone remembering.

10

The payoff

A report that writes itself

A daily record consolidating operations, outreach and advertising performance into one dated row, so trends are visible without anybody building a report.

What changed

The same team. Nearly four times the customers.

Read the table as

Measure

Before

After

Registered customers

~300

Over 1,150

Issuing a reference

Manual, hours to a day

Automatic on registration

Parcel notifications

Written by staff, per parcel

Generated from system events

Invoices

Assembled by hand

Generated from the transaction

Visibility

Counting spreadsheet rows

Live dashboard and a daily report

Issues

Messages in a chat thread

Referenced tickets with owner and due date

New business

Word of mouth

~150 reviewed leads per week

Operations headcount

—

Unchanged

We describe the growth as running alongside the systems work rather than being caused by it. What we can evidence is this: the work that would have required more people no longer exists.

Figures verified against live data on 15 September 2026

Is this you?

You do not have to be a parcel depot.

The specifics were parcels. The pattern was not. If enquiries are answered one at a time, if customer details live in more than one place, if documents are assembled by hand, or if the only way to know how the month is going is to count something — the same approach applies.

Hospitality

Recipe costing, purchasing and prep, connected so a change in one cascades through the rest.

Trades and construction

Quotes, scheduling and supplier documents, out of the inbox and into a system.

Professional services

Lead generation, proposals and client reporting, produced rather than assembled.