Revenue Systems Architect · the math behind the decision

I'm the bridge between the people who sell and the people who build.

I sit between sales and engineering and speak both, which means I can't be snowed by either. I read where a business is quietly losing revenue, decide what actually needs to happen, and tell the decision-maker plainly: build this, fix this, kill that. I can build it myself if I have to. I'd rather define exactly what gets built and why.

Drop me into a business and I won't touch anything for a while. I watch how it actually runs, in the owner's chair, in sales, in operations, in the codebase, because the leak is rarely where the org assumes it is. I learn the vertical cold and earn the read before I make a single assertion. Then I start asking questions, quietly, to test how close I am to the reality. When I'm right, I move. When I'm wrong, I reverse fast and say so. Twenty years of this, across commerce, trading, events, and security.

01What I do

Three things, mostly.

Make the product instantly clear to the right buyer.

Most products are explained in the language of the people who built them, not the people who buy them. I find the buyer the product is failing to reach, define what it does so they get it in one second, and, if it does several things, split the positioning into the right number of use cases so each buyer sees their own problem, not a generic pitch.

Find the money already in the business.

There are almost always revenue streams sitting untapped that wouldn't take much to turn on: a sponsorship slot, a new category of buyer the product already serves, a price the math supports but nobody set. I find them before anyone spends a dollar building something new.

Be in the room when the real decisions get made.

Which product to back, which to kill, which build is quality and which is garbage dressed up to look finished. I get to the root of the problem before any major move, because the expensive mistakes are the ones made fast and confidently in the wrong direction.

02The work

The same move, four verticals.

20+

Years operating

commerce · trading · events · security · decision systems

$1B/mo

FX volume supported

1→3 products · ~30 broker-dealers · 16 countries

4–5×

Signup benchmark beaten

Black Hat / CISO Network · ~1,400 registrations

1997

Own mail & web servers since

bare-metal, run continuously

PEO financial decision engineCurrent flagship

A neutral computation layer that certifies the tax-and-premium math behind a PEO decision, from code, serving owners, their CPAs, and brokers from one source everyone can trust. The thesis at its sharpest: take a decision everyone argues over and make the math defensible from the ground up.

FX trading product14 years

Took one retail algorithm and rebuilt it as an institutional product line. One product became three, sold through roughly thirty broker-dealers, supporting about $1B per month in volume across sixteen countries.

Trusted Move: interstate-moving voice AI

A turnkey system that catches every inbound lead and calls it back in under thirty seconds, runs a ten-point interview, books the in-home estimate, and syncs to the CRM. Built as a quiet sidecar: n8n watches the feeds, Vapi and Twilio place the call, with zero change to existing systems. Reach the lead before any competitor dials.

Black Hat / CISO Network events

Rebuilt event registration and a two-way SMS-and-email engagement engine. A target of a few hundred became roughly 1,400 signups, four to five times the prior benchmark.

Different industries, identical shape. That's not range for its own sake. It's the same diagnosis-then-build, proven it travels.

03Own vs rent

I own what I depend on. I rent what's meant to be swapped. Knowing which is which is the whole job.

Own & operate

Bare-metal cluster
GPU inference workstation
Self-hosted database, automation, and orchestration
My own mail and web serverssince 1997

Rent & use

Automationn8n, Make
Voice & messagingVapi, Twilio
Web & formsWordPress, Elementor, ACF, Gravity Forms
Data & analyticsBaserow, SQL, Matomo
InfrastructureCloudflare
LanguagesPython, PHP, JavaScript
AIAnthropic Claude (orchestration via API and SSH), local Ollama

The split is the point: what I depend on, I control, so the speed and stability a client relies on isn't rented out from under them.