ENTERPRISE SYSTEMS · CLEAN-ROOM PORTFOLIO

I build operational software that connects the work people actually do.

Full-stack applications across ERP-adjacent workflows, CRM, HCM, approvals, multi-tenant SaaS and business automation — from data contracts and security boundaries to production-ready user experiences.

Confidentiality-safe: employer systems are represented by original recreations with synthetic data. No corporate source code or production data is published.
system-map.ts
const platform = {
  frontend: ["React", "TypeScript"],
  data: ["Postgres", "RLS"],
  domains: [
    "inventory",
    "sales",
    "finance",
    "people",
    "approvals"
  ],
  principle: "secure by default"
}
SELECTED WORK

Systems designed around real operational problems

These portfolio builds reproduce the workflows and architecture patterns behind private enterprise work without exposing employer IP.

ENTERPRISE RECREATION02

Enterprise Approval Hub

Clean-room recreation of a procurement and approval workspace: requests, line items, historical purchasing context, approvals and ERP integration boundaries.

  • Next.js patterns
  • SQL
  • Approvals
  • Audit
Request→Review→Approval→ERP
PR-1048Industrial filtersPending
PR-1047Electrical suppliesApproved
PR-1046Safety equipmentApproved
ENTERPRISE RECREATION03

Modular Business OS

Interactive clean-room recreation for internal operations spanning HCM, attendance, recruiting, support workflows and organizational access controls.

  • HCM
  • Workflow
  • RBAC
  • Multi-company
PeopleRecruitingAttendanceTicketsRolesAudit
ENTERPRISE RECREATION04

CRM Intelligence Workspace

Interactive customer operations recreation covering lead intake, qualification, pipeline, tasks, account context and management reporting.

  • CRM
  • Pipeline
  • Analytics
  • Automation
NewAcme NorthPacific Retail
QualifiedMetro SupplyNova Services
ProposalCentral Foods
HOW I BUILD

Architecture before features

My strongest work is the layer between “a nice screen” and “a system people can safely operate.”

01

Domain contracts

Model organizations, roles, records, states and workflow transitions before wiring screens.

02

Tenant security

Organization boundaries, RLS/RBAC, audit trails and trusted mutation paths.

03

Operational UX

Interfaces that create, update, approve and reconcile work — not dashboards that stop at display.

04

Integration boundaries

ERP/service APIs treated as explicit systems of record with retry, validation and failure semantics.

05

Deterministic automation

Rules and validation own high-impact actions; AI assists where language/context add value.

06

Release discipline

CI gates, regression tests, staged migrations and rollback-aware deployment.

TOOLBOX

Technologies I work with

FrontendReact · TypeScript · Next.js · Vite · responsive UI
Backend & DataNode.js · PostgreSQL · SQL · Supabase · REST/RPC patterns
EnterpriseSAP B1 integration patterns · approval workflows · ERP/CRM/HCM
Cloud & OpsCloudflare · GitHub Actions · IIS/PM2 · environment hardening
AutomationBusiness rules · event-driven workflows · API orchestration
AI SystemsAgent architecture · tool boundaries · human-in-the-loop controls
AVAILABLE FOR REMOTE WORK

Need someone who can turn an operational problem into working software?

I can walk through the architecture and implementation decisions behind these builds in a live interview.