# Marcus Delgado, Head of Payment Operations at Trellpay — read of Fintech Risk Monitor, June 12 2026

> 9 years in payments, currently managing processor relationships across 6 acquiring banks, 2 payment facilitators, and one deeply regrettable ISO partnership.

## How I got here

A guy I worked with at Stripe forwarded this in our group chat with the message "lol or maybe not lol." I clicked it during my train ride in from Montclair. I've been burned by "dependency risk" promises before (we paid $40K/yr for a GRC tool that was basically a fancier way to store PDFs). So I was already in "prove it" mode before the page loaded.

## What I clicked first

"Third-party risk that doesn't disappear in a spreadsheet." That got me. That phrase is doing real work because it names exactly what I have right now: a 200-row Google Sheet my team calls The Monster. If a processor goes down, I am literally color-coding cells to figure out which merchants are affected. So the problem statement is accurate.

I wanted to see the product immediately. I scrolled fast looking for a screenshot, a demo, a GIF of a dashboard. Nothing.

## Where I paused

The scoring box. Hard stop. "66/100 Adoptability. $-66,360 Year-1 take-home (Fermi). 1 in 11 meaningful-success odds."

I read it twice. This is not what I expected a product page to say about itself. I genuinely could not tell if I was reading a founder being unusually honest or a marketing trick dressed up as unusual honesty. The phrase "Fermi" appearing next to a dollar figure is doing a lot of lifting and I don't know if I trust the math or the methodology.

## What I distrusted

About two thirds through the page I realized I was not reading a product page. I was reading a pitch to become the person who builds this product. "We shipped the strategy package; you ship the customer conversations." That is a very different thing from "here is software that solves your problem."

The feature list reads like a product exists: "Real-time risk scoring by transaction volume and uptime criticality." "Backup routing recommendations for critical payment paths." That sounds like a live system doing live things. But then: "Honest disclosure: we don't have live customers on this idea yet."

So the feature bullets are describing a hypothetical. Which means when I read "Real-time risk scoring," I was imagining something that does not exist. That gap between implied and actual is the thing I trust least here.

Also: no company logo. No team page. No screenshot. "Trusted by" with nothing after it.

## What would convince me

I don't want another dossier. I have a strategy. I need a product. What would actually move me is one reference call with someone running a fintech between $10M-$100M ARR who replaced their processor dependency spreadsheet with this and can tell me what broke during the Worldpay outage in March. One real conversation beats every "backup routing recommendation" bullet point.

If this is a tool I'm supposed to go build, I want to see the working code starter they mention at the $99 tier. What does "working code starter" mean for a product that requires live integrations with processors, uptime APIs, and compliance cert tracking? That is not a weekend project.

## What I'd ask in an email reply

1. The feature list describes things like "real-time risk scoring by transaction volume" -- what data sources does that actually pull from, and who maintains those integrations as processors update their APIs?
2. You're pricing adoption at $99-$199, but the page says speed-to-MVP is 3/10 and financial upside is 2/10. Who is the right person to adopt this, and why would they pay $99 for a business idea with 1-in-11 odds when they could spend that hour finding a paying customer instead?
3. Is there a live demo of anything, or is the $5 dossier the most concrete artifact that currently exists?

## Verdict: on-the-fence

The problem is real and the headline earned my attention. But I came here looking for software to buy and I'm leaving having been pitched on becoming a founder. Those are very different conversations and the page blurs the line in a way that felt like a bait-and-switch, even if it wasn't meant to be.

---
*Memo by skeptic persona, generated 2026-06-12. Studio breaks own self-grading loop.*