Work
Billing & payments, end-to-end
I’ve spent my career on the part of software where mistakes cost money: metering, invoicing, checkout, and subscriptions. Here’s a sample, weighted toward the billing work I do most.
Flagship billing products
BillingLogix→
Billing & invoicing SaaS I built end-to-end as the founding engineer — automated billing cycles, invoicing, subscription management, and multi-tenant architecture on a custom merchant-gateway platform with Stripe support. Live in production with paying customers and real financial transactions.
- Custom merchant gateway
- Stripe
- TypeScript
- Node.js
- AWS
Meshes→
Multi-tenant SaaS on a production Stripe integration, built end-to-end — checkout, subscriptions, and metered billing across several different resource types, on an event-driven backend that keeps billing state in sync.
- Stripe
- Go
- Next.js
- TypeScript
- Serverless
Payments & billing track record
Custom billing infrastructure
Automated billing cycles, precise invoicing, and deliverable tracking for membership and subscription platforms.
- Stripe
- Java
- Go
- Node.js
- TypeScript
Multi-tenant SaaS billing
Multi-tenant platforms where each tenant configures its own billing — plan levels, meters, and pricing setups — with metered pricing options and multiple gateways supported, Stripe included.
- Stripe
- Multi-gateway
- Metered billing
- Multi-tenant
Webinar & meeting platforms
A live webinar and meeting platform billed with metered pricing — charging on attendees and the number of registrants per event.
- Stripe
- Metered billing
- WebRTC
- Java
- Node.js
Multi-processor checkout systems
Checkout integrated with Stripe, Braintree, PayPal, and Venmo, plus revenue features: upsells, downsells, cross-sells, and order bumps.
- Stripe
- Braintree
- PayPal
Enterprise API integrations
Serverless APIs (AWS Lambda, API Gateway, DynamoDB, Kafka) and containerized workloads orchestrated with Kubernetes (GKE on Google Cloud and on AWS) and HashiCorp Nomad — plus Zapier / Make integrations connecting billing and CRM systems.
- Kubernetes
- Nomad
- GKE
- AWS Lambda
- Kafka
Infrastructure as code
Every system I build is defined entirely in code — Terraform, AWS CloudFormation, and the like — so billing infrastructure is reproducible, auditable, and never clicked together by hand.
- Terraform
- CloudFormation
- AWS
- GCP
Other work
A broader range of products I’ve shipped — and billing ran through these too, from subscriptions and credits to token-based usage:
Page & funnel builders
Multi-tenant drag-and-drop builders where users buy access to templates and features — entitlements granted through billing.
AI assistants
AI assistants billed by token usage — used to generate full websites, courses, and other content.
Learning management systems
Multi-tenant learning platforms where courses sell as part of membership subscriptions, as one-off purchases, or with credits — access granted through billing.
Want billing that works like this on your Stripe?
Start with a paid Billing Teardown — a concrete plan and a fixed-price quote.