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
Scellus operations engine
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
Brings source material into the system.
Turns unstructured input into structured records.
Cross-checks data against sources and flags issues.
Applies rules and compliance logic to produce numbers.
Produces the working output you hand off.
Gives a person controlled approval over machine output.
Moves work to the right person, queue, or next step.
Watches deadlines and time-sensitive events.
Records what happened, when, and on whose authority.
Captures reviewer corrections and feeds them back into the rules.
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
New client documents become a verified file, ready for engagement. Replaces the opening week of manual checks, form chasing, and compliance review.
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.
Extracts dates from matter files, tracks them against statutory deadlines, and escalates before anything slips.
Turns standard instructions into a first-draft document, checked against clause libraries, with every change logged.
How we work
Diagnostic — two hours on site. We identify where the revenue leaks or the delays happen.
Design — a one-page block diagram of the proposed shape, with scope and cost.
Build — two to six weeks, depending on the shape.
Handover — SOP, audit pack, training. Your team owns it.
Retainer — we keep the blocks working, and we add new ones when you need them.
What makes this different
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.