The window you give the client.

Every consulting engagement creates a window of visibility from the client into the operator's work. The size of the window is a choice the operator makes — often unconsciously, often by following the path of least resistance. That choice determines almost everything about how the relationship feels and how long it lasts.

Most operators give the smallest window they can get away with. The cheapest window to ship is a status email. The most expensive window — though only at first — is a real client portal. The math of the trade-off is rarely calculated, and is asymmetric in a direction that surprises most consultants when they finally do the calculation.

The default window: a status email

The default window in consulting is a weekly status email. It lists what got done, what's next, any blockers. The format is curated — what the operator wants the client to see, written in the operator's voice, sent on the operator's schedule, summarizing data the client cannot independently verify.

Friction to the operator: 30 to 60 minutes once a week. Cost to set up: zero. Path of least resistance: yes.

What the client gets: a snapshot of someone else's interpretation of the work, delivered on a delay, presented in the most favorable light the operator can plausibly offer. What the client cannot get: the actual hours logged this morning, the actual current state of the in-flight task, the actual cost-to-date, the conversation thread where a real decision was just made.

The portal window: a real surface

The portal window is a live URL the client can open at any time. Hours logged today are visible. Active conversations are visible. Invoice line items are visible. Milestones are tracked in real time. The client doesn't ask what's the status — they look.

Friction to the operator: a few weeks of engineering work upfront, then near-zero ongoing. The portal eliminates the status email. It eliminates the weekly check-in call. It eliminates the did you get my email about X follow-up. After the first month of the engagement, the operator's communication overhead drops below what the status-email model required.

What the client gets: a real-time view of what they are paying for, queryable on their schedule rather than on the operator's. What the client cannot get: an excuse to be in the dark about anything that matters.

The cost nobody calculates

The cost of the smaller window is paid by the client, not the operator. This is why the calculation rarely gets made: the person who pays is not the person who chooses.

The smaller window costs the client three things, all of them invisible until they aren't.

Anxiety between updates. The client has hired the operator and now lives between status emails wondering what's happening to their codebase, their AI feature, their fraud model. They cannot ask without feeling like they are micromanaging. They cannot verify without feeling like they are distrustful. The anxiety is real and it builds.

Slower problem detection. A real issue happens on a Tuesday. The status email is sent on Friday. By Friday, the issue has either resolved itself or compounded. In the first case, the client learns about a problem they could not have helped with anyway. In the second case, the client learns four days later than they could have, and acts four days later than they could have.

Curated communication. The status email is, by structure, an interpretation. The operator decides what to highlight, what to soften, what to omit. None of this is malicious. All of it filters the signal. The client decides on stale, partial information, and discovers later that the picture they had was incomplete in ways they could not have known.

The operator pays for the smaller window too, on a longer time horizon. Clients who hire under the smaller-window model churn faster, refer less, push back harder on invoices, and require more sales effort to win in the first place because they have learned, from previous engagements, that the smaller window does not protect them.

The cost of opacity is anxiety, slow problem detection, and worse decisions made on stale data. The operator does not pay this cost directly. They pay it indirectly, through every client they couldn't keep.

Why the larger window always wins

Run the trade-off both directions and the answer comes out the same.

For the client, the larger window costs nothing they would not happily pay. They get certainty, faster issue detection, and the ability to make decisions on real data. They get a relationship that does not require them to manage their own anxiety about whether the operator is doing what they were hired to do.

For the operator, the larger window costs an upfront investment in engineering and an ongoing commitment to keeping the data live. In return, they get clients who churn less, refer more, accept invoices without friction, and arrive at the kickoff with the trust pre-built. The infrastructure pays for itself within the first year of the first engagement, and pays compounding dividends across every subsequent client.

The math is asymmetric. The window pays for itself. Operators who don't build it usually haven't run the math.

What to look for if you're buying

Four diagnostic questions for any consulting practice you're considering:

1. Can the practice show you the portal before you sign? A real portal exists; a sales mockup does not. If they cannot demo a live workspace from another client (anonymized) or your own pre-provisioned account, the portal is theoretical.
2. Is the data in the portal live, or is it batch-updated? Live means the hours logged this morning are already visible. Batch means yesterday's hours show up tomorrow. The first is infrastructure. The second is automated reporting dressed up.
3. Does the portal include hours, costs, milestones, and the actual conversation history? Or does it include only one of those? Partial portals are common — they show invoices but not hours, or hours but not the threaded conversations. The complete window matters because problems usually cross categories.
4. Can you export everything if the relationship ends? A portal that locks you in is not a window — it is a cage. The right answer is: yes, here's the export endpoint, here's the data format, take everything.

If a practice answers yes to all four, you are evaluating a continuity-model practice with the infrastructure to back it up. (See capacity versus continuity for why this is not the same category as most consulting practices.)

If they answer no to most of them, you are evaluating a practice that ships status emails. That can be fine — for short, transactional, well-scoped engagements. It is genuinely insufficient for any engagement where you need to understand what's happening to your money, your systems, or your customers in real time.

The closing argument

The window is not a feature. It is the architecture of the trust the relationship requires. Every consulting practice that has lost a client they wanted to keep can usually trace the loss back to a moment where the window was too small for what the client needed to see.

The cost of the larger window is real. The cost of the smaller one is much, much higher than most operators realize, because the people paying it are not the people choosing it.

Build the window. Make it bigger than your competitors. Then watch your retention curve.

— Mikkel, Bangkok