Portfolio

Selected work across SaaS, commerce, platforms, and developer tooling.

FIG. 07 — SELECTED PROJECTS

Project index

Representative work across domains. Detailed case studies on request.

PRJ-01

§ SAAS

Growica operations platform

CRM, site management, affiliate content workflows, reusable components, and production rollouts for distributed web infrastructure.

PRJ-02

§ COMMERCE

MotoPress booking platform

Booking, scheduling, availability, REST APIs, permissions, integrations, and admin workflows.

PRJ-03

§ PLATFORM

WPForms product engineering

Payments, Stripe, PayPal, form-builder UX, and product architecture at 7M+ active installations.

PRJ-04

§ FINTECH

Flint Group automation

CRM, Laravel modules, queue-driven processing, provisioning, and deployment workflows across approximately 10K websites.

PRJ-05

§ MEDIA

Engineering delivery systems

Code review, automated checks, smoke tests, documentation, and release workflows that make production delivery repeatable.

PRJ-06

§ TOOLING

Cross-technology technical leadership

Architecture and hands-on delivery across backend platforms, interfaces, APIs, integrations, automation, and production operations.

FIG. 08 — FIELD NOTES

Notes from the work

Personal observations from building and maintaining systems at very different scales.

FLINT GROUP

At ~10K websites, adding more people does not solve the operational problem. Infrastructure does. If updates, deployments, content changes, or rollbacks still depend on repetitive manual work, the network scales almost linearly with headcount. The real leverage comes when one controlled action can be rolled out, verified, and reversed across the whole fleet.

PROJECT NOTE — FLINT GROUP · ~10K WEBSITES

WPFORMS

At 7M+ active installations, a small change is never really small. You do not control the PHP version, server stack, WordPress setup, or combination of add-ons running around your code. A fix that removes one known problem can introduce a less predictable regression elsewhere. At that scale, reducing uncertainty matters as much as fixing the bug.

PROJECT NOTE — WPFORMS · 7M+ INSTALLATIONS

MOTOPRESS

Building a smaller product alone taught me a different kind of responsibility. Architecture, payments, security, APIs, integrations, releases, and support all landed in the same place. There was no separate team to hand the problem to — every technical decision had to make sense for the product as a whole.

PROJECT NOTE — MOTOPRESS · PRODUCT OWNERSHIP

FIG. ✕ — ENGAGE

Looking for senior engineering leadership?

Architecture direction, performance engineering, and senior technical ownership for teams that need it. Let’s see if it’s a fit.

Let’s talk →

— EOF