Projects & Case Studies
I don't just write code - I build systems that solve real problems. Below are focused case studies of core projects I've worked on, including an HR Management System and a Service Tracker platform.
HR Management System (HRMS)
Centralizing people, roles, and internal workflows into one web system.
The Problem
Managing staff data manually (spreadsheets, scattered documents, and chat logs) quickly becomes messy: duplicate records, unclear roles, and no single source of truth. The organization needed a structured, web-based HR system that could grow with them.
The Solution
I built a custom HR Management System that centralizes employees, roles, and key HR processes in one place. Instead of forcing the team into a generic SaaS template, the system is designed around how they actually work.
- Employee profiles with roles, departments, and status.
- Clear separation of permissions (admin, HR, standard user, etc.).
- Structured data, instead of loose files and messages.
- Built so features can be extended as needs grow.
What I Focused On
The goal was not just to "get it working", but to make it maintainable and clear for the next person who touches the code - or for future versions I'll build myself.
- Clean, readable PHP/Laravel backend with clear separation of concerns.
- Responsive, component-based UI using HTML, CSS, and modern JS.
- Database structure designed for clarity and reporting (e.g. employee status, role history).
- Attention to validation and user feedback, so mistakes are caught early.
Outcome
The team moved from scattered records to a single HR system they can log into from anywhere. Instead of hunting for information across multiple tools, everything is now centralized and structured.
Bible Reading Progress Tracker (Flutter)
Turning daily scripture reading into measurable, motivating progress.
The Problem
Many readers start plans with good intentions but lose track of where they stopped or how far they are. Without visibility, progress feels abstract and motivation fades.
The Solution
I built a tracker that shows exactly what was read, what's next, and how close a user is to finishing. It separates completed, current, and remaining readings so momentum stays visible.
- Structured tracking of chapters and books read.
- Visual progress indicators that keep motivation in view.
- Clear daily focus with minimal UI for quick check-ins.
- Data model ready for streaks, summaries, and plans.
What I Focused On
Discipline through simplicity—no clutter, just steady progress.
- Mobile-first design for fast daily updates.
- Progress feedback without overwhelming stats.
- Logical structure to support future streaks and summaries.
- Lightweight interactions to keep users in the flow.
Outcome
Readers move from “I think I'm somewhere in Psalms” to clear, visible progress. Consistency improves, momentum builds, and plans get finished with confidence.
Forex Transactions Manager
Tracking deposits, withdrawals, and trades with clarity and auditability.
The Problem
Traders juggle deposits, withdrawals, and open positions across notes and spreadsheets, making it hard to reconcile balances or explain where money moved.
The Solution
I built a transactions manager that centralizes money in/out and trade records with clear separation of funds and searchable history for accountability.
- Structured logging for deposits, withdrawals, and fees.
- Trade records with pairs, position size, and notes.
- Separation of cash flow vs. positions for quick reconciliation.
- Searchable history to spot trends and audit trails.
What I Focused On
Accuracy and clarity without accounting jargon.
- Simple flows for logging cash movements and trades.
- Consistent naming to reduce input mistakes.
- Relationships that keep balances and positions aligned.
- Ready to grow into reports, exports, and summaries.
Outcome
Instead of guessing balances, traders can see exactly what was funded, withdrawn, or traded—and reconcile accounts with confidence.
Service Tracker
Turning recurring services into data that can be tracked, reviewed, and improved.
The Problem
Repeated events and services were happening regularly, but the information lived in scattered notes: who attended, who served, what changed, and what needed follow-up. Without a tracker, patterns were hard to see and decisions were based on memory instead of data.
The Solution
I built a Service Tracker that lets users log services over time and quickly see what's happening: not just "we had an event", but who was involved, what roles they played, and what needs attention.
- Structured records for each service or event.
- Ability to attach people, roles, and notes to each service.
- Search and filters to find patterns over time.
- Foundation for future insights and reporting.
What I Focused On
The core of the system is clarity: a clean interface, obvious actions, and no unnecessary complexity for people who just want to log what actually happened.
- Simple, guided flows to log each service without confusion.
- Consistent layouts and naming so users don't get lost.
- Careful database structure so data is usable later for insights.
- Room to plug in analytics or exports in future versions.
Outcome
Instead of losing history in chats and paper, services can now be tracked over time - making it easier to see who is active, how often things are happening, and where support is needed.
What I Bring to New Projects
These case studies represent the way I like to build: grounded in real problems, structured in design and data, and flexible enough to evolve. If you need a system that feels custom to your workflow - not just a quick template - I'd be glad to talk about how we can build it.
Start a project conversation