Consulting
I take a small number of engineering engagements alongside the products I build in public.
The categories below are the work I actually do. The linked projects and articles are how you can check that.
Custom Software Development
Web apps, internal tools, and small SaaS products in React, TypeScript, Laravel, and Python — built around the workflow people already use.
- React, TypeScript, and Next.js interfaces
- Laravel, PHP, and FastAPI backends
- APIs and internal business tools
- Progressive web apps and static reporting sites
Related work
AI Automation & Engineering
Agent workflows, LLM features, and integrations where a person still reviews the output. I use this on my own repositories before I recommend it.
- GitHub-based agent pipelines with human merge gates
- Repository rules, prompts, and review loops
- LLM application features and integrations
- Retrieval and transcription systems, scoped to what is actually built
Related work
Application Modernization
Legacy PHP and WordPress systems that need a safer deploy path, a clearer API boundary, or fewer manual upgrades — without a rewrite for its own sake.
- PHP, Laravel, and Symfony codebases
- WordPress fleet operations and self-hosted infrastructure
- API cleanup, performance, and maintainability
- Static publishing when a server is the wrong tool
Related work
Technical Discovery & Architecture
A written read on the system you have: constraints, a proposed shape, and a sequence to build it. Useful before a large commitment of engineering time.
- Requirements and constraint gathering
- Technical assessment of an existing app or workflow
- Architecture options with the tradeoffs attached
- An implementation sequence, not a slide deck of tools
Related work
Request a technical consultation
Email [email protected] or use the contact form. A useful first note says what the system does today, what is breaking, and what decision you need.
Request a technical consultation