AI / CAPE TOWN, ZA

AI, wired into the work you already run.

We connect AI to the software, records and workflows your business already uses. An agent has one job, the tools to do it, and a person who can stop it. Then we write it down and hand it over.

Talk to an engineer See how it is built
FIG. 01 — THE AGENTSCROLL
01WHAT AN AGENT IS

One job. The tools for that job. A person who can stop it.

  1. 01

    Inside the systems you have

    The model reads and writes where the work already lives: your software, your records, your inbox.

  2. 02

    A person stays in it

    An agent does a defined job. Someone can see what it did, and stop it when they should.

  3. 03

    Handed over, limits and all

    Prompts, connections, logs and access, in your name. No black box and no lock-in.

02WHAT WE DO

AI for the work you already do.

The same team that builds your software and looks after the office. We put AI where it earns a place, and we leave it out where it does not.

01 SYSTEMS

Into the systems you run

The CRM, the database, the internal tool, the inbox. We connect a model to the systems that already hold the work, through the same permissions your team uses.

  • Your software and CRM
  • Your database and files
  • The permissions you have
  • A record of every call

Built forTeams who want AI in the work, not in a separate tab.

02 AGENTS

An agent with one job

An agent is software that can read, decide and take a step: file a record, draft a reply, ask for an approval. It gets one job, the tools for that job, and a point where a person takes over.

  • A job, written down
  • Only the tools it needs
  • Approval before it acts
  • A log of what it did

Built forA repeated task that still needs judgment.

03 KNOWLEDGE

Answers from your records

Questions answered from the documents, tickets and records you already keep. Access follows the permissions you have. The source of an answer stays attached to it.

  • Your documents and records
  • An answer with its source
  • Access that follows your rules
  • A way to correct it

Built forTeams who search the same files every day.

04 WORKFLOWS

The repetitive steps

Reading a form, drafting a reply, sorting a request, moving a record on. AI does the part it is good at. A person keeps the part that matters.

  • Forms, mail and documents
  • Drafts a person approves
  • Sorting and routing
  • The step that stays human

Built forOperations buried in the same steps.

05 GUARDRAILS

What it may do

Before anything runs, we write the boundary. Which systems it may touch, what it must never send out, and how a person stops it. Every action can be traced.

  • A written boundary
  • Secrets kept out of the prompt
  • A log you can read
  • A switch that turns it off

Built forWork that cannot be a guess.

06 HANDOVER

Yours when we are done

Prompts, connections, logs and access move into your name. The engineers who wired it in can stay, or your own team can take it. Either way, you can leave.

  • Prompts and instructions
  • Connections, in your accounts
  • Logs and tests
  • A runbook

Built forTeams who intend to own what they run.

03HOW IT IS BUILT

From a job to something you can run.

  1. 01

    Frame

    The job, the data, and the line it must not cross. We agree those before anything is connected.

    You get — a written brief
  2. 02

    Connect

    We join it to the systems that already hold the work, with the permissions your team already has.

    You get — a working connection
  3. 03

    Try

    A small version on real work, with a person watching. You see whether it earns its place.

    You get — something you can try
  4. 04

    Guard

    Logs, limits, and a stop. What it may touch is written down, and what it did can be read back.

    You get — a boundary you can read
  5. 05

    Hand over

    Prompts, access and the runbook move into your name. You can keep us, or you can take it.

    You get — the keys
  6. 06

    Stay

    We keep it with you, or your team runs it. Either way it stays documented, and it can be switched off.

    You get — a way to continue
04WHAT YOU OWN

You can read it. You can leave with it.

No lock-in and no black box. When we hand over, you have what it takes to run the AI, change it, or turn it off — with us, or without us.

  • 01PromptsThe instructions, in your repository.
  • 02ConnectionsHow it reaches your systems, in your accounts.
  • 03LogsWhat it did, so the next question has an answer.
  • 04LimitsWhat it may touch, and what it must not.
  • 05TestsSo a change does not quietly change the job.
  • 06A way outAccess in your name, and a switch that stops it.
05WAYS TO START

Start with the job, not with a model.

A YOUR SYSTEMS

Wire it into what you have

AI joined to the software, records and inbox you already run. Same permissions, a log, and a person in the loop.

Talk it through B ONE JOB

An agent for one job

Pick one repeated task. We give an agent that job, the tools for it, and a point where a person takes over.

Name the job C YOUR RECORDS

A first version on your data

Answers from the documents you already keep, with the source attached, so you can see whether it earns a place.

Start with the records
→YOUR MOVE

Tell us the job. We will say if AI belongs there.

You will talk to an engineer, not a salesperson. If it should not be automated, we will say so — and you will still leave with a clear next step.

Talk to an engineer info@saltonsync.com