# Ben Kowalczyk, CTO at Fleetable — read of Entitlements Sync API, June 15 2026

> 9 years building software, 4 running a 12-person fleet-management SaaS on Rails + Stripe. We have about 800K ARR and a permissions system I wrote in 2021 that I regret daily.

## How I got here

Spent Friday afternoon debugging a churned customer who still had full export access three weeks after downgrade. Our Stripe webhook handler dropped the event silently (we log to a table nobody checks), and nobody caught it until the customer emailed us asking why their card wasn't being charged. I Googled "stripe subscription feature gate sync automated" around 4pm, clicked the third result, ended up here. I was looking for a product I could sign up for and pay monthly. I'm still not sure that's what this is.

## What I clicked first

The problem block landed. "Your subscription lives in Stripe. Your feature gates live in your codebase. Your support team syncs them manually in Slack." Okay, yes, that's us. The Slack part especially. We literally have a channel called #customer-access-requests and it has 340 messages. I kept reading.

The phrase "webhooks that fail silently" is the one that made me feel like the person who wrote this had actually dealt with this problem, not just researched it.

## Where I paused

Bottom of the page. There's a box that says "$-26,192 Year-1 take-home (Fermi)" and "1 in 10 Meaningful-success odds." And then: "Honest disclosure: we don't have live customers on this idea yet."

I had to reread the page from the top. I thought I was evaluating a product to use. Turns out this is a product idea being sold to someone who wants to build it. The $49/month pricing in the middle of the page is what the builder would eventually charge customers. Not what I'd pay to use it now. That's a significant thing to bury below the fold.

## What I distrusted

"No configuration. No code changes." And then Step 3 literally says: "Replace your hardcoded feature checks with a simple API call." That's a code change. Maybe a small one, but I have about 60 callsites for feature checks across our codebase. Calling that "no code changes" is doing a lot of work.

"15 minutes" setup vs "3-5 days of engineering" in the comparison table. Nobody measured this. The 3-5 days might be right for someone starting from scratch. For us it would be a day, maybe two. The 15 minutes would be longer once I'm mapping our 4 plan tiers, 11 add-ons, and the grandfathered cohort from our 2023 pricing migration that nobody wants to touch. That complexity doesn't disappear because there's a dashboard.

"Your team gets 10 hours back each week." Where did this come from? Our team wastes maybe 2-3 hours a week on permission issues. 10 hours sounds like a slide number.

## What would convince me

If this were a real, shippable product today: one case study from a team with a messy entitlements situation (grandfathered plans, add-ons, custom enterprise deals) showing what the setup actually looked like. Not a simple 3-tier Stripe setup. The hard case. Show me the dashboard mapping screen with something ugly in it.

If this is a concept being sold to builders: a live demo environment I can poke at would do more than any copy. The page says "Start Free Trial" but I'd bet those buttons don't go anywhere yet.

## What I'd ask in an email reply

1. Is there a working product I can actually sign up for today, or is this an idea at pre-product stage? The page layout made me genuinely uncertain for five minutes.
2. How does the API call work when my backend is making a permission check during a request -- do I take a synchronous latency hit on every check, or do you push state to my side that I query locally?
3. What happens when your service goes down? Do my feature gates fail open or fail closed, and who controls that?

## Verdict: on-the-fence

The problem description is accurate and the copy doesn't read like garbage, which puts it ahead of most tools in this category. But I still can't tell if there's a product here I can actually use, and the page seems to be trying to sell me two different things at once (the tool AND the idea). That confusion kills momentum.

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