There is a particular silence in IT consultancies that nobody discusses openly at leadership meetings. It arrives in the gap between project completion and project commencement — those days or weeks when senior consultants are technically available but operationally adrift. This interstitial period, often euphemistically labelled 'bench time' or 'internal development,' represents one of the most significant and least examined drains on consultancy profitability. Having advised IT service firms across London, Frankfurt, and Boston on their operational efficiency, I can state with confidence that the between-project period is where the difference between a thriving consultancy and a struggling one becomes starkly apparent.

IT consultancies that treat between-project periods as structured capacity-building intervals — rather than accepting them as unavoidable dead time — consistently achieve 15-20% higher annual utilisation rates. The solution lies in pre-planned transition protocols, systematic knowledge capture, and deliberate business development allocation during these windows.

The True Cost of Unmanaged Transition Periods

The average IT consultancy operates at 60-65% utilisation when the target should sit between 75-85%, according to SPI Research data. That gap — often 15-20 percentage points — does not emerge primarily from poor project execution or insufficient client demand. It accumulates in the transitions. Each between-project period that lacks structure adds another fraction of lost capacity to the annual total, compounding until the firm finds itself consistently below its revenue potential.

Consider what actually happens during an unmanaged transition. A senior consultant finishes a twelve-week systems integration project on Friday. Monday arrives with no clear directive beyond 'update your CV on the bench list' and perhaps some vague encouragement to pursue certifications. By Wednesday, that consultant has settled into a pattern of half-productive administrative tasks, extended lunch breaks, and the creeping professional anxiety that accompanies feeling surplus to requirements. Project management overhead alone consumes 15-20% of agency working time according to Forecast.app research — and that figure inflates considerably when projects begin and end without systematic handover protocols.

The financial arithmetic is unforgiving. A senior IT consultant billing at £1,200 per day who spends ten unstructured days between projects represents £12,000 in lost revenue per transition. Multiply that across a team of fifteen consultants averaging four project transitions per year, and you are examining potential revenue leakage approaching £720,000 annually. This is not theoretical. These are the figures that emerge when we conduct time audits with mid-sized IT consultancies, and they routinely shock the leadership teams who commissioned them.

Why Information Retrieval Becomes the Hidden Bottleneck

When IT consultants transition between projects, they confront a particular operational friction that rarely appears in management dashboards: the time spent searching for information. Project documentation scattered across SharePoint sites, Confluence spaces, local drives, and email threads creates a retrieval burden that intensifies during transitions. A consultant ramping onto a new engagement may spend three to five days simply locating relevant methodologies, previous proposal templates, architectural reference documents, and client communication histories.

Research from McKinsey's workplace productivity studies indicates that knowledge workers spend approximately 19% of their working week searching for and gathering information. In the context of IT consultancy transitions, this figure frequently escalates. The consultant needs not merely to find information but to find the right version, confirm its current relevance, and establish whether colleagues have developed improved approaches since it was last filed. Agencies that implement time tracking accurately see 15-20% revenue uplift from previously leaked hours — and a substantial proportion of those leaked hours occur during precisely this retrieval-heavy transition phase.

The compounding effect is what makes this particularly damaging. Each poorly managed transition creates more information entropy. Consultants who cannot find existing materials recreate them, producing duplicate or contradictory documentation that makes the next person's search even more difficult. Without deliberate intervention, IT consultancies develop an ever-expanding labyrinth of semi-organised knowledge that actively works against operational efficiency. The firms with documented SOPs are 3x more likely to achieve successful exit valuations — and the reason is precisely that they have solved this retrieval problem systematically rather than leaving it to individual initiative.

Structuring the Between-Project Period as a Strategic Asset

The most effective IT consultancies I advise have fundamentally reframed the between-project period. Rather than treating it as an operational inconvenience to be minimised, they structure it as a deliberate phase within the project lifecycle — one with its own deliverables, timelines, and accountability measures. This shift in perspective transforms what was previously a cost centre into a genuine competitive advantage.

The framework operates on a simple principle: every between-project day is pre-allocated before the current project ends. Typically, this allocation follows a 40-30-20-10 distribution. Forty percent goes to structured knowledge capture and documentation from the completed project. Thirty percent is directed toward pre-engagement preparation for the next confirmed or probable project. Twenty percent feeds deliberate business development activities — not speculative networking, but targeted proposal development and relationship nurturing. The remaining ten percent covers genuine professional development aligned with the firm's strategic direction. Agencies that batch client communication into set windows save 8-10 hours per week, and this same batching principle applies powerfully to between-project administration.

