Skip to content

The operating substrate for an MSP

Every surface of the practice, one system underneath.

ClearStax is the vendor-neutral Managed Intelligence Platform — the substrate that runs an MSP's entire operation. Seven surfaces share one accountable record, and every capability resolves to a provider, evidence, a risk, and a client-ready report. No silos, no parallel ledgers, no lost handoffs.

RUN · Run the practice

Run the practice on one record.

Clients and business economics live on the same accountable record — pipeline, onboarding, contracts, and the cost of serving each client, in the system the rest of the practice reads from.

CLI

Clients

One record per client, from first contact to renewal — the spine of the system of record.

  • Client record

    Contacts, companies, deals, and proposals in one record the whole practice reads from.

  • Onboarding

    Onboarding records linked directly to delivery work and compliance evidence.

  • Contracts & renewals

    Contract and renewal pipeline tied to the client's operational and evidence history.

  • Client health

    Health scoring derived from live operational signals, not manual status fields.

BIZ

Business

See the cost and margin behind every client and service — modeled today, moving toward discovery from telemetry.

  • Cost & margin modeling

    Model the cost of each client and service from your cost components and accounting sync, not guesswork.

  • Margin per service

    Cost and margin per client and per service, on the same system of record.

  • Before renewal

    Profitability surfaced before the renewal conversation, not discovered after.

  • Toward telemetry

    Cost discovery from live operational telemetry is the direction, rolling out.

See how founder-partner scoping works

PSA · Deliver the work

Deliver the work where the context lives.

The service desk and IT operations read from the same client record — tickets carry SLA, owner, and asset context, and work is coordinated across the tools you already run.

SVC

Service Desk

Tickets, SLAs, and work that shares state with the client record and the evidence model.

  • Tickets & SLAs

    Tickets, SLAs, and escalation routing with operational ownership.

  • Shared state

    Service-desk work shares state with the client record and with evidence — no handoff tax.

  • Time & ownership

    Time entries, owners, and operational state recorded against real assets.

  • Ingests your stack

    Reads from the RMM and tools you already run; coordinates work without replacing them.

OPS

IT Operations

Coordinates work from the RMM, identity, and backup tools you already run, and routes it to the service desk with context — rolling out.

  • Coordinates your stack

    Coordinates across the RMM, identity, and backup tools you already run, rather than replacing them (rolling out).

  • Routed with context

    Work is routed to the service desk with the client and asset context already attached.

  • Asset & endpoint inventory

    Asset and endpoint inventory drawn from your existing operational stack, organised by client (rolling out).

  • Above the stack

    Coordinates the tools you run rather than replacing your RMM, EDR, or backup.

Browse supported integrations

CMP · Prove the work

Prove the work with records, not checkboxes.

Auditor-grade evidence — every control resolves to a source, owner, and timestamp, linked back to the work that produced it. Your auditor and your client read the same artifacts.

  • Controls & remediation

    Controls, remediation tracking, and reviewer workflow in one assessment model.

  • Frameworks you need

    Assess against the frameworks your clients actually need from a single workflow.

  • Recorded evidence

    Evidence carries a source, owner, and timestamp, linked back to the work that produced it — not a checkbox.

  • Audit-ready

    Auditor export and retention with forward-linked records. Client-ready from the same model.

Controls mapped to evidence · illustrative sample

SOC 2 · CC8.1

Change management

EVD-CC8.1-014

Signed change log · asset-bound

CIS v8 · 6.3

MFA for external applications

EVD-6.3-021

MFA enforcement export

NIST CSF · PR.DS-1

Data-at-rest protection

Evidence pending · queued to roadmap

Encryption-at-rest attestation

EVD-CC8.1-014 CS-1042

Every evidence artifact points back to the closed ticket that produced it.

Evidence is refreshed through automated recurring checks against connected sources, where integrations are configured. Where a check isn't wired up yet, the gap is shown as pending — never papered over.

How records are protected

RCH · Grow through trust

Grow through trust, not slideware.

Trust-led pipeline backed by the same evidence model your auditor sees. Posture conversations start from real scan artifacts and end as pipeline — on the same record as the rest of the practice.

Read the operating notes on the blog
GRW

Growth

  • Guarded scanner

    External security scanner covering DNS, SSL, headers, and exposure — guarded by design.

  • Attach to client

    Scan artifacts auto-attach to the client record inside the system of record.

  • Evidence-backed proposals

    Proposals backed by real evidence, not slides — outbound that earns the meeting.

  • Handoff reports

    White-label client-handoff reports drawn from the same model.

RUN · PSA · CMP · RCH — every pillar

An accountable AI workforce — not a chatbot bolted on.

ClearStax agents are first-class operators across every surface — observing and proposing on the same system of record the rest of the practice runs on, under a Trust Ladder with per-tenant trust-phase governance.

  • Works everywhere

    Agents observe and surface proposals across clients, service desk, IT operations, compliance, and reporting.

  • Trust Ladder

    A Trust Ladder with per-tenant trust-phase governance gates what agents may do — starting in Shadow and earning the right to act.

  • Agent health

    Agent-health and activity visibility so the operator always knows what ran.

  • Recorded proposals

    Every agent proposal records an actor, source, and timestamp, linked back to the work that produced it — inspectable and approvable.

Every agent proposal is recorded as actor: agent.<name> — the same provenance model as a human operator. Operators inspect, approve, or reject before anything commits. There are no silent agent decisions and no black-box automation.

See the operating model.

A 30-minute walkthrough with the founder — your practice, mapped onto the platform.

Book a demo