About
I improve systems. Frontend is how I start — ownership is how I finish.
I'm Lord Kelvin Abellana — frontend developer, automation builder, and former product owner. I work best where interfaces meet real operations: SaaS products with messy workflows, startups where decisions move fast, and systems where removing manual work creates actual value.
At Alphaus I grew from Junior Frontend Developer to Lead to Product Owner across cloud cost management products. That progression taught me to think beyond code — into delivery ownership, product decisions, and the kind of internal tooling that quietly makes a team faster. The Slack-to-ClickUp reporting system I built became the company standard. Stepping into UI/UX design when our designer was blocked kept delivery moving. These weren't assigned responsibilities — they were gaps worth filling.
I care less about impressive implementations and more about systems that reduce friction and actually get used.
Career in three chapters
Jul 2023 – Dec 2025
From engineer to product owner
At Alphaus I progressed from Junior Frontend Developer to Lead to Product Owner in under two years. As Lead I owned frontend quality, release coordination, and PR standards for Octo. As Product Owner I ran sprint planning, backlog refinement, and UI/UX design for Ripple and four connected products — stepping into design ownership when delivery depended on it.
Oct 2025 – Apr 2026
Startup and full-stack work
At Ardexa I was the only frontend developer alongside two founders and one backend developer, building MVPs from scratch. I worked across frontend, backend, product decisions, and architecture planning — often in the same week. Products included RentWise (rental qualification with scoring logic), LexaDraft (contract template builder), and TicketDesk (centralized support triage).
2023 – Present
Automation and systems
I've built automation systems that remove real manual overhead — a Slack-to-ClickUp bug reporting workflow that became the company standard at Alphaus, an AI-powered weekly coaching delivery system with approval flows, and a job-matching pipeline with LLM scoring and smart email notifications. The goal is always the same: reduce the repetitive work.
What I care about
Systems over features
Good software improves how something works, not just how it looks. I try to understand the workflow before touching the interface.
Ownership over handoffs
When delivery was blocked at Alphaus, I stepped into UI/UX design. When bug reporting was frustrating the team, I built the automation. The missing role is worth filling.
Practical over clever
Maintainable systems built for real workflows are more useful than sophisticated ones that only the original author understands.