Burnzoft
View Systems
Software systems in production

Practical tools for real operational work

Burnzoft is a small showcase of systems I've built and run for real teams — from tracking QA hours to planning workforce leave. Each one replaces a spreadsheet or a manual process with something faster, clearer, and easier to trust.

Explore the systems Get in touch
2 systems live today Built & maintained end-to-end Designed for daily real-world use

Burnzoft builds systems from scratch.

Advertisement
What I've built

Two systems, built to solve real problems

Each card below is a live, working system — not a concept. Click through to see it in action.

QA & Time Tracking

QATool

A web-based time-tracking and reporting system for QA and development teams. It replaces manual timesheets with structured, filterable logs of billable and non-billable work across every project.

  1. Log timeTeam members record daily hours against tasks and projects, tagging billable vs. non-billable work.
  2. Filter & reviewLeads filter entries by date range, project, or role to review what was logged and catch gaps early.
  3. Report instantlyGrouped, exportable reports are generated on demand for billing, payroll, and productivity reviews.
Visit QATool
Workforce & Leave Planning

VPlot

A visual leave-planning platform for HR teams. Vacation and sick leave requests are plotted on a shared calendar board, organized by company, so approvals and headcount gaps are visible at a glance.

  1. Request leaveEmployees submit vacation or sick leave requests through a simple form.
  2. Plot & visualizeRequests appear instantly on a shared visual board, grouped by company and date.
  3. Approve & trackHR admins manage companies, approve or decline requests, and track balances from one dashboard.
Visit VPlot
Reporting, visualized

What comes out the other end

Both systems turn raw entries into a clear, at-a-glance report. Here's the shape of that output — illustrative sample data, not a live feed.

QATool

Hours logged by project

  • Client Onboarding 46h
  • Platform QA 38h
  • Payroll Integration 31h
  • Recruiting Portal 24h
  • Internal Tooling 15h

Illustrative sample data

VPlot

Leave days approved by month

  • February 18d
  • March 22d
  • April 27d
  • May 24d
  • June 33d
  • July 39d

Illustrative sample data

Try it yourself

Compare two blocks of code

Paste code on both sides and see exactly what changed — added, removed, and edited lines highlighted line-by-line and word-by-word. Runs entirely in your browser; nothing is uploaded.

Why it works

Built the same way, every time

Both systems share the same underlying approach to getting real work done.

Built for daily reliability

These aren't demos — they run in production, every day, for real teams who depend on them.

Fast, focused workflows

Every screen is built around one task done well — logging time, plotting leave — not a bloated feature list.

Designed for real teams

Shaped directly by feedback from the people using them daily, not by guessing what teams might need.

Clients

Built for real businesses

A look at who I've worked with.

Accounting & Business Advisory

PELLAS Associates & Co.

A Philippine CPA firm helping local and foreign businesses register, operate, and scale in the Philippines — offering accounting, tax strategy, bookkeeping, payroll processing, and cloud-based financial systems so clients get real-time visibility into their numbers.

Visit alpellas.com
Advertisement

Have a similar problem to solve?

If you're dealing with messy timesheets, manual leave tracking, or another process that deserves a proper system, I'd be glad to talk it through.

Email info@burnzoft.com