Chief Risk Officer — Enterprise-Software Suite

The mandate

A deliberate change of pace is required to deal with a reset of enterprise risk ownership and board assurance within a multinational-owned enterprise technology and digital-products group. The immediate arena is the enterprise-software suite during a shift from licences to subscriptions. For mandate 120, the successful executive inherits decisions that have been deferred, competing stakeholder expectations and a need to establish facts before committing further capital.

The Chief Risk Officer operating perimeter covers approximately ₹2,000 crore in annual recurring revenue portfolio, with activity spanning several enterprise-software suite customer, product and delivery clusters rather than a single asset. The Chief Risk Officer Technology remit carries direct influence over roughly 375 colleagues and third-party capacity.

The chair, executive committee and principal capital sponsors want a Chief Risk Officer who can convert ambiguity into a short list of explicit choices for the enterprise-software suite. The Chief Risk Officer Technology seat must resolve a shift from licences to subscriptions, while preserving the underlying strengths of the enterprise-software suite. For mandate 120, value will come through sharper allocation, stronger leaders and an operating cadence that exposes variance early.

The Chief Risk Officer’s first year on the enterprise-software suite is expected to end with early-warning quality, control effectiveness and regulator-ready evidence. In mandate 120, authority covers resources and leadership appointments; material trade-offs go directly to the board sponsor.

Why this seat is open

This is a planned replacement for the Chief Risk Officer — Enterprise-Software Suite seat. The incumbent continues to lead the enterprise-software suite through an agreed succession period and will support a structured handover. The board has allowed 4–6 months to assess candidates, complete diligence and protect continuity while a shift from licences to subscriptions is addressed. The search is confidential so the transition can be communicated to employees, customers and partners in a controlled sequence.

What you will own

• Set the Chief Risk Officer value-creation thesis for the enterprise-software suite, translate it into no more than five enterprise priorities and stop work that does not support them.
• Carry stewardship of approximately ₹2,000 crore in annual recurring revenue portfolio, including allocation, risk acceptance and board forecasts.
• Lead the Chief Risk Officer Technology organisation of about 375 employees and partners, appointing a team with clear decision rights and credible succession for every critical seat.
• Resolve the enterprise-software suite economics and execution constraints created by a shift from licences to subscriptions, with Chief Risk Officer-approved owners, dated milestones and transparent escalation thresholds.
• Establish one Chief Risk Officer operating review across commercial, customer, financial, people, technology and risk outcomes for the enterprise-software suite; remove reconciliations that obscure accountability.
• Have held independent challenge authority and closed material issues with evidence accepted by board or supervisory review in mandate 120.
• Build the Chief Risk Officer’s three-year succession and capability plan for the enterprise-software suite, reducing dependence on individual executives and improving mobility across the wider Technology organisation.

The first 12 months

• Days 1–90: Validate the enterprise-software suite baseline, meet the 30 stakeholders most consequential to a reset of enterprise risk ownership and board assurance, assess the leadership team, stabilise immediate delivery risks and agree a board-owned scorecard with explicit decision gates.
• Months 4–9: Make the principal Chief Risk Officer portfolio and organisation choices for the enterprise-software suite, install the new operating cadence, fill critical leadership gaps and deliver the first measurable release of cash, capacity or customer value.
• Months 10–12: Demonstrate a repeatable enterprise-software suite trend against early-warning quality, control effectiveness and regulator-ready evidence, lock the following year’s capital and talent plan, evidence control sustainability and present a credible three-year value case with downside actions.

What the board will measure

• Delivery of the Chief Risk Officer’s agreed first-year enterprise-software suite value case within a 10% tolerance, with variance explained before rather than after the relevant quarter closes.
• A Chief Risk Officer forecast that remains decision-useful across three consecutive quarters and reconciles the enterprise-software suite’s operating, cash, customer and people assumptions.
• Closure of the Chief Risk Officer mandate’s highest-priority enterprise-software suite risk and execution issues by their board-approved dates, with independent evidence that fixes are sustained.
• Retention of at least 90% of critical enterprise-software suite talent and ready-now successors for at least 70% of the Chief Risk Officer’s direct reports.
• A quantified Chief Risk Officer-owned improvement in the enterprise-software suite operating constraint behind a shift from licences to subscriptions, supported by a clean baseline and named data owner.
• Clear stakeholder confidence in mandate 120: no unresolved high-severity escalation older than 30 days and no material surprise withheld from its agreed governance forum.

The person

You are currently a CRO, Deputy CRO or Chief Compliance and Risk Officer in a multinational-owned Technology or adjacent enterprise. In relation to the enterprise-software suite, your Chief Risk Officer track record includes a transition where the original plan was no longer sufficient; you can explain your choices, evidence and numerical impact. Candidates from software, cloud services, digital platforms, IT services or technology-enabled business services will be considered where the operating model, customer stakes and governance intensity match this Chief Risk Officer brief.

As a Chief Risk Officer candidate, you bring 22–28 years of progressive Technology or adjacent-sector experience, consistent with the 22-28 experience band. At minimum, you have carried a P&L, book, budget or accountable portfolio of ₹1,150 crore and led an organisation of at least 275 people.

For mandate 120, the board wants two transitions: a difficult enterprise-software suite portfolio choice and a leadership-system change during a shift from licences to subscriptions. As the prospective Chief Risk Officer for this enterprise-software suite, you must challenge optimistic cases and still create followership. References for mandate 120 must distinguish your contribution from the institution around you.

The Chief Risk Officer role in Technology is based in Chennai; relocation is expected, although a structured weekly commute may be considered during the first quarter.

Non-negotiables

• Current or recent accountability at the level of CRO, Deputy CRO or Chief Compliance and Risk Officer, with direct exposure to a board, investment committee or equivalent Technology governance forum.
• Proven Chief Risk Officer ownership of at least ₹1,150 crore and leadership of no fewer than 275 employees in a comparable enterprise-software suite context.
• One completed Technology or adjacent-sector example of a reset of enterprise risk ownership and board assurance with outcomes sustained for at least two reporting periods after the initial intervention.
• Sector credibility from software, cloud services, digital platforms, IT services or technology-enabled business services; experience that is purely functional and lacks Chief Risk Officer-level enterprise-software suite consequences will not meet the bar.
• Willingness to meet the Chennai location expectation, complete conflicts and background diligence, and protect the confidentiality of mandate 120.

Compensation and terms

The anticipated Chief Risk Officer package is ₹2.2–3.0 crore fixed + performance variable, calibrated to the final enterprise-software suite scope and the candidate’s current mix. Any long-term participation for mandate 120 follows standard vesting and performance conditions. The Chief Risk Officer appointment in Chennai, centred on the enterprise-software suite, offers regular exposure to the chair, executive committee and principal capital sponsors. A notice period of up to 6 months can be accommodated for the selected executive in mandate 120.

Confidentiality

To protect the board, incumbent team and candidate, the organisation remains unnamed until a confidential conversation confirms mutual relevance for mandate 120. The operating facts have been rounded and blended expressly to remove identifying signals for mandate 120.