Client work

Things I have built
for other people's businesses.

A few of the engagements I can talk about, going back a good many years, plus the products I build and run myself. Where a client is named, they agreed to it or the work was public. Where one is not, that is deliberate: what I see in a business stays in that business.

Integration · ERP · data pipeline
Fastbolt, now part of AFC Industries Fastener distributor and federal contractor · South Hackensack, NJ

An ERP connector that turned a week of reconciliation into a minute of input.

The problem
Fastbolt received CSV files that were really several reports stacked in one file, with section boundaries nobody marked and dates in European format in some sections and American in others, depending on which country the section came from. Getting them into their Microsoft ERP took a week of manual work every cycle.
What I built
A parser that reads the file line by line, finds the section boundaries, corrects the date format per section, stages the clean data, merges the records and pushes the result into SQL Server for the ERP to consume.
What it did
A week of manual work became about a minute of input and ten minutes of waiting. After Fastbolt was acquired, the new owners assumed they would not need the tool. They called me back for a change request because it still outperformed what they had replaced it with.
Microsoft SQL Server · Microsoft ERP · Access · Excel · multi-section CSV
Custom functions · modelling · localisation
Zvi Weis Independent futures trader

Custom functions for modelling futures trades, delivered in Hebrew.

The problem
A trader with his own way of modelling futures positions, and no off-the-shelf tool that calculated things his way. He also needed to work in Hebrew.
What I built
A set of custom modelling functions built to his specification, with the interface and documentation translated into Hebrew so the tool matched how he actually worked.
What it did
His model, his language, his numbers, checkable against his own expectations rather than a vendor's assumptions.
Custom calculation functions · Hebrew interface and documentation
Excel · live market data · rules engine
Name withheld Private bettor in horse-racing markets

A live odds feed in Excel that flagged mispriced bets by the client's own rules.

The problem
He bet horse racing seriously and had his own view of what a fair price was. The odds moved live and faster than anyone could scan a card by hand, and the price he wanted was gone by the time he found it. He wanted the market screened against his criteria the moment it changed, inside the tool he already lived in: Excel.
What I built
An Excel application that pulled real-time racing odds, kept them refreshing, and ran every runner through his pricing rules as the market moved, highlighting prices that fell outside his bands so he could act or pass. His criteria were parameters, not hard-coded, so he could tune them himself.
What it did
He stopped scanning and started choosing. The method stayed his; the tool applied it faster than the board changed. Which bets he took, and how they ran, stays with him.
Excel · live odds feed · client-defined pricing rules
Secure workflow · order processing
Name withheld for confidentiality Order processing, operated offshore

A secure order-processing system for an offshore operation.

The problem
Orders had to be taken and processed by a team working outside the United States, with customer and payment details protected and every step of the process controlled and recorded.
What I built
A locked-down web application for order intake and processing, built so each person saw only the step they worked and every action was recorded.
What it did
The operation ran at distance without the data leaving the process. The client's name, industry and the particulars stay with me, which is the point.
Secure web application · controlled access · full activity record
Compliance · signatures · records
Bright Horizon Institute Vocational school · Jersey City, NJ

A web-based student sign-in sheet that captures handwritten times and signatures for state compliance.

The problem
The state requires a signed, written attendance sheet per student, with start, lunch and end times. The school wanted to stop keeping paper without giving the regulator anything to object to.
What I built
A tablet-friendly sign-in sheet where students and staff sign by hand with a finger or a mouse, the system stamps dates and times, and the output reproduces the paper form the state expects, ready for an auditor to compare against billed hours.
What it did
No training for the student, a complete record for the school, and a sheet the inspector already recognises.
Laravel · PostgreSQL · signature capture · PDF output
Workflow · email intake · LMS · QuickBooks
Sunsoft Services IT services and staffing · Jersey City, NJ

Emailed contractor timesheets checked against the LMS and turned into QuickBooks invoices, without retyping.

The problem
A staffing business bills its clients for contractor hours. The hours arrived as emailed timesheets, in whatever form each contractor used, and somebody had to open every one, total it and key it into QuickBooks before an invoice could go out. Billing ran late, every retype was a chance to bill wrong, and nobody was checking the hours claimed against the hours the learning management system said were delivered.
What I built
A workflow that watches the mailbox, pulls each timesheet off the email, reads the hours by contractor and client, matches them against the placement's rate and period and against the sessions recorded in the LMS, and creates the invoice in QuickBooks. Anything that does not reconcile lands in a short review queue instead of on an invoice.
What it did
Invoices go out when the hours come in, the numbers match both the timesheet and the LMS, and nobody retypes anything.
Email intake · LMS integration · QuickBooks · validation and review queue
Access to web · CRM · QuickBooks · Google Maps · Calendar
Arithmetickles Live math game show touring schools in New Jersey and beyond, still on the road in 2026

A very large Access application rebuilt as a web app, with a CRM and a query builder its staff could use themselves.

The problem
A touring school show is a logistics business: thousands of schools to market to, bookings to confirm, a calendar of performances to route around the state, and every show to invoice. All of it lived inside one huge Microsoft Access application that only worked from the office, talked to nothing else, and needed an Access expert every time somebody wanted a mailing list.
What I built
A complete conversion to MySQL and PHP, delivered as a multi-user web application. Email integration for outreach and confirmations, Google Maps for school addresses and routing, Google Calendar for the performance schedule, and QuickBooks integration for billing. The new product added CRM functions and a point-and-click query builder so non-technical staff could build their own mailing lists from any combination of criteria.
What it did
The business kept running on its own data, now reachable from the road, connected to accounting, and no longer dependent on one person to pull a list. The show is still booking schools today.
PHP · MySQL · Google Maps · Google Calendar · QuickBooks · email
My own properties

The software I build and run for myself.

These are not demos. They take payments, sign people in, send email, run AI agents and serve real users every day, on the same stack and the same operations layer I bring to client work. Each one is proof of a particular kind of job.

This site, too. moduspromethean.com is a Laravel application with Stripe checkout and subscription schedules for the bootcamp, Zoom scheduling, Google sign-in for students, a signed-URL student portal with hand-drawn class sign-in, inbound email that becomes records, a certificate-gated operations console, and an AI content pipeline behind the news page. If you want to see how I build, you are looking at it.
JP Howlett in a hood, index finger raised to his lips
Confidentiality

What I see and hear in your business stays in your business.

  • Your books, your margins, your customer list, your mess. None of it leaves the room, from the first call on, whether or not you hire me.
  • I do not name a client or describe their project without permission. Some of the work on this site says "name withheld" for exactly that reason.
  • Your credentials never pass through an AI model, and your data never trains one.
  • When we are done, I hand back every account and credential in your name and keep nothing I do not need to support you.

Want it in writing? Send me your NDA or use mine, signed before we talk specifics. It is in the terms too, section 6.

Have something like one of these?

Every one of them started with a conversation about how the business actually ran.

Call or text 973-944-0574 Free 20-min call