For me, tools serve a single purpose: delivering real results. This badge validates the ecosystem I've chosen to build, test, and scale projects with speed without losing technical rigor.
My focus as a mid-level developer remains exactly the same:
Building Web and Mobile applications.
Developing SaaS platforms.
AI Orchestration — whether implementing an agente autonomo for complex workflows and database integrations, or an agente lite for targeted automations.
If you have a robust project or need to get a product off the ground with solid architecture, the link to my Expert page is below. No fluff, just execution.
Crenaly: a booking SaaS I designed and built end-to-end for appointment-based businesses in France: salons, barbers, beauty and wellness.
The core idea: when a client cancels, the freed slot is automatically offered to clients who asked for an earlier time. The first to accept gets it, their appointment moves in place, and the slot they leave is offered next. No double booking, no manual work.
Around it, a full product:
→ Branded booking page for each business, embeddable on their own site
→ Mobile-first booking flow, no account needed
→ Agenda, client management, team roles & permissions
→ Verified reviews, analytics, Stripe billing
Automatically offering a cancelled slot to the next client is such a practical feature for salons and barbers. Designing and building Crenaly end to end must have made those flows much tighter.
Congrats on shipping it! AI support tools all start to look the same, so a template with this much personality will stand out. How long did it take from idea to marketplace?
A WhatsApp chatbot that automates tasks is NOT the same as a custom-built web application.
And honestly, I’ve noticed how much people love AI-powered WhatsApp bots lately.
As someone who develops AI workflows and custom websites, I personally believe that combining a well-built web application with AI puts you one step ahead.
Imagine having a custom interface, your own database, automated workflows, and an AI agent working together in one place.
That’s a completely different level of flexibility.
Don’t get me wrong: WhatsApp bots aren’t always the inferior option. They’re great for customer-facing interactions and quick communication.
But personally? I’d rather give customers a dedicated web experience whenever the project calls for it.
When the web app and the bot share one database, which side owns the conversation state: the n8n workflow or the app? That choice seems to decide whether a customer can switch between WhatsApp and the web view mid-request.