You do not get a blank month.

The advice I was given most often was to start with one thing and do it well. I did the opposite, and I would do it again.

Since I announced I was leaving, one question has come back more than any other. So what are you actually doing — consulting, or advisory? Neither, quite. Working out why took four months, and I was building the thing the whole time.

That last part is what I want to write about, because it is the part that gets left out. Every account of starting something has a chapter where the founder sits down and designs the business. I have read dozens of them. I have never met anyone who got that chapter.

You do not get a blank month. You get clients arriving before the process exists, a website going up while the positioning is still moving, and a decision about engineering that has to be made long before you know how much work there will be. The model, the operating system, the stack and the growth are all built at once, by the same person, in the same week.

That is not a failure of planning. It is the actual condition — and it is exactly the condition every growing business is in, which is why so many of them end up with seven good tools and no answers.

One decision did come before all of it. This was never going to be a consultancy only. Twenty years taught me to name a problem precisely, and naming it was never what I wanted to do. I wanted to be accountable for fixing it. Everything below is downstream of that.

I

Month one — what a blank page actually costs.

What is this actually going to be?

Three arms: Advisory, Products, Fluency. Four markets rather than one. What each arm sells and to whom. The pricing logic — not the prices, the logic. And the boundaries of the IP, drawn early, because they are almost impossible to draw later.

None of it was built. All of it was written down.

I want to be honest about how unglamorous that month was, because the temptation to skip it is enormous. There is nothing to show anyone. No product, no client, no revenue. Just a document that changes every second day.

But on paper, a business costs nothing to change. Everything after that has a price — in code, in commitments, in what you have already told people. Sense is the cheapest month you will ever have and the most consequential. It is also the one every founder I know wishes they had spent longer in.

II

Month two — advice, not feedback.

Does any of it hold outside my own head?

I took the model to a dozen people. Advisers, former colleagues, people who had sat in the seats I was describing. Not a survey — real conversations with people whose judgement I trust and who had no reason to be polite.

The three arms held. The four markets held.

The language did not. Three drafts of the positioning died in those rooms, and the version that survived came out of a conversation rather than a document.

Here is the thing I would tell any founder, and it took me most of that month to learn it.

Feedback gets you encouragement. And encouragement kept coming — warmly, constantly, from people who genuinely wanted this to work. Almost none of it was information. It felt wonderful and it moved nothing.

Advice is different, because advice requires the other person to imagine themselves buying it. To put their own money or their own reputation next to the thing, and then tell you what stops them.

The question that finally worked was not what do you think of this. It was: what would stop you from buying this? The first time I asked it properly, the answer cost me a draft. That was the most useful conversation of the month.

III

Month three — the decision before the tool.

What has to exist for me to be accountable, not just right?

Month one's conviction had a cost, and this was the month to pay it. Advice you cannot deliver is only a recommendation. So there would be engineers — not a vendor list, a team. One team, two countries, and no handoff between the people who design and the people who build.

Then the less visible work. Who holds judgement, brand and the client. Who holds architecture and build. How work actually moves — enquiry, conversation, proposal, delivery, invoice — written down before any software was involved.

I nearly bought software in month one. Buying things feels like progress, and it produces something you can look at on a Tuesday.

A tool cannot fix a decision nobody has made. Deciding who decides was the harder work, and it had to come first. It is also the single most common thing I watched large organisations get backwards for twenty years, usually at a cost of about two years each time.

IV

Month four — going live is a stage.

What has to be running before anyone arrives?

The site. The rooms open for applications. The operating layer carrying real work rather than a spreadsheet and a good memory.

This was the first month where things built earlier started paying for themselves rather than costing time. That compounding is real, and it arrives later than you want it to.

Going live is a stage, not a deadline. It deserves its own design. Most people treat it as the moment the work stops. It is the moment a different kind of work starts.

V

The thing I could not buy.

Somewhere in month three I did what every growing business does. I went looking for tools.

I found them, and they were good. A proper CRM. Something for invoicing. Something for the project work. Something for content. Each one solved the problem it was built for, and solved it well.

Then I asked a question that crossed two of them.

How much of this month's revenue came from conversations that started in the rooms? Which client costs more to deliver than it earns? Where is capacity actually going?

Every one of those needed three tabs, an export, and a spreadsheet I built by hand and never opened again.

The tools were answering me point to point. Nothing was joining them up to serve the business.

That is not a tooling problem. It is an operating system problem — and it is precisely the gap I spent twenty years watching large organisations paper over with headcount. They can afford to. A business of one cannot.

So the team and I built one. Not because we set out to make a product. Because I needed the thing to exist in order to run the business, and we happened to be the people who could build it.

VI

It was never about the hours.

I could tell you how many admin hours came back. That is the number every product in this category leads with, and it is the least interesting thing about any of it.

What it gave me was awareness. One place that tells me what is happening, what is due, and what is coming next month. I open it in the morning and I know where the business is — without assembling it from four places and my own memory.

And awareness is what buys the decisions. Before, I made calls on instinct. Not because instinct was better, but because getting the information cost more than the decision was worth. Now the call gets made on something.

I have said for years that time is the only thing you cannot get more of. Running this on my own made that literal in a way it never was inside a large organisation. Every hour on admin was an hour losing money or losing time with my family. Usually both.

And the worst of it was never the hours. It was carrying a hundred small unfinished things around at nine o'clock at night. None of them important. All of them mine.

VII

What did not work.

Three, honestly.

I mistook encouragement for validation. Everyone I spoke to in month two was supportive. It took several conversations to work out that supportive is not the same as would buy, and to start asking the question that actually hurt.

I over-configured before I had volume. Two modules set up for a business three times the size, then simplified back. Configure for the next six months, not the next three years. The version of you that needs the complexity will build it better than the version of you guessing at it now.

I wrote the process after the first client, not before. It should have been before. I now do that work in the first week of every engagement, because I know exactly what it costs not to.

VIII

The four questions.

If you take one thing from this, take these. One per month, in order. They are the whole method and they cost nothing.

1. What is this actually going to be?
2. Does any of it hold outside my own head?
3. What has to exist for me to be accountable, not just right?
4. What has to be running before anyone arrives?

If you cannot answer one and two, do not spend money on three.

That is the mistake I nearly made, and it is the one I see most often — in businesses of one and in businesses of ten thousand. The size changes. The mistake does not.