The delivery maths no one runs until October

Why does the delivery maths only get run in October?

Because October is the first month where the gap becomes undeniable rather than theoretical.

Until then, a delivery plan is a set of intentions. Roadmap commitments made in June assume a team that will exist by September, and nobody checks that assumption in June because it still has time to come true. By October, the remaining working weeks can be counted on two hands, and the difference between the team you planned for and the team you have becomes a number.

That number is usually smaller than it should be, and the options have narrowed to the expensive ones: descope, delay, or throw people at a problem they have not had time to understand.

The maths itself is not difficult. It is not a hard calculation that companies get wrong. It is an easy calculation that nobody is scheduled to perform.

The clocks that never line up

Inside most organisations, three separate cycles govern whether an engineer is at a desk in November, and they run at different speeds without ever being reconciled.

The budget clock runs on the financial year. Approval to hire arrives at a moment chosen by the accounting calendar rather than by when the work needs doing.

The hiring clock runs on the market, and does not care when the budget was approved. Sourcing, screening and offer negotiation take the time they take, and for senior roles that is longer than the plan usually allows.

The delivery clock runs on the roadmap. It is the only one with a customer attached, and the one that gets blamed when the other two fail to align.

The failure is rarely that one clock is wrong. It is that no single person is asked to look at all three at once, early enough for the answer to still be actionable. The gap opens up in the space between them.

Why notice periods make the gap wider than the plan assumes

Here is the part most Q4 plans underestimate, and it is not a matter of opinion.

Even after the right person accepts the offer, they usually cannot start immediately. In Portugal, a permanent employee resigning from their current role must give 30 or 60 days' notice, depending on whether they have up to or more than two years of service, according to the Legal 500 country guide to Portuguese employment law. Comparable requirements exist across most European markets.

So the sequence is not "decide to hire, then hire." It is: approve the role, source, run the process, make an offer, wait out a notice period, then onboard.

An offer accepted on 1 October, with a 60 day notice period, produces an engineer who starts in December, still learning the codebase when the year ends. The hire was real. The Q4 contribution was not.

This is the arithmetic that does not get run. Not because anyone doubts it, but because the notice period sits in a different mental category from the hiring timeline, and gets treated as an administrative detail rather than as two months of the delivery calendar.

The countdown most teams never run

Here is the calculation itself, built from two components only: a recruitment process that closes in around three weeks for a well-scoped role, and the statutory notice the person owes their current employer. Ramp-up time sits on top of all of these and is not included, because it varies by codebase and role.

Two things tend to become obvious once this is on a page.

The first is that a December start needed a September conversation if the candidate is a senior person with tenure, which is the profile most Q4 gaps actually call for. The second is that the gap between the fastest and slowest column is roughly nine weeks, most of a quarter, and it turns almost entirely on one variable: whether the right person is available now or is currently employed somewhere else.

Note that the three-week process figure used here is KWAN's own, not an industry average. A search run from scratch will usually take longer, for reasons the next sections cover.

What "we'll hire in January" actually costs

By late October, the most common response to a capacity gap is to defer it. Hiring in January feels sensible: the budget resets, the market reopens, and the pressure to decide immediately disappears.

The problem is that deferring the decision does not defer the cost. It relocates it.

A January start, allowing for a hiring process and a notice period, tends to produce a productive engineer around the end of Q1 at the earliest. That is not a delayed Q4. It is a compromised Q1 as well, with the original work now competing against whatever Q1 was supposed to deliver.

There is a second cost, harder to see on a spreadsheet. Teams that spend a quarter under-resourced accumulate decisions made in a hurry, shortcuts taken to hit a date, and documentation that never got written. That debt surfaces later, usually as a slower quarter blamed on something else.

How to run the maths earlier

The fix is not complicated, which is both the good news and the frustrating part.

Count backwards from the delivery date, not forwards from the approval. The question is not "when can we start hiring" but "what is the last date someone could start and still contribute." Everything else derives from that.

Ask the capacity question in the roadmap meeting. Not in a separate cycle, and not to a separate audience. Most of the misalignment described above dissolves if both questions are asked together, once, in June.

