How these systems actually get built.
Walkthroughs of real systems, most of them running inside Viacala itself. What each one does, what it is built from, where it broke, and what it changed for the business.
These are the posts where we show the work. Where a system is one of ours, we say what it is built from and what went wrong with it, because the failure modes are the part you cannot get from a vendor page.
Technical depth here is evidence, not the subject. Every one of these starts from a business problem, a lead going cold, a no-show costing a slot, a prospect who needs proof before a call, and ends at what changed. If you want the concepts first, the fundamentals posts come before these.
This is one of three pillars. If a term here is unfamiliar, the fundamentals posts define it properly, and commentary covers the research behind these choices. All of it points back to the AI systems we install for Mallorca businesses.
4 posts in this pillar
- How to install a speed-to-lead system in a Mallorca-based service business
A walkthrough of the speed-to-lead system: what it does, what it needs, and how to install one.
- The AI stack we run Viacala on, and why
The actual tools behind Viacala's own systems, and why we chose each one over the alternatives.
- How a Palma-based clinic could implement follow-up automation
A walkthrough of reminders, no-show recovery, and post-visit follow-up for a small clinic, and the stack behind each one.
- How we built our own AI audit system for Viacala, using n8n and Claude
The architecture behind our own AI audit tool, and the failure mode that broke it first.
Browse the other pillars: If a term here is unfamiliar, the fundamentals posts define it properly, and commentary covers the research behind these choices. Or see every post.