The Sledge Blog

One runner, one Saturday. You penciled in 10 km at tempo — then ran 14 on Tuesday, slept five hours, and rain is forecast from six. A readiness score tells you it's an amber day; it never tells you what to do with Saturday. The missing layer: given your state and what you were actually about to do, what the session should become — before you're too deep to change it.

A runner sets a 10K in 45:00. At km 7 her watch shows 4:32/km. Every watch shows the number — none of them answer the question. This is the specific gap the next quarter of Sledge is being built to close: pace against your own shape, live, while you're running the line.

Four posts in June, one shape underneath. Every real-world experience has a rhythm — before, during, after, and next. Most tools own one beat and lose the others. Here's the argument, pulled from the feed into one durable read.

Listings are no longer where experiences begin — they're where experiences get repeated. A founder's account of the wound that reframed the whole product: experiences dissolve, and Sledge is adding the layer that keeps them.

The first live test of Sledge's Games tab — queue, live scoring, match history, and winner-stays-on — running during a birthday gathering. About a dozen people, a beer pong table, and a phone in the host's pocket.