What changed on the new Scellus website?
The new scellus.com is live, and it now reflects the way we actually run work: functional blocks connect into workflow stacks, and Scellus operates those stacks against named outcomes.
Instead of presenting a service list, the site shows the operating model behind the work. Visitors can now see how blocks such as Collect, Read, Verify, and Deliver become managed workflows for intake, claims, billing, document control, and other recurring operations.
What is the Scellus Model?
The Scellus Model has three parts:
- A block is one function with a defined input and output, such as Collect, Read, Verify, Chase, Review, or Deliver.
- A workflow stack is a sequence of blocks built around a recurring process, such as intake, billing, claims, or document control.
- A managed outcome is the result Scellus operates toward on a schedule your team can check.
Once a workflow stack is scoped, Scellus builds, operates, monitors, and improves the workflow with your team. Your team keeps the judgment calls; Scellus runs the repeatable collection, reading, checking, chasing, review preparation, and delivery work around them.
Which functional blocks does Scellus operate?
The new site makes the Scellus operating vocabulary visible. Each block page explains a reusable function that can appear inside many different workflow stacks.
- Collect. Capture requests, messages, files, and form submissions from scattered channels so work starts from one shared record.
- Read. Turn documents, emails, uploads, and attachments into the fields a workflow needs before anyone reviews the file.
- Verify. Compare what was captured against the rules, source records, registries, or policy checks that decide whether it can move forward.
- Chase. Keep follow-ups moving when documents, approvals, payments, or answers are missing, with the next request tied to the same record.
- Review. Package the evidence, exceptions, and context so a person can make the judgment call instead of rebuilding the file.
- Deliver. Send the finished record, export, update, or handoff to the place the team already uses, on the cadence the workflow requires.
You can trace any workflow Scellus runs back to this set. The block pages explain the reusable building blocks; the workflow pages show how those blocks combine into a specific operating rhythm for intake, billing, claims, document control, and other recurring work.
Which industry pages are new?
Capture, billing, and visibility problems look different by industry, so we split them out. The new Law Firms, Professional Services, and Logistics pages each cover the specific version of intake, billing, claims, or document control that industry runs into.
That matters because the same operating model does not mean the same workflow in every setting. A law firm intake workflow has different verification steps from a logistics claims workflow. A professional services billing workflow has different handoffs from recurring charges. The industry pages make those differences easier to see before a review call.
Which managed workflows are documented?
Three managed workflows are documented in full:
- Claims Processing
We match receipts to claim forms, apply policy rules per claim, and deliver a payroll-ready export before the cut-off date. - Client Intake
We turn inquiries from WhatsApp, email, and web forms into complete, review-ready records, so your team spends its time on judgment calls instead of data entry. - Recurring Charges
We run cards, mandates, pro-rata billing, dunning, receipts, and reconciliation on a fixed calendar, so billing stops depending on someone remembering the date.
Each page states what we operate, what your team still decides, and what a named outcome looks like.
Where should you start?
Start with the workflow that leaks the most time, not a full operating-model redesign. Book a Workflow Review and we will map the channels, rules, handoffs, and named outcome that Scellus would operate with your team.