Automation · AI integration · Custom software
Twenty-four years in sales and operations taught me where businesses bleed hours and money. I build the software that stops it — CRMs, billing, lead pipelines, AI workflows, internal tools. Because I've lived the work, what I build gets used instead of worked around.
About
Rep on the phones, sales manager, operations manager with a P&L, then data and product analyst. There isn't a part of a revenue system I haven't sat on the wrong side of.
I don't hand-write most of what I ship — I direct AI coding agents, review everything, and own every architectural decision. What you're paying for is judgment: knowing what to build, seeing where it will break before it does, and insisting on the unglamorous parts — accurate billing, locked-down data, records you can audit — before anyone asks.
Industry depth
Where this usually starts
They call because something is costing them money and they can't quite see where. These come up the most, across very different businesses.
You bought a CRM and your team still runs the real work somewhere else.
Two people type the same information into two different systems.
Customers email you for things they should be able to look up themselves.
A new hire waits a week for access, and someone who left last quarter still has a login.
Work stops because something is sitting in an inbox waiting for a yes.
The number you need Monday morning takes someone all of Friday to pull.
You hear about the problem from your customer first.
A payment fails and nobody notices until the customer is gone.
A lead comes in at six o'clock and nobody calls it until Thursday.
The process that matters most lives in one person's head, and nobody else can run it.
If one of those is yours, that's the conversation. It's usually a smaller fix than you'd expect — and if it isn't, I'll tell you that instead.
Engagements
Most take two or three days. You leave with a written scope, a fixed build price, and a date, whether or not I build it. This is where I tell you what you didn't think to ask for.
A product that needs to exist, or a new surface on the backend you already run. One agreed price, one date, one person accountable.
LLM and transcription pipelines wired into real systems — background jobs, cost controls, and a UI people actually use.
Stripe subscriptions, self-service billing, failed-payment recovery, affiliate programs — and the admin tooling to run it without calling you.
Iterable campaigns, onboarding tours, and the prompts that move people from signup to first real use — automation that runs itself.
A standing block of hours each month, owning a surface outright.
A dataset in the morning becomes a working interactive visualization by end of day. Fixed price, no meeting, yours to keep.
Not on this list? Ask anyway. Revenue systems are where I'm deepest, but I build custom software generally — internal tools, portals, integrations, a CRM for a business that has outgrown spreadsheets.
Capabilities
Whole products, start to finish.
Getting the money in, and stopping the leaks.
The work nobody should still be doing by hand.
The unglamorous parts that decide whether it still works in a year.
Evidence
These are the largest builds — the revenue generators — alongside a steady run of smaller automations and internal fixes that quietly delete a manual workday. Everything here is complete and working: the platform runs in production; the other two products I finished and chose not to take to market when my focus changed.
A complete platform — custom CRM, self-service billing, two-sided marketplace, affiliate program, partner API, escrow product, 20 lifecycle journeys — rebuilt solo in four weeks with agentic coding. In production today.
The build story →Transcribes sales calls and scores them against real sales methodologies — recurring objections become scripts, managers get a weekly digest.
The build story →Court-ready state filing packets from a guided interview — engineered so a broken form cannot ship.
The build story →Not one product — a running category. Heat maps built same-day. Static data ships in days; dynamic in one to two weeks. Enrichment pipelines feed several of them.
The build story →Word of mouth
“Jon helped me build a feature that an enterprise customer was asking for. I thought it was a cool idea but didn’t know how to actually deliver this service. Jon executed flawlessly in a matter of hours — and my customer was so impressed with me.”
Not my scope
Contact
Six quick fields, no call booking, no qualification maze. I read every submission myself and I'll tell you straight away whether I'm the right person for it.
Got it. Your note is in my inbox — I'll come back to you at the email you gave me.
Availability. I take one build at a time, and I'm taking the next one now. Based in the United States, working remote.
Existing client? Your quotes and invoices live in the client portal.