One order book. Every payment proof checked. One kitchen list a day.
















| Before | Now | |
|---|---|---|
| Orders arrive | Messenger threads | One book, website and chat |
| Payment proof | Checked in the chat | Kept with the order, duplicates flagged |
| Kitchen list | Retyped every night | One screen, opened each morning |
| Month-end numbers | Nobody could say | On the dashboard |
Menu, payment proofs, daily cap, kitchen list.
Slots, deposits, reminders, day sheet.
Customers, payments, refunds, exports.
Every system is built for the business that ordered it.
Built for how you take money. Price fixed in writing before work starts.
Ads, posts and company sites are quoted separately — see what else I do.
The part owners skip and engineers read.
| How it works | |
|---|---|
| Stack | Laravel, rendered on the server so it opens fast on a phone |
| Money | Derived from the payment rows, in centavos, never typed in |
| Audit | Every payment event appended to a log nobody can edit |
| Tests | Over a thousand automated checks, run on every push through GitHub Actions |
| Deploys | The deploy script reads the diff, runs the gates, and refuses to ship on red |
| Migrations | Additive only, rehearsed against a restored live database |
| Backups | Nightly, with a restore proven before launch |
| Question | Answer |
|---|---|
| Do we stop using Messenger? | No. Staff paste those orders into one form. |
| Who owns it? | You. Domain in your name, records yours, logins handed over any time. |
| GCash and bank transfers? | Yes. Same screenshots, checked in the system instead of the chat. |
| If you get sick, or stop? | Ordinary Laravel another developer can pick up. The handover pack has logins, backups and notes. |