# Marcus Oyelaran, Head of Payments Operations at Meridian Pay — read of Fintech Risk Monitor, June 12, 2026

> 9 years moving money through fintech stacks. Currently responsible for keeping Meridian's processor relationships, SLA tracking, and incident response from living in three different Notion docs and a Google Sheet my predecessor built in 2021.

## How I got here

Two weeks ago our Stripe payouts API went dark for 40 minutes on a Tuesday afternoon. I spent that incident manually digging through our internal wiki trying to figure out which downstream partners were affected and whether we had a backup routing option. We did not. I've been googling "payment processor dependency mapping tool" and variations of it ever since. This page showed up mid-page on a Google search for "fintech vendor dependency risk software." The title matched the exact phrase I had in my head.

## What I clicked first

The headline pulled me in: "Third-party risk that doesn't disappear in a spreadsheet." That is a real sentence about a real problem I have. I kept reading. The feature list is solid on paper: dependency mapping, backup routing recommendations, audit-ready reports. I've been describing those exact three things to my VP of Risk for six months.

## Where I paused

The scoring block. There's a number on the page that says "$-66,360 Year-1 take-home (Fermi)" and another that says "1 in 11 meaningful-success odds." I had to read that three times. I came here looking for a tool to buy. These look like... founder economics? For someone who would build this? I scrolled back to the top trying to figure out if I misread the page. I had not misread the page.

## What I distrusted

This is not a product. I eventually figured out the page is selling the idea of building this product, not the product itself. The pricing section says "Unlock the dossier $5" and "Adopt the build $99-$199." And then there's this line: "Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations."

I respect the transparency. I genuinely do. But I came here because I have the pain right now, not because I want to become a founder. The "70/100 adoptability" score and the "pain intensity: 10/10" confirm what I already know: this problem is real and people would pay for a solution. That's cold comfort when I still don't have the solution.

The feature list reads like what someone would write after doing customer discovery interviews, which I suspect is exactly what it is. "Backup routing recommendations for critical payment paths" is either a deeply considered feature built by someone who has been inside a payment incident, or it's a sentence that sounds right. I can't tell which from this page.

## What would convince me

If someone had actually built this and was running it for even two or three fintech companies, I'd want to see a single incident debrief: what happened, what the tool surfaced, what decision got made faster because of it. Not a case study with revenue numbers and logos. An actual timeline. "Processor X went down at 2:14 PM. Alert fired at 2:15 PM. Ops team rerouted by 2:22 PM." That's what I'd forward to my VP.

## What I'd ask in an email reply

If I were emailing the person behind this page, which I won't be because they're not building the product themselves:

1. The backup routing recommendation feature -- how does it know what backup routes exist? We have three processors and the routing logic is deeply specific to transaction type and geography. How does a generic tool know that?
2. What's the data model for "dependency mapping"? Do you ingest our contracts, our API logs, or do we fill out a form?
3. The compliance tracking feature says "certifications, SLAs, and regulatory requirements" -- does that mean the tool monitors live SLA performance or just stores the SLA documents?

## Verdict: dismissive

Not because the problem is wrong (it's right), and not because the page is dishonest (it's unusually honest). But because I came here to buy a tool and left having learned I'd have to become its founder. That's not the trade I'm making on a Thursday morning.

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