Specs and prototypes that arrive ready to build.
You write the spec in Claude, build the prototype in Make or v0, and hand it to engineering. sleds is the hand-off: your AI asks what a good engineer would ask, reads the product map, puts the prototype on the row, and files a request that's sized before anyone starts. You set what it's worth, and you see what's in flight, waiting and landed.
Who builds is changing. sleds serves the seam.
Business users are moving toward engineering: writing the spec, building the prototype in Make or v0 or Bolt, filing the request with the repro. Engineers are not moving the other way. The builder tools make you productive on your own; the coding agents make engineers productive on theirs. The seam between you is where the cost and the hand-off are, and it is where nothing sat until now.
Intake sits there. It asks the questions a good engineer would ask, turns the answers into a shape an engineer can size without losing the why, and shows that why first to whoever picks it up.
A brief, not a ticket.
Every field says where it came from: your words, the artifact, or the product map.
Who it is for and why now, from your spec or your words.
What done looks like, and the smallest version still worth doing. Smart routing sizes the smallest first.
The areas and repos from the product map, and what on the board collides with it.
Your Make or v0 prototype and screenshots on the row. Ask your AI for a clickable prototype in your design system, and it is the request.
Stated by you, marked as yours. Due dates move the routing.
How many customers or teams asked. Demand is a signal smart routing uses.
You say what it's worth. It shapes what runs.
Worth is value and priority on one gauge. You set it at intake because you know what it's for; a lead can adjust it on the board; over time sleds suggests it from your own stated and landed rows, always overridable. Tokens never become worth, and a missing worth is never a low: rows with no worth wait and ask the filer.
unvalued 5 rows · ask the filer waiting 2 rows · product's yes in flight 6 rows · $31k worth landed 9 this week · $35k worth · all receipted
Review what came in. Say what it's worth.
Everything requested, in one place, priced before it runs.
waiting on product2
ready6
on the sled8
landed11
In flight, waiting, landed. From your own AI.
The same aggregates the board shows are what the connector answers with, by area.
sled: size this specA letter, a band, which model fits, a confidence, a cap. Recorded before anyone commits.sled: send this to engineering, worth high, Acme renewalQuestions if the spec left gaps, then a brief, then a row on the board with the estimate on it.sled: where is ENG-482Who has it, what it has cost against the band, what is waiting on you.sled: what happened with the Acme thingLanded Thursday, 31 min, $5.20, overnight. The receipt, in your words.sled: what does this touchThe repos and areas from the product map, and what on the board collides with it./sled wallThe six exits, priced, from inside your own session./sled handoff ENG-471 to DanaParked with the brief and the snapshot. Dana hears where it is and can decline without explaining.sled: what's stuck in billing4 rows waiting on review, 2 days median, $48k worth waiting. Never who has the most open.sled: helpThe whole table. Generated from one file so chat, terminal and app never disagree.Hand off the spec, not a ticket.
Request an invite and file your first spec with its prototype.