Yevgeniy Melnik

Yevgeniy Melnik

I build systems that verify things people otherwise take on faith.

About

I moved to the US with no network and no degree anyone here recognized. I spent twelve years at every layer of freight logistics — driving trucks, brokering loads, running operations, assessing facility security. Somewhere along the way I started trading markets and writing software. Most of what I know came from being inside the problem before I had the language for it.

Ten years of trading taught me pattern recognition — the same discipline I now apply to fraud detection and risk modeling.

In 2025 I founded D74 Technologies. We're building rMIND — the trust intelligence layer for supply chains, the thing that tells defense commands and manufacturers who's actually touching their freight. I build with AI as my engineering team — it's how one person ships production systems.

I also consult on supply chain security through Gold Bird Group — mostly facility assessments and red team engagements across aerospace, pharma, food, and defense.

I shoot with a Sony A7R3 and vintage Soviet lenses — I prefer the character of old glass over clinical sharpness. I have a passion for long-distance running — I've done the Chicago Marathon, the Miami Marathon, and the Chicago Triathlon. Working on getting selected for the New York City Marathon. It's the closest thing I've found to how building a company actually feels.

Currently

How I see the world

A few things I've come to pay attention to, across different industries:

Gaps between what's sold and what's real

Most businesses report upward in ways that obscure the last mile. The person at the dock sees the gap. The person in the C-suite sees the slide. My favorite work happens in the distance between those two.

Risk is a function of who's carrying it

A family managing its own retirement has a different risk posture than a corporation with shareholders, which has a different posture than a government with a constituency. Watching how different actors price, transfer, and deny risk is one of the most useful exercises I've found.

Systems thinking is a kind of empathy for complexity

If you can't draw the ontology — who touches what, who authorizes what, what gets logged and what doesn't — you're guessing. Most compliance theater exists because nobody drew the map.

The last mile teaches everything

I learned more about supply chain security from driving into warehouses than from reading about supply chain security. The places where things actually happen are almost always undermeasured.

Things I've built

2025 — present

D74 Technologies / rMIND

The freight industry loses $15-35 billion a year to fraud and theft, and the organizations with the most at stake — defense commands, manufacturers, shippers — have almost no visibility into who’s actually operating in their logistics network. D74 builds trust intelligence infrastructure for supply chains — outside-in scoring of carriers, brokers, and facilities, continuous risk monitoring, and end-to-end verification that doesn’t depend on self-reports.

d74.io
Side projects
RentCompare

I built this after moving and realizing that every single person I know had rebuilt the same decision framework from scratch — same spreadsheets, same forgotten-to-check items. Renting pretends to be a one-time problem and it isn’t. The tool turns “am I paying the right price?” into a ten-second answer.

rentcompare.app
IsItDue

Most household failures aren’t decision failures. They’re memory failures. “Did we change the filter?” “When did we last pay the HOA?” “Is the car registration due soon?” I built IsItDue because I got tired of rediscovering every expiration date the hard way.

isitdue.com

Ideas I'd like to see built

Things I've thought through but can't personally build right now. I notice gaps compulsively — it's the same pattern recognition that drives D74, just applied to everything else I encounter.

The Framework

Every profitable service business I’ve looked at shares the same pattern: something that’s mandatory, unpleasant, and complex enough that people will pay to outsource it. Taxes, compliance, vehicle inspections, estate planning — the formula is always the same. If it’s required by law, hated by the person responsible, and easy to get wrong, someone is already making money doing it for them. Whenever I hear about a regulation getting more complex, I don’t see a burden. I see the next business.

Personal Purchase Analytics

I pulled my Amazon order history to check my coffee buying pattern. Seventeen bags over 165 days. One bag every eleven days, but I was buying one-off instead of subscribing. Subscribe & Save would have saved me $82 a year on coffee alone — and Amazon never told me, because their incentive is for me to forget and pay full price. Businesses have sophisticated inventory and reorder systems. Consumers are flying blind on their own household supply chain. Someone should build the personal procurement layer — your purchase history, your consumption patterns, your reorder timing, your cross-retailer view. Not what the retailer wants you to buy. What you actually need and when.

School Photography

My kids’ school photos cost $50 per package and the quality is terrible. The photographer shows up once, herds 400 kids through a backdrop in 3 hours, and the parents get stiff poses with bad lighting. The obvious startup move is to build a better platform — AI sorting, digital delivery, face matching. But that’s the wrong problem. The real problem is operational: the photographer is incentivized to maximize throughput, not quality. Fix the ops — better lighting rigs, more time per kid, a second pass for retakes — and you win without building a platform. The technology already exists. The execution is what’s broken.

Address Update Helper

Every time someone moves, they spend weeks tracking down every service, subscription, bank, insurance company, and government agency that has their old address. There’s no master list. Every person rebuilds the same checklist from scratch and still misses half of it. Your email already knows every company you’ve ever interacted with — the confirmation emails, the shipping notifications, the account alerts. A tool that scans your email headers, identifies every entity that has your address, and generates your personalized “who to notify” list would turn a month-long anxiety project into a ten-minute task. The fact that nobody has built this well says more about the difficulty of email parsing than about the value of the solution.

Regulated Inefficiency Plays

In every regulated industry, complexity creates information asymmetry. Whoever bridges that gap takes a cut of enormous transaction volumes. Medical bill negotiation: hospitals charge opaque prices, patients don’t know how to push back, a negotiator saves 50-80% and takes a percentage. Property tax appeals: data shows the assessed value is wrong, you file on contingency, win rate is over 60%. Government IT staffing: match cleared professionals to agencies, mark up 40-60%. The pattern is always the same — mandatory spend, confused buyer, knowledgeable intermediary. Software makes the intermediary faster, but the judgment call is what the client pays for. These aren’t sexy. They’re durable.

Local Business Job Discovery

Job boards are designed for companies that pay to post listings. Most local businesses — the restaurant, the auto shop, the warehouse down the street — don’t post anywhere. They put a sign in the window. If you’re looking for work in your neighborhood, there’s no way to see what’s available without physically driving around. A tool that maps local businesses and shows which ones are hiring would bypass the entire application-tracking-system problem. The people who need local work the most — hourly workers, parents with commute constraints, people re-entering the workforce — are the ones most underserved by the current job search infrastructure.

If you decide to build any of these, let me know — I'd love to see it live. Happy to talk through the details or give feedback if it's useful.

Field Notes

Observations from the work. I add one when it survives sixty days of cooling.