Projects/BayadTayoOpo
PRODUCT CASE STUDY LIVE WEB APPLICATION
BTBayadTayoOpo

Splitting the bill shouldn’t become another task.

A spontaneous birthday trip exposed how much setup can surround a small social problem—and led to a group-expense product designed to get out of the group’s way.

DALAGUETE TRIP3 BIRTHDAYS · 6 FRIENDS
ADD EXPENSEDinner after the beach
Amount (PHP)₱ 2,400.00
YJMC₱600 each

May nagbayad. May may utang.
Kami na bahala sa math.

WHYTHOUGH CASE FILE / 01FRIENDLY, NOT FINANCIALBUILT FOR REAL AMBAGAN

Dalaguete, Cebu · three birthdays · one group trip

Money started moving everywhere.

Someone paid for food. Someone else covered transportation. Another person bought something for the group. Some expenses included everyone; others did not.

None of that was unusual. Eventually, though, somebody had to answer one ordinary but uncomfortable question:

Who owes whom?
DALAGUETE / DAY 01Birthday trip
  • Breakfast₱780
  • Van + fuel₱2,150
  • Entrance fees₱900
  • Drinks₱460
  • Dinner₱2,400

paid by different people
shared by different people

TOTAL ≠ THE HARD PART

The tool reduced arithmetic—but introduced ceremony

Setup felt disproportionate to the day.

This was not a household managing recurring bills. It was simply: we are going somewhere together; let’s track what we spend today.

01Install an app

A store detour before participating.

02Create or access an account

Establish a product relationship.

03Join the group

Get everybody into the same system.

04Learn the interface

Understand it during the trip.

Why does everyone need to install something just because one person wants to keep track of the expenses?

Then came another mismatch

Free-tier limits made every small expense feel consequential.

Food, transportation, entrance fees, drinks, groceries—spontaneous trips can generate many small expenses quickly. Nobody wants to ask whether an expense deserves one of the remaining entries.

The foundational question

How little should someone have to do before they can start splitting expenses?

1Open a link2Add people3Track the expense4Continue the trip

Something happened. Add it. Move on.

Distribution is part of the experience

Installation became an option—not an admission requirement.

A traditional mobile application immediately adds the step the product is trying to remove: “Install this first.” A web application makes entry simpler: open a link, start using it, and share it.

People who use BayadTayoOpo often can still choose to keep its Progressive Web App on their device.

TRADITIONAL APP ENTRY
  1. Find the store listing
  2. Install the app
  3. Open and configure
  4. Then participate
BAYADTAYOOPO WEB ENTRY
  1. Open the shared link
  2. Start participating
PWA install remains optional

A participant is not necessarily a user

The group can represent real people before everyone authenticates.

Only one person may want to organize the trip. Everybody else should still be representable in expenses with as little effort as possible.

The group can exist before everybody decides how much they want to interact with the software.

A three-day group does not need a lifelong product relationship.

FRICreate the group

The birthday trip begins.

···
SATSpend together

Expenses move everywhere.

···
SUNSettle balances

Everyone understands what remains.

···
DONEGo on with life

No retention ritual required.

The lifetime of the software relationship shouldn’t have to exceed the lifetime of the real-world group.
BT

The name

BayadTayoOpo

“Bayad tayo” connects immediately to paying and settling up. The playful construction gives the product the casual character of the situations it serves.

FRIENDLYFINANCIALCASUALCORPORATEUSEFULOVERBUILT

This should feel comfortable to send into a group chat after dinner.

What BayadTayoOpo is not

A narrow responsibility keeps the product honest.

Financial products are often expected to accumulate financial features. BayadTayoOpo deliberately draws a smaller boundary.

NOT A BANKNOT A DIGITAL WALLETNOT AN ACCOUNTING PLATFORMNOT A BUDGETING APPNOT A PAYMENT PROCESSORHelp a group understand shared expenses and settle with less friction.
bayadtayoopo.web.app
The live BayadTayoOpo homepage showing a group expense form for a sample barkada trip
Live working web application · captured August 2026
LIVE

The trip problem became a working web application.

The product has grown beyond Dalaguete, but its original constraint still evaluates each feature:

Does this make splitting expenses easier, or does it make BayadTayoOpo more complicated?

The goal is not the longest feature list. It is less attention spent on the awkward administrative part of spending money together.

Open BayadTayoOpo

An evolving case study

The simple interface moves complexity underneath.

The next chapters will document the actual engineering and product decisions as the application evolves.

01

Group creation and membership

02

Participants without immediate accounts

03

Expense modeling and balance calculation

04

Payment instructions and settlement

05

PWA and offline decisions

06

Data synchronization and onboarding

07

Technical architecture

08

Decisions that did not work

09

Features changed or removed

10

Evolution after real use

09

What BayadTayoOpo taught me

How much of a process exists because the problem requires it—and how much because the software requires it?

Accounts, installation, onboarding, and persistent groups can all be useful. None should exist automatically just because they are conventional.

Sometimes people aren’t looking for a platform. Sometimes they’re three birthdays into a trip in Dalaguete and just need to know:Sino pa ang may bayad?

The software should meet them there.