ROI-first AI for operators

Marc Pelberg

I help operators put AI where it pays for itself, cutting cost or growing revenue, and skip the projects that won't.

Marc Pelberg

95%

Enterprise AI projects never show a real ROI.

I'm building the other 5%. The difference isn't the model. It's about putting AI only where it reduces costs or increases revenue, and discarding everything that doesn't.

Built across operating companies

RealArb SkuTrue Zayda Dragon Apparel Midas Holiday Lighting Eli & Associates, Inc. Artex Knitting Mills

The ROI test

If it doesn't reduce costs or increase revenue, it won't get built.

ROI is the gate

Every stage is screened against one question: does it cut cost or grow revenue? Work that passes gets built. Everything else is skipped.

  1. Core business

    The work that drives revenue and margin. That's where AI pays first, by making it sharper.

  2. Secondary work

    The tasks quietly draining cost: cleanup, matching, reconciliation, reporting. Prime targets to automate.

  3. Automation boundary

    Dashboard, quiet background agent, or recommend-only, matched to the risk and the payoff.

  4. Trust before action

    Review, audit trails, and thresholds. Autonomy grows only as the return is proven.

Marc Pelberg paragliding high above a valley

Why this perspective is different

Operator first, builder second, AI only where it earns trust.

I have built and run real operations: international e-commerce, retail automation, and AI-driven product data, not just advised on them. That is why my AI work is not decoration. It closes the gap between a process, a decision, and a result you can trust.

RealArb
Marketplace and arbitrage operating experience across international e-commerce, where small decisions compound into margin.
SkuTrue
AI-driven retail operations and product-listing automation for catalog work that should not stay manual forever.
Risk judgment
Private pilot, EMT, and state/regional paragliding distance record holder across New Jersey, Pennsylvania, New York, Michoacán, and Puebla. I am comfortable deciding where automation is safe and where a human has to stay in the loop.
Consulting & ownership
Owner-level operating context from Midas Holiday Lighting, Eli & Associates, Inc., and Artex Knitting Mills, plus advisory work with e-commerce and retail brands.

What I've built

Systems built to pay for themselves.

01

Automated market scraping

RealArb turns automated scraping into structured product, price, and availability signals, so marketplace opportunities can be reviewed, ranked, and acted on faster.

02

10-marketplace catalog sync

SkuTrue syncs catalog workflows across 10 marketplaces, including Amazon, eBay, Walmart, and Mexico's Sellopublico.mx, normalizing listings, attributes, and channel rules without hand-copying every SKU.

03

Automated ad serving

Ad systems that turn margin, audience, and inventory into controlled spend, with budget guardrails and a review step before spend scales.

04

Self-checking workflows

Workflows that check their own output against real business results and improve over time, so fewer bad decisions get repeated and the rules keep getting better.

How engagements work

How a project actually runs.

01

Audit the work

I map where your team's time and money actually go, and separate revenue work from the repetitive tasks no system owns yet.

02

Build the first system

We start with one high-leverage workflow, with a human in the loop, and ship something real instead of a slide deck.

03

Raise autonomy carefully

The system takes on more only once accuracy, the review trail, and the business outcome prove that it should.

Reach out

Have a workflow that is eating your team's time?

Send me the process, the pain, and what a good outcome looks like. I will help you decide whether it should stay human, become software, or run quietly with the right checks in place.