Selected work
Most of what we build is private client work: payment rails, marketplace payouts, background-job pipelines, and integration systems that run under someone else's brand. We can't name clients or share code, but we can describe the kind of systems we've owned end-to-end. Below is a representative picture of that work, plus the public plugins we've shipped.
The kinds of systems we build
Payments & payouts
Stripe Connect platforms, split payouts, subscription billing, and reconciliation across payouts, refunds, and disputes. The kind of code where small mistakes are expensive.
Marketplace platforms
Multi-vendor platforms with onboarding flows, seller dashboards, escrow logic, and dispute handling, from schema through deployment.
Background-job infrastructure
High-volume sync pipelines, idempotent queued jobs designed so a double-run is safe, retry logic, and the observability layer around it.
Integrations & data pipelines
Third-party API integrations, webhook ingestion that handles replays and ordering, ETL pipelines, and reporting dashboards over live transactional data.
Public & open-source examples
JetEngine Importer
Open sourceImport into JetEngine fields with WP All Import. Free on WordPress.org.
Advanced JetEngine field support for WP All Import: Repeater, Gallery, Maps, Relations, and CCTs.
Feed Import
Open sourceImports from CSV, XML, and JSON feeds into EmDash collections, by hand or on a schedule, with field mapping, matching that creates or updates entries, and a log of every run.
Free features
Export & Feeds
Open sourceScheduled CSV and JSON exports of your collections, plus Google Merchant, RSS, Atom, and JSON feeds served from your own site.
Free features
File Import
Open sourceImports CSV, JSON, NDJSON, and XML files into EmDash collections, pasted or linked from Google Sheets, Google Drive, GitHub, or Dropbox, with field mapping and a log of every run.
Free features
Sheets Sync
Open sourceSync EmDash collections with Google Sheets, Airtable, or Notion, so the people who live in a spreadsheet can keep working there.
Free features
Editorial Workflow
Open sourceApproval before publishing, an editorial calendar, and scheduled unpublishing for content that expires.
Free features
Content Backups
Open sourceScheduled snapshots of your entries and media to an R2 or S3-compatible bucket you own.
Free features
Bulk Editor
Open sourceFilter entries in a grid, select the ones you want, and apply one change to all of them: set a field, find and replace text, publish, or unpublish.
Free features
Have a system like this?
If you're building something in payments, marketplace infrastructure, or background-job reliability and need a senior engineer to own it end-to-end, let's talk.
Start a conversation