The most common framing for a fractional CTO engagement is a 90-day sprint: assess the technology, build a roadmap, install an operating rhythm, and hand off to the team. That framing isn’t wrong — there is real value in 90 days of focused, experienced technology leadership. But the engagements that produce the most durable impact are rarely the ones that end there.
The reason is simple: technology problems compound, and so do their solutions. The architectural decisions made in month three produce consequences in month eighteen. The team dynamics shaped in the first quarter are still producing results two years later. An engagement that ends before those downstream effects play out captures only a fraction of the available value.
journey title The Board's Confidence Through a Multi-Year Engagement section Orientation Technology audit complete: 3: Board Roadmap presented: 4: Board section Execution First modernization milestone: 4: Board Investment thesis visible: 5: Board section Compounding Architecture supporting faster delivery: 5: Board Technology as competitive asset: 5: Board
What the First 90 Days Actually Accomplish
The first 90 days of a fractional CTO engagement are diagnostic. The CTO is mapping the current state — the architecture, the technical debt, the team’s capabilities and dynamics, the vendor relationships, the infrastructure risks. That map is essential. It’s also not where the value lives.
The value lives in what gets built on top of that map. The roadmap produced in 90 days is a plan; it is not an outcome. The operating rhythm installed in 90 days is a starting point; it has not yet been tested under real delivery pressure. The team development that begins in the first 90 days is early; the engineers haven’t yet internalized the architectural principles the CTO is establishing.
A 90-day engagement produces a deliverable. An 18-month engagement produces a changed capability.
How Compounding Actually Works
My engagement with LERETA ran roughly five years. LERETA is the second-largest property-tax payment processor in the United States, processing approximately $18 billion annually. The work that came to be known internally as “the Livermore Report” — a wall-sized enterprise architecture diagram that laid out the full legacy-modernization critical path — took months to develop and became the foundation for a board-approved $20 million modernization investment.
That report couldn’t have been produced in 90 days. The institutional understanding of the system, the relationships with the development teams across multiple products, the credibility with the CTO and board that made the presentation land — all of that required time. It required being in enough meetings to understand the organizational dynamics, not just the technical architecture. It required being present when the system failed in ways that revealed structural problems the documentation didn’t show.
The Livermore Report was a document. The five years that produced it were what made it authoritative.
The Architectural Dividends
Long engagements produce architectural dividends that short ones cannot. A fractional CTO who is embedded long enough to see the consequences of the decisions made in year one is a fractional CTO who learns what to do differently in year two — and has the institutional standing to make those adjustments.
During the LERETA engagement, the organization acquired a Texas company that offered similar technology, with the intention of retrofitting that technology into one of the flagship products being rebuilt. The data structures differed in subtle but important ways. The processing logic was fundamentally different. The retrofitting attempt caused delay and required rework.
In retrospect, it would have been faster and less expensive to start from scratch with a fresh requirements process rather than adapt the acquired system. That conclusion was knowable at the outset — but only by someone who understood both the target product’s requirements and the acquired system’s architecture at a deep enough level to evaluate the compatibility. That level of understanding takes time to develop, and it only exists inside an extended engagement.
A 90-day CTO would not have had it. The engagement that ran five years did.
The Organizational Change That Short Engagements Don’t Reach
Technology leadership is also people leadership. The development teams that produce the best results are the ones where the engineers have been hired well, managed consistently, and developed over time. A fractional CTO who is embedded for 18 months has shaped the team in ways that persist after the engagement changes scope.
During the LERETA engagement, the organization acquired another company with its own development culture. Part of the embedded work was helping integrate that culture — bringing the acquired team’s engineers into a cohesive operating model alongside the existing teams. That cultural integration work doesn’t happen in 90 days. It happens over the course of shared delivery cycles, shared retrospectives, and the gradual development of mutual professional respect built on demonstrated results.
The companies that get the most out of fractional CTO engagements are the ones that resist the temptation to define a tight scope and a short timeline. They bring in someone who can assess the current state, then commit to the engagement long enough for the architectural decisions and team development to compound. The ones that end the engagement when the roadmap is done have a roadmap. The ones that continue through execution have a technology function that’s materially different than when they started.
