IntakeAnyone files from Claude or ChatGPT, in a real conversation.The board and DocsEvery request with its brief, size, worth and seat, and the specs and decisions beside it.Smart routingThe best seat and the best model for every request.The recordEstimate against actual, signed. Better with every row.ConnectionsClaude, ChatGPT, Claude Code, Codex, GitHub, Slack and more.
Business teamsSales, success, ops: send the customer's request and hear when it lands.Product teamsSpecs and prototypes that arrive ready to build, and a say in what runs.EngineeringThe right work, on the right seat and model. For engineers and leads.
Docs and helpEvery verb, every surface.Developerscurl -fsSL sleds.ai/install | shTrustWhat we keep, and the exceptions.ManifestoWhat we are doing, and why.Claude connectormcp.sleds.ai/mcpSelf-hostThe record in your cloud, on your keys.ContactTalk to the people building it.
Request an inviteSign in
sleds/Resources/Contact
contact · what we ask for up front

Start with one engineer.

One line on one laptop is useful the same day and costs the workspace nothing. When the team wants the board, routing, the roll-up and the policy, write to us through the invite form and we set the early-access terms together.

Request an invite
what helps us help you

Four things to tell us.

Agents

Which agents and seat platforms the team runs today.

Where work lives

How requests reach engineering today, and whether they carry a size or a priority.

Key

Whether a platform key exists and who holds it.

Policy

A name for the policy at the wall: hold by default, or continue within an allowance.