We spent weeks building a Telegram automation system.No one cared.
A week ago,we thought we had something valuable.
We built a system called Hermes---a Telegram-based automation stack using Make,Notion,and Payhip.
The idea was simple:
automate digital product sales end-to-end.
Webhook→Telegram→AI processing→Notion CRM→Payhip delivery.
Technically,it worked perfectly.
Everything ran 24/7.
No manual work needed.
But there was a problem.
Nobody cared.
Not because it didn't work-
but because nobody understood why they should use it.
We realized something painful:
👉We built a tool.
👉But people don't buy tools.
👉They buy outcomes.
So we started asking a different question:
Instead of:
"What can this system do?"
We asked:
"What problem does this actually solve?"
And the answer changed everything.
We are no longer building:
.a Telegream bot
.an automation tool
.or a Make workflow system
We are now thinking in a different direction:
→ A system that helps creators sell digital products automatically
Not automation for the sake of automation.
But:
.automatic lead capture
.automatic sales handling
.automatic delivery
.automatic CRM logging
Same stack:
.Telegram(interface)
.Make(logic engine)
.Notion(CRM)
.Payhip(payments)
Different framing.
Different product.
Different story.
What we learned:
Building infrastructure is easy.
But without a clear user-facing outcome,it's invisible.
Now we are rebuilding Hermes as:
-A sales automation system for solo creators selling digital products.
Not a tool.
A system that runs your business in the background.
If you are building solo tools or automation systems:
What's your biggest struggle right now?
Would love to hear how other are thinking about this.
Eva
on June 29, 2026
Top comments (1)
We're currently shifting from"automation tool thinking"→"business system thinking."
Curious if others here have gone through the same shift.