Scellus operations engine

Back-office operations, built from ten blocks.

We assemble the blocks your firm needs, connect them, and hand you a system that runs. One block or ten. Start where the pain is.

Most back-office work at SME firms is held together by spreadsheets, one-off scripts, and people who know how it used to work. When someone leaves, it breaks. When volume grows, it slows.

You do not need another tool. You need a system with ten parts, each doing one job well.

The ten blocks

Each block does one job well.

  • Ingest

    Brings source material into the system.

    Inputs:
    PDFs, scans, forms, emails, spreadsheets, portal exports.
    Outputs:
    Structured file intake with source references.
    Use when:
    Work starts outside your system of record.
  • Extract

    Turns unstructured input into structured records.

    Inputs:
    Ingested files.
    Outputs:
    Names, IDs, dates, clauses, amounts, metadata.
    Use when:
    You re-type data from documents more than twice a week.
  • Verify

    Cross-checks data against sources and flags issues.

    Inputs:
    Extracted records, source files, rulesets.
    Outputs:
    Verified records, exception list with reasons.
    Use when:
    Data comes from multiple sources, or errors carry cost.
  • Calculate

    Applies rules and compliance logic to produce numbers.

    Inputs:
    Verified records, rulesets.
    Outputs:
    Fees, tax, duty, timelines, risk scores.
    Use when:
    The same calculation is repeated across many matters.
  • Generate

    Produces the working output you hand off.

    Inputs:
    Calculated records, templates.
    Outputs:
    Reports, filing packs, drafts, summaries, updates.
    Use when:
    A human is assembling outputs from copy-paste.
  • Review

    Gives a person controlled approval over machine output.

    Inputs:
    Generated outputs.
    Outputs:
    Approved outputs, corrections, escalations.
    Use when:
    Final signoff must stay with a qualified human.
  • Route

    Moves work to the right person, queue, or next step.

    Inputs:
    Approved or flagged items.
    Outputs:
    Task assignments, state transitions.
    Use when:
    Work sits in inboxes or gets forgotten.
  • Track

    Watches deadlines and time-sensitive events.

    Inputs:
    Extracted dates, filing windows, SLA rules.
    Outputs:
    Reminders, countdowns, escalation triggers.
    Use when:
    Deadlines exist and missing one has consequences.
  • Audit

    Records what happened, when, and on whose authority.

    Inputs:
    Every action from the other blocks.
    Outputs:
    Evidence pack, version history, action log.
    Use when:
    You operate in a regulated or high-accountability context.
  • Learn

    Captures reviewer corrections and feeds them back into the rules.

    Inputs:
    Review decisions, error patterns.
    Outputs:
    Ruleset updates, extraction refinements.
    Use when:
    You want the system to improve without re-engineering it.

How the blocks fit together

A block on its own does one thing. Blocks connected do work.

The simplest useful composition is two blocks: Ingest then Extract. That alone replaces hours of re-typing.

A typical composition is five to seven. A full system uses all ten.

Below are four example compositions. The blocks are the same. The shape changes.

Four shapes

Same ten blocks. Different outcomes.

Client intake pack

New client documents become a verified file, ready for engagement. Replaces the opening week of manual checks, form chasing, and compliance review.

  • Ingest
  • Extract
  • Verify
  • Calculate
  • Generate
  • Review
  • Route
  • Track
  • Audit
  • Learn

Billing recovery pack

Finds unbilled time and expenses across matter records, drafts invoices, and routes them for partner sign-off. Targets revenue that is already earned but never billed.

  • Ingest
  • Extract
  • Verify
  • Calculate
  • Generate
  • Review
  • Route
  • Track
  • Audit
  • Learn

Filing and deadline pack

Extracts dates from matter files, tracks them against statutory deadlines, and escalates before anything slips.

  • Ingest
  • Extract
  • Verify
  • Calculate
  • Generate
  • Review
  • Route
  • Track
  • Audit
  • Learn

Document drafting pack

Turns standard instructions into a first-draft document, checked against clause libraries, with every change logged.

  • Ingest
  • Extract
  • Verify
  • Calculate
  • Generate
  • Review
  • Route
  • Track
  • Audit
  • Learn

How we work

Five steps, no surprises.

  1. 01

    Diagnostic — two hours on site. We identify where the revenue leaks or the delays happen.

  2. 02

    Design — a one-page block diagram of the proposed shape, with scope and cost.

  3. 03

    Build — two to six weeks, depending on the shape.

  4. 04

    Handover — SOP, audit pack, training. Your team owns it.

  5. 05

    Retainer — we keep the blocks working, and we add new ones when you need them.

What makes this different

Four things most tools skip.

  • Built in blocks, not in one piece. If one part needs to change, the rest does not.

  • Every action is logged. Audit is a block, not a feature. It runs whether or not anyone asks.

  • Your team stays in the loop. Review is a block, not an afterthought. Machines propose. People approve.

  • Local compliance is built in. PDPA, data residency, and WhatsApp Business integration are configured before the first block is turned on.

Two hours on site. Clear answers on what to build first.