The September 2026 issue of IT for Business on CIO priorities puts budget pressure and governance at the centre of IT decisions. For an SME without a CIO, the question is therefore not limited to choosing an ERP, CRM or implementation partner. Someone must represent the company’s interests throughout the project.
Four operating models are available: let the implementation vendor manage everything, appoint an external project manager, use a fractional CIO or recruit an internal IT leader. The main differences lie in decision-making authority, independence and continuity after go-live.
The decision facing the business owner
The company does not merely need someone to schedule meetings. It must assign four responsibilities:
- Arbitrate scope when departments request additional features or the vendor proposes a change.
- Control commitments covering deliverables, dependencies, data migration and acceptance conditions.
- Prepare decisions for management on budget, timing and business processes.
- Retain control of documents, credentials, configurations and knowledge required to change vendors.
France Num’s project management guidance for SMEs highlights coordination between internal departments and external providers. That coordination needs an identified owner; it cannot be delegated implicitly to project software or to the main supplier.
Our article on managing an IT project without a CIO explains why a task-management tool cannot replace governance. The operational question here is different: which management model matches the project and the company’s internal capabilities?
On Monday morning, ask the business sponsor to produce a mandate sheet stating the expected outcome, the decisions they may take, the matters reserved for senior management and the person authorised to approve acceptance. If no names can be assigned, the client side of the project does not yet have an owner.
The available options
The implementation vendor manages the project
The vendor configures and deploys the solution while managing workshops, schedules and actions. This provides a single operational contact and may work for a standard deployment if an internal manager can challenge proposals and approve or reject deviations.
The vendor is nevertheless responsible for its own delivery. Asking it to be the sole judge of its deliverables or additional charges creates a conflict between implementation and control, even when the vendor performs professionally.
An external project manager receives a defined mandate
An external project manager handles a bounded initiative such as a CRM deployment, cloud migration, ERP replacement or project recovery. They coordinate departments, monitor the supplier, maintain the decision log and prepare acceptance.
This model provides independent control without immediately creating a permanent IT management role. It is particularly suitable when the need starts and ends with an identifiable project.
A fractional CIO owns the broader roadmap
A fractional CIO does more than manage a schedule. The role connects the project with the existing architecture, contracts, other suppliers, technical debt and future investments.
The same person can support scoping, vendor selection, deployment and post-go-live governance. This model is appropriate when several IT decisions are interconnected or when the SME needs technology leadership without immediately creating a permanent position.
The company recruits an internal IT leader
Recruitment brings authority, knowledge and business relationships inside the organisation. It becomes relevant when IT decisions are continuous because the company has a significant application portfolio, multiple suppliers, frequent changes or an internal team to manage.
Recruitment does not eliminate the need for specialist support. An internal IT leader may still require dedicated assistance for an ERP tender, complex migration or independent acceptance process.
France Num also distinguishes upstream support—formalising requirements and selecting a solution—from integration work in its guidance on ERP projects.
The criteria that really matter
| Criterion | Vendor-led project | External project manager | Fractional CIO | Internal hire |
|---|---|---|---|---|
| Cost | Often bundled or spread across the proposal; change requests require scrutiny | Variable and tied to project scope | Recurring but adjustable to workload | Permanent fixed cost plus recruitment and management |
| Time to mobilise | Fast if the vendor has already been selected | Fast, subject to availability and domain knowledge | Can start with scoping and expand into oversight | Depends on recruitment and onboarding |
| Supplier dependency | High without internal challenge | Limited if independence is protected by the mandate | Limited through a multi-vendor perspective | Low, apart from dependency on one employee |
| Internal skills required | A sponsor able to arbitrate and control | Business representatives available to make decisions | Senior management available for strategic approval | Capacity to recruit, onboard and manage the role |
| Reversibility | Must be explicitly contracted | Good if records remain in company-controlled tools | Good if handover is included in the mandate | Good if knowledge is properly documented |
Visible cost should not be the only criterion. A lower initial proposal may shift expenditure towards change requests, unplanned employee workload or the later reconstruction of undocumented configurations.
When to choose each model
Choose vendor-led management when the project is standard, has few interfaces and already has an internal sponsor able to examine proposals, reject out-of-scope requests and organise acceptance. Require a contractual schedule, a named list of deliverables and a change-approval procedure.
Choose an external project manager for a bounded initiative with a delivery supplier that needs independent oversight. The first deliverable should be a governance note identifying decision-makers, useful meetings, risks, escalation rules and end-of-mission criteria.
Choose a fractional CIO when the project raises broader questions involving legacy applications, cloud contracts, data quality, technical debt or a sequence of related initiatives. The mandate should include an IT roadmap, management decisions to prepare and the transition from project delivery to operations.
Choose an internal hire when decision-making and coordination remain permanent after go-live. Before publishing the vacancy, define the role around the authority actually required: supplier governance, budget, architecture, team management or support. This avoids hiring a mainly technical profile for a leadership need.
For a business-critical ERP or CRM, a hybrid structure is often more robust: the vendor delivers while an independent project owner represents the company. The IT requirements document provides the baseline for comparison and control, followed by the test plan and formal functional acceptance.
The hidden risks of each option
With the vendor alone, the hidden cost is a gradual loss of the ability to challenge decisions. Demonstrations may replace acceptance evidence, additional requests may become contract changes and documentation may focus on the product rather than future operations.
With an external project manager, the risk is an excessively narrow mandate. If the person only maintains the schedule, no one owns architecture decisions, contracts or post-project operations. Require a decision log, handover file and inventory of credentials from the start.
With a fractional CIO, the trap is purchasing advice without delegating authority. The agreement must state which decisions the CIO prepares, which ones they may take and which records they maintain throughout the engagement.
With an internal hire, knowledge can become concentrated in one person. Use a company-owned documentation repository, company-controlled administrator accounts and a regular review of supplier dependencies.
The ANSSI guidance on information-system outsourcing recommends addressing transfer, operation and reversibility. In practice, contracts should cover the return of data, configurations, documentation and knowledge required for an internal takeover or a move to another supplier.
How D1 Consulting approaches the decision
Our IT Project Management and Fractional CIO service begins by identifying the role that is actually missing rather than imposing a predefined operating model.
Together with management, we produce:
- A mandate sheet defining the sponsor, business representatives, project manager’s authority and decisions reserved for executives.
- A project baseline covering scope, suppliers, applications, data, interfaces and dependencies.
- A decision memo comparing management scenarios, fixed or variable costs, dependency risks and continuity after go-live.
- A governance system including the schedule, decision log, risks, contractual monitoring and acceptance plan.
- A handover file bringing together credentials, contracts, configurations, decisions and remaining actions.
D1 Consulting can act as an independent project manager for a bounded initiative or as a fractional CIO for a longer IT roadmap. In both cases, the implementation vendor remains accountable for its solution, while company management retains final authority over business decisions.
👉 Book a free 30-minute diagnostic to identify the right management model and leave with a clear list of responsibilities to assign before consulting suppliers.
