Senior Product Manager
I build what others
build on top of.
A decade in platform work — Stripe Payment Links, Masterschool through its $100M seed and twenty-country build-out, Embedded Finance at eOS. The work that compounds is the work underneath the screens: the APIs, the ledgers, the state machines, the contract between the platform and the operators on top of it. This site is the field notes from that layer.
AI-augmented · autonomous PM
The engine proposes. I choose where to go.
Most PMs use AI as a chatbot. I designed and built an autonomous PM operating system — 19 agents that listen across my channels, draft strategy, propose roadmaps, surface convergences. Every morning, takes and drafts reach my desk. The judgment — what to actually ship, what to overrule, where to compound — stays mine.
- Judgment
Me. The only loop AI doesn't close.
- Reflection2 agents
A retrospective agent (weekly scoring) and a meta-agent (monthly prompt tuning) — the system improving itself.
- Synthesis4 agents
Pattern detection · strategy drafting · culture learning · decision drafting.
- Listening12 agents
Scouts on cron — GitHub, Jira, Slack, Gmail, calendar, competitors, regulators, customer voice.
- Foundation1 agent
Cowork runtime, 6 MCPs, scheduler, audit log, plus the action executor that runs Tier 4 actions after `/pm-approve`.
What reaches my desk every morning
- →Strategy takesDrafted opinions on convergences across 7-day windows, ready to approve or overrule.
- →Roadmap proposalsSpecific bets the synthesis layer thinks deserve compounding — with the alternative it rejected.
- →Drafted memosBriefings, decision memos, ticket drafts — sitting in drafts until I sign or rewrite.
0 agents propose.
1 me decides.
The premise is simple. AI is good at listening, drafting, and detecting patterns. I’m good at judgment. The architecture separates those — and the autonomy model makes sure the line never blurs.
Graduated autonomy · 5 tiers
- T1Read anythingauto
- T2Write to memory / Obsidianauto, audited
- T3Draft artifactsauto, lands in drafts
- T4Create Jira / Confluence / Slack/pm-approve
- T5External comms · deployhuman only
What I work by
Four claims worth arguing about.
Each one is a position, not a slogan. If you disagree with any of them, that's the conversation worth having.
- 01
AI doesn’t take the PM job. It takes the parts you didn’t actually want.
Listening, drafting, pattern-detection — agents are great at all of them. Judgment isn’t a part of the job. Judgment is the job. And it doesn’t shrink as the engine gets stronger. It gets concentrated.
- 02
The product is the contract underneath.
Screens are the cheapest part. The contract underneath is the part that compounds — the spec, the state machine, the agreement between a platform and its regulator. Most product debates are contract debates dressed up as feature debates.
- 03
The org chart is your second product.
Every product is, in the long run, a function of the org that ships it. The features matter. The team and the operating cadence around them matter more. Founding seats teach you this fast.
- 04
Make the system legible before you change it.
The most underrated PM job is describing what already exists — accurately, currently, in one place everybody points at. The legibility work doesn’t show on a quarterly OKR. It shows in the speed of the team six months later.
Selected work
Four case studies across four different jobs.
The work, not the resume. Each one a deep dive into a real launch — the problem, the calls, the trade-offs.
- 2026 — Now
PM OS — An autonomous PM engine I built for myself
19 agents · 12 scouts · 4 synthesis brains · 1 me. Live since May 2026.
AI-nativeAutonomous AgentsCowork - 2024 — Now
eOS — Building a banking platform from Israel
What it takes to ship a BaaS platform locally and prepare it for jurisdictions that haven’t opened yet.
BaaSIsraelCross-jurisdiction - 2021 — 2024
Masterschool — Founding PM
Joined a bootstrapped ed-tech six months before its seed. Owned everything until the specialists arrived.
Ed-techMarketplace0 → 1 - 2019 — 2021
Stripe — Payment Links
PM on the team behind one of Stripe's most opinionated products.
PaymentsAPIDeveloper Tools
Notes
Writing about platforms, payments, and PM craft.
Short essays from inside the regulated rails. Updated occasionally — quality over cadence.
- Essay · 5 minRead essay
Autonomous, not co-pilot
Why most AI-in-product is shipping the wrong shape. The case for autonomous systems with real audit logs over polite co-pilots that ask permission for every step.
- Essay · 5 minRead essay
The product is the contract underneath
Screens are cheap. The contract — the spec, the state machine, the agreement — is what compounds. The PM work that pays you back in three years.
- Essay · 4 minRead essay
Decisions, not discussions
A regulator emails about a transaction from eight months ago. In one company that's two weeks of forensic work. In another it's 90 seconds. What separates the two is one habit.
- Essay · 4 minRead essay
Vendor PM vs Fintech PM
Same industry, different muscle. Selling to banks is a different game from selling to consumers — and it changes everything about the job.
- Essay · 4 minRead essay
Three jurisdictions, three philosophies of regulated rails
Three regulators, same goal, three architectures. What each one is right about, wrong about, and what cross-jurisdictional PM work actually looks like.
- Essay · 4 minRead essay
Draw the actual system
Two engineers argued about a roadmap for forty minutes. I went to the whiteboard and drew the eight boxes that mattered. The argument ended in five.
Career path · interactive
Law to API contracts.
Click any node for the take. The story doesn't go in a straight line; few do.
About
Who's writing this.
The thing I liked about law school was reading contracts. The *systems* part — who owes what to whom, where the contract holds and where it leaks. Product is the closest job I've found that asks me to do exactly that for a living.
Stripe Payment Links: the contract was the API. Masterschool: the deal between a learner and a school six months in the future. eOS now: between a banking platform and the bank running on top of it. Different rooms. Same job.
I built PM OS because the parts of the work I actually want to do are getting smaller and more concentrated. Nineteen agents on Cowork listen, draft, and surface convergences across my week. They produce. I judge.
Tel Aviv. If you're building something where the contract underneath is the interesting part, I'd like to hear about it.
Now · May 2026
What I'm working on this quarter.
Inspired by Derek Sivers’ /now page. Updated quarterly.
- Embedded Finance at eOS. Public-facing detail in the case study. The rest is NDA.
- PM OS in production every working day. Currently calibrating the T3 → T4 boundary as the synthesis layer's draft quality climbs.
- *Lords of Finance* (Ahamed) at night. The 2024 Synapse trustee filings when I forget how sponsor-bank composition actually fails. *Complex Systems* (Patrick McKenzie) on the walk home.
- Sharpest open question on my desk: where exactly the line lands between PM judgment and AI judgment over the next 24 months.
Contact
Say hello.
Email is the best signal. I read every message.