What I build
Pick a problem.
Not a technology.
Nobody hires a stack. They hire someone to make the thing work: the orders, the accounts, the screen their staff live in all day. Here is the range of problems I actually solve, and what each one looks like when it is done properly rather than approximately.
The work
six kinds of problem, one developer
Platforms
Marketplaces, directories, newsrooms and membership systems. Not a template with your logo on it: the public side, the data model underneath, and the screen somebody runs the whole thing from.
Payments & orders
Checkout, manual payment verification for GCash and bank transfer, promo codes, shipping rules, and refunds that reverse everything the sale set in motion, including the parts nobody remembers to undo.
Dashboards outside wp-admin
The screen your staff live in all day, built for their actual job. WordPress's admin area was designed for publishing posts, not for running a business, and it shows within about an hour of anyone trying.
Accounts, roles & access
Registration, permissions, invitations, profiles and self-serve accounts, so your members, merchants or writers do their own work instead of queueing behind you for every small change.
Data & automation
Feeds, mirrors, scheduled jobs, and email that sends itself. If a number already exists somewhere, nobody should be re-typing it into your site by hand every morning.
Custom WordPress architecture
Custom themes, mu-plugin architecture, REST endpoints and proper data models. Fifteen stacked plugins is not an architecture, it is a list of things that can break independently of each other.
How I work
the same three steps, every project
Understand
Show me how the operation actually runs: who does what by hand, what breaks at the end of the month, what nobody can do unless you do it yourself. Most of the real requirements are hiding in there.
Build
I build the specific system that fixes what is actually broken, including the unglamorous half: the order states, the reversals, the permissions, and the email nobody thinks about until the day it fails.
Improve
Software is not done at launch. I stay on to fix what breaks and extend what works as the thing grows into whatever it turns out to be.
Not sure which of these you need?
That's fine, most people aren't. Tell me the problem and I'll tell you what to build.