Decide what capacity you need before deciding how it gets delivered. Adding engineers to an existing team is a different decision from building a team around a product objective, and both can be delivered nearshore, remotely or on-site. Our complete guide to IT outsourcing in Lisbon works through that distinction.

Assume ramp-up time is real. An engineer's first weeks are spent building context, not just writing code. Our account of a nearshore engineer's first 30 days covers what that period involves.

Where KWAN fits into this

KWAN offers two solutions, IT Staffing for extending an existing team and Dedicated Teams for building a stable group around a longer-term objective, delivered nearshore from Portugal, remotely, or in a hybrid or on-site setup. Which of the two fits is a separate question from how quickly it can happen, and worth deciding first.

Everything above describes a sequence that starts from zero: the role gets approved, the search begins, a candidate is found, they resign, they start. Most of that is not a law of nature. It is a consequence of beginning the sourcing work at the moment the need becomes urgent.

KWAN's model changes the order of operations, because sourcing, technical vetting and employment happen continuously and in advance. Profiles are vetted and matched against real technical and team contexts before any brief arrives, and a proportion of consultants are between engagements at any time, already employed and ready to integrate.

Two clarifications matter here.

The first is that these figures are KWAN's, not a market benchmark. A provider without a pre-vetted pipeline starts the same sequence a client would start alone, and takes correspondingly longer. It would be misleading to present the five-day and three-week numbers as what any partner can do.

The second is the notice period row, identical in both columns. No partner can shorten a statutory notice period, and any provider suggesting otherwise is worth questioning. What changes is everything either side of it: the sourcing and vetting weeks already spent, and the availability of consultants who owe no notice because they are already part of KWAN.

That is the single biggest lever in the calculation, and the reason a Q4 capacity gap is not automatically impossible to close. Sometimes it is, if the role is highly specialised and nobody suitable is available. Often it is not.

Speed is only half of it

Speed on its own solves nothing, because a placement that arrives in three weeks and leaves in month four does not close a Q4 gap. It reschedules it, and the countdown at the top of this article starts again from zero.

That is why continuity is the number worth asking any partner about. KWAN's talent continuity runs at around 70%, excluding internalisations, supported by a dedicated People Experience Partner for every engagement.

The published work with Critical TechWorks shows what that looks like sustained rather than as a one-off: 66 professionals integrated over two years, including 24 within a single six-month period. Volume at that pace is only possible when people stay long enough for the next round of hiring to build on the last one instead of replacing it.

Frequently asked questions

1. Why do engineering teams discover capacity gaps so late in the year?

Because until the final quarter, a resourcing plan is still a projection rather than a measurement. Budget approval, hiring and delivery run on separate cycles inside most companies, and nobody is formally responsible for reconciling all three early enough for the answer to change anything.

2. How long does it actually take to get a new engineer contributing?

Longer than the hiring process alone suggests. After sourcing, interviewing and an accepted offer, a permanent employee in Portugal owes 30 or 60 days' notice depending on how long they have been with the employer they are leaving. Onboarding and ramp-up come after that, before meaningful roadmap contribution begins. The notice period is the part most plans leave out, and on a senior hire it can account for two of the three months available in a quarter.

3. Is it better to wait until January if the gap appears in October?

Waiting is often the most expensive option rather than the safest. On a typical sequence, a January start produces a productive engineer near the end of Q1, which means the Q4 shortfall carries into Q1 rather than being resolved.

4. Can a staffing partner remove the notice period problem?

Not entirely. Statutory notice periods apply regardless of the partner. What changes is that sourcing and vetting have already happened, and already-vetted consultants who are ready to integrate can start much sooner than a candidate resigning from another role.

5. How quickly can KWAN actually present candidates?

First profiles typically within five days, with the full process closing in around three weeks for a well-scoped role. Highly specialised or senior profiles take longer. This reflects how KWAN's process is built rather than a market-wide standard.

6. Does hiring faster mean compromising on quality?

It does if the speed comes from skipping steps. It does not if the vetting and sourcing happened before the brief arrived, which is the difference between a partner with an existing pipeline and a recruitment process starting from scratch.

If your Q4 plan depends on people who are not yet hired, the useful thing to do is count backwards from the delivery date and see where it lands. Send us the role and the deadline, and we will map the realistic sequence with you.