The Founder’s Brand

Why the consult is one session, not a week

The structure isn’t arbitrary, and it matters more than most founders expect.

6 min read · 2026-05 · by Kenny

The consult is one working session. Founders who book it sometimes ask whether it could be longer: a few days, a full week, something spread across a month. The shorter answer is no, and the longer answer is the subject of this essay.

I want to walk through the reasoning, because the structure isn’t arbitrary and the structure matters more than most founders expect.

This is one of the design decisions I get asked about most often, and one I’ve thought about most carefully. The honest answer is operational, partly cognitive, partly a reflection on what constraint produces in service-design. None of those reasons are obvious; all of them are load-bearing.

The operational reason

The operational reason is that discovery quality is constraint-shaped.

A short engagement forces prioritisation. We can’t map every task in one session, so we map the ones that matter most. The read that comes out of it is the sharpest version precisely because there wasn’t time to dilute it with second-tier observations. The sequence is the most actionable version precisely because we had to commit, and couldn’t defer.

A longer engagement loses this. Extra days create room for the work to drift sideways into territory that is interesting but not load-bearing. A week creates room to second-guess earlier conclusions, which is occasionally useful and mostly produces revision-without-improvement. The work that benefits most from constraint suffers most from extra time.

I have watched discovery engagements at adjacent firms run for two weeks and end with less actionable output than one focused session produces. The pattern is consistent enough that I treat it as a design parameter, not an accident.

The cognitive reason

The cognitive reason sits behind the operational one.

Founder attention degrades reliably under sustained focus on a single problem. Not because founders are inattentive: most founders running businesses at the 4-to-25-person stage have proven attention discipline. The degradation happens because the problem space changes shape as you stare at it. A few days into picking apart how your own company works, your mental model has already shifted. Questions that felt sharp at the start feel familiar. The patterns you spot late are partly real and partly artefacts of fatigue.1

This isn’t a moral failure. It is an operational reality. Sustained attention on a single complex problem reliably degrades quality. The cognitive research on attention-fragmentation goes back decades, and the application to professional services is straightforward.

One session is calibrated to the work a founder can do well. A week is calibrated to the hope that more time produces more value, which the research does not support.

One session versus a week

The difference in what comes out the other end is visible.

One session ends with a locked read: the founder can explain it to their team in sixty seconds. The sequence names what to do first and what to leave alone, and each item has a reason attached. The founder finishes with energy left for the work itself.

A week ends with a read that is still moving, because the constraint never forced anyone to commit. The plan covers more ground at lower specificity, because there was room to be ambitious without having to choose. The founder finishes having spent the attention the exercise was supposed to protect.

One session is calibrated to the work; a week would be calibrated to hope.

That is not theoretical. It is the difference between an exercise that produces something usable and one that produces an aspirational document. The consult’s job is the usable thing. The structure protects that.

Constraint as quality

The one-session calibration is part of a broader pattern in how these engagements are designed.

The engagement itself is scoped and fixed before it starts. Not “we’ll see how long it takes.” The price reflects the work rather than hours logged against it, which means the number moves before you commit instead of after. And it ends: your team is trained, the work is handed over, and there is no retainer waiting on the other side. The free line afterwards runs 90 days, which is roughly how long it takes a new way of working to meet enough real cases to prove it holds.

Each of these constraints is calibrated, not punitive. We’re not making the engagement difficult; we’re aligning the duration with what the work needs. Most agencies use longer engagement structures because longer structures bill more hours. Most agencies use ambiguous duration because ambiguity creates room for scope creep. We use specific, short, fixed durations because the work itself benefits from the constraint.

The pattern is service-design discipline. Founders who recognise it from inside their own businesses, the same way constraint sharpens product decisions, are usually the founders I work best with.

If one session doesn’t suit your situation, the free call is the right place to say so. We can walk through the reasoning together, and if the constraint is wrong for your business I will be honest about it and point you toward better-fit alternatives.

If it does suit your situation, and it suits most founders running 4-to-25 staff, the consult is where the work begins. One session, fixed price, refund if it isn’t useful. The structure matches the rest: calibrated, not punitive; specific, not arbitrary; sharp, not maximal.

Most of the founders I work with appreciate the structure once they’re inside it. The shape of the engagement matches the shape of the work the engagement does. That’s the discipline.

— Kenny

Notes + references

  1. The cognitive-attention research underlying this essay draws on several well-documented threads: Microsoft Research’s work on attention-fragmentation in knowledge work, Anders Ericsson’s research on deliberate-practice plateaus, and Cal Newport’s synthesis in Deep Work (2016). The 48-hour-degradation threshold for sustained single-problem attention is the rough empirical pattern that emerges across these sources; the precise hours vary by individual and context. Reference these for the underlying mechanisms; the application to professional-services design is RTSN’s.

Written by

Kenny

Founder, RTSN Studios · Singapore

RTSN Studios is a Singapore studio. We build AI into how founder-led teams actually work, and train their people to run it without us.

One session, calibrated to the work. The consult is where it begins.