Operators from industry. Held accountable for the strategy and the number.
Ecosystem Alchemy works with leadership teams whose growth depends on companies they don’t control. Growth through an ecosystem starts inside. Your own functions first, partners second.
You get a clear view of what growth depends on before you commit.
Independence changes the conversation.
A problem that sits between functions is hard to solve from inside one of them.
Your leaders know the business. They also have a number, a team and a story to protect. The same facts land differently depending on who says them.
We have no function to defend and no package to sell. We test the evidence across the business, find what growth depends on and set out what leadership has to decide. More work follows only if the evidence calls for it.
The aim is one view the leadership team can test, own and act on together.
THE TEAM
Three Principals.
All three have had a seat at the leadership table and been accountable for results. Whoever leads your work stays in it and draws on them all.
Rhody Hill
Founder and Principal
Thirty years running go-to-market inside technology companies, start-up to incumbent. Sold software, data and AI to business buyers, with a number the whole way.
Business Objects · VMware · SAP · IBM · Google Cloud · HashiCorp
LinkedIn
Tara Ridley
Principal
A revenue systems architect. Thirty years running enterprise sales, services and partner teams. Has led the sales teams that business growth depends on.
HP · Macquarie Telecom · Cisco · Salesforce
LinkedIn
Renee De Laine
Principal
Thirty-five years in sales and alliances. Nineteen years selling at IBM, then ran IBM’s largest alliance, with SAP. Most recently unlocked stalled accounts with bank C-suites in London.
IBM · KPMG · Dell · Movius
LinkedIn
THE FOUNDER
Pattern recognition is earned in the room.
Rhody Hill
Founder and Principal
Thirty years building, scaling and rebuilding Ecosystem Aligned go-to-market across ANZ and APAC, from category creation and hypergrowth to transformation and acquisition.
I have always looked at the whole commercial system before coming down into the ecosystem function. Carrying the ecosystem number makes silos impossible to ignore.
That is where Ecosystem Alchemy’s judgement comes from: knowing when a motion needs improving and when the design itself is holding it back.
Tested across every stage of growth and every wave of technology.
She has carried the number through the same conditions you are now trying to read.
Crystal Decisions · VMware ANZ
Category creation and disruption
Built while categories and the role of partners were still taking shape.
Learned how market creation depends on the commercial system around the product, not the product alone.
Google Cloud ANZ
Building from zero to hypergrowth
Built the ANZ ecosystem in Google Cloud’s challenger phase, with plays the field adopted.
Owned the strategy and the number. Built in region, not handed down from a global plan.
HashiCorp APJ
Building, proving and scaling a regional model
Built one commercial model across APJ, with partners and the direct team in it together.
Took the role only if it owned every route to market, hyperscalers as well as integrators. Much of what was built in region was adopted globally.
SAP · IBM ANZ
Enterprise transformation
Brought in as a change agent on partners at both. Leadership team at SAP, senior leadership team at IBM.
Learned that big companies run by function, and that growth through partners needs someone to join them up.
CRYSTAL DECISIONS · HASHICORP
Leadership change, acquisition and transition
Saw Crystal Decisions acquired by Business Objects. Stayed through HashiCorp into IBM by choice, to learn it.
Learned what you have to prove, protect and change for a working model to survive an acquisition.
Company names describe Rhody’s career experience and do not imply endorsement of Ecosystem Alchemy.