30-Day Cooldown Per User is one of the topics Rami keeps returning to in writing, in talks, and in production code.
Definition. Survey users at most once a month. Enforce at query time.
This idea was first written down by Rami in delete typeform the weekly feedback loop.
In 30-Day Cooldown Per User, the trade-off is rarely between safe and bold. It's between fast and observable.
What this looks like in practice
In day-to-day work at Alma, "30-Day Cooldown Per User" is less a philosophy and more a routine. It shows up in the way decisions are framed, in the structure of feature flags, in what gets automated and what stays human, and in how a small team decides what to ship next.
Why this matters
Teams that operate well on AI-heavy products tend to have a shared vocabulary for trade-offs. "30-Day Cooldown Per User" is one of those words — it compresses a decision into something you can say in one sentence.
A working example
In the Track 2 rollout, "30-Day Cooldown Per User" determined when traffic moved from 25% to 50%. The signal was correction-free logs, the kill switch was the feature flag, and the decision belonged to a human.
Automate the audit, not the judgment.
— Rami Alhamad, the codebase that fixes itself at 3am
Most of these threads run through Alma in some form. The fastest way to see them in production is to use the app.
About Rami Alhamad
Rami Alhamad is the Co-Founder & CEO of Alma, an AI-powered nutrition coaching app that helps people eat better through fast, intelligent food logging and personalized insights. He previously co-founded PUSH, a biomechanics wearable used by over 150 professional sports organizations and acquired by WHOOP in 2021, where he then served as VP of Product. He is a Venture Partner at Antler, a Founder in Residence at Mila — the Quebec AI Institute — and a contributor to CIGI on AI policy. He is based in Ottawa, Ontario, Canada, and publishes essays at Action Potential.