How I build: the logic behind the screens
The interface is the small part. Most of the work is what happens when nobody is looking: a reminder that has to go out, a message that has to reach the right person, an invoice that has to add up, a server that has to come back on its own.
One event, the right channel
Business events (order placed, reminder due, invoice issued) go through one rule layer that decides who is told, how, and what happens if the first channel fails.
Events
- Order placed
- Reminder due
- Invoice issued
- Threshold crossed
Rules
- Who
- Language
- Retry and fallback
Channels
- App push
- Telegram bot
- Webhook to n8n
What I do
The skills and techniques I bring. I keep client and employer systems private.
Automation and notifications
- Design and run workflow automations with n8n and webhooks, connecting apps that were never meant to talk to each other.
- Reminders, order alerts and billing notifications that choose the right channel and fall back when one fails.
- Telegram and WhatsApp bots that let people query and act from a chat instead of opening a dashboard.
WhatsApp and AI agents
- Build on the WhatsApp APIs so talking to a business is as easy as sending a message, with no new app to install.
- Run several AI agents on those chats at once, each with its own role, talking to clients and handing over to a person when needed.
- Keep agents safe and useful: scoped access to data, conversation memory, guardrails, and logs of what was said and done.
Servers and services
- Split systems into small services and run them across several servers, so one failure does not take everything down.
- Mix edge platforms and self-managed Linux servers, choosing per workload for cost, latency and control.
- Multi-tenant design with isolated data, per-tenant settings and permissions.
Correctness and resilience
- Idempotent writes, atomic operations and audit trails, so retries never double-post and every change has an author.
- Offline-first apps that sync when the network returns; backups with restores that are actually tested.
- Business rules enforced in code, not left to the interface.
Delivery and operations
- CI/CD that tests, builds and deploys to staging and production, with health checks and one-command rollback.
- Docker, nginx, systemd and Cloudflare; secrets kept out of repositories.
- End-to-end browser tests, including accessibility and contrast checks, before anything merges.
Want something like this?
Tell me what you run and what keeps going wrong. I will tell you honestly if it is worth building.
Message on WhatsApp