Building Protocol while running a consulting practice: what actually happens to your evenings

The question I get asked, in different forms, is this: how do you build a product at night while running a consulting practice?

The honest answer is that the question assumes a cleaner separation than exists.

There is no separate founder life waiting politely after work. Protocol gets built in the edges: nights, weekends, late windows after the house is quiet, and the occasional nap-time pocket where the task has to be small enough to land before the window closes.

Saturdays are sacred. Family, no screens, no pretending that another hour in the product is always the responsible choice.

That matters because the reason for building this way is not to escape family, but to be near them.

That means the rhythm has constraints. Working out is not optional; reading, no screens, and actually touching grass are not nice-to-haves. They are part of the operating system. Without them, the work gets worse and the person doing the work gets worse with it.

This is a deliberate structure, not martyrdom.

The real tradeoff is not hours

The energy difference between building my own thing and employed work comes down to weight, not hours.

Client and employed work carry inherited gravity: legacy systems, old workflows, organisational friction, half-visible politics, and decisions made before you entered the room. You spend a lot of energy understanding the shape of the system before you can move it.

Protocol does not have that weight.

The infrastructure is clean, the decisions are mine, and AI can be used fully and freely without waiting for permission, interpreting someone else’s process, or negotiating with a legacy stack that was not designed for the work I am asking it to do.

The strange part is that a solo builder with clean infrastructure and AI can move faster than a larger team trapped inside inherited overhead.

Not always, not on every problem, and not without cost.

Still, the difference is real.

The discipline is honesty

Building alone sounds like freedom until you realise there is nobody in the room to stop you from lying to yourself.

A good session is simple: you sit down and work.

A wasted session is also simple: you sit down and do not.

The hard part is admitting the difference. You can make a wasted session look productive very easily: open the repo, move between files, rewrite a note, check a dashboard, think about scope, and tell yourself you are orienting.

Sometimes you are, and sometimes you are avoiding the next hard decision.

The solo stand-up matters for that reason. I have to check in with myself the way a team would check in with each other, with basic questions that are harder to answer honestly than they look: what am I doing, is this still the task, did the scope drift, am I making progress, or am I constructing the feeling of progress?

Staying honest is harder without someone else in the room.

That may be the most underrated discipline in solo building.

What the evenings actually feel like

The theory is three or four clean hours after everything else is done; the reality is messier.

Some nights the session is sharp. The task is small, the context is loaded, the next move is obvious, and the product advances. Other nights I sit down with the correct intention and the wrong energy: the work is there, I am technically there, and nothing useful happens.

I have had to accept that pace is an energy problem before it is a scheduling problem.

That does not mean waiting until conditions are perfect. They rarely are. The point is being honest about what kind of work the current state can support.

Some nights are for implementation, some nights are for a small decision, and some nights the best move is to stop before I turn tired thinking into architecture I will have to undo later.

The path I chose

The parallel build is not efficient in the clean, spreadsheet sense.

It is also the path available to me.

I do not have the luxury of dropping everything and going all-in. Consulting keeps the ground under the work. Family gives the work its reason. Protocol has to fit inside that shape, not pretend the shape does not exist.

So the system has to be built around reality: nights and weekends, sacred Saturdays, small windows, workouts, decompression, and enough self-honesty to know when I am building and when I am just sitting near the work.

The only thing I would say to someone in the same position is the thing I am mostly saying to myself:

Learn to breathe before the world makes you.

I am bad at following it, but that does not make it less true.