Back to Insights
AIJanuary 2026·9 min read

Building Your First AI Agent: What to Automate First

W

Diwa “Wawi” del Mundo

Founder & CEO · Apper Cloud Labs

AUTOMATION PRIORITY MATRIXFREQUENCY (how often?)REPEATABILITY (always same steps?)LOWHIGHLOWHIGHSTART HEREHigh freq + repeatable→ Tier-1 support→ Invoice processing→ Data entry tasksDO NEXTLow freq + repeatable→ Monthly reports→ Compliance checksAUGMENTHigh freq + variable→ AI assists humans→ Don't fully automateSKIP FOR NOWLow freq + variable→ Edge casesIMPLEMENTATION PHASES01 IDENTIFYMap your repetitive tasks02 PRIORITIZEScore by freq × repeatability03 PROTOTYPEBuild smallest version first04 MEASURETrack time saved & accuracy05 EXPANDRoll out to more use cases

Every week, I talk to business owners who want to "implement AI" in their operations. The conversation usually starts the same way: they've been reading about AI, they know their competitors are looking at it, and they want to make sure they're not left behind.

That instinct is right. But the next question — "where do we start?" — is where things get complicated. Because starting in the wrong place is how you spend months and significant budget on an AI project that nobody uses.

After building AI agents for Philippine businesses across BPO, retail, healthcare, and financial services, here's the framework I use to figure out where to start.

The wrong way to start

The most common mistake I see: starting with the most exciting thing, not the most impactful one.

"We want an AI that can predict customer churn." That's genuinely useful — but it requires historical data pipelines, model training, integration with your CRM, and a process for acting on the predictions. It's a 3–6 month project minimum.

Meanwhile, your customer support team is manually answering the same 40 questions 200 times a day. An AI agent for that is a 2–3 week build. The ROI is visible within the first month.

Start with the process that costs you the most hours per week doing the most predictable work. Not the most interesting problem.

The Automation Priority Matrix

When I help businesses identify where to start, I use a simple two-axis framework:

  • Frequency — how often does this task happen? (daily, hourly, once a month?)
  • Repeatability — does this task follow the same steps every time, or is it highly variable?

Plot your tasks on those two axes. The ones in the top-right quadrant — high frequency, high repeatability — are your starting point. Those are the tasks that AI automates most reliably and where you'll see ROI fastest.

QuadrantWhat it looks likeWhat to do
High freq + RepeatableAnswering FAQs, data entry, report generationAutomate first — strongest ROI
Low freq + RepeatableMonthly compliance reports, quarterly auditsAutomate next — easy wins
High freq + VariableComplex customer complaints, account managementAugment — AI assists humans, doesn't replace
Low freq + VariableOne-off decisions, novel situationsSkip for now — not worth the effort

Three good starting points for most Philippine businesses

1. Customer support tier-1 — the most common starting point

If you have a customer support function, start here. Take your 30 most common customer inquiries. Document the correct answer to each one. Build an AI agent that handles those 30 scenarios automatically — and escalates everything else to a human.

This is a two-to-three week project. It's measurable (volume of tickets handled, response time), and the impact is immediate. Once you've seen it work on the easy cases, you expand the scope.

2. Internal document search and Q&A — underrated

How much time does your team spend looking for information? Digging through old emails, searching shared drives, asking colleagues where to find the right policy document?

An AI agent that can answer questions about your internal documents — employee handbook, SOPs, product specs, contracts — is a surprisingly high-impact project. You upload your documents, connect it to your communication channel (Slack, Teams, email), and your team can ask questions in plain language and get instant answers.

I've seen this save teams 30–60 minutes per person per day. The productivity gain is real and measurable.

3. Data entry and document processing

Do you receive forms, invoices, or documents that need to be manually keyed into a system? This is a strong candidate for AI automation. Modern AI can extract structured data from PDFs, images, and scanned documents with high accuracy, then push it directly to your systems.

The key question to ask: what percentage of these documents are "standard" (same format every time) vs. highly variable? The more standardized, the easier and more accurate the automation.

2–3 wks

to build a working tier-1 support agent

30–60 min

per person saved daily by internal Q&A agents

85–95%

accuracy on standardized document extraction

What it actually takes to get started

1

Document your processes — before you touch any technology

You cannot automate a process you haven't written down. Before any AI work begins, write out the steps: what triggers the task, what happens at each step, what the correct output looks like, and when to escalate to a human. This documentation is what the AI learns from.

2

Gather your existing data and content

AI agents are only as good as the information they have. If you want a customer support agent, you need your FAQs, product documentation, and policy documents cleaned up and organized. If you want a document processor, you need sample documents that represent what you receive. Most projects spend 40–50% of their time in this data preparation phase.

3

Define success before you build

What does "working" look like? How will you know if the AI is performing well? Set measurable targets upfront — tickets handled per day, accuracy rate, response time, escalation rate — so you can evaluate the system objectively and improve it.

4

Plan for exceptions from day one

Every AI system encounters situations it wasn't built for. Design the escalation path before you go live: what happens when the AI doesn't know the answer? Who does it escalate to? How is the escalation handed off? A system with no escalation path creates frustrated customers and erodes trust in the technology.

How long does this take?

A focused, well-scoped first AI agent — tier-1 support, internal Q&A, or document processing — typically runs 2–4 weeks from kickoff to live. That's a short enough timeline to prove the concept before committing to bigger projects.

From there, expansion is faster. Once the core infrastructure is in place (integrations, escalation flows, monitoring), adding new capabilities is incremental.

Honest caveat

AI projects fail when the scope is unclear, the data isn't ready, or the business process being automated is poorly understood. The technology isn't the hard part. Getting alignment on what the agent should do — and making sure it has the information it needs — is where most of the work happens.

The right mindset

Think of your first AI agent as a proof of concept, not a final product. The goal is to demonstrate that AI can reliably handle a defined set of tasks in your specific business context — and to learn what you need to build on top of that foundation.

Every successful AI deployment I've been involved in started small, measured carefully, and expanded deliberately. None of them launched as a comprehensive AI transformation program. They started with one well-chosen use case.

Pick the right one, build it properly, and let the results speak for themselves. That's how AI adoption actually works in practice.

W

Diwa “Wawi” del Mundo

Founder & CEO, Apper Cloud Labs

Wawi holds all 13 AWS certifications alongside CISSP and CCSP — one of the most credentialed cloud architects in the Philippines. He founded Apper Cloud Labs in 2019 to make enterprise-grade cloud and AI expertise accessible to Philippine SMBs.

Have questions?

We're happy to talk through your specific situation.

Schedule a Free Consultation