Implementation requires commitment from leadership. The founder trap — where 78% of agency revenue depends on the owner's direct involvement according to BenchPress UK research — often prevents this kind of systematic approach because the founder is too consumed with delivery to design operational infrastructure. Breaking this pattern demands that someone with authority creates the transition protocol, assigns accountability for its execution, and measures compliance with the same rigour applied to billable project milestones.

The Knowledge Capture Imperative

Every IT project generates institutional knowledge that exists, initially, only in the minds of the delivery team. Technical decisions, client preferences, integration challenges overcome, architectural patterns that proved effective — all of this represents future competitive advantage, but only if it is captured before the team disperses to new engagements. The between-project period is the natural window for this capture, yet most consultancies treat it as optional rather than mandatory.

Staff turnover in agencies averages 30% annually, with replacement costs of £15,000-30,000 per role. Each departing consultant takes with them not merely their technical skills but the accumulated contextual knowledge from every project they touched. When between-project knowledge capture is treated as a deliverable rather than a suggestion, the firm builds resilience against this turnover. New hires can access structured project retrospectives, decision logs, and methodology refinements rather than starting from zero or relying on the institutional memory of whoever happens to still be employed.

The most effective knowledge capture I have observed operates on a 'future colleague' principle. Consultants are asked to document their project learnings as though writing for a competent professional who will face a similar challenge in six months but has no access to the original team. This framing produces dramatically more useful documentation than generic 'lessons learned' templates, because it forces specificity, context, and practical application rather than abstract observations.

Business Development Windows and Revenue Pipeline Protection

Sixty-eight percent of agencies cite 'too much client work, not enough business development' as their top challenge. The between-project period represents a natural solution to this tension, yet most consultancies waste it precisely because they have not pre-structured how business development should operate during transitions. The result is a feast-and-famine revenue cycle that creates cash flow anxiety and forces acceptance of suboptimal projects simply to maintain income.

The average UK digital agency has a net profit margin of 11-15% according to The Wow Company's benchmarking data. Margins at this level leave minimal buffer for revenue gaps between projects. Client churn costs agencies 5x more than client retention, per Bain research, which means that between-project business development should prioritise existing client expansion over new client acquisition. A consultant transitioning between projects is ideally positioned to conduct relationship maintenance with previous clients, identify expansion opportunities within current accounts, and develop proposals that leverage institutional knowledge while it remains fresh.

Retainer-based agencies have 40% more predictable revenue than project-based ones. For IT consultancies, this suggests that between-project periods should include deliberate effort to convert project relationships into ongoing advisory or support arrangements. A consultant who has just delivered a successful systems integration is uniquely credible when proposing a quarterly architecture review retainer to that same client. The between-project window is when this conversion conversation must happen — wait until the next project consumes all available attention and the opportunity evaporates.

Building Systematic Transition Protocols

The Agency Growth Flywheel — attract, deliver, systematise, scale — depends fundamentally on the 'systematise' phase, and nowhere is systematic thinking more urgently needed than in project transitions. Building an effective transition protocol requires acknowledging that between-project behaviour will default to entropy unless actively structured. People do not naturally organise their time optimally during periods of low external accountability, and expecting them to do so is a management failure rather than a personnel one.

An effective transition protocol specifies daily structures for the first five days post-project. Day one focuses exclusively on project close-out: final documentation, time sheet reconciliation, client feedback solicitation, and formal handover of any ongoing responsibilities. Days two and three address knowledge capture and methodology refinement. Day four turns to business development and relationship maintenance. Day five provides pre-engagement preparation for the next project, including technology research, team introductions, and scope familiarisation. This structure can flex according to circumstances, but its existence ensures that no transition day begins without clear purpose.

Agencies with productised services grow 40% faster than those offering only custom work. The between-project period is where productisation thinking should occur — where consultants examine their recent delivery and ask which elements could be standardised, templated, or packaged for repeatable deployment. This converts experiential knowledge into scalable assets, directly addressing the utilisation challenge while simultaneously building long-term firm value. The consultancy that treats transitions as strategic infrastructure-building periods will, over time, dramatically outperform the one that merely waits for the next project to begin.