Selected work

Practical systems, described plainly.

These are the kinds of production problems I have worked on: billing state, sensitive payment data, multi-tenant product surfaces, APIs, and the engineering decisions around them.

Start a Project View GitHub

Usage-based billing system
B2B SaaS · Stripe · React · Node.js · PostgreSQL · AWS

B2B SaaS / billing infrastructure

Move billing beyond manual monthly work.

A SaaS team needed a more structured path for usage-based billing without creating a new set of support and finance problems.

Problem

Manual billing made customer operations slower and limited pricing flexibility.

Approach

Implemented metering, subscription states, webhooks, portal flows, and billing state handling.

Engineering outcome

A clearer billing foundation that the product and operations team could reason about.

Stripe metered billingWebhooksReactNode.js

PCI-aware payment vault
Healthcare SaaS · VGS · Laravel · REST API · AWS

Healthcare SaaS / payment compliance

Keep sensitive payment data in the right boundary.

A healthcare SaaS platform needed payment collection without increasing the raw card data handled by its own application.

Problem

Existing payment flows exposed more compliance and maintenance risk than the team wanted.

Approach

Added VGS tokenization, Laravel API updates, and a clearer boundary around sensitive values.

Engineering outcome

PCI-aware payment handling with less raw-card exposure inside the product flow.

VGSTokenizationLaravelREST API

Multi-tenant dashboard & API
SaaS product · Vue.js · Laravel · RBAC · Bitbucket

Agency delivery / SaaS product build

Build the product surface an existing team can own.

An agency needed senior overflow help on a SaaS build with tenant workflows, permissions, and delivery pressure.

Problem

Tenant workflows, roles, and delivery speed had to stay aligned.

Approach

Built dashboard flows, RBAC, tenant-aware APIs, and practical implementation documentation.

Engineering outcome

A cleaner product surface with a handoff path that reduced future rework.

Multi-tenant SaaSVue.jsLaravelRBAC

ThreatIP product engineering
Production B2B SaaS · AI-assisted decisioning · APIs · billing

Founder / product proof

Operate the full loop, not only an isolated ticket.

ThreatIP is a live B2B SaaS product I built and operate across product experience, multi-tenant architecture, AI-assisted decisioning, CRM integrations, billing, dashboards, APIs, and infrastructure.

What it proves

Experience making product, engineering, operations, and customer context work together.

Working style

Founder/product ownership keeps maintainability, onboarding, support, and handoff visible.

More context

Visit ThreatIP.io ↗

Proof, not theatre

Specific enough for a technical conversation.

I can walk through the tradeoffs, what was owned, and what the next engineer needs to know. The point is not a logo wall; it is confidence in how the work gets done.

Verified review5.0 Upwork client rating and feedback on PHP, Docker, GitHub, and workflow fit.

Public presenceGitHub ↗ · LinkedIn ↗

FocusSaaS, AI systems, integrations, payment workflows, and product delivery.

EngagementDirect communication, visible progress, and maintainable handoff.

Your system next

Bring a problem that crosses layers.

Tell me what is at stake, which systems are involved, and where the current implementation is getting in the way.

Start a Project