We’re building AzeniqTech: tiny tools with one “gesture” (not another platform)
Build small. Ship often. Stay sane.
Hey Indie Hackers 👋
I’ve noticed a pattern in my own building habits:
Whenever I’m excited, I accidentally try to build a platform.
New idea → big architecture → feature roadmap → “just one more mode” → weeks pass → nobody uses it.
So we started AzeniqTech with a constraint that keeps us honest:
Every product must be explainable as one gesture.
If we can’t describe the core action in one line, it’s not a product yet — it’s a wishlist.
What “one gesture” means in practice
Instead of building feature lists, we build a tight loop:
- user does one clear action
- gets value immediately
- repeats without thinking
And we measure that loop, not vanity metrics.
A simple example is Rephrazo (one of our tools):
It’s not “AI writing” or “content generation.”
It’s a tiny rewriting helper designed to remove friction from editing.
The gesture is:
highlight → rephrase → insert
No tab switching, no prompt boxes, no 10-tone dropdowns.
Just a fast micro-edit that keeps you in flow.
The biggest surprise so far
I assumed people would want “more powerful” controls:
- tone options
- length sliders
- prompt customization
In reality, most users ignore flexibility and just want:
- one strong default
- speed
- and “don’t kill my voice”
Removing options increased usage.
It was a bit painful to admit, but it’s been consistently true.
What I’m trying to learn (and where IH might help)
If you’ve built focused tools (or a small studio of them), I’d love your take:
-
What’s the best early signal that a narrow tool is becoming a habit, not a toy?
-
For products like this, which metric is most predictive early on:
- retention
- repeat actions per session
- sessions per week
- something else?
-
How do you decide when to add “control” (modes/settings) vs doubling down on one default?
Build small. Ship often. Stay sane.
Would love any lessons from people who’ve gone from “tiny utility” → “sustainable business.”
