Skip to content

FAQ

Straight answers before you reach out.

Scope, boundaries, deliverables, pricing, and how to get started - no hidden claims, no manufactured urgency.

What is a fractional CIO here?

A part-time senior IT lead who helps leadership frame decisions, connect business goals to technical work, and keep ownership clear across roadmap, vendors, risk, and change. The exact scope is set by what you need.

Is this managed IT support?

No. We're primarily advisory and fractional leadership, not a help desk or ticket queue. Managed support can be coordinated as part of an agreed scope, but we don't offer 24/7 support or a response-time guarantee on this site.

Can we start with just one decision?

Yes. A single vendor, renewal, platform, governance, or project question can fit a focused decision brief before you consider any broader roadmap or retainer work.

What does a roadmap engagement produce?

Usually a current-state view, priority logic, project briefs, dependencies, ownership, and a review point. The exact deliverables are confirmed when we scope the work.

Do you implement the recommendations?

We follow through hands-on where that is part of the scope, but who implements what depends on the engagement. We might guide your internal team and vendors, do the work ourselves, or hand off cleanly to whoever picks it up next.

Are outcomes guaranteed?

No. Technology and organizational change involve factors outside any advisor’s control. The goal is better decision quality, clarity, and follow-through - not a guaranteed result.

How is pricing handled?

Pricing follows the shape of the decision: how many options, how much evidence, who needs to be involved, the deadline, and how deep the review needs to go - plus whether the work stays a single brief, grows into a roadmap, or becomes ongoing support. This is advisory work; there is no per-user managed-support price attached to it.

What should we send before a first call?

A short description of what changed, who is affected, the decision that is pending, and any real constraint. Do not send passwords, tokens, private keys, or other credentials.

Who should be involved on our side?

The smallest group that covers business consequence, day-to-day context, technical evidence, commercial context, and decision authority. A single decision might only need an executive owner and one or two others; roadmap and governance work usually pulls in project and operating owners too.

How often do we meet?

It depends on how many decisions are in flight and how fast things are changing. A focused brief might need a handful of working sessions; a roadmap uses checkpoints; ongoing support uses a regular check-in. We do not promise a fixed meeting count or response time.

When should an engagement end?

When the decision can hand off to a named owner, the record makes sense without us in the room, and leadership knows the next action and when to revisit it. Ongoing work should be reviewed against real, continuing need rather than assumed to continue indefinitely.

How is a fractional CIO different from an MSP?

A fractional CIO focuses on executive decisions - roadmap, vendors, investment, risk, and ownership. An MSP or internal support team typically focuses on day-to-day service and user or systems support. Many organizations need both, with a clear line between them.

How is this different from a project manager?

A project manager runs an already-approved project through planning, dependencies, communication, and delivery. Fractional IT leadership helps decide which project should move at all, what trade-offs leadership is accepting, and who owns the result afterward.

When does it make more sense to just hire someone full time?

When you need daily executive authority, ongoing people management, and a permanent mandate over a substantial IT function. Fractional work can help you figure out whether that is actually the case - it should not be used indefinitely as a substitute for a role that truly needs to be full time.

Still weighing whether to start at all? See honest answers to the common hesitations

Still not sure how to frame it?

Start from a typical decision example.

The decision library covers renewals, investment, risk, portfolio conflicts, ownership, leadership fit, roadmap deferral, and executive escalation. These are worked examples, not client stories.

Open the decision library

Not sure yet?

Try the diagnostic first.

The unscored diagnostic can tell you whether this is a technical task or a wider decision-and-ownership problem.