Our stack
The tools we build on, and what can be swapped
Most builds use three tools: n8n for workflows, Claude for language tasks and GoHighLevel for CRM and messaging where a client wants it. This page says why, what each costs you directly and which parts are replaceable.
From a customer message to your systems
- Customer channel (Messenger, Viber, WhatsApp), Your side
- Workflow engine (n8n), Tools we build with
- AI model (Claude), Tools we build with
- CRM and booking (GoHighLevel or yours), Tools we build with
- Your systems and staff (Sheets, calendar), Your side
n8n for workflows
Why
Connects things that do not connect by themselves
n8n links messaging channels, sheets, CRMs and APIs in visible workflows that another person can open and read later.
Hosting options
Self-hosted or n8n Cloud
n8n can be self-hosted on your own infrastructure, in a private cloud, or run on n8n's hosted service. We choose with you based on where data may sit and who will pay for what.
What you own
Workflows in your n8n account
Where the plan allows, workflows sit in an n8n instance that is yours, and the handover notes say how to open and change them.
Claude for language tasks
Why
Reading and writing replies
Claude reads a message, finds the answer in your approved information and writes a reply in plain words, or says it does not know.
Data-usage terms
Terms for customer content
Anthropic's commercial terms state that Anthropic may not train models on Customer Content from its services (terms effective 17 June 2025). We re-read them before each build.
Alternatives
Other model providers
The design is not tied to one model. Where your policy or an existing contract points to another provider, the build can use it, and the scope names the one chosen.
GoHighLevel for CRM and messaging
Why
One place for contacts, pipelines and booking
For businesses without a CRM, GoHighLevel holds contacts, follow-up pipelines, calendars and some messaging in one account.
When yours stays
If you already use a CRM
If your team works in HubSpot, Zoho, a sheet or another tool, the build connects to it. Nothing here requires moving your records.
Channel platforms and their rules
- Meta (Messenger)
- Messenger bots follow Meta's Messenger Platform policy, including the standard messaging window for replying after a customer's last message.
- WhatsApp Business Platform
- Needs a Meta business account. Messages the business starts use approved templates and the customer's opt-in. See the Cloud API overview.
- Viber
- Per the Viber bot API documentation, bots can only be created on commercial terms, through Viber or an official partner. We confirm this route before planning a Viber assistant.
- Voice
- A phone assistant runs on a voice platform and a phone number from a provider. The scope names both and who is billed for them.
Component by component
| Component | What we usually use | Can be replaced by |
|---|---|---|
| Workflow engine | n8n | Make, Zapier or Power Automate, with the workflows rebuilt |
| AI model | Claude | Another model provider, if your policy requires it |
| CRM | GoHighLevel | Your existing CRM or a sheet |
| Channels | Messenger, Viber, WhatsApp | Whatever your customers use. These are their choices, so we adapt to them |
Replacing a component changes the build and is scoped as part of the project.
In your name, billed by the vendor
In your name
- Accounts for the tools, wherever the tool allows
- Your customer data and conversation history
- The workflows and assistants built for you
Billed by the vendor
- The n8n plan or hosting
- AI usage fees for the model
- GoHighLevel or another CRM plan, if used
- WhatsApp and other messaging fees set by the platform
Partner status
This page claims no partner, reseller or certification status with any vendor named here. If that changes, it will be stated on this page. Vendor names are trademarks of their owners.
Questions we get asked
Can you build on tools we already pay for?
Often yes. If you already use a CRM or a workflow tool, we check what it can do in the assessment and build on it where it makes sense.
Which subscriptions will we pay directly?
The tool vendors bill you for their plans, usage and message fees. Our fee covers scoping, building, testing and handover, and any support is quoted on its own.
What happens if a vendor changes its terms?
We re-read the terms before each build, and platform changes can affect a running assistant. Support, if you have it, covers updating the build when a vendor changes something.
Next step
Check whether your tools fit.
List the tools you already use and we will say what the build would reuse and what it would add.