The "Nakalimutan Ko" Problem: Why Philippine Businesses Leak Money

Every Filipino business owner knows this problem. I think I found the right tool for it, and I'm testing it now. Follow along.

The most expensive phrase in Philippine business is "nakalimutan ko."

I forgot.

Every business owner here has heard some version of it.

Nakalimutan ko mag-follow up.

Nakalimutan ko ma-record.

Nakalimutan ko sabihin.

Nakalimutan ko ma-confirm.

Sometimes it's small. Sometimes it's expensive. Usually it's both.

The thing is, I don't think this is mainly a people problem.

It's easy to get frustrated and blame the person who forgot. And to be fair, sometimes there is an accountability issue. But from what I've seen, the bigger problem is that most small and mid-sized businesses are running on memory, chat threads, and verbal handoffs.

So of course things get dropped.

We're asking humans to act like infrastructure.

That works for a while. Until the business gets even a little more complex.

One customer follow-up gets missed.

One supplier update doesn't get passed along.

One receipt doesn't get recorded.

One delivery detail stays in somebody's head instead of going into a system.

Then everybody is surprised when something breaks downstream.

What actually happened was the system had no way to catch the miss.

That's why I think "nakalimutan ko" is not just a phrase. It's a signal.

It usually means one of three things:

• there was no reliable handoff
• there was no shared visibility
• there was no reminder or escalation layer when something stayed pending too long

And when those three are weak, forgetting becomes expensive.

You pay for it in rework.

You pay for it in delays.

You pay for it in awkward customer conversations.

You pay for it in tax records that are incomplete.

You pay for it in trust, which is harder to measure but probably the most painful cost of all.

I've seen versions of this across normal business operations:

Missed deliveries because someone assumed someone else had already confirmed.

Procurement delays because the supplier follow-up stayed inside a chat thread.

Accounting bottlenecks because documents were submitted late or recorded late.

Even something as basic as receipt logging can turn into leakage if the task is annoying enough that people keep putting it off.

The pattern is familiar.

Nobody is trying to sabotage the business.

People are just busy. Context switches are brutal. SMEs usually don't have clean systems. The same person is wearing three hats. There are too many moving parts and too much information is trapped in heads, inboxes, Viber, Messenger, paper, and random spreadsheets.

So yes, people forget.

Humans forget. That's normal.

The expensive part is building a company that assumes they won't.

This is also where I think a lot of AI talk misses the point.

Developers usually see forgetting as a scheduling problem.

"Just use a cron job."

"Just send reminders."

"Just integrate the task app."

Those things can help, but they don't solve the deeper issue. The problem isn't just that a reminder failed to go out. The problem is that the business often has no persistent layer watching what matters, what is still pending, what is overdue, and what needs escalation.

Business owners don't wake up asking for better prompt engineering.

They wake up asking why the quotation didn't go out, why the follow-up didn't happen, why the stock wasn't updated, why the customer is suddenly angry, and why everything seems to rely on one person remembering at the right time.

That's an operations problem first.

Technology is just one possible fix.

I think that's why I'm more interested in systems that catch forgotten tasks than in flashy AI demos. A lot of value comes from making the business easier to remember for. That sounds almost stupidly simple, but it's real.

If the process depends on memory, it will eventually fail.

If the process depends on a system that records, tracks, reminds, and escalates, the business gets more forgiving.

That's a better use of automation in my opinion.

Not replacing people.

Supporting people where human memory is weakest.

And in the Philippine context, this matters even more because many companies are still operating with very light process discipline. That's not always because they're careless. Sometimes they're just growing faster than their systems. Sometimes the culture is highly relationship-based and informal, which has upsides, but informality breaks down once volume increases.

Everything feels manageable until one forgotten thing touches another forgotten thing.

Then suddenly the issue isn't one missed task.

It's a chain reaction.

This is also why I don't think the cure is "be more disciplined" and leave it there. That's nice advice. It just doesn't solve much by itself.

The better question is:

Where are the business-critical tasks that still rely on memory?

Where are the handoffs that happen verbally?

Where are the follow-ups with no owner, no timestamp, and no escalation path?

That's where the money leaks.

I'm increasingly convinced that some of the best AI or automation work for SMEs will look very boring from the outside. Not chatbots. Not avatars. Not ten-agent systems talking to each other.

Just a persistent operational layer that catches the "nakalimutan ko" before it becomes expensive.

That's what I'm interested in building and testing.

Not because it sounds advanced.

Because forgetting is expensive, and we keep pretending it's normal overhead.

Maybe it is normal.

But normal doesn't mean harmless.

If you're running a business, you probably already know your version of this phrase. You hear it enough that it stops sounding alarming.

I think that's the danger.

Once "nakalimutan ko" starts sounding ordinary, the business has already accepted leakage as part of daily life.

I don't think we should accept it that easily.

Note: I use AI as a writing and thinking tool. The ideas, examples, and judgment in this post are mine.