The stack if you want to know
Most of our clients don't care about this page, and that's fine. But if you're evaluating us technically, or you're the person who has to sign off on what goes into your infrastructure, here's exactly what we use and why.
No black boxes. No vendor lock-in pitch. Just the actual tools and architecture.
n8n
Every automation we build runs on n8n, an open-source workflow automation platform that handles triggers, logic branching, API calls, and integrations in a single visual pipeline.
We chose n8n because it gives us fine-grained control over every node in the workflow without abstracting away the logic. When something goes wrong, we can see exactly where and why, not just that something failed.
Each client's workflows are isolated. Your data doesn't touch another client's workflow under any circumstance.
VAPI
Our Phone Receptionist is built on VAPI, a voice AI platform designed specifically for building production phone agents. It handles call routing, speech-to-text, LLM inference, and text-to-speech in a single low-latency pipeline.
VAPI's end-of-call webhook fires a structured JSON payload (caller ID, transcript, call duration, and metadata) into our n8n workflow, which then scores the lead, logs it, and fires alerts.
Average latency from speech to response is under 800ms in production. Callers experience a natural conversation, not a robotic pause.
Scoring & Routing
Lead scoring runs through a custom JavaScript scoring engine inside n8n, backed by Groq for fast LLM inference on unstructured inputs like email bodies and call transcripts.
Scoring factors include job title seniority, company size, industry vertical, inbound source, and intent signals extracted from message content. Scores map to three tiers: Hot, Warm, and Cold. These determine routing, follow-up cadence, and alert priority.
For the Automated Receptionist Suite, RAG (retrieval-augmented generation) is used to pull answers from a client-specific knowledge base stored in Google Sheets, ensuring responses are always grounded in your actual business information.
What we connect to
Gmail / IMAP
Inbound email parsing, outbound sending, reply detection
Google Sheets
Lead logging, knowledge base, CRM-lite for smaller clients
Google Calendar
Booking detection, availability checks
Calendly
Appointment booking link injection and booking confirmation
HubSpot CRM
Contact creation, deal logging, pipeline updates
Slack
Hot lead alerts, meeting notifications, internal ops
WhatsApp (Twilio)
Real-time SMS/WhatsApp alerts for time-sensitive leads
Twilio SMS
Outbound SMS sequences, opt-out handling
Hunter.io
Email discovery for outbound prospecting workflows
What happens to your data
We come from a cybersecurity background. Data handling isn't an afterthought. It's part of the architecture.
Customer data processed by your workflows stays in your own Google Sheets and CRM. We don't aggregate client data, we don't train models on your leads, and we don't store sensitive contact information in our own databases.
Credentials are stored in n8n's encrypted credential store, never in workflow code, never in plain text. API keys are scoped to the minimum permissions required for each integration.
If you have specific compliance requirements such as HIPAA, PCI, or SOC 2, tell us on the intake call. Some configurations require additional setup; we'll be straight with you about what's possible.
Want to go deeper?
If you have architecture questions, integration edge cases, or security requirements, book a technical call. We'll go into as much detail as you need.
Book a Technical Call