You took the seat. The documentation did not come with it.
Most CIO seats turn over with no current-state architecture document, no defensible roadmap, and no peer-level translator between IT and the rest of the leadership team. The new CIO inherits the consequences of vendor and architectural decisions made before they arrived, and is expected to answer AI and cyber questions the prior CIO never had to. The fix is producing the foundational baseline document fast, in writing, before the second board meeting.
Where you sit today
Three truths from inside the seat.
Three patterns recur across portfolio CIOs we work with. They are independent of company size or sector. Most apply within the first 90 days of a new seat.
The architecture lives in someone else's head
The current-state map exists in the head of the longest-tenured IT person. It gets redrawn from memory whenever a buyer, a board, or an auditor asks. Nothing about that map reconciles with what is actually running.
The board is asking questions the prior CIO did not have to answer
SEC Item 106 made cybersecurity oversight a documented board responsibility in 2023. NIST CSF 2.0 added Govern as a top-level function in 2024. Boards now want AI exposure quantified, not described. The seat carries those questions whether or not the prior CIO built the answer set.
You are carrying decisions you did not make
The vendor portfolio, the contract calendar, the architectural commitments. Each one was reasonable in its moment and is now your accountability. The cost of unwinding the wrong ones grows the longer you operate without the documented baseline that would let you choose.
What changes with Preside
Three artifacts, not three projects.
A documented current-state architecture
Four-domain map (business, data, applications, technology) drawn against what is actually running, not what the diagram says. The document a new CIO, a board chair, or a buyer's diligence team can read in 20 minutes.
A prioritized roadmap your CFO and board can read
The next twelve to eighteen months of technology decisions, sequenced, costed, and tied to the business outcomes they support. No engineering language without translation. One reference document that survives your tenure.
A peer to think strategically with
The Technology Operating Partner relationship is the durable form. Not a vendor selling implementation. A senior operator on your side of the table when the hard decisions land on your desk. You stay accountable; the conversation stops being lonely.
A sample of the artifact
What the current-state baseline actually contains
Illustrative excerpt from a Three-week Architecture Review Initiative output. Format is the four-domain enterprise architecture view (TOGAF v9.2 reference) calibrated to mid-market scale. Specifics anonymized; representative of the document a portfolio CIO receives at handoff.
Current-state architecture summary
Portfolio company, $140M revenue services firm
Six business capabilities mapped, three currently dependent on technology decisions outside the IT function. The Customer Success capability runs on a CRM that finance does not have visibility into.
Flag: Customer Success and Finance are operating on misaligned data models. Pricing decisions are being made on different revenue figures.
Four data stores hold customer records. Two are authoritative; two are operational copies that have drifted. Data lineage exists for one of the four. AI use cases the leadership team has discussed cannot ship today because the underlying data quality bar is not met.
Flag: AI roadmap requires twelve to fourteen weeks of data foundation work before any production deployment.
One hundred and forty-eight SaaS applications in use across the organization. Leadership can name forty-three. Twenty-seven have not been opened in ninety days. Three are in active renewal within the next six months.
Flag: SaaS rationalization opportunity at the conservative end of BetterCloud's mid-market range (~106 apps; this firm sits above) and Zylo's 2025 SaaS Management Index range for the 501-2,500 employee band.
Identity is in Microsoft Entra ID; conditional access policies cover ninety-two percent of access paths. Eight percent run on legacy mechanisms with no documented review schedule. Cyber insurance renewal in nine months will require evidence the legacy paths are remediated.
Flag: Identity gap is the highest-impact remediation by insurance-renewal date math.
Format: TOGAF v9.2 four-domain reference (The Open Group). Benchmarks: BetterCloud State of SaaSOps, Zylo 2025 SaaS Management Index. Each flag carries an effort and dollar estimate in the full output, redacted here.
Your recommended initiative
Three-week Architecture Review Initiative
The deliverable
A current-state enterprise architecture document covering all four TOGAF domains. A target-state direction with a sequenced transition architecture. A list of named, costed decisions queued for the next two quarters. One reference document a board meeting, an incoming CIO, or an investment review can consume in 20 minutes.
See the initiative methodology →What we typically find
CIOs who get the most from this engagement do not use it to redo the work the IT team is already doing. They use it to produce the foundation document the seat needed when it came open. The team's work does not change. What becomes documentable does. That is what makes the next conversation with the CFO, the board, or the operating partner end with a decision instead of a delay.
What CIOs ask first
The four questions that come up before the engagement.
In writing, because every CIO we've worked with raises some version of these in the first conversation. Better to address them here than to leave them as a reason to defer.
I'm new in seat. Why bring in an outside firm before I get my bearings?
The bearings need a current-state document, and producing one takes three weeks in parallel with the relationship-building you're already doing. The document is yours to use however you want, with whichever team you decide to keep or change. It is faster to walk into the second board meeting with a defensible baseline than to produce one from inherited materials over the next six months.
How is this different from a fractional CIO?
A fractional CIO is the seat itself, done part-time. The Three-week Architecture Review Initiative is the work that gives any CIO (a new full-time hire, a fractional, or you continuing in seat) the documented foundation to operate from. The Technology Operating Partner relationship is the durable form if the fractional model is what fits longer-term. Different decisions; the Initiative answers either path.
What happens to my IT team during the engagement?
Their day-to-day does not change. The Initiative draws on them for interviews, access to systems where permitted, and existing documentation. Most engagements ask for two to four hours of senior IT time per week across the three weeks. The output is yours, not theirs. The team continues running operations.
What if I'm eighteen months in and already have the baseline?
Then the Architecture Review is not the right starting point. The conversation is about which gap you're feeling now: a cost-rationalization read, an AI-readiness assessment before a planned deployment, a security posture refresh for cyber insurance renewal, or a documented exit-prep posture twelve to twenty-four months out from a transaction. The Initiative catalog covers each. The Find Your Path tool helps you decide.
If you are a portfolio CIO
Four pressures specific to the PE-backed seat.
CIOs operating at companies inside a PE portfolio carry operating constraints generalist enterprise content does not address. Each of these shapes the work and the timeline.
- Board reporting cycle. The board does not move; your reporting cadence does. Quarterly board reads are the audience. Annual planning happens against the fund cycle, not your fiscal year.
- Exit window math. Decisions made twelve to twenty-four months before exit show up at the bid. Tech-debt unaddressed in that window is priced into the offer or used to walk. The cost of inaction compounds.
- Add-on integration tempo. Add-on acquisitions arrive faster than the IT integration plan. The seat carries the consequences of integrations that were technically feasible at signing and operationally fragile at month nine.
- Cost discipline that varies by hold position. A portfolio company at the start of a hold has different cost flex than one twelve months from exit. The operating partner's quarterly question is "what changed", and it has to be answerable in dollars.
Start with the documented baseline. Decide from there.
Three weeks. A current-state document and a sequenced roadmap. If it does not change how every subsequent decision gets framed, you are under no further commitment.