IFS bought Copperleaf. What it means if you're an SAP shop.

~5 min read · For SAP-aligned councils, utilities and agencies evaluating AIP

For years the simple answer to "which asset investment planning tool integrates with SAP?" was Copperleaf — the category leader and, notably, the only SAP-certified AIP. Then IFS acquired Copperleaf. The product didn't change overnight, but the ownership question did, and for SAP-aligned organisations that question matters more than a feature comparison.

The uncomfortable position

IFS competes with SAP in enterprise asset management. So the certified AIP that plugs into your SAP digital core is now built and owned by an SAP competitor. If you're a council or utility that has standardised on SAP, you're being asked to run a strategic capability — the brain of your capital planning — on a rival's product, integrated into your SAP estate.

It's not that the software stopped working. It's that "buy your capital-planning brain from a competitor of your core platform vendor" is a sentence that makes CIOs uneasy — and should.

Why this is a real strategic moment, not just gossip

In Hamilton Helmer's language, this is counter-positioning: an incumbent holds a position a challenger can occupy precisely because the incumbent can't easily follow without harming itself. IFS will not rebuild Copperleaf as a clean-core SAP-native product against its own commercial interest. Copperleaf's heavy, services-led, 6–18-month delivery model won't collapse into a 30-day clean-core motion without cannibalising its own revenue. The gap that opens is structural, and it's open for a while — call it a 12–24 month window.

The questions worth asking in any AIP evaluation

• Who owns it, and do they compete with my core platform? Strategic capability shouldn't depend on a rival's roadmap.
• Is it clean-core? Or does it modify my digital core in ways I'll pay to maintain forever?
• How long to value? A year-long rollout is a year of backlog you didn't address.
• Does it ship the AU regulator content, or do I build IPART/IP&R/AASB S2 logic myself anyway?
• Can my own team tune the model, or am I dependent on the vendor's consultants to re-run it?

Where AIPP sits

AIPP is deliberately the opposite of the incumbent on the axes that now matter to SAP shops: SAP-EAM-native and clean-core (it runs on your BTP, no core modifications), IFS-independent, 30-day-to-portfolio off live data, with AU regulator content shipped, not configured, and a self-service value framework your engineers tune themselves.

We won't claim feature parity with a decade-old enterprise platform — that's not the game. We win on SAP alignment, speed, independence and pre-loaded Australian content. For a council or utility that has bet on SAP, that combination is the point.

This is commentary, not legal or procurement advice, and reflects our reading of a public market development. Evaluate all vendors against your own requirements. AIPP is an early-stage product; we lead with a pay-on-acceptance pilot precisely so you can judge the claims on your own data.