Four products. Three visible control points. One underlying execution layer.
Encapsulated is organized this way because firms lose control in different places for different reasons. Accepted setup is not the same problem as live workflow. Live workflow is not the same problem as financial review. And none of those stay clean for long if the movement underneath them is brittle, hidden, or hard to recover.
Begin where the firm is already paying the highest cost for disorder.
Why the products are separate
A firm can have weak setup and readable live work. It can have readable live work and still spend too much effort preparing for financial review. It can improve all three and still be carrying fragile jobs, retries, vendor dependencies, and quiet recovery work underneath them.
That is why Encapsulated is not arranged as one broad platform with a long feature list. The products are separated where the operating failures are separated. The first three are the visible control points. SQLX is the layer underneath them that helps keep the visible chain trustworthy.
Client Onboarding controls what is allowed to become accepted setup
Client Onboarding
The first operating decision is whether incomplete intake is allowed to become an accepted record. Client Onboarding governs that threshold. Required data, documents, approvals, billing details, engagement detail, and validation are handled before STAR inherits the setup.
That matters because weak entry never stays at entry. Missing contacts, unresolved exceptions, informal approvals, and incomplete setup reappear later in tax, audit, billing, client service, and operations.
When a client record is created before billing terms are settled or required documents are actually in hand, the system has already accepted uncertainty as if it were finished. Client Onboarding prevents that handoff.
Tax Dashboard keeps live work legible while it is moving
Tax Dashboard
Once work is active, the next risk is fragmentation. Requests, signatures, client documents, routing, exceptions, and handoffs spread across portals, email, the DMS, and private follow-up. The work still exists, but the team no longer has one dependable reading of what is happening now.
Tax Dashboard becomes that working surface. It keeps requests, receipts, review state, signature progress, routing, and the real point of delay attached to the return while the work is still underway.
If a K-1 is still missing, a reviewer note is still open, or an e-file authorization has stalled, the team should not have to ask three systems and two people before it can move the return forward.
Financial Dashboard lets leadership review without assembling the picture first
Financial Dashboard
By the time leadership reviews WIP, net billings, collections, AR, and budgets, the data usually already exists. The burden is the preparation wrapped around it: repeated STAR exports, spreadsheet stitching, manual cleanup, and side-by-side reconciliation before review can even begin.
Financial Dashboard gives leadership a cleaner path from firm-level signal to client and engagement detail, with fewer resets around period framing, comparisons, and the question of which version should be trusted.
If collections trail plan in one month and someone asks whether the issue sits in one office, one partner group, or one cluster of clients, the meeting should move into the detail immediately instead of breaking for another reporting exercise.
SQLX governs the execution layer underneath the visible products
SQLX
The visible products deal with accepted setup, live workflow, and financial review. Underneath them, jobs still run, files still arrive, vendor calls still return, states still update, retries still matter, and failures still need clean recovery.
SQLX gives that recurring system work a stronger operating standard for scheduling, logging, permissions, retries, recovery, and controlled change, so the visible parts of the system are not resting on hidden scripts, patched services, and person-specific repair steps.
If an overnight update fails and the workflow surface no longer matches what actually happened underneath, the firm does not experience that as a technical abstraction. It experiences it as doubt about the work. SQLX is there to prevent that doubt from becoming normal.
Choose the first product by the strain the firm already feels
The products form one operating system, but firms do not need to enter all of it at once. The right first move is usually the part of the business already paying the most in correction work, follow-up, reporting preparation, or fragile recurring movement.
1
Client Onboarding
When weak setup keeps creating downstream correction work.
2
Tax Dashboard
When live execution has become hard to trust across requests, documents, routing, and review.
3
Financial Dashboard
When leadership still needs exports, workbooks, and explanation before review can begin.
4
SQLX
When recurring system work has become too important to remain brittle, hidden, or person-specific.