Kairo

Every alarm clock ever made has the same flaw. It trusts you.

You set it the night before, full of conviction, certain that tomorrow's version of you will be a disciplined stranger. Then morning comes, and tomorrow's version of you turns out to be the same person, only warmer and more resentful. A thumb finds the snooze button before the brain finds consciousness. The contract is broken before you're even awake enough to remember signing it.

I wanted an alarm that didn't trust me. One that made the act of waking up something I had to earn, not something I could dismiss with a reflex.

---

---

The Greeks had two words for time. Chronos is the clock on your wall, indifferent and continuous. Kairos is the moment that matters, the window that opens and then closes. Most alarms are pure chronos. They mark a number on a dial and ask nothing of you. I named this one Kairo because waking up isn't a number. It's a window. Miss it and the whole day tilts.

An alarm you can't lie to

The core mechanic is simple and slightly cruel. When Kairo goes off, you don't get a snooze button. You get a photo to match. You set it up the night before by photographing something far from your bed, the bathroom sink, the kettle, a poster in the hallway. To silence the alarm in the morning, you have to physically walk there and take the same photo again.

By the time you've stood up, crossed the room, and lined up a shot of your own kitchen tap, the war is already won. You're vertical. You're moving. The hardest part of any morning, the part where you're horizontal and negotiating, is over.

There's no exit. No five-more-minutes, no swipe-to-dismiss while half asleep. The only way out is through, and through means out of bed.¹

The night before is the real fight

Here's the thing I learned building this: the morning isn't where you lose. The night before is.

So I leaned into a second mechanic. Kairo can block the apps that keep you up, the ones you open at 11pm intending to scroll for two minutes and resurface at 1am with no memory of the time passing. I shipped this on top of Apple's Screen Time framework, so at the hour you choose, the distractions simply stop opening. The phone goes quiet so you can too.²

It felt right to put the whole loop in one app. An alarm that fixes your morning is treating a symptom. An app that also guards your night is treating the cause. You can't out-discipline a phone that's engineered to keep you awake, so I just turned it off for you.

Make waking up a game

I didn't want Kairo to feel like punishment. Punishment is a bad long-term strategy, you eventually delete the thing that punishes you.

So the photo missions have a texture of play to them. There's a small thrill to the hunt, stumbling toward the right corner of the apartment, holding up the phone, watching it recognize the scene. It's a tiny puzzle you solve every morning before your brain has fully booted. The reward is immediate and physical: silence, and the quiet pride of having actually gotten up.

The trick was tuning how forgiving the photo matching is. Too strict and you're standing in your kitchen at 6am, increasingly awake and increasingly furious, while the app insists your sink isn't your sink. Too loose and you can fool it with a photo of a photo. Most of the craft in this app lives in that one threshold.

Little big details

A few decisions that took longer than they should have:

• The validation has to feel fair. When a match fails, Kairo tells you why, too dark, wrong angle, move closer, instead of just rejecting you. A morning is no time to feel gaslit by software.

• The alarm sound escalates gently. It starts soft. The goal is to wake you, not to launch you out of bed with your heart pounding. Kairo wants you up, not traumatized.

• No streak guilt. I deliberately left out the angry red "you broke your 14-day streak" pattern. The point is to wake up tomorrow, not to feel like a failure today. Shame is a terrible alarm clock.

• Setup happens at night, on purpose. You photograph your targets when you're calm and capable, so that morning-you, who is neither, only has to follow a trail already laid.

Where it came from

Kairo started as a frustration and a bet. The frustration: I am very good at setting alarms and very bad at obeying them. The bet: that the fix wasn't more willpower but less choice. Remove the snooze, remove the negotiation, and the problem mostly dissolves.

It shipped in May. It found its first people not through ads but through short videos of the thing actually working, someone half-asleep staggering across a room to photograph a kettle, which turns out to be both funny and uncomfortably relatable.³ Apparently I'm not the only one who needs an alarm that won't take "five more minutes" for an answer.

The milestones so far

I build in public, so most of these happened in full view. Here's the project, milestone by milestone.

Late April, the first wave. Before the app was even fully out, i was posting on TikTok and pushed it to around 3.5 million organic views with zero ad spend. Two large Brazilian brands also turned up in the comments. The run climbed across a few days, 354K views, then 1.2M, then 1.7M, and brought in the first couple thousand users.⁴

May 10, launch. The app went live properly. Within about ten days it had roughly 4,600 downloads across 45-plus countries and its first real revenue, all of it organic, around R$10K in May.

Mid-May, retention. I shipped a major stability release that pushed authorized devices from 43% to 63% among active users in three days. That was the moment the app started keeping people instead of just attracting them.

The pricing structure. I rebuilt subscriptions into three clean plans, including a weekly plan with a trial, and the new structure started converting.

Late May, the night side. I applied for Apple's Family Controls entitlement expecting a four-to-six-week wait and got approved the same day. That unlocked the app-blocking feature, and I built the night-time flow into onboarding. The launch reel kept compounding, 144K, then 171K, then 202K views over six days. I formalized the Gabi partnership on a performance deal and negotiated my first paid amplification deal.

Taken together: the virality brought the people in, the product kept them, and the night side turned Kairo from half a loop into the whole one.

Footnotes

1. There is, technically, one way out: delete the app while the alarm is screaming. I'm told some people have done this. I choose not to think about them. ↩

2. Getting Apple to approve the entitlement for this was its own small saga. Worth it. ↩

3. The going theory is that watching someone else lose the snooze fight is deeply satisfying, in the way watching someone else fail at a thing you also fail at always is. ↩

4. People call this luck. It wasn't. I built a thing engineered to film well, put it in front of the right people on purpose, and made sure none of the attention went to waste once it arrived. You don't stumble into 3.5 million views, you build the conditions for them and then earn them. ↩