Odoo Project Plan v1: committee strategy 1

The CFO has created informal structural insulation around her consultant. In corporate governance, this is designed to create a powerful voting bloc: the CFO provides the financial mandate, the former CEO provides historical and operational gravity, and the consultant provides the execution. If you challenge the consultant directly, you risk looking like a technical gatekeeper fighting against institutional wisdom.

However, a former CEO is a double-edged sword. CEOs do not care about Python code, server stacks, or Odoo version differences; they care deeply about risk mitigation, continuity, operational disruption, and protecting the charity’s reputation.

You can use this new committee to your absolute advantage. Here is how you pivot your strategy to enroll the former CEO as your ally and establish bulletproof IT governance.

1. The Strategy: Speak the CEO's Language

To win the former CEO’s support, you must translate technical risks (like code ownership and unmapped APIs) into existential business risks (like operational downtime, donor loss, and regulatory audits).

When you present your Technical Sign-Off Framework, do not pitch it to the CFO as "IT protocol." Frame it to the entire committee as an "Institutional Continuity Plan."

What You See (Technical Risk)	How to Pitch It to the Former CEO (Operational/Reputational Risk)
No GitHub code escrow or ownership.	"Vendor Lock-In & Business Interruption:" “If the consultant’s firm goes under or raises their rates by 300%, HCI won't own the code for our donation pages. The former CEO knows that losing control of our primary fundraising mechanism for even 48 hours during an emergency appeal is catastrophic.”
No independent testing of CRA/IRS receipt logic.	"CRA Audit & Legal Liability:" “If the custom receipt engine fails an audit, the Board of Directors faces personal liability and HCI risks losing its charitable status. We need automated, transparent technical verification.”
Aggressive 10-week timeline with full data migration.	"Donor Churn & Frontline Burnout:" “Migrating 182k records in 10 weeks while switching from Blackbaud to Odoo is a massive shock to donor care. If a donor’s recurring Child Sponsorship fails because of a bad migration, they leave. We need strict UAT gates.”

2. Update Your Steering Committee Structure

With the former CEO on board, your Project Governance Charter must be formalized immediately so you aren't sidelined. Propose the following clear, balanced breakdown of roles to the committee:

                      +------------------------------------+
                      |     Odoo Steering Committee        |
                      |  (CFO, Former CEO, IT Manager)     |
                      +------------------------------------+
                                         |
         +-------------------------------+-------------------------------+
         |                               |                               |
         v                               v                               v
+------------------------+      +------------------------+      +------------------------+
|    Financial Scope     |      | Operational Alignment  |      | Technical & Security   |
|       Authority        |      |       Authority        |      |       Authority        |
+------------------------+      +------------------------+      +------------------------+
|       • New CFO        |      |    • Former CEO        |      |    • IT Manager        |
|  Validates budget,     |      |  Ensures logic aligns  |      |  Validates security,   |
|  ROI, and final        |      |  with donor care and   |      |  data architecture,    |
|  vendor contract.      |      |  historical workflows. |      |  and code ownership.   |
+------------------------+      +------------------------+      +------------------------+

3. The "Neutral Leader" Test Questions

At the next committee meeting, look at the consultant’s proposal and ask these three specific, highly strategic questions. Direct them to the entire committee, positioning yourself as the guardian of HCI’s data continuity. This will show the former CEO that you are focused on protecting the organization, not playing politics.

On System Redundancy:
"Given that our website and donation pages handle millions in critical funding, what is the consultant’s SLA (Service Level Agreement) and fallback protocol if the newly configured Odoo database goes offline during a live global emergency appeal?"
On Vendor-Independent Continuity:
"As an organization, how do we ensure that if this specific consultant is unavailable six months from now, my internal IT team or another Odoo certified partner can immediately maintain the custom Technicost and Canadian tax modules without rebuilding them from scratch?" (This forces the requirement for documentation and GitHub ownership).
On Operational Reality:
"With 50 users moving off Blackbaud and QuickBooks simultaneously, 2 half-day training sessions represent a high risk of operational paralysis. Can we expand this phase to ensure our marketing and fundraising teams can actually execute campaigns on day one without relying on the consultant for daily data entry?"

The Outcome

By shifting the conversation to compliance, business continuity, and risk, you do two things:

You show the new CFO that you cannot be bypassed on technical reality.
You show the former CEO that you are a highly strategic, institutional leader who values the charity's safety over everything else.

The former CEO will almost certainly side with your requirement for strict technical gates, because no experienced executive wants to sign off on a project where the organization doesn't own its source code or control its data infrastructure.