Sorellan & Kairoth

The back office, run by digital workers.

A digital worker reads what arrives, does the routine the way your procedures say, and stops at the decision only you can make. Built by a founder who audited at a Big Four firm, then ran finance and operations at a multi-facility operator.

Not a chatbot. Not a dashboard. Not a copilot waiting for a prompt. A worker with a queue, a procedure, and a supervisor — you.

↓ Where the work waits

A representative audit record: the disbursements worker (version 4) approved a payment because the vendor is on the whitelist, the invoice is within tolerance, and the general-ledger code matches the prior fourteen invoices — confidence 0.96, approved by the controller under policy version 4, written to an immutable, timestamped record.

Where the work waits

Six places the work piles up. The money goes with it.

None of this needs a licence. All of it is done by licensed and senior people because there is nobody else. A digital worker takes the routine; the decision stays with the person whose name is on it.

  1. 01

    Denied and underpaid claims

    A remittance comes back short. Nobody has time to read it against the contract page, so it is posted as a contractual adjustment and disappears.

    The worker
    Reads every remittance line against the rate you actually agreed, drafts the appeal with the evidence attached, and queues it.
    You
    You sign the appeal, or you don’t.
  2. 02

    Records requests with a clock

    A payer, a regulator, or opposing counsel asks for a packet. The clock runs from the date on the letter, not the day it is opened, whether your best person is on vacation or not.

    The worker
    Assembles the packet from the record, flags what is missing, and tracks the clock from the day the letter arrived.
    You
    You approve what leaves the building.
  3. 03

    Invoices, approvals, and the close

    The pharmacy invoice is approved by an administrator who has never seen the contract price. The close runs late because the month is reconstructed, not recorded.

    The worker
    Codes and matches each invoice, routes it under your approval limits, and keeps the ledger current as the month happens.
    You
    You approve the exceptions. The routine is already done.
  4. 04

    Compliance that is sampled, not read

    Your audit reads a sample of the files. The surveyor, the examiner, or the plaintiff opens the one you missed: the psychotropic without an indication, the pre-authorisation that lapsed.

    The worker
    Reads every file against the rule that applies to it, every night, and lists what does not comply.
    You
    You decide what to fix first.
  5. 05

    Onboarding, credentials, and paperwork

    A nurse aide’s certification expires, a hygienist’s licence lapses, a new hire waits on a form. The people chasing documents are the people you hired to do something else.

    The worker
    Chases the documents, files the forms, and keeps the roster and the expiry dates current.
    You
    You see the list of what is still outstanding, and who.
  6. 06

    Reporting that arrives late

    The census, the aging, and the days in receivables you need on Monday are ready on Thursday, and by then they have been re-keyed twice.

    The worker
    Assembles the report from the systems you already own, with each figure traceable to its source row.
    You
    You read it. You do not build it.
What a digital worker is

A chatbot answers. A dashboard shows. A copilot suggests. A digital worker finishes.

Software gave your people a place to do the work. A digital worker does the work. It reads the inbox, the portal, the fax queue, and the record; it follows your procedure step by step; it writes down what it did and why; and it stops at the point where a person has to decide.

So the screen you look at is not a list of tasks waiting for you. It is a short queue of decisions, with the finished work behind each one and the evidence one click away. The handled column is long. The needs-you column is short. That inversion is the whole product.

  • Follows your procedure
  • Reads, never guesses
  • Stops at the decision
  • Writes it all down
How it gets built

Three things from you. No workshops.

Your team’s time is the one thing we do not ask for. A worker is built from what already exists in your operation.

Your procedures

However they exist. A binder, a shared drive, or a veteran’s habits written down. The worker does the job the way your procedure says.

Read-only access

A replicated copy of the systems you already run, on credentials you issue and can revoke the same day. Nothing writes to a system of record until you have watched it be right.

The expected output

The report, packet, or number your team already produces. That is the target the worker is measured against, in your numbers.

First it watches. It produces the same output your team produces, next to theirs, at your buildings, in your numbers. Then it does the work, and your people review finished work instead of preparing it. Capacity grows without another hire. The labour effect is measured at your buildings, in your numbers, during the engagement, and never promised before it.

Who builds this

Most digital workers are built by engineers who have never closed a month, sat for an audit, or owned the P&L. One founder. Four seats, all held.

01 Auditor Big Four. Sat across the table as the auditor.
02 CFO Owned the close, the controls, the board number.
03 Operator Ran the operating company, not a slide about one.
04 Engineer Now builds the workers those seats needed.
How it holds up under audit

A person at every gate. A receipt behind every action.

Bounded

Nothing money-facing or payer-facing leaves without a named approver. Your roles decide who can approve what. The worker cannot widen its own authority.

We ran the operation

Recorded

Every action is a row: what was read, the reasoning in plain English, the confidence, the person who approved it. Timestamped, immutable, replayable. The record is the walkthrough.

We sat for the audit

Read-only first

Workers read a replicated copy on credentials you issue and can revoke. In the first iteration they write to nothing. A wrong answer is a wrong recommendation on a screen a person then rejects.

We owned the downside

Policy as code

Approval limits, roles, and rules are versioned. Every decision remembers the exact policy in force when it was made. The kill switch fails closed.

We signed the rep letter
Where it stands

Built. Running on production-scale data. Ready for its first operating partner.

It is not in production anywhere yet, and we say so. The first engagement is read-only, runs in shadow next to your team, and is measured in your numbers. Fixed fee, fixed window, terms in writing.