The evidence behind the homepage.
Case studies, thirteen years of record, migration figures, and the questions everyone asks.
Looking for the case studies?
The NGO software estate, the legislative platform, the government document system and two CRMs now have their own page.
Thirteen years
I started building business systems in 2013. Since then the stack has changed three times and the work has not: somebody has a process that does not fit any product they can buy.
University systems, Philippines. Mail tracking, ticketing, records. PHP and MySQL. Where I learned that the requirements are never what the first meeting said.
Employed developer, then first international clients. Spare-parts ERP with barcode labels, valet-storage platform with payments, welding distributor back office, charity and volunteering sites. Node, Express, MongoDB.
Agency and enterprise work. Document routing for a government department, marketing analytics for online sellers, a sustainability app, membership portals and a headless CMS for an international policy body. Vue, Strapi, AWS.
Products and platforms. Legislative tracking, two CRMs, a creative-approval workflow, an outreach tool, my own wedding-planning platform with an AI assistant. React, Next.js, Supabase, Postgres.
Approval workflows · CRMs · inventory and ERP · membership portals · marketplaces · product search · document generation · dashboards · field and dispatch tools · data migrations
HR systems (BambooHR) · association membership databases · Monday.com · QuickBooks · PandaDoc · Google Workspace · Stripe, PayPal and PayMongo · Typeform · Webflow · single sign-on (Auth0, SAML)
Word and Excel documents generated to your exact template · multi-stage approvals with an audit trail · role-based permissions · moving twelve years of old records · making it work on a phone in the field
For the technically minded: React, Next.js, Vue, Node, Python, Laravel, PostgreSQL, Supabase, AWS. Happy to go deeper if that matters, happy to skip it if it does not.
- Postgraduate Certificate in Information Technology ManagementAsian Institute of Management
- Master of Information Technology, System DevelopmentAteneo de Zamboanga University, 2015 to 2022
- BSc Information Technology, Web DevelopmentAteneo de Zamboanga University, 2011 to 2015
I also taught web and mobile development at undergraduate level at the same university, and advised final-year capstone projects in its College of Science and Information Technology. Teaching a thing badly is the fastest way to find out you only half understood it.
Moving old data is where projects go wrong
Most projects report one number at the end: “2,400 records transferred.” That tells you nothing about what did not come across, and that is the part that causes trouble six months later. So I hand over an account of both. Real figures from a 2025 project, and not the first of these: several of the university systems I built between 2013 and 2016 replaced an older system and carried its records across. What is new is the accounting, not the moving.
| Travel requests | 679 |
|---|---|
| Hotel bookings | 847 |
| Transport bookings | 1,487 |
| Unfinished drafts | 302 |
| 3,315 moved. None lost. | 3,315 |
| Moved, with their records | 93 |
|---|---|
| Left behind: no longer employed | 2,115 |
| Left behind: no email on file | 154 |
| Every account left behind has its reason written down. | |
The second table is what lets a finance lead or a board sign a project off. It is the difference between “we think it worked” and being able to prove it.
You are hiring one person. Here is what that means.
You are one person. What happens if you get sick, or disappear?
A fair question, and the honest answer is that it is a real risk with any individual. Three things reduce it. Everything runs in your accounts, not mine, so you always hold the keys. The code is yours, documented, and handed over with a recorded walkthrough made while the reasons were still fresh rather than reconstructed afterwards, so another developer can pick it up without me in the room. And I tell you my availability before you commit rather than taking work I cannot finish. If you need a guarantee that a company cannot vanish, hire a company, and I will say so on the call.
And if you go quiet halfway through a build, not after it?
The harder version of the same question, and the one worth asking. Payment stages are tied to things you can see working rather than to dates on a calendar, so at any point you have paid for something that runs rather than for elapsed time. It runs in your accounts and on your hosting, so the access and the data are yours throughout. What you would not have is a finished system, and nothing about hiring one person changes that. This is the case where hiring a company genuinely buys you something, and if that risk is not acceptable for your project I would rather say so before you sign than after.
Who fixes it at six on a Friday when my staff cannot log in?
For the first month after go-live, me, uncapped and included in the price. That is when everything surfaces, so metering it would have you counting hours at the worst possible moment. After that, if you want it, ₱25,000 a month for up to eight hours, for as long as five months, agreed in writing before handover so nobody is guessing. I do not disappear at handover, and I do not hold your system hostage either.
Will I be locked in to you?
No. Your accounts, your hosting, your code, your data. If you want a different developer in a year, everything transfers with no conversation needed.
What about our data and confidentiality?
I sign your NDA, or provide mine. Your data stays in your infrastructure. All intellectual property in the work is yours on final payment, in writing. If you handle personal data, we put a data processing agreement in place before I touch anything.
Can I talk to someone you have worked for?
Yes. Ask on the call and I will arrange it. Some clients are under agreements that prevent me naming them publicly, which is why this page describes them by sector.
I also turn down work where nobody on your side can make decisions, and anything needing me physically in your office.
Tell me what you are trying to fix.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
Replies within one business day. Manila time.