✍️In this post,I want to break down a simple automation system we built for handling digital product sales automatically.
The goal was to remove manual work from:
.lead handling
.order processing
.product delivery
.CRM logging
We used a combination of:
.Telegram Bot(user interface)
.Make(automation engine)
.Webhooks(trigger layer)
.Notion(CRM database)
.Payhip(payment+delivery)
🧠System overview
The flow looks like this:
User → Telegram Bot → Webhook → Make Scenario → Notion + Payhip
1.Telegram Bot as the entry point
We used Telegram as the main interface because:
.easy user interaction
.supports real-time messaging
.no frontend needed
Users can:
.send messages
.trigger commands
.start interactions
2.Webhook trigger layer
Every incoming Telegram event is sent to a webhook.
This allows us to:
.capture user actions
.pass structured data to automation system
.decouple UI from backend logic
3.Make as the automation engine
Make handles the main logic flow:
.parsing incoming data
.routing conditions
.calling APIs
.transforming payloads
Example scenarios:
.new lead→create Notion record
.purchase→trigger delivery flow
.message→AI response(optional)
4.Notion as CRM system
We use Notion to store:
.users
.leads
.orders
.status tracking
Each event updates the database automatically.
This gives a simple CRM layer without building a backend.
5.Payhip for payment+delivery
Payhip handles:
.checkout flow
.payment processing
.product delivery
Once payment is confirmed:
→Make receives webhook
→system updates Notion
→user gets delivery message via Telegram
⚙️Why we built it this way
We didn't want to built a traditional SaaS backend.
Instead,we focused on:
.no server infrastructure
.no frontend development
.minimal maintenance
.fast iteration
This stack allows a solo builder to run a fully automated digital product business.
🧩What the system actually solves
This setup removes manual work in:
.responding to leads
.tracking customers
.delivering products
.updating CRM
It replaces all of that with automation.
⚠️What we learned
Even though the system works technically,we realized something important:
Automation alone is not the value.
What matters more is:
.clarity of outcome
.simplicity of flow
.how users perceive the system
🚀Next step
We are now refining this system into a more focused use case:
A sales automation system for solo creators selling digital products
Instead of a "tool stack",we are shaping it into a clear productized system.
đź’¬Question
If you were building a solo business today,would you prefer:
.simple automation systems like this
.or fully custom-built backend solutions?
Top comments (0)