Somewhere inside NextPay's original ledger are Easter eggs. Don Pansacola put them there for engineers he had not yet hired, small signs that the architect of a financial system had retained a programmer's taste for mischief. Ledgers are supposed to be sober things. They remember every movement, tolerate no ambiguity and become interesting mainly when they fail. Pansacola built the core one himself. Then he left a wink in the machinery.
That detail explains more than a résumé does. Pansacola is the co-founder and CEO of NextPay, the Philippine company that helps businesses send payouts, collect money, issue invoices and connect payment workflows through software. He is also an engineer who has never quite accepted that executive work must happen at a safe distance from code. He once described his job with three unofficial titles: “Chief Learner, Chief Questioner and Chief Doer of Stuff.” The doing included coding, automation, workflow diagrams and technology partnerships. CEO, in his telling, is less a throne than a drawer full of tools.
The path to those tools ran through Vancouver. Pansacola studied at Simon Fraser University and worked across product, design and software. He joined the early core product team at OpenDNS, the internet-security company Cisco acquired in 2015. His public biography describes a background in distributed systems and product building, along with a life outside the terminal as a musician, composer and producer. He played guitar and keyboards for COCAHALA. The combination feels apt: a ledger and a song both require structure, timing and the occasional surprise.
The pivot hidden inside a crisis
Pansacola moved from Vancouver to Manila and, in 2019, started NextPay with Aldrich Tan and Artie Lopez. The first idea centered on financial wellness. The product would help employees set aside part of a salary for savings goals. Then 2020 arrived, and a more immediate problem announced itself. Philippine businesses, especially small ones, struggled to pay workers and suppliers when familiar bank and branch routines became difficult or impossible. The founders shifted the company toward business disbursements.
The word “pivot” can make a difficult act sound like a smooth quarter-turn. This one meant changing the customer, the urgency and the center of the product. It also meant noticing who the conventional system embarrassed. Large companies could absorb maintaining balances, paperwork and separate banking tools. A small operator might spend days collating timesheets and entering data twice. One NextPay customer used to send a staff member to a remittance outlet carrying payroll cash, with a driver acting as a bodyguard. The old process took three days. With the platform, it fell below three hours.
The opportunity was hiding in the phrase “we've always done it this way.”
That is Pansacola's favorite terrain. His advice to newcomers in finance is to question the status quo and use first principles. Regulation, in his view, does not remove the room for invention. It can preserve habits long enough that nobody remembers the problem they once solved. Average daily balances, branch visits, screenshots sent as proof of payment and spreadsheets used as shadow ledgers begin to look natural. A new entrant has the useful rudeness to ask why.
A boring problem becomes durable
NextPay joined Y Combinator's Winter 2021 batch and received the accelerator's $125,000 investment. Four months later, the company announced a $1.6 million seed round led by Golden Gate Ventures and Gentree Fund, with participation from investors spanning the Philippines and Southeast Asia. Funding is the part of a startup story that photographs well. The more consequential milestone was quieter: the company processed its first cumulative billion pesos in 2021.
By 2022, NextPay had become a runner-up in the Business Innovation category of Shell LiveWIRE's global Top Ten Innovators Awards, selected from 195 applications across 17 countries. Pansacola was also named one of Tatler Asia's Gen.T Leaders of Tomorrow in the Philippines. By 2023, the platform had served more than 12,000 companies and moved ₱5 billion. The company's present-day site reports more than ₱30.1 billion processed by June 2026, alongside over 1.7 million transactions and connections to more than 90 banks and e-wallets.
Numbers can make infrastructure sound abstract. Its actual unit is the avoided indignity: no bodyguard for a payroll run, no afternoon lost matching screenshots, no supplier waiting because one bank portal refuses to speak to another. NextPay's modern products include business payouts, receivables, invoicing and NextAPI for embedded payment workflows. The promise is not that money becomes exciting. It is that moving it becomes uneventful. In finance, uneventful is a feature with excellent manners.
The office after the laptop
Pansacola has lately turned his systems curiosity toward the way software itself gets made. At NextPay, members of the engineering team have been experimenting with a shared virtual private server. Repositories, development servers, tmux sessions and coding agents can live on the same persistent machine. A task continues after an engineer closes a laptop. A teammate can enter the session when help is needed. For parallel work, people branch into separate worktrees, then land changes back on the main line.
The team built a command-line tool called npdev to manage sessions, visibility and repository context. Pansacola also describes background “HEARTBEAT” loops that keep maintenance, documentation and follow-up tasks moving. It is an engineering experiment, not a victory lap. A central machine creates concentration risk. Shared state invites collisions. CPU, memory and human patience all have limits. He has said plainly that not everyone at NextPay works this way and that parts of the system may change next week.
The unexpected result has been cultural. When engineers inhabit the same environment, a slow script or fragile setup becomes a public nuisance. Fixing it helps the group. Shared infrastructure produces shared responsibility. The idea is more interesting than “one giant computer,” which is a good premise for a sitcom and a poor disaster-recovery plan. The deeper question is whether the personal laptop should remain the natural boundary of an engineer's workplace when code, runtime and artificial collaborators persist elsewhere.
This question connects to another of Pansacola's projects, a personal AI he calls 0000. He describes it as a system that remembers yesterday's work, suggests the next task and captures ideas during periods of concentration. His side of the bargain is to improve the prompts, workflows and memory. Better assistance creates time to make the assistant better. It is a recursive loop, the kind of thing that delights a person who can happily discuss game theory, memetics and evolutionary biology for hours.
A first-principles founder is really a professional asker of impolite questions.
Curiosity as an operating expense
The corporate story and the engineering experiments share an instinct. Pansacola looks at scaffolding and asks which parts serve the work and which parts merely serve habit. In banking, the inherited scaffolding included branch rituals, average balances and disconnected portals. In software teams, it includes a development environment that ends at one employee's screen and processes designed around the limits of human memory. His conclusions can be provocative, but his experiments stay close to the machinery. He builds a tool, watches it fail, revises it and reports the rough edges.
There is playfulness in the method. Pansacola's favorite movie is Edge of Tomorrow, a story built around repetition, death and incremental learning. His preferred ice cream is chocolate or coffee, a choice so efficiently caffeinated it could be a developer setting. He makes music. He leaves secrets in ledgers. None of this turns payments into a personality cult, which would be an alarming use of a reconciliation engine. It simply makes visible the curiosity behind the infrastructure.
His stated purpose for NextPay is financial health for businesses and their people. The scale of that aspiration is large, but the daily work is deliberately specific. A payout arrives. An invoice reconciles. A small company closes the books without asking customers for screenshots. An engineer inherits a ledger and finds that somebody expected them, perhaps even hoped they would smile.
Founders are often encouraged to tell stories about changing the world. Pansacola's more persuasive story is about changing the workflow. He followed an awkward process until it exposed a market, then followed the code until it exposed a company, and now follows the development environment until it hints at a different organization. The future, in this telling, is not a gleaming abstraction. It is the boring part working properly, plus one Easter egg tucked safely out of the transaction path.