Kobe Ricafrente Message me
Custom ordering sites and booking systems

Stop losing orders in Messenger.

Your own ordering site, built around how you sell. One order book, every payment checked, one kitchen list a day.

Message me See the live system
Owner dashboard showing money collected and orders on the books
The kitchen list on a phone
Built with

Where orders go

Today
Orders come inMessenger/Instagram DMs, a group chat, text/call
Written down somewhereWhatever is nearest
Retyped at nightA second list, for the kitchen
Proof checked in the chatScroll back to find it
With the system
Order placedWebsite, or pasted from chat
Payment takenPaid online, or the proof checked
Slot heldFull dates show as full
Kitchen listOne screen, pickup order
Money trackedPaid, underpaid, refunded
Live today

Chicky'Oink Manila, lechon belly, three branches

Owner dashboard showing money collected and orders on the books
The Chicky’Oink website showing the menu and sizes
The order form: two lechon bellies chosen, with size, flavor and salt for eachThe order form: branch, pickup date and time, and pickup chosenThe order form: customer details and the total before submitting
After ordering: the order number, the amount to pay and the payment deadlineChoosing how to pay: GCash, Maya or a bank, with the account to send toUploading the payment screenshot, with the reference number
After paying: proof received, waiting for the shop to check itPayment verified: the order is confirmed
A payment proof under review, with the amount and reference beside it
The order book listing branch, pickup slot, items and payment state
The kitchen schedule listing the day’s paid orders by pickup time
The owner’s queue of cancellation requests and unsettled balances
Demo data

BeforeNow
Orders arriveMessenger threadsOne book, website and chat
Payment proofChecked in the chatKept with the order, checked in one place
Kitchen listRetyped every nightOne screen, opened each morning
Month-end numbersNobody could sayOn the dashboard

What I build

Your own customer site

Built for you, on your domain: your menu, prices, branches, pickup days and payment accounts, in your own look. Customers order there instead of in your inbox.

Ordering and pre-orders

Menu, payment proofs, daily cap, kitchen list.

Bookings and appointments

Slots, deposits, reminders, day sheet.

The back office behind both

Customers, payments, refunds, exports.

Every system is built for the business that ordered it.

What it costs

Built for how you take money. Price fixed in writing before work starts.

Add-ons, quoted on top
Online paymentsPayMongoGCash, Maya and card taken on your own site. No screenshot to check.
Text message updatesSemaphore or PhilSMS“Order confirmed.” “Balance due Friday.” “Pickup tomorrow.”
Customer accountsBuilt in, no third partyRegulars log in, see past orders, reorder in two taps.
Delivery bookingLalamoveBook the rider from the order. Tracking link to the customer.
Facebook and Instagram adsMonthlyPixel and Conversions API wired to the order book, so sales are counted from real orders, not Ads Manager.
Posts and graphicsMonthly or per jobMenu cards, promos, announcements, drawn to your branding, scheduled and posted for you.

The engineering behind it

Company sites are quoted separately. See what else I do.

How we would work

  1. Plan
    1. 01You message meMessenger, text or the form
    2. 02Video callHow you take orders now
    3. 03Written quoteFixed price, fixed dates
  2. Build4–8 weeks
    1. 04I buildYou try it on a test site
    2. 05LaunchStaff trained, you go live
  3. Upkeepmonthly
    1. 06I keep it runningHosting, backups, fixes and small changes

How it’s built

The part owners skip and engineers read.

How it works
StackLaravel, rendered on the server so it opens fast on a phone
MoneyDerived from the payment rows, in centavos, never typed in
AuditEvery payment event appended to a log nobody can edit
TestsOver a thousand automated checks, run on every push through GitHub Actions
DeploysThe deploy script reads the diff, runs the gates, and refuses to ship on red
MigrationsAdditive only, rehearsed against a restored live database
BackupsNightly, with a restore proven before launch

Questions people ask

QuestionAnswer
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.

Tell me how you take orders now.

Message me Or fill this in →
m.me/kobe.ricafrente Viber: 0995 106 9920

I read every one myself. Nothing here is shared with anyone, and I don’t send newsletters.