Put AI on the work you already do.
Automations between your tools. Claude and platforms you already pay for. Chat on the website. A phone that answers. Internal apps that use AI. Quoted on the job — not a demo that dies in a week.
- Your toolsClaude and the rest
- Front doorchat and the phone
- R6 000website chat from
The work is stuck on a person.
If the business only moves when someone copies, answers, or remembers, you do not have a process. You have a bottleneck.
- The same email, written twenty times a week, with last week's details still in it.
- The phone rings out. After hours, it dies in voicemail.
- People ask the same questions on the website, then leave because nobody is there.
- The handoff is a WhatsApp. Status is whoever last replied.
- Someone copies from the form, into the sheet, into the inbox, every time.
- The team has Claude or ChatGPT, and the knowledge lives in one person's chat history.
We put AI on the work. People keep the exceptions.
What this actually covers.
Automations
When the form lands, the next step fires. No one copying between the inbox, the sheet and the CRM.
Claude, and tools you already pay for
Projects, knowledge, the jobs the team actually runs — set up in Claude or the platform you already use. Not a blank chat nobody opens twice.
Website chat
Answers the questions you already answer ten times a day. Hands off to a person when it should not guess.
Phone receptionist
Answers, takes the details, books or routes. A person still handles the conversation that actually needs a person.
Internal apps that use AI
The system people log into, with AI on the repetitive bits — drafts, sorting, the next field from the last one. Not a chatbot glued on the side.
App development →Map it first
Who touches what, what "done" looks like, where it dies. Automating a mess just makes the mess faster. If it is not ready, we will tell you.
AI types
What a job can include.
- A map of the process before we switch anything on
- Automations between tools you already use
- Claude or the platform you already pay for, set up for the team
- Website chat that can hand off to a person
- A phone that can answer, take details, book or route
- AI inside an internal app where it earns it — from R25 000 on the app page
Answers the questions you already answer ten times a day. Hands off to a person when it should not guess.
- Answers the usual questions and can take an enquiry
- Hands off to a person when it should not guess
- Can land in Linkssi or the inbox you already have
- Sits on the site you already have
- Phone receptionist quoted separately
The team already pays for Claude. We set it up for the actual jobs — knowledge, projects, the way you work — not a blank chat.
- Projects and knowledge for the real work
- The whole team can use it, not one person's chat history
- Claude or the platform you already pay for
- Your subscription stays yours
- Platform fees not included
When the form lands, the next step fires. Nobody copying between the inbox, the sheet and the CRM.
- Connect the tools you already have
- The next step fires without a person in the middle
- Wired to the site, CRM or inbox where it saves a step
- We don't add a sixth login for the sake of it
- Platform fees not included
Prices are set in South African rand. Dollar figures are an approximate conversion — we quote in your currency.
These are starting prices. Claude, phone numbers and usage are billed by those providers. A phone receptionist is quoted on the job. AI inside an app is on the app page, from R25 000.
Not sure which one it is? Send the work that eats the week and we'll say.
Get a quoteQuestions we get about ai workflows.
Is this ChatGPT with our logo on it?
No. It might be automations between tools you have, Claude set up for the team, chat on the website, a phone that answers, or AI inside an app. Sometimes more than one.
Will it replace people?
It replaces the copying, the chasing, and the tenth time you answer the same question. The exceptions, the client conversation and the sign-off stay with whoever already owns them.
Do we need an app built first?
No. Often the first move is Claude, an automation, or chat on the site you already have. If it does need an app, we will say so before you pay for both. More →
Can you set this up in Claude?
Yes. From R8 000. Projects, knowledge, the way the team actually works — in Claude or a platform you already pay for. That is often cheaper and faster than building a new login.
Do you have a starting price?
Website chat from R6 000. Claude and tools you already use from R8 000. Automations from R12 000. Phone receptionist is quoted on the job. AI inside an app starts on the app page, from R25 000. More →
What do chat and the phone actually do?
Chat answers the usual questions and can take an enquiry. The phone answers, takes details, and can book or route. Both hand off to a person when they should not guess.
What if our process is a mess?
Then we map it first. Automating a mess just makes the mess faster. If it is not ready, we will tell you.
Can it use Linkssi contacts?
Yes, if that is where the enquiry already lands. Same idea as Smart Sites — one record, the next step fires. More →