Solution · Content and publishing
How we run ClrSlate on ClrSlate
The founder decides what carries his name and what is his to decide; agents carry the rest, and the record shows both.
CSFounder’s desk
Waiting on your word
- A post in your nameFounder brand seat · drafted by its agentYour approval
- Which concept becomes the live pagePublic website seat · options preparedYour decision
- A follow-up to a demo requestSales development seatSent by its seat
Waiting on Piyush Rathi · Founder
A post in your name, drafted by the founder brand seat
Post, then Piyush approves, then Published.
How it runs
Our company is modelled in ClrSlate: a founder seat with the office of the CEO’s agent; a Product Marketing Manager seat; an Organization Brand Manager and a Founder Brand Manager, so that every post in Piyush’s name is drafted by an agent and approved by him, every time; a Growth Manager; and a Sales Development Rep who owns the follow-ups. At founding one person often holds several seats; the chart says which.
A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.
Rule
Nothing in the founder’s name without him
- Agent carries08:30The roll-up on the founder’s desk
- Rules check08:45
Rule
Nothing in the founder’s name without him
- Person decides08:45Piyush approves the posts, asks for one change
- Agent carries09:30A demo request gets its follow-up drafted
- Person decides13:00Piyush decides which concept goes live
- Person decides15:00The go to publish, naming the action
- Agent carries19:00The day reconciled; the playbook learns
ClrSlate, run on ClrSlate
- 01Piyush Rathi, founderReads the daily roll-up: what moved across the teams, what is blocked, and the decisions that are his.
- 02The Founder Brand Manager seat’s agentDrafts the posts in his name; he approves some and asks for a change on one, from the desk.
- 03The Sales Development Rep seatTakes a demo request from the site with the visitor’s message; the agent drafts the follow-up, the person sends it.
- 04The Product Marketing Manager seat’s agentHands over the day’s copy with the decisions it needs.
- 05Piyush Rathi, founderDecides which concept becomes the live page, with the options and who prepared them on the record.
- 06The public website seatAsks for the go to publish; the approval names the action, and the pipeline deploys.
- 07The office of the CEO’s agentFiles a conversation from the event against what we want to learn, and proposes a follow-up.
- 08Piyush Rathi, with the officeReconciles the day with the office: what moved, what failed to hand over, what the playbook learns.
Where the decisions sit
Decision, who decides, up to where, and above that whom.
- Anything published in the founder’s nameDecides: the founder, every time——
- A post fits the brand planDecides: the Founder Brand ManagerUp to: the plan as approvedAbove that: the founder
- Copy in the company’s nameDecides: the Product Marketing ManagerUp to: the approved positioningAbove that: the founder
- Which concept becomes the live pageDecides: the founder——
- Publishing a releaseDecides: the founder approves the goUp to: the release as prepared—
- A follow-up to a demo requestDecides: the Sales Development RepUp to: approved copyAbove that: the founder, for a new claim
How much the agent decides, to start. The founder’s name asks every time and stays so. Drafting, scheduling, the follow-ups and the roll-up run within limits; a new claim, the live page and the go to publish ask the founder.
The record it leaves. Every decision of the day: who asked, who prepared it, which rule applied, who decided and what was done. The event was one brief in the founder’s seat, reconciled each evening and captured as a playbook.
How it plugs in
No new inbox, no new tool to learn.
- 01
An app in your tools
Connects to your repositories, trackers and chat as an app
- 02
A check, not a meeting
Holds a decision as a check the owner clears
- 03
Where people already work
Asks the owner where they already work, and carries out what was decided
- Who decides · Piyush Rathi · Founder · anything in his name, every time
The tools it runs through
- Issue trackers
Azure DevOps BoardsGitHub IssuesJiraLinear
- Coding agents
Agents you built
- Chat and email
EmailMicrosoft TeamsSlack
- Alerting and incidents
DatadogGrafanaOpsgeniePagerDutySentry
- CRM
HubSpotSalesforce
- Business systems
Microsoft Dynamics 365SAPServiceNow
We connect to the systems you run, and build the connection before the demo.
From the catalog
Where it leads
Start with howyou run today.
Bring one piece of work that breaks at the handoffs: an initiative spread across twelve tools, an escalation nobody owns, a launch waiting on the founder. We model the seats it crosses, give one of them an agent, and follow one decision to its record.