Product & systems engineering · Batangas, PH
Most people will build you a website
I build the system that runs it.
I'm Glen Rieta, a developer in Batangas who builds complete web products: the booking engine, the checkout, the roles and permissions, the dashboard the staff actually live in, and the email that goes out at 2am. Six of them are live right now, including a regional newsroom, an NFC pet-tag product, and a province-wide directory. Usually built on WordPress, almost never as just a website.
Selected work
real projects, real before/after
A lottery results site that runs itself
- A personal experiment: could a site actually read PCSO results and post them automatically
- A basic results tracker, no AI, no notifications, nothing installable
- AI-powered ticket scanner so players check tickets automatically
- Results auto-publish to Facebook the moment a draw lands, with generated captions
- Automated SEO content pipeline for every draw result
Paper business cards → a full digital identity platform
- A single experiment: embedding a working vCard into a QR code
- One card, one person, no CRM, no organizations, no AI
- Full contacts CRM with CSV import, vCard export, and org-wide badge/membership system
- Self-serve dashboards so organization admins manage their own teams, no ticket to me required
A province-wide directory that finally acts like a real platform
- No organized directory for Batangas businesses, most had no way to take a booking or order online beyond a Facebook message
- Nothing to build on: no dashboard, no bookings, no real system, just an idea worth solving
- A dedicated booking system for places to stay, a reservation system for places to eat, and a mini e-commerce system for places to go
- A full review system, a branded HTML email system, AJAX-driven search and map view, plus a merchant dashboard on a real REST API, entirely outside wp-admin
A collective that outgrew its Google Form
- No platform at all for a Batangueño art collective: membership through a Google Form, announcements in chat threads, artwork sold by posting a photo and haggling in the comments
- No roster the officers could actually look at, no record of who had paid dues for the year, nowhere a sale left an accountable trail
- Native membership applications, officer review, three roles, public member profiles, and yearly renewals with an officer-set fee and grace period
- A members' marketplace with GCash checkout and auctions, community boards with polls and upvotes, and an officer panel holding the roster plus a ledger that records marketplace income automatically
A pet tag that can actually bring a pet home
- A collar tag held a phone number stamped into metal, usually worn half illegible, and the owner could never change a character of it
- No product existed for this: someone who found a lost pet and wanted to help had one move, call that number and hope it still belonged to the owner
- Tap the tag and read a profile the owner edits any time: identity, markings, microchip, medical notes, vet, and how to reach them
- A full storefront on a custom theme with PayPal checkout, Philippine address cascade, shipping zones, promo codes and referrals, plus Lost Mode that alerts the owner with the finder's location, only when the finder allows it
A regional newsroom, not a blog with a news theme on it
- No independent news site covering CALABARZON and MIMAROPA, and nothing off the shelf that does what a newsroom actually needs
- A blog can publish a post. It cannot hold a byline that means something, an editor's front page, a correction that stays visible, or photo rights
- A full newsroom at its own URL: editor, overview, analytics, mailbox, ads, team, media, lotto and newsletter, with writers kept out of wp-admin entirely
- Corrections in four levels matching the published policy, live blogs, editorial control of the front page, mirrored PCSO results, photo watermarking, and first-party analytics that store no IP address
What I build
the parts a website doesn't have
Platforms
Marketplaces, directories, newsrooms and membership systems. The whole thing, from the public page to the screen somebody runs it from.
Payments & orders
Checkout, manual payment verification, and refunds that actually reverse what the sale created, with order states that survive real life.
Dashboards outside wp-admin
The screen your staff live in all day, built for their job instead of bent out of WordPress's admin area.
Accounts, roles & access
Registration, permissions, invitations and member accounts, so the right people can do their own work without going through me.
Data & automation
Feeds, mirrors, scheduled jobs and the email that goes out on its own, so nobody re-types anything that already exists.
Custom WordPress architecture
Custom themes and real plugin architecture underneath, not fifteen stacked plugins hoping to agree with each other.
Things I fix
sound familiar?
Does your team work inside wp-admin all day because nobody built them a real screen?
Do orders arrive fine, but someone still confirms every payment by hand in a chat thread?
Does a refund or a cancellation leave stock, codes or credits wrong until somebody notices?
Does every new member, listing or article still have to come through you?
About
the person behind the ledger
I'm Glen, the person behind the ledger.
I'm a web developer and graphic artist based in Batangas, Philippines. I spent years building software from inside a business, watching up close what happens when a company outgrows its manual processes but never gets around to replacing them. Freelance since 2026. This site started as a one-page link list. It became where I keep the systems I wish more businesses had.
Outside client work I'm a member of BAGSIK, the Batangueñong Grupo sa Sining at Kultura, and the graphic artist behind three coffee table books, two NCCA exhibits, and the logo on a hospital in Padre Garcia.
Tell me what your operation actually does all day.
Not your tech stack. What gets typed twice, what breaks at month end, what nobody can do unless you do it. Then I'll tell you what's worth building, and build it. No jargon, no "let's circle back."