One hour a week: what pace costs, and what it does not

A prospect tells me their calendar is full. They can give me an hour a week, maybe two. They want to know whether that kills the engagement.

It does not. It moves the launch date, and I would rather they hear the number now than in week five.

The arithmetic is short

The capture is three hours of recorded interviews. At one hour a week, capture takes three weeks.

A client who clears those three hours inside a single week launches in about two weeks. A client who gives one hour a week launches in six or more. The same work, the same scope, the same price.

The same three hours, spread out, cost a month of calendar.

Nothing gets built until the capture is finished

Everything I produce derives from the recordings. The guides come from them, and the website, the content, and the email sequence come from the guides.

So the build cannot start early. Beginning the site after one interview would mean writing around the parts I have not heard yet. And the depth of the capture sets the ceiling on the quality.

There is no partial version to work on in the meantime. The project waits, and the waiting is the whole delay.

The gaps cost more than the hours inside them

Three sessions across three weeks means 18 days when nothing is being recorded. That is where the extra calendar hides.

Some of it is scheduling friction. A week that gets missed costs a week, because the next opening is seven days out. Two rescheduled sessions in a row can add a month by themselves.

The rest is restart cost. People who run client projects for a living describe the same pattern. A project that sits idle gets harder to restart. Momentum has to be protected deliberately.

What the slow pace does not cost you

It does not cost you quality. I want to be exact about that, because the opposite claim would be convenient for me.

Researchers who interview the same person several times find that gaps between sessions can help. Time between conversations builds trust, adds nuance, and gives people room to reflect before the next round. My own sessions behave that way. A client who has been thinking all week often opens with a story. In a same-week session I would have had to dig for it.

It does not cost you money either. The price is the price at any pace. It does not rise for a rush or fall for patience.

One hour a week buys the same brand. It buys it a month later.

Six weeks is still a short calendar

Set that six weeks next to the market. One studio publishes its ranges: 8 to 10 weeks for brand identity, 12 to 16 with a website. Those ranges assume a client who answers quickly and one decision maker.

The reason the comparison holds is that the working time here is short. A website goes up in about twelve working hours once the decisions have been made. Those decisions get made during capture.

Your calendar is the slowest part of this build. It is also the part you control.

Why I say this before you sign

A provider who hides the participation requirement gets a signature and then a slow, quiet stall. The client feels behind on someone else's project. That is a worse experience than a plain number stated in a first conversation.

So the number goes in the proposal and in the conversation. One hour a week works, and it means launching in six weeks instead of two.

If the calendar is the obstacle, the format flexes before the depth does. Clients who cannot sit for live sessions record guided monologues alone. They work through the same question list, whenever the hour appears. The hours stay the same. The scheduling stops being a negotiation with two calendars.

Your launch date depends on your calendar, not mine. Pick the pace you can hold and tell me what it is. I will tell you what it means before you commit to anything.