ENGINEER · OPERATOR · BUILDER

From complexity
to execution.

I build and operate systems where product, infrastructure and economics meet. Some of that work is public. Some of it isn’t.

The pattern has held across two decades of software, product, infrastructure and company-building: the interesting problems usually live between disciplines.

How I work
OPERATING PATTERN

Find what matters. Move it.

Useful work rarely stays inside one discipline. Start with the real constraint.

I start with what is actually limiting the product, system or business. Then I connect the pieces around that problem — product, software, infrastructure and automation — and stay close enough to see whether the outcome actually moved.

01

Find the constraint

Before adding technology, find what is actually limiting the product, system or business.

02

Build the system

Connect product, software, infrastructure and automation around the problem — not the org chart.

03

Stay close to the outcome

Ship. Measure. Adjust. Elegance matters; leverage, adoption and economics tell you if it worked.

SELECTED PROOF

Range is useful
when it compounds.

The strongest proof is work that crossed boundaries and still moved something measurable.

At Terapeak, experimentation, engineering, data and revenue converged around outcomes. AI prototypes had to prove ROI. Retention work had to move churn. Product decisions had to move ARPU.

That same operating instinct carries into mobility, financial technology and software platforms: architecture, reliability, cost, automation and product direction belong in the same frame when the outcome depends on all of them.

SYSTEMS · SCALE · JUDGMENT

Scale changes the stakes, not the question.

MOBILITY · FINTECH

At scale, engineering decisions become operating decisions: reliability, cost, workflow and product direction move together.

AI · SOFTWARE · PRODUCT

I still build because proximity matters. New capability is only useful when it survives a real constraint, a real user and real economics.

BREADTH OF WORK

Different industries.
The pattern holds.

From marketplaces to mortgage lending, risk software, ERP, mobility and digital products, the environment changed. The instinct stayed the same: understand the system, find the friction, make the decision better, and build for real use.

MARKETPLACES · MOBILITY

Make complex markets legible enough to act on.

Terapeak and eBay meant marketplace intelligence at scale. Peer-to-peer car sharing meant a live transaction platform with vehicles, owners, renters, trust and operations in the loop. Different surfaces; both demanded clarity, reliability and useful decisions.

LENDING · RISK · ENTERPRISE

When the system carries risk, details become leverage.

Digital mortgage lending, risk-management software at Dyadem and ERP work at IHS put workflow, integration, decisioning and reliability under real pressure. The cost of friction — and of getting the system wrong — was visible.

DIGITAL PRODUCTS · INDEPENDENT BUILDING

Keep building long enough and the medium changes.

Agency work at JaTech and Asskickin Solutions, plus my own design firm, began with web and digital work. That grew into software, platforms and product. Alongside company roles, I’ve kept building independent products and experiments across other industries.

A WORKING PRINCIPLE

“The interesting problems usually live between disciplines.”

That is why I don’t separate engineering, product and business when the problem itself doesn’t. The system is the thing.

More about how I think

OPEN CHANNEL

Interesting problem?
Start there.

The best conversations usually start with a hard problem, a real constraint, or something ambitious that needs to work. If that’s what you’re building through, I’m interested.