What an ongoing engagement looks like
Most companies bring me in to own the technology agenda over time, not to run a single project. I step in as your fractional CIO or CTO and carry the responsibility a full-time executive would, on a defined commitment of a few days a week.
The first few weeks are about getting oriented: understanding the systems, the team, the vendors, the security posture, and what the business actually needs from technology. From there the work settles into a steady rhythm. I attend the leadership meeting and the board technology discussion, hold a standing check with whoever owns delivery, and stay reachable for the decisions that cannot wait.
Over months, the picture changes. The roadmap moves from a document to work that ships. The engineering team gets clearer on priorities and stronger in execution. Systems that were fragile get stabilized, and security and compliance move from a standing worry to something handled. What you have is a senior technology leader accountable for outcomes, without the cost or the commitment of a full-time hire.
A fractional engagement is not meant to run forever. It runs for the period the business needs senior technology leadership in the seat, and part of the job is building toward what comes next. When the foundation is in place, I help you decide whether you need a permanent hire and what kind. If you do, I help define the role and hand off cleanly.
Ways to engage
The ongoing seat is the heart of the work. The other two are there for companies that need something narrower, and they often lead to the first.
Ongoing fractional leadership
I take the CIO or CTO seat on a defined commitment of a few days a week and own the technology agenda for the period the business needs it. Scope is set at the start and revisited as the work evolves, and the engagement is built to wind down once the foundation is in place. This is how most engagements run.
Fixed-scope project
A focused piece of work with a defined deliverable, like an assessment, a roadmap, or a SOC 2 readiness review. Scope, timeline, and fee are agreed before work begins. Often how a longer relationship starts.
Advisory
A senior technology perspective on a specific decision or situation, by the hour or day, without committing to a larger engagement.
One way in: a focused assessment
A common way the relationship starts is a focused, time-boxed assessment. You get a clear, written picture of where technology stands before deciding on anything ongoing. What follows is drawn from a real engagement, with the organization details generalized.
The organization was a regional health plan that had recently acquired a smaller competitor. It had two separate IT organizations, overlapping systems, unresolved vendor contracts, and a technology roadmap that had been paused during the deal. Leadership needed a clear picture of what they had, what was at risk, and what to prioritize before committing to an integration plan. No single person had visibility across both environments, and the board was asking questions the existing team could not yet answer.
What an assessment can include
Every engagement is scoped to the situation, so the actual deliverables, timeline, and fee are agreed before any work begins. What follows is the kind of work an assessment can include, drawn from real engagements with the details generalized. Not every assessment produces all of it; the mix depends on what the business needs.
Technology landscape document
A written inventory of every system in use: what it does, how it connects to other systems, where the known gaps and pain points are, and what the organization does and does not control.
Compliance and security review
A structured review of the organization's posture across HIPAA, applicable privacy regulations, and disaster recovery and business continuity. Delivered as a gap inventory with a prioritized action list.
IT team and organizational review
Structured conversations with each member of the IT team to understand workload, capacity, strengths, and gaps. The review surfaces role clarity issues and structural adjustments that can make the existing team more effective without adding headcount.
Executive priorities map
Individual conversations with each executive to understand what they need most from technology in their own words. The process surfaces alignment and misalignment that has been implicit but never documented, giving the leadership team a shared language for technology conversations.
18-month technology roadmap
A practical roadmap organized into near-term actions the existing team can begin immediately, medium-term initiatives addressing the most important gaps, and longer-term investments requiring additional planning. Designed to be realistic and executable from day one.
How an assessment can unfold
One example of how an assessment can run over twelve weeks. The pace and sequence flex with scope.
| Timeframe | Focus | Output |
|---|---|---|
| Weeks 1, 3 | Introductory conversations with executive team and IT staff. Review of current systems, documentation, and known issues. | Preliminary landscape notes shared with the CEO |
| Weeks 4, 6 | Deeper dives into system configuration, compliance posture, vendor relationships, and team capacity. | Executive priorities map drafted for feedback |
| Weeks 7, 9 | Synthesis of findings. Draft deliverables prepared and reviewed informally with the CEO before finalization. | Draft roadmap shared with the CEO for review |
| Weeks 10, 12 | Final deliverables completed. Presentation to the leadership team. | Final deliverables delivered and presented |
Experience behind the approach
Both the ongoing seat and the focused project draw on the same 30 years in technology leadership. A few engagements behind the approach.
M&A technology integration
Led technology due diligence and post-close integration for a multi-entity healthcare acquisition.
- The combined entity had two separate IT organizations, overlapping systems, unresolved vendor contracts, and no shared view of the technology environment across both entities.
- Scoped the combined environment, identified redundancies and gaps, and assessed vendor concentration risk across both organizations.
- Produced the integration roadmap the merged organization used to rationalize systems and consolidate vendors over 18 months.
SOC 2 Type II readiness
Guided three separate organizations through SOC 2 Type II readiness programs, each starting from an informal security posture.
- Each organization was starting with no prior audit experience and an unclear picture of where their gaps were relative to the Trust Services Criteria.
- Ran a gap assessment against the applicable criteria, produced a prioritized remediation plan, and managed the readiness process through to audit for each organization.
- Each engagement resulted in successful SOC 2 Type II attestation within the agreed timeline.
Technology assessment for a growing nonprofit
Conducted a full technology ecosystem assessment for a regional behavioral health organization with 300-plus staff following a major EHR transition.
- Leadership had no consolidated view of the technology environment after the EHR transition and needed a reliable baseline before setting priorities.
- Conducted structured interviews with executive and IT staff, reviewed systems and vendor relationships, and assessed compliance posture across HIPAA and related requirements.
- Delivered a landscape document, compliance gap review, executive priorities map, and 18-month roadmap within 90 days. Leadership described it as the first time they had a single, accurate picture of their technology environment.
What organizations walk away with
Clarity
A complete, written picture of the technology environment shared across the full leadership team
Prioritization
A ranked list of technology investments with clear rationale, ending the debate about where to focus first
Compliance confidence
A documented gap inventory and action plan giving leadership an honest picture of their risk posture
Team alignment
Surfaced misalignment between what executives needed from technology and what the IT team understood those needs to be
Does this sound like your organization?
Every engagement starts with a conversation to make sure the scope is right. No pitch, just an honest discussion about whether there is a useful fit.