AI adoption in Philippine banks: why people come before technology
Article
Find out why skills and people are the biggest barrier to AI in Philippine banks and lenders and what that means for your next AI budget.
What’s holding AI back in Philippine banks and lenders? A global survey of chief data officers named data and technology as the top obstacles to getting generative AI from pilot to production. When we asked the people who work with AI inside Philippine banks and lenders, 35% named skills and people as their biggest barrier and only 5% named old systems.
This article covers what our respondents said holds AI back, what they meant when they would say skills, why this all changes where your next budget should go and what to do about it now.
Only got five minutes? Here are the key takeaways of this article:
35% of Philippine respondents named skills and people as the biggest challenge stopping wider use of AI, ahead of data quality (20%) and integration challenges (15%).
Skills, budget and not knowing where to start account for half of all answers (50%).
Among respondents further along, skills and people, data quality and integration challenges were each named by a quarter (25%), so the technical work grows as AI moves into daily processes.
If skills are the first constraint, more technology adds capacity your team may not be able to use yet.
Get the full findings in From AI interest to operational value. You can also book a call with vanda.jirasek@oradian.com to talk it through with our Manila team.
Want to find out more first? Read the rest of this.
People came first inside Philippine institutions
Asked to name the single biggest challenge stopping wider use of AI, 35% of Philippine respondents chose skills and people. Data quality came second (20%), followed by integration challenges (15%), budget (10%) and regulations (10%). Old systems and not being sure where to start were each named by 5%.
Grouped together, people and organisational barriers account for half of all answers. Data accounts for 20%, systems for 20% and regulation for 10%.
Informatica’s CDO Insights 2025 tells a different story. Its 600 chief data officers and chief data and analytics officers across the US, Europe and Asia named data (43%) and technology (43%) as the top obstacles, ahead of people (35%) and process (35%). Informatica asked data leaders to name their obstacles while we asked the people working with AI inside Philippine institutions for their single biggest challenge, so the comparison is directional. Still, the view from inside these institutions puts people first.
Defining skills
Skills can mean several things our survey didn’t separate: data and engineering specialists, people who can judge which use cases are worth doing and business teams able to run a process once AI is part of it.
Skills and people were the top barrier for respondents at an early stage (42%). Among respondents further along, skills and people, data quality and integration challenges were each named by a quarter (25%). Skills look like the first constraint, with data and integration joining them once AI is in daily use.
Why this changes where your budget goes
If skills are the first constraint, spending on new technology adds capacity the institution may not be able to use yet. A stalled project then makes the next budget harder to win.
The same Informatica survey found that 97% of those using or planning to use generative AI face difficulty demonstrating the business value of their initiatives. Measured results are what win the next budget, so every AI use case needs someone who owns those results.
We also asked how confident respondents are that their data and systems can support AI. The average was 3.1 out of 5, with 45% choosing 3 and no one choosing 5. A score of 3 describes an institution whose data and systems are ready for some uses of AI and not yet for others.
Apply these findings to your own firm
Here’s what we recommend doing next based on these findings:
Build, hire or source: decide use case by use case which skills to build, which to hire and which to source from partners.
Name an owner: give every use case an owner in the business, plus the team who will run it once it’s live.
Fix the data you need first: start data quality work with the data your priority use case needs.
Plan for production: plan the integration work for production at the same time as the test.
Measure from day one: agree with finance which measures count for each use case and report them from the first month.
Governance points the same way. Bangko Sentral ng Pilipinas’ Memorandum No. M-2026-031 sets out five STARS principles for AI in financial services. Accountability is one of them and institutions are expected to apply all five in proportion to how much they rely on AI, so naming an owner for every use case is a governance step too.
Where Oradian fits
Technology makes people barriers smaller when it reduces how many specialists each use case needs. Oradian is the AI-native banking platform for banks and lenders in emerging markets and here’s how it keeps the specialist load down:
Your product team: configures rates, fees, schedules and eligibility without code.
Your engineers: write the logic that’s yours alone in Custom Code, versioned and auditable, with an AI agent writing it alongside them.
Our team: Oradian’s own team in Manila implements the platform and works directly with yours.
Esquire Financing went live on Oradian in three months, with the implementation run by Oradian’s Manila team.
Start with your people
Every AI use case needs an owner in the business, people who can judge whether it’s working and a team who will run it once it’s live. Plan those roles before the first use case goes live.
Get the full findings in From AI interest to operational value and book a call by emailing vanda.jirasek@oradian.com to talk it through with our Manila team before the end of the year.