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/Use cases/Business teams
Intake world · the business requests
business teams · sales · success · ops · anyone

Send the customer's request. Hear when it lands.

You talk to customers all day, and you already have Claude or ChatGPT open. Now you can send what they asked for straight to engineering from that same chat, with the screenshot and the deadline, and get an answer back in the same place. No seat, no ticket form, no chasing anyone in Slack.

Request an inviteHow intake works
chatgpt · Priya, customer success · sleds connectorno seat needed
PriyaNorthwind says exports time out on their big workspace. They renew in November. Here's their screenshot and the error.
screenshot.pngerror.txt
sledsThe export job hits the 30-second limit over 10k rows. It touches api › exports. Who's waiting on it, and by when?
Their admins, plus two accounts that asked last month. Before Oct 15.
sledsOn the board as ENG-503 · M · $6–14 · 30–70 min, worth high. Routed to Dana for tonight. I'll tell you when it lands.
sleds · oct 3 · 06:20ENG-503 landed. Large exports now run in the background and email a link. Actual $5.80 · 44 min, overnight.
what changes

From "I'll ask engineering" to "it's on the board".

beforeA DM to someone who knows someone

The request lives in a thread, loses the screenshot, and nobody knows if it's being worked.

with sledsOne sentence in the chat you already have open

Your AI reads what you attached, asks the two questions engineering would, and files it.

before"Any update on the export thing?"

You chase. They context-switch. The customer waits.

with sledsAsk it where you asked

"Where is ENG-503?" Who has it, what it has cost against its band, what is waiting on you.

beforePriority by who shouts loudest

Worth is a guess made in a meeting you weren't in.

with sledsYou say what it's worth

Renewal, churn risk, three accounts asking. Marked as yours, and it moves the routing.

questions come back to you

Engineering asks. You answer in a word.

When the engineer building it needs something, one question lands in your chat and as a Slack DM. Reply with a date, a number, or a word, and it goes on the row. If you already said it, your AI answers for you from what you sent.

SLEDSAPPSlack DM · 11:04 AM
Dana asked on ENG-503: Should the email link expire? Reply here and it goes on the row.
you: 7 days · answered on the row
what you get

Free for everyone in the company, forever.

No seat

A member of the workspace is enough to file, answer and check status. Seats are for the people who build.

Evidence travels

Screenshots, recordings, the customer's file: on the row, one click for the engineer.

A receipt

What changed, when, what it cost, in your thread. Forward it to the customer.

Any AI you use

Claude, ChatGPT or Cowork. The same questions and the same answers in each.

invite only

Bring your customer's request.

Request an invite. Your whole company can file from day one.

We'll only use it to reach you about sleds.
connectorhttps://mcp.sleds.ai/mcp