Lessons in namaz for your startup

There is a structure I follow that is older than any framework I have ever read in a business book. It is the namaz. The five prayers a Muslim is asked to perform every day, at five different times of the day, for as long as they are alive and able.

I want to write down what running a startup looks like through the lens of this structure, because the structure has shaped my operating model more than any reading I have done.

The first lesson is the cadence itself.

If you can pray in jamaat, in congregation, with other people, that is the best version. If you cannot, pray at home standing. If you cannot stand, pray sitting. If you cannot sit, pray lying down. If you cannot lie down, pray with signals. If you cannot signal, pray in your heart. But you must pray, if you are alive and conscious.

The structure has a remarkable property. It assumes you will not always be at full capacity. It does not say “stop praying when life gets hard.” It says “lower the form to whatever capacity you have, but do not stop.” It is engineered to survive every state a human being can be in, including the states you have not encountered yet.

I have run my company through this lens since the year I learned to pray seriously.

If you can build with a team, build with a team. If you cannot, build alone. If you cannot build full-time, build on weekends. If you cannot build on weekends, build for one hour after the children are asleep. If you cannot build for an hour, build for fifteen minutes. But do not stop. Move toward the thing you are trying to build, at whatever capacity you have, every day.

The first version of DevBatch in 2011 was built in fifteen-minute increments. Some weeks the only thing I did was send three follow-up emails. Some months the company existed only because I was unwilling to stop. The lesson from namaz applied: lower the form, do not stop the function.

The second lesson is the time discipline.

The five prayers are not at convenient times. Fajr is before sunrise. Zuhr is around midday. Asr is in the late afternoon. Maghrib is at sunset. Isha is at night. None of those windows aligns with how a CEO would design their day. They cut across calendars. They interrupt meetings. They show up on the wrong side of the time zone when you are traveling.

The discipline is the interruption.

A startup founder’s calendar is the most aggressive thing in their life. It tries to consume every available hour. The five-prayer day is the only thing I have found that pushes back against the calendar with the same authority. It says: this hour is not yours. The work will wait. The world has already organized itself around these moments for fourteen hundred years. You can fit your meeting somewhere else.

I do not advocate for namaz to people who do not already believe in it. That is a different writer’s beat. I am writing instead about what an externally imposed, non-negotiable interruption five times a day does to the way you run a company. It makes you a better operator. It enforces patience. It enforces transitions. It enforces the realization that the work is not the only thing happening today.

The third lesson is amp-up.

After all the regular prayers comes Friday prayers. After all the regular months comes Ramadan. After all the regular years comes Hajj. The structure builds in periodic intensification on top of the daily cadence.

Apply the same shape to the company. After regular essays comes a signature piece. After regular quarters comes an annual planning intensive. After regular years comes a strategic reset. The cadence is the floor; the amp-up is what produces the compounding.

The fourth and last lesson is the most important.

You can find any of the four buckets above in any other operating tradition. Stoics talk about cadence. Athletes talk about discipline. Founders talk about intensification. None of those traditions tell you why. The namaz does. The structure exists because it is keeping you in conversation with something larger than your company. The work is not the point. The work is what you do while the conversation is going on.

If you are running a startup, build the floor. Hold the cadence. Schedule the amp-up. And remember what the structure is for.