Monk mode for founders: shipping one thing in 30 days

Founders have a particular version of the focus problem. It isn't that they can't work; most of them work too much. It's that the work spreads. There is always a landing page to improve, a competitor to study, a thread to write, a tool to evaluate, an investor to have coffee with, a feature a user mentioned once. All of it is justifiable. Almost none of it is the thing.

Monk mode for a founder is not about working harder. It is about spending thirty days in which only one output counts, and everything that isn't that output is treated, politely, as noise.

Pick the one thing

The first job is to name it, and the naming is harder than it sounds. The test is this: on day thirty, a stranger can use it. Not "the architecture is in place". Not "the beta is almost ready". A stranger, with a link, no walkthrough, uses it and either gets value or doesn't.

If your project is early, the one thing is the smallest version that a stranger could use. If your project is live, the one thing is the feature, the pricing, or the fix that you've been circling for months because it's uncomfortable. The discomfort is usually the tell. The thing you keep not doing is the thing.

Write it in one sentence with a date. "Paid plan live, with a working checkout, by the 30th." Then stop improving the sentence.

What gets cut

A founder's season is defined mostly by what it excludes. For thirty days:

No building in public, unless it is the output. Writing about the work is the most respectable way of not doing it. If the thing is a product, the thread can wait until it's live. One short update a week to the people who care, and nothing more.

No research. You know enough. "Looking at how others do onboarding" is browsing with a job title. If a real question comes up during a block, write it down and answer it in the afternoon slot, with a timer.

No new tools. The stack you have is the stack that ships. Thirty days is not long enough to recover from a migration.

No redesigns. Ugly and live beats beautiful and local. The redesign is next season's one thing, if it still seems important then.

No founder social. The coffees, the Slack groups, the podcasts about building. They are pleasant and they produce the feeling of progress without the substance. Thirty days without them costs nothing.

No new ideas. You will have a better idea on day eleven. Everyone does. Write it in a file called "after" and close the file.

The shape of thirty days

Days 1 to 7: cut scope and build the skeleton. The first week is for getting the thing to exist end to end, badly. If it's a feature, it should be reachable, even if it does nothing useful yet. If it's a product, a stranger should be able to go from link to the main action, even if the action is faked. The scope you cut in week one is scope you won't have to cut in week four, when it hurts more.

Days 8 to 16: the ugly middle. This is where the real work is, and it is unglamorous: the edge cases, the auth bug, the payment webhook that fails silently, the copy that has to be written four times. Nothing here makes a good screenshot. Two blocks a day, every day. The temptation to "step back and rethink" peaks around day twelve. It is almost always avoidance.

Days 17 to 23: the pivot temptation. By now you know the thing's flaws intimately and a different project looks clean by comparison. It isn't; you just haven't lived with it yet. The instruction for this week is to finish what exists. If the sentence from day one no longer makes sense, you'll know on day thirty, with evidence. Not on day nineteen, with a feeling.

Days 24 to 30: ship and tell. Last week: freeze the scope, fix only what blocks a stranger, go live, and then tell people in the plainest language you can manage. Not a launch. A sentence: "this exists now, here it is." Then the season ends, on the day you wrote down.

A day that protects the thing

The founder's day has one rule that matters more than the rest: the first block happens before the inbox. Not after a quick check. Before. Email, Slack, analytics and social are all designed to hand you someone else's priorities, and once you've read them, the morning belongs to those priorities. Ninety minutes on the thing, then the world.

The second block goes in the afternoon, after the operational work that keeps the company alive. It's shorter and rougher, good for the mechanical half of the work.

Everything else, customer support, the one meeting you couldn't move, the admin, goes between. It doesn't go in the blocks. The blocks are the thing.

The founder's nightly review

The three questions apply, with one adjustment for founders. What did I move forward? What did I avoid? And: did I build today, or did I perform building?

That last one is uncomfortable, which is why it's useful. Performing building looks like updating the roadmap, polishing the deck, writing the thread about the feature before the feature works, re-reading the competitor's pricing page. It feels like work and it keeps the company exactly where it was. The review is where you catch it, and catching it once makes it harder to repeat.

The missing cofounder

Solo founders fail at monk mode for a specific reason: there is nobody to answer to. A cofounder, when the relationship works, is the person who asks on Friday whether the thing is live. Without one, the question never gets asked, and the thing stays almost ready for a very long time.

You can borrow the function. A friend who gets a two-line message each night. A small group of founders who report, briefly, without encouragement. Or something that asks the question every night, remembers what you said yesterday, and notices when "nearly done" has lasted a week. The form matters less than the fact that someone is waiting for the answer.

What thirty days buys

Not a company. A thing in a stranger's hands, and an honest answer to whether it was worth building. That answer is worth more than the next three months of founder activity, because it is the only one that tells you what the next season should be.

If you want the thirty days with a daily timetable and a master who asks every night whether you built or performed, La Orden is in free beta.