BOT timeline estimator

Make schedule pressure visible before it becomes a promise.

Use a disclosed planning model to test how scope, scale, complexity, controls and client readiness can change the route to transfer.

Working scenario

Describe the operating burden.

Change the inputs to see which part of the path carries the schedule pressure.

Indicative planning window

A schedule to pressure-test, not promise.

Sequential path to transfer-ready17 to 25 monthsPhases may overlap in a real mandate. This simplified model adds them sequentially.
01

Mandate

1 to 3 months

Scope, ownership case, governance and transfer conditions.

02

Build

5 to 7 months

Entity path, founding leadership, first hiring waves and operating controls.

03

Operate

8 to 11 months

Delivery stabilisation, knowledge capture and progressive client governance.

04

Transfer

3 to 4 months

Readiness evidence, acceptance, employment and operating handover.

See how this scenario changed the base model
  • 2 functions add 0 months to each build boundary beyond the first two functions.
  • A target team of 40 adds 0 months to each build boundary.
  • Complexity adds 1 month to build and operate boundaries.
  • The control profile adds 0 months to the upper build boundary and both transfer boundaries.
  • Client readiness adds 1 month to operate and transfer boundaries.

What this estimator does not know

The output is not a delivery commitment, market benchmark or substitute for a mandate plan. It does not know the hiring market for your roles, legal structure, approval path, technology dependencies, vendor contracts or the client team’s actual capacity to accept ownership.

The base model uses sequential planning windows. A real engagement may overlap entity work, leadership hiring, team waves and governance preparation. GrowGCC should replace the working ranges with an evidence-based plan during mandate design.