The Day CogniFocus Ended Up in Startup Fortune

How a tiny frustration with passive focus timers turned into a product, an accountability Goblin, and a story I never really expected to see published.

I Never Really Planned for This

I don't think I ever planned for CogniFocus to end up in an article like that. When I started building it, the idea was honestly much smaller. I was just annoyed.

I would start a focus session, put the timer on, tell myself I was finally going to get something done, and then somehow end up opening Instagram or TikTok “for a second.” And the funny part was that the timer didn't care. It kept running. Twenty minutes could disappear and the app would still happily tell me I had been focusing for twenty minutes. Technically, it wasn't lying. I just wasn't focusing.

That was the whole reason CogniFocus started becoming what it is now. I didn't want another timer that politely sat there while I destroyed my own session; I wanted something that would actually notice when I slipped.

That eventually became the Goblin. It was never a perfectly planned product decision. It started as a stupid little idea, a character that would basically call me out when I got distracted, and then it stuck. Somewhere between building the Shield, messing with reactions, breaking things, fixing them, rebuilding parts of the app and wondering whether anyone would actually use this thing, CogniFocus became a real product. Then Startup Fortune wrote about it.

“CogniFocus Catches You Mid-Scroll”

On June 2, Startup Fortune published a story about CogniFocus titled “CogniFocus Catches You Mid-Scroll During a Focus Session That Is the Entire Point.” I remember reading that headline and thinking: yeah, that's basically the entire reason I built it.

The article, written by Amilia Bon, focused on the problem behind CogniFocus rather than just listing its features. It described the difference between measuring time and actually responding to attention, and that distinction is probably the part that stayed with me the most.

When you're building something yourself, you spend so much time looking at tiny things: a button that doesn't align, a permission flow that's annoying, a Shield overlay that appears twice, a Goblin reaction that needs to change, a streak system that needs fixing, something that breaks on one particular Android phone and, somehow, only that phone. You can spend days buried in those little problems. Then someone outside the project looks at it and explains the thing you were actually trying to build, and suddenly the whole mess makes sense.

It Was Never Really About a Timer

The interesting thing about CogniFocus is that the timer is probably the least interesting part. There are thousands of timers: start, wait, stop, congratulations, you focused, except sometimes you didn't. That's what bothered me. I wanted the session to have some awareness of what was happening inside it.

So CogniFocus became more reactive. Shield watches for the apps you already know are going to steal your attention. The Goblin reacts when you try to escape. Recovery nudges are there because getting distracted shouldn't automatically mean the whole session is ruined.

That last part matters to me. I don't like productivity systems that turn one mistake into a reason to give up. You opened Instagram. Okay. Come back. That's it. The session doesn't need to become a courtroom. The current version of CogniFocus is built around that idea: protect the session, react to the distraction, recover when you slip, and keep going.

The Goblin Was Supposed to Be a Joke

Somehow the Goblin became one of the most recognizable parts of the whole thing. It started as an accountability character that would roast me when I lost focus. Now it has moods: it can be calm, it can get annoyed, it can get angry, and it can celebrate when you actually finish a session without running away to TikTok.

There is something slightly ridiculous about building a productivity app where a little Goblin is basically sitting there watching you, but that's also why I like it. Most productivity software feels very serious, all charts and numbers and streaks and percentages: “your productivity increased by 14%.” Cool, meanwhile I'm opening Instagram for the ninth time. The Goblin is much more honest: “Bro, you literally just opened TikTok.” Maybe that's exactly what I needed.

The Article Came at a Strange Point in the Journey

The Startup Fortune article wasn't the beginning of CogniFocus, and it definitely wasn't the end. It came somewhere in the middle of the mess. By then I had already spent a ridiculous amount of time building and rebuilding things that probably looked completely insignificant from the outside: the Shield, character reactions, streaks, recovery nudges, the whole progression system, and all the little details that make the app feel less like a timer and more like something that is actually present during a focus session.

I was also still learning what CogniFocus even wanted to become. That's probably the weirdest part of building something yourself. You start with an idea, then you build it, then people use it, then they do things you didn't expect, and then you realize the thing you originally thought was the product was just the first version of the idea. CogniFocus has gone through that process constantly.

The product today is much more developed than the version described in that June article. Focus Shards, stronger Goblin reactions, improved Shield behavior, progression systems and recovery mechanics have all moved on since then. But the original problem hasn't changed: I still don't want a timer that keeps counting while I'm scrolling.

Seeing Someone Else Tell the Story Is Different

When you're the founder, you get used to explaining your own product. You write the landing page, you write the posts, you explain the features, you make the screenshots, you tell people why it exists, and eventually you start wondering whether you're just repeating yourself.

That's why seeing somebody else write about it felt different. Startup Fortune wasn't me saying “hey, look at this cool app I built.” It was somebody else looking at the thing I had been building for months and pointing straight at the interesting part. That was meaningful, not because CogniFocus suddenly became some huge company, it didn't. It's still a small product, I'm still building it, still changing things, and there are still plenty of things I want to fix. But somebody outside the little bubble of my own project noticed what I was trying to do, and honestly, that meant something.

So, What Now?

I don't really know, and that's probably the most honest answer. There are a lot of ideas for CogniFocus: more companions, more ways for the system to react, better Shield behavior, more ways to recover from distraction, more progression, and more platforms eventually. But I don't want to build features just because they look good on a roadmap.

The whole point of CogniFocus was always simple. I needed something that would notice when I was losing focus, so I built it, and then I kept building it because I wasn't satisfied with the first version. Now there's an article somewhere on the internet about a little focus app and its weird Goblin, which is a pretty strange sentence to write.

A few months ago I was mostly just trying to make the thing work. Now there's a published story about it. I guess that's one of the strange things about building something: you spend so much time staring at the unfinished parts that you don't always notice when something has actually started becoming real.

And maybe that's what I took from the Startup Fortune article. Not that CogniFocus “made it,” it hasn't, not even close. Just that, for a moment, someone else could look at the thing I had been obsessing over and see the idea underneath all the bugs, features, rewrites and ridiculous Goblin reactions. That was enough, for now.

Original Startup Fortune coverage: “CogniFocus Catches You Mid-Scroll During a Focus Session That Is the Entire Point,” by Amilia Bon, published June 2, 2026.