
Executive AI Advisory
Private advisory on governance, decision architecture and human + AI organizational design for established organizations.
A private advisory relationship for leaders who are introducing AI into an organization whose decision structure is already carrying strain.
What we actually work on
01
Where decision authority lives
02
What the organization knows, and where
03
What AI should and should not be permitted to decide
04
Human + AI organizational design

How the work runs
Engagements are scoped individually. Most begin with a period of establishing what is actually true about the current decision structure, because most organizations have never had cause to write it down.
I take a small number of advisory relationships at a time. There is no packaged program, and the commercial structure follows the engagement rather than the reverse.
Questions
What is private advisory?
Private advisory is the most direct way to work with Melissa McCrery. Unlike traditional coaching or consulting, the focus is not tactical guidance or productivity strategies. Instead, advisory examines identity structure, decision patterns, and leadership posture so a woman can operate with greater clarity and internal authority. The work focuses on structural recalibration rather than incremental improvement.
How is advisory different from coaching or consulting?
Coaching typically focuses on goal-setting, accountability, and performance improvement. Consulting often focuses on strategy or problem-solving within a specific domain. Private advisory operates at a different level. It examines the internal architecture governing decisions, leadership, and identity so the underlying structure guiding a person’s life becomes coherent.
Who is accepted into private advisory?
Private advisory is selective and typically reserved for women operating at significant responsibility or influence who want structural recalibration rather than tactical guidance. Because the work is intensive and trust-based, acceptance happens through an application process to ensure alignment.
How do I know whether my company needs a Fractional Chief AI Officer?
One question decides it: has the organization become complex enough to require intelligence that currently sits in one or two people?
In practice that shows up as several distinct functions with handoffs between them, the same decisions escalating to the same person, and the reasoning behind those decisions never having been written down. That is usually evidence the business was built well. It is also what caps it.
The answer should be a number, a name or a document — six functions reporting to one person, three handoffs on the last engagement, a pricing exception that lives in an email thread. Not a sense that things are busy.
Where that condition holds and AI is being introduced into it, the gap is an executive one: someone has to decide what AI is permitted to do, who owns the outcome, and how the organization will know it worked. Fractional is the right shape when those decisions have become consequential but do not yet justify a full-time executive.
Where it does not hold — where AI is one workflow, one team, or one defined build — this is the wrong call, and I will say so.
What does a fractional Chief AI Officer actually do?
Executive AI leadership without a full-time hire.
The work is deciding where AI belongs and where it does not, where it can create meaningful organizational capacity, what it is permitted to decide, who owns the result, and how the organization will know whether any of it worked. It sits at the level of authority and accountability, not tooling.
Fractional makes sense when AI has become strategically consequential but the organization cannot yet justify a full-time executive for it.
How is this different from an AI consultant, a CTO or a CIO?
A consultant is engaged to deliver a defined project. A CTO owns technology and engineering. A CIO owns enterprise systems.
This work sits across all three and answers a different question: how decisions, knowledge and accountability should be arranged now that part of the intelligence in the organization is not human.
I am not replacing anyone. The people already here hold the customer knowledge, the institutional memory and the judgment. The work is the architecture that lets them and the AI operate together without either one quietly taking authority nobody granted.
What happens to my team?
The question underneath this is usually whether AI is a reason to have fewer people. Here it is not.
Experienced people hold what a model cannot manufacture — customer context, relationships, institutional memory, the reasons behind decisions that were never written down. The more useful move is to build around them, so that expertise becomes reachable by the rest of the organization instead of resident in one person.
The failure mode worth designing against is not headcount. It is reversion: authority gets delegated, pressure arrives, and it comes straight back.
Do I need an AI strategy if my team is already using ChatGPT and other AI tools?
Using AI is not the same as having an AI strategy.
If different people are choosing their own tools, solving isolated problems and developing their own practices, the organization may be getting useful local results without building organizational capability.
The question is not whether people are using AI. It is whether what they are learning becomes available to the organization, whether the tools connect to a larger operating model, whether authority and risk are explicit, and whether anyone can show what the investment is producing.
Experimentation is useful. The problem is when experimentation becomes the architecture by default.
How does an engagement start?
With an application, then a conversation.
Most engagements begin by establishing what is actually true about the current decision structure, because most organizations have never had cause to write it down. One condition matters more than the rest: someone other than the founder has to be able to carry the work forward. Where that person does not exist yet, building that capacity becomes the first piece of work rather than a reason to decline.
What this is not
It is not technical AI implementation, model selection, or engineering. It is not coaching. If what you need is a build partner, I am the wrong call — and I will say so.