1,000+
conversations per month
Representative workload from published comparable WhatsApp deployments.
Portfolio
Real systems, built for real businesses. Client identities and production metrics are confidential — the architectures are not.
Where exact client figures cannot be disclosed, representative metrics are informed by published industry case studies and benchmarks, and are labelled as such.
Case study
Built on n8n, Python, Meta Business and the official WhatsApp Business API, powered by Claude. One multi-industry architecture serving cleaning, insurance and travel businesses — in English and Spanish.
The handoff is designed, not accidental: on low confidence, an explicit request for a person or a sensitive conversation, the agent stops and delivers a summary — contact, intent, history, suggested next action — so the customer never repeats themselves.
Assistant
online 24/7
Hi! Do you clean offices? How much for ~200 m²?
We do! For ~200 m² a deep clean starts at $X. Want a free on-site quote this week?
Yes — Thursday afternoon?
Thursday 3:00 PM is open. Booked ✓ You'll get a reminder the day before.
Handoff: pricing exception → forwarded to a human with full context.
1,000+
conversations per month
Representative workload from published comparable WhatsApp deployments.
~65–70%
of routine interactions automated
Representative range from comparable published AI-agent deployments.
~3 weeks
to production
Representative timeline for a scoped WhatsApp deployment.
Case study
A Python daemon running 24/7 on a VPS. Nothing publishes without human approval — every piece passes a Telegram review first. Currently the content infrastructure behind two web properties, including the blog on this site.
38AI agents
8 specialised departments, one orchestrator.
Model routing by cost and difficulty, daily budget with kill-switch. Internal technical cost: ~$0.10/post — model usage only, excluding human review, infrastructure and distribution.
EN/ES output with a voice profile per language, auto-maintained sitemap and blog index, and a hard "never invent statistics" grounding rule.
7+ articles published on this site's blog, both languages. ai-gentlab.com is the live demo.
The productised version (in development): a modular skill engine with fail-closed QA, self-revision, credit billing and SEO/GEO skills for AI-engine citability.
Content OS · approval
Ready to publish
"5 workflows your team still does by hand"
Blog EN + ES · LinkedIn · X — scheduled Mon 09:00
Third-party industry benchmarks — not measurements of this system.
Case study
Built for an insurance agency's real sales process — HubSpot's methodology as inspiration, none of its rigidity. It replaced spreadsheets and inboxes with a single source of truth: leads, pipeline, tasks, follow-ups, scoring and history in one place.
Automatic lead scoring
Source, intent, interaction, stage and recent activity — the team opens the day knowing who needs attention.
Context before every contact
The full conversation history, summarised before each touchpoint. No scrolling through months of notes.
Follow-ups, drafted
AI drafts and next-best-action recommendations. Where commercial judgement is needed, it proposes — never executes alone.
No lead left behind
Leads without recent follow-up surface before they go cold, not after.
Lead · Example S.
Proposal stageAI score: high intent
Auto-renewal quote requested · 3 interactions this week
AI suggests: call before Thursday — policy expires in 12 days.
~10
team members supported
Representative deployment size.
500+
active lead records
Representative CRM workload.
The FairBuild case is the published deployment behind the representative figures above.
Beyond the case studies
Organised by the four services behind them.
24/7 receptionist, lead qualification, appointment setting — with human handoff and outcomes synced to your CRM. Retell AI or similar + Twilio + n8n.
Published stack results: 17,000+ calls, 200h saved/mo ↗ · 65% containment, 600h/mo ↗
In production today: the approval bot behind our own content system. Human-in-the-loop from a chat, without touching a server or CMS.
WhatsApp, web chat, email, voice and Telegram — EN/ES, with routing to a person by intent, risk or confidence.
Fleets of specialised agents: one model per task, budget controls, automatic QA, human checkpoints, logging. Ours runs 38 agents in 8 departments.
We don't sell "automations." We remove the manual steps between the tools your business already uses — the Portland Trail Blazers cut a 50h/week manual process to 3h ↗.
HubSpot pattern: lead from form/WhatsApp/call → contact updated → AI classification + score → summary attached → task + owner → automatic follow-up, escalation past a threshold.
The full pipeline from the case study above — research, drafting, QA, human approval, publishing, repurposing, analytics — as a service.
Your team shouldn't have to remember where the answer lives. At the far end of the scale, Nubank's internal knowledge tools reach 5,000+ employees monthly ↗.
PDFs, SOPs, docs and FAQs → vector search, hybrid retrieval, reranking, permission-aware access — with cited answers, eval sets and guardrails.
Employee knowledge assistants, support copilots, policy lookup, SOPs, sales enablement, onboarding — standalone or wired into agents and CRMs.
This site is the live demo: bilingual architecture, structured data, internal linking, automated sitemap and GEO for AI-engine citability.
Sales, attribution, funnel, pipeline value, response times, automation health — one operational view instead of scattered spreadsheets.
Clock-in/out, job assignment, timesheets, supervisor approval, payroll export. Built for teams tired of hours arriving over WhatsApp. Optional GPS, always with consent.
Our internal venture: research, content, SEO/GEO, distribution, lead capture, CRM and reporting — with human approval at critical checkpoints.
Client identities and production metrics are confidential. Figures labelled "representative" are informed by published industry case studies and benchmarks from comparable deployments — they describe what architectures of this type achieve, not audited results of a specific confidential client. Third-party statistics link to their original sources. UI mockups are illustrative recreations, not real customer data.
Tell us what eats your team's hours. We'll tell you which of these architectures fits — including when none of them does.
Let's talk