Founder Essay

Why I built Spoke

I did not want to build another giant productivity system. I wanted to solve a smaller, more frustrating problem: the habit happened, but the record disappeared before I got it down.

The problem felt smaller than it was

On the surface, logging a habit sounds trivial. Open the app. Tap the thing. Move on. But real life does not usually hand you a calm logging moment. It gives you transitions, interruptions, and low-energy windows.

That is where tracking starts to fail. Not because the habit stopped mattering, but because the record became too easy to postpone.

I kept seeing the same failure mode

The habit was often already done. The app was the hard part. That inversion stuck with me. If the real breakdown is capture friction, then adding broader analytics, coaching, or more screens does not solve the core problem.

Why the product stayed narrow

Spoke focuses on capture before analytics because that is the part most products quietly treat as solved. Voice-first logging, review-before-save, manual fallback, and recovery all come from that same belief: logging should never interrupt life more than the habit already did.

What I wanted the product to feel like

Calm. Fast. Honest. Useful in the moment before people forget. That is why Spoke is intentionally not a task manager, AI coach, or life operating system. The narrowness is part of what makes the product believable.

Read next

If you want the category explanation, read What is a voice-first habit tracker?. If you want the problem lens, read Why people forget to log habits.