ACTELUS
Discuss a workflow

Somebody is still doing this by hand.

  • The weekly export that gets re-keyed.
  • The price list matched line by line.
  • The check that runs twice, because the first one left no trail.

ACTELUS is a UK digital systems studio. We build the software that does the matching, the reading and the checking, and hands back the cases it could not decide.

Reconciliation run supplier-prices-q3.csv
  • Read 412 of 412 rows
  • Matched against your catalogue 381 rows
  • Flagged for a person 31 rows

NF-2211-TE25 68.40 → 72.10

NF-9043-MCB16 3.95 → 4.12

NF-5521-FLTG4 no change

NF-7740-CU8SP 142.00 → 151.75

NF-1180-VNT30 no price given

One run, on a synthetic catalogue. Nothing here is a client file, and the studio has not measured hours saved.

A supplier file, and what we hand back

The file arrives in the supplier's codes, not yours, with their casing, a repeated line and a row that has no price. This is the same data after the comparison: what changed, what did not, and what a person still has to decide.

supplier-prices-q3.csv What arrives
Reference Price
NF-2211-TE25 72.10
nf 9043 mcb16 Their casing, not yours 4.12
NF-5521-FLTG4 11.20
NF-7740-CU8SP The same line again 151.75
NF-1180-VNT30 No price given none
… 408 more rows
price-change-review.xlsx What you approve
SKU Old New Outcome
CBL-TE-2.5-100 68.40 72.10 Matched
MCB-B16-6KA 3.95 4.12 Matched
HVAC-FLT-G4-595 11.20 11.20 No change
CU-8W-SPD 142.00 151.75 Matched
— — 18.60 Needs review
412 catalogue rows compared · 381 matched · 23 flagged for review · 8 supplier rows with no catalogue match Illustrative interface Synthetic catalogue and supplier data, not a client file.

How the sprint is scoped

What it looks like now

Four descriptions of the same situation, from the processes we are most often asked about. None of them is unusual, and none of them is anybody's fault.

  • Re-keyed three copies

    The same figure, typed three times

    It arrives in an email or a PDF, goes into a spreadsheet, then into the system that actually holds it. Every copy is a chance to introduce an error nobody can trace later.

  • No match 14 of 412 rows

    Two days to find the rows that changed

    A supplier price list arrives in their codes, not yours. Most lines are identical to last quarter, so the ones that matter are buried among the ones that are not.

  • No trail unrecorded

    Checked twice, because the first check left nothing behind

    When a process keeps no record of what was checked and against what, the safe response is to check it again. Nobody can tell the second check from the first.

  • Single point one person

    One person knows how it runs

    It works until they are on leave. The knowledge is real and valuable, and it is written down nowhere the business can use.

What we build instead

Five kinds of work, all of them aimed at the handling rather than the judgement. An engagement usually touches two or three.

  • Workflow automation

    A defined sequence runs without a person carrying the data between steps, and records what it decided so the decision can be reviewed.

  • System integrations

    Two systems that each hold part of the truth get one reliable connection, with a direction of travel, a schedule and a record of what failed.

  • Document processing

    Values are read out of PDFs, forms and exports into a structured shape, each one linked back to the page it came from so a person can check it in seconds.

  • Internal tools

    A small application for one team and one job, usually the screen that replaces a spreadsheet and the routine that grew around it.

  • Price list reconciliation

    Supplier files are compared against your own catalogue line by line, so the changes to approve are separated from the rows that need a decision.

How an engagement is scoped

What exists, and its state

Two systems, both built around a process somebody was doing by hand. Each one is labelled with its real status, the data it runs on and what it will not do.

Supplier Price Update Sprint

Distributors receive a new supplier price list and have to work out, row by row, which of their own catalogue lines changed. This compares the two lists against the catalogue and produces a change file a buyer can review.

In development Data used: Synthetic distributor catalogue and supplier price lists. No client data.

See what the sprint includes

What it does

  • Matches supplier rows to catalogue lines and reports the change per line.
  • Separates confident matches from rows that need a human decision.
  • Produces one import-shaped file plus a list of unmatched rows.

What it does not do

  • Write to a live ERP, pricing table or catalogue.
  • Guess a match it is not confident about.
  • Replace the approval and import process you already run.

Commercial Insurance Submission Engine

An account manager re-reads a submission package to find what is missing or contradictory before it goes to a carrier. This reads the package and lists findings with a link back to the page each one came from.

Live product Data used: Shipped as PacketSlip. The demonstration here ran on synthetic ACORD 125 and 126 documents.

Open PacketSlip

What it does

  • Reads a package of PDF and text files and lists findings with their source.
  • Flags missing fields and values that conflict between documents.
  • Produces a summary for the account manager to check before the next step.

What it does not do

  • Replace an agency management system.
  • Underwrite, quote, bind or submit anything to a carrier.
  • Send a message or take an action without a person approving it.

See all systems and demos

Three groups of work

Business systems is the focus. The other two groups stay available because they are often what a client needs next, not because the list looks better with them.

  • Business Systems

    Work that removes repeated handling from an information-heavy process: automation, integrations, document processing and internal tools built for one workflow.

    What this involves

    • AI and workflow automation
    • Data and application integrations
    • Document and submission processing
    • Custom internal tools and business applications
    • Supplier price list processing and reconciliation

    Two systems exist and are shown with their real status on Systems and Demos.

  • Growth and Conversion

    Search, content and conversion work delivered as a defined audit or an implementation project, with a retainer only where the work is genuinely ongoing.

    What this involves

    • SEO and content
    • Performance marketing
    • Marketing and email automation
    • Conversion rate optimisation
    • Landing pages and funnel improvement

    No published campaign results. This page describes scope and method, not outcomes.

  • Digital Experiences

    Websites, brand and creative production, each with a stated scope, revision count, deliverable list and a clear split of launch responsibilities.

    What this involves

    • Website design and development
    • Brand strategy, identity and brand voice
    • AI-assisted advertising films
    • Virtual try-on and product imagery

    No client work is published for this group yet. Capability and engagement model only.

Understand, scope, build, test

Every engagement runs through the same five steps. The point of naming them is that you always know which one you are in, and what is expected from each side.

  1. Understand the workflow

  2. Define scope and inputs

  3. Build or configure

  4. Test and review outputs

  5. Agree what happens next

Scope is written, not implied

What is included, what is excluded and which inputs are required, in a document you can hold us to. Anything outside it is quoted as further work rather than absorbed quietly.

What each step involves

Bring the process you still do by hand

A weekly export that gets re-keyed. A supplier list that takes two days to reconcile. A form that is checked twice because nobody trusts the first check. That is the conversation this studio is built for.