How it works
Founders Climb
Products move forward through consequential decisions — not through completed tasks or accumulated deliverables. Most work fails quietly because ambiguity goes unresolved, decisions dissolve back into conversation, and effort never compounds into judgment. Founders Climb makes meaningful work legible — what you’re building, the question you’re inside right now, what you’ve decided, what you’ve made, and what you’ve learned — and hands you that legibility every morning in under a minute.
What it is
One method, and the platform that runs it. Founders Climb is built and operated by Summit, a brand, product, UX, and digital experience studio organized around a repeatable decision-making process rather than a menu of services. The studio runs its own work here, in the open, on the same objects clients get. What we say in a conversation is what you see in the portal.
It is an orientation system, not a task manager. A to-do list tells you what to do next; Founders Climb tells you where you are. Tasks are the smallest, cheapest object here — the weight sits on questions, decisions, and reflections, the things that actually accumulate into judgment.
Three ways to be inside it
The model never changes. A Domain, the Hill being climbed, the Question on the current Climb, the Decision at its Summit. What changes is who does the climbing and who carries the decision — and that is the only difference between these three.
Summit runs itself here. Client acquisition is a Hill with no target date — never finished, only stewarded — carrying a weekly Climb. We don’t ask clients to work in a system we wouldn’t.
The First Climb opens your Domain and resolves the first consequential decision; Additional Climbs resolve the ones that follow. We do the exploring and make the artifacts. You commit at the Summit — the decision is always yours.
A team doing the work internally runs its own Domain — its Hills, its Climbs, its Decisions — with the studio reading alongside and returning judgment rather than production. The ongoing form of this is being reworked and isn’t currently sold; the shape it should take is a question we’d rather answer with the people already in it than guess at.
Every client has exactly one Domain and sees only their own, always. The studio works across every Domain it has been invited into; a client is only ever inside theirs.
Who it’s for
People doing meaningful work under real ambiguity — founders, CEOs, product and design leaders, small leadership teams, anyone whose output is judgment rather than throughput. The strongest fit has a meaningful initiative, a consequential unresolved decision, and one person who can commit to a direction. If the hard part is deciding what’s true and what matters, not remembering your errands, this is built for you.
The one idea
There are two layers, and they never collapse into each other. The meaning layer is where work has significance: a Domain holding your vision, and inside it one Hill at a time — the product, project, or pursuit you are moving forward right now — climbed through time-boxed Climbs organized around a single question, each reaching a summit — the moment the question resolves into a decision — then evidenced by artifacts and closed with a reflection. The attention layer is where you spend finite time — today, and only today. It points at work in the meaning layer; it never owns it. Pulling a task into today doesn’t move it, it aims at it. That’s why daily life stays light while the record stays meaningful.
The loop
You climb one Hill at a time. Progress happens in Climbs — a bounded period asking one question. You explore it through actions, reach the summit when the question resolves into a decision, evidence it with artifacts, and close it with one reflection that feeds the next climb. Enough Climbs and the Hill is behind you; then the next one begins. Daily texture is a one-line update, not a ceremony.
Why now
Execution is becoming abundant. Work can be written, designed, coded, and prototyped faster than at any point in the past. But more options do not create clarity on their own — they often make commitment harder. As execution becomes cheap, orientation becomes scarce. Tools execute and AI can reduce uncertainty, but neither can hold the consequence of a choice. That belongs to a person, which is why this is organized around decisions rather than deliverables.
How to use it
- 1Open a Domain and write its vision — the whole of what’s being built, and what holds it together.
- 2Name the Hill you’re climbing and write its chief aim — the vision you’re moving toward, not a tagline.
- 3Start a Climb around a real question. Lead with inquiry (“what must we resolve?”), not just scope.
- 4Check in daily with a one-line update. Pull a few actions into today; complete or release them as the day moves.
- 5When you decide something, record it. Decisions are immutable — a change is a new decision that supersedes the old one, never an edit.
- 6Close the climb with one honest reflection. It’s gated on a recorded decision and spawns the successor climb on the chain.
- 7Read the hill’s history — the accumulating story of what you built, decided, and learned. That’s the payoff.
What it refuses to be
No estimates, no dependency graphs, no gamification, no social feed, no notification stream. Not an unlimited design subscription, not a menu of disconnected deliverables, not a way to avoid making a decision. The discipline is the point: heavy objects appear only where meaning actually occurred. The biggest risk to a system like this isn’t scale — it’s dilution.