Lead engineer · New York · Taking on 2 new projects this month
Custom AI and software engineering for businesses carrying one specific technical gap. Usually the kind that quietly costs somebody a day every week.
$1,000
To start, scoped and fixed
1–2 weeks
To first delivery
Your risk
If it doesn’t land, you keep the work
01 · What I do all day
I’m the lead engineer at a growth-stage e-commerce platform in NYC, where I’ve spent the past several years building the real-time payments, data, and fulfillment infrastructure the business runs on. Outside of that, I take on a small number of projects each month for businesses who could use the same kind of help, scoped to fit.
02 · What I build
I
Orders in one place, inventory in another, fulfillment in a third, and someone reconciling all of it every morning. I connect them up and write the reconciliation logic down, so it lives in the system rather than in somebody’s head.
II
Document intake, claims triage, classification, extraction. Usually that means a model sitting in the step someone does by hand today, with the awkward cases handled, rather than a chatbot on the homepage.
III
Most businesses have one: the file that only one person fully understands. Rebuilt as real software, with permissions and history, so the whole thing no longer rests on one person’s memory.
03 · Where I already know the terrain
Perishable distribution
I spent time inside perishable food distribution at True World Group before moving into engineering leadership. So I know what reconciling orders before the truck loads actually looks like, and what aging inventory costs when nothing flags it.
Health share ministries
From my time in the health share space at Healthshare Works: member intake, needs-sharing requests and claims processing carry a real operational load, and a lot of it is solvable with engineering rather than more hiring.
The pattern shows up anywhere a business runs on disconnected systems and manual review — not just these two. If that sounds like where you are, it’s worth a conversation regardless of industry.
04 · How the work usually goes
01
I usually come in with something specific I noticed about how your systems fit together. Fifteen minutes is normally enough to tell whether it’s worth pursuing.
02
One gap, one deliverable, a scope we agree on before I start. You know exactly what you get, and it’s usually delivered in one to two weeks.
03
Production code, documented and running in your environment, in a state your team can pick up and keep going with.
04
If it worked, there’s usually a larger system worth building. If it didn’t, you walk away having lost very little.
05 · Where we start
$1,000
Projects start at $1,000 for that first tightly scoped piece of work, usually delivered within one to two weeks. Enough for both of us to see how we work together before talking about anything larger.
If it doesn’t work out, you still own everything built, and neither of us spent much finding out. It’s a real project, not a trial run — the easiest way to find out whether the bigger system is worth building together.