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.
13 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.
- Speed to lead: the three tools we recommend, and how they connect
The three ordinary tools behind a speed-to-lead system, what each one does, and how they connect, from the stack we run on our own enquiries.
- How we set up client intake automation for Viacala
How a new person becomes a record, a reply and a booking on our own site, including the people who start the check-up and stop halfway.
- How to give an AI agent access to your calendar without breaking anything
How a daily routine reads our calendar and prepares us for every external call, and the four decisions that keep it from doing anything we did not intend.
- How we design a lead reactivation sequence
How to bring quiet leads back without spamming them: segment the list, reference where the conversation stopped, and set firm stop rules.
- How to build a simple lead qualification workflow
A step by step design for rating incoming enquiries against your ideal client and routing each one, with the rules kept plain enough to inspect.
- How we run a business with Claude: the folder, the rules and the retrieval table
Why writing your business down once beats prompting every time, and the folder structure and retrieval table we use to run our own company with Claude.
- How we built the AI chat widget on our own website
How our website assistant works, the limits we gave it, and what to know before building one: a narrow job, server-side keys, a person one click away.
- How we build a client reporting dashboard on Supabase
How we structure a reporting dashboard: sources into an automation, clean rows into a database, a chart layer on top, and why we removed Metabase.
- How we automated our own follow-up sequence
The three workflows behind our own outreach follow-up: the AI drafts, a person sends, a reply stops everything, and a no is recorded.
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.