# Marcus Theriault, Staff Platform Engineer at Crestline Health Tech — read of aiops-ai, May 11 2026

> 11 years in SRE and platform work, currently the oldest engineer on a 190-person health-tech team, maintaining PagerDuty hell for four squads while eyeing my first solo product.

## How I got here

LinkedIn served me this ad around 8:45am on the Caltrain. I'm on my phone, my 8-year-old has a dentist thing I have to leave early for, so I'm in a "skim fast and maybe save it" mood. The hook was something like "For SRE leads, reclaim your sleep from alert storms." That's my actual words back to my wife last Tuesday so I clicked. I landed somewhere that felt like... two websites duct-taped together. Ten seconds in I was not sure what I was looking at.

## What I clicked first

The hero copy isn't bad. "Your team wastes hours buried in notifications. We surface critical signals so your engineers spend time fixing production instead of hunting noise." That's a real sentence about a real thing I feel on Monday mornings. But immediately below there's "Unlock the dossier for $5" and suddenly I understand I'm not being sold a SaaS product. I'm being sold... a plan to build one? I had to re-read three times to confirm.

## Where I paused

The honest disclosures section stopped me cold. "We don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations." That is a genuinely unusual thing to put on a landing page. Most of these "build this SaaS" idea shops just hand you a Notion doc and say good luck. The fact that they wrote it out loud, in the main body, not buried in a footer disclaimer, made me actually read the surrounding paragraph twice. That's probably the most interesting thing on the page.

## What I distrusted

"Cutting alert fatigue by 70%." That's the hero stat. It's cited nowhere. The product doesn't exist yet by their own admission, so where did 70% come from? That number is doing a lot of work for something with zero customers. It reads like a comp number pulled from Datadog's marketing copy and re-pasted here.

Also: "Trusted by" with a blank space where logos should be. I've been around long enough to know that's a template section that someone forgot to fill in or left as social-proof bait. Either way it's a trust signal that backfires.

The navigation bar says "Platform Solutions Resources Customers Sign In Talk to Sales" and none of those links are real. It's a mock. I get that it's demonstrating what the landing page would look like, but it's disorienting when you're reading on a phone and you don't immediately realize the top half of the page is a product demo and the bottom half is the actual pitch.

## What would convince me

I'd want one real conversation with someone who actually bought the $99 package and did something with it. Not a case study. A Loom or a tweet thread or a "here's what I found when I tried to sign up my first customer." Just one person, with a name, who can say what month they started and what they ran into. The Fermi math shows -$59K year-1 take-home and a 9% success rate. I'm fine with those numbers being honest, but if you're going to show me a hard number like that you need to also show me one person who hit the 9%.

Also: what does the "working code starter" actually look like for $99-199? Language, repo structure, what's wired up and what's stubbed. That would tell me in about 30 seconds whether the builders actually know this domain or just wrapped a GPT prompt around PagerDuty's docs.

## What I'd ask in an email reply

1. The page says 12-18 weeks to MVP and $70K investment. Is that assuming I'm writing code, or hiring someone? Because those numbers feel like they assume a solo technical founder doing evenings and weekends, and those are very different conversations.
2. What does "encode your runbooks as decision rules" actually mean in the MVP scope? Is that a YAML config file, a UI, a drag-and-drop thing? That sentence is doing a lot of work without explaining the mechanism.
3. Who built the ML baseline model that learns your "infrastructure baseline"? Is that a pre-trained model you're shipping in the code starter, or is that a wave-your-hands-we'll-figure-it-out situation?

## Verdict: on-the-fence

The honesty about failure odds and negative year-1 economics is genuinely unusual and I respect it. But the page doesn't resolve the fundamental confusion about who I am when I land here: am I an SRE being sold a tool, or an operator being sold a build kit? Until that's clearer in the first 10 seconds, most of my ICP lands and bounces before they get to the good part.

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