β AI SaaS with auth, coaching agent & subscription logic β apex-eta-liard.vercel.app
β B2B2C marketplace with real-time map & pharmacy dashboard
β Voice AI receptionist platform (Arabic Β· French Β· English)
π My background is unusual.
I study Accounting & Finance β and I build AI systems.
That means I understand the business problem before I write a single line of code.
π¬ "Western quality. MENA pricing. Delivered in 72h."
π Open to:
β AI & automation builds
β Full-stack MVP development
β Long-term partnerships
π contra.com/yosr_faris
π οΈ I'm Yosr β freelance AI developer & automation engineer. I design intelligent workflows (n8n Β· Make.com Β· Claude API) and web apps (Next.js Β· Supabase) for SMEs and accounting firms. Based in Morocco, working worldwide.
Lost 2 days building a complex n8n workflow. Here's what I learned.βοΈ
The project: A 12-node AI Receptionist automation for a luxury resort in Bangladesh. Multi-channel (WhatsApp, Telegram, Voice), 9 Google Sheets, Gemini API, payment automation, customer CRM.
What went wrong: Added a new voice integration node. Accidentally deleted the entire workflow.
Why it happened:
No JSON exports after milestones
No version control (Git)
Testing changes LIVE on production workflow
No documentation
Building locally with zero redundancy
The fix (now implemented):
β JSON backups after every 2-3 nodes
β GitHub versioning
β Clone workflows for testing
β Modular design
β Complete documentation
For automation professionals: You're not just buildersβyou're engineers.
Treat workflows like software:
Documentation
Version control
Backup strategy
Modular testing
Client delays = lost revenue + credibility damage.
Make the systems bulletproof.
How do you prevent data loss in your automation builds? π
#n8n#Automation#WorkflowAutomation#NoCode#LessonsLearned#make#AIAutomation#DataAnalyst#MachineLearning