Platform
Your stack
We build a working model of your organization from the tools you already run, without asking you to change how you operate.
Your stack
What you get
A new platform usually means a new inbox and a migration. The tools a company runs should stay where they are, and the organization should be modelled from them.
A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.
Works in the tools you already run
Through your toolsYour issue tracker, repositories, pipelines, chat, incident tool, CRM and document store stay where they are; the agent in the seat picks the work up there and answers there.
A working model of your organization, built from your tools
Through your toolsWe build the model of your organization from the tools you already run, without asking you to change how you operate.
Connect a tool that is not on the list
Through your toolsA tool we have not connected yet connects through the standards it already speaks: webhooks, OAuth and MCP; in a discovery conversation we build it before the demo.
How it plugs in
Through your toolsClrSlate connects to your repositories, trackers and chat as an app: it holds a decision as a check the owner clears, asks the owner where they already work, and carries out what was decided.
The tools,by category.
Each with what happens there, and the job that shows it.
Issue trackers
A ticket is assigned to a seat; the agent picks it up and the owner gets a review packet.
At work: Code review and release that keep pace with coding agentsRepositories
A pull request opens; its owner is asked, with the checks and the packet.
At work: Code review and release that keep pace with coding agentsCI pipelines
A release is ready; its owner approves and the pipeline deploys in the window.
At work: Code review and release that keep pace with coding agentsCoding agents
The agent works in a seat, answers to a person, and asks above its limit.
- Agents you built
- Claude Code
- Cursor
- Gemini CLI
- GitHub Copilot
- OpenAI Codex
Chat and email
Mention the seat and get a plan; decisions arrive where the team already talks.
- Microsoft Teams
- Slack
Alerting and incidents
An alert fires; the on-call lead decides what touches production.
At work: Environments and production changesCloud and platforms
A project, a namespace or a database is a request with a standard and a decider.
At work: Environments and production changesCRM
A key account escalates; it gets an owner, a cause and an answer.
At work: Customer escalations into the backlogDocument stores
A spec or a runbook is drafted; the right seats answer; the version is on the record.
At work: Your procedure, run by the agentIdentity providers
People sign in with the identity you already run; seats and roles follow from it.
At work: A coding agent joins the teamModel providers
Every call goes through one gateway, with the models each seat may use.
- Amazon Bedrock
- Anthropic
- Azure OpenAI
- Google Gemini
- Models you host
- OpenAI
Business systems
A change, a case or a request raised there lands on the seat that owns it; above a limit, a person signs off, and the record links back to the ticket.
At work: A coding agent joins the team
A tool not on the list connects through the standards it already speaks: webhooks, OAuth and MCP.
Where the handover happens
In your own tools, drawn as they show it.
Your repository host · invoicing-service
Add entity column with backfill #4812
- TestsPassed
- Security scanPassed
- CClrSlate · waiting on Ana OkaforRequired
In your repository host: the owner’s decision is a required check.
Your team chat · #payments-eng
Invoicing service agent Agent
Not this one: schema changes are Ana’s to decide. She has the packet.
Waiting on Ana Okafor · Head of platform
Schema change: invoicing service
In your chat: the agent asks, the owner decides in the thread.
Your issue tracker · Payments
PAY-1182
Retry rule for payout batches
- Assigned to
- SBInvoicing service seat
- Status
- In review
In your tracker: the ticket is assigned to a seat, not a queue.
Your alerting · payouts
Payouts delayed
02:10 · Tuesday
Owner paged: Joon Park, on-call lead
In your alerting: the owner is paged by name.
How it plugs in
ClrSlate connects to your repositories, trackers and chat as an app: it holds a decision as a check the owner clears, asks the owner where they already work, and carries out what was decided.
- 01Connects to your repositories, trackers and chat as an app
- 02Holds a decision as a check the owner clears
- 03Asks the owner where they already work, and carries out what was decided
At work,job by job.
The jobs that use this part, each with how it runs.
- HaldenCode review and release that keep pace with coding agents
- HaldenCustomer escalations into the backlog
Told end to end
Halden, Corvane and Kestrel Labs are fictional companies.
The rest of the platform
Start with howyou run today.
Bring one piece of work that breaks at the handoffs: a pull request waiting on three reviewers, an initiative spread across twelve tools, a release nobody owns. We model the seats it crosses, give one of them an agent, and follow one decision to its record.