Your next customer might not be a person.

The diagnostic

Run the six-point check.

Six things decide whether an AI assistant can find you, understand what you sell, and place an order. Tick what's true of your business today.

FINDABLEAI crawlers are allowed to read your site — not blocked in robots.txt. FINDABLEYour business is described as structured data: name, services, location, contact. READABLEYour prices, service area and hours are written in plain text — not only in a PDF or an image. READABLEThere's a summary written for AI: what you sell, who it's for, how to buy. ORDERABLEAn AI can book or order through an API, not a human-only form. ORDERABLEAgent orders land behind an approval step and are logged.

Invisible to agents

An assistant can't find you, so it recommends someone else.

A low score is the easy part to fix. The harder part is what happens after an order lands.

How it works

Four functions, wired through the tools you already have.

Synapse isn't another tool to log into. It's the layer that connects the ones you use.

Sense

Agents watch where work arrives.

Email and WhatsApp
Forms and documents
Payments and invoices

Think

Each signal is read in context, against your rules.

Priority and intent
Your business rules
Human approval gates

Act

Decisions become motion, in the tools you already use.

Automated follow-ups
System updates
Escalation to a person

Remember

Everything is written to a permanent trail.

Full audit trail
Why each action ran
Reports on demand

What we build

Three ways in. Most clients start at the first.

Being findable is where it starts. What happens after the order lands is where it pays.

Entry point

Agent-ready website

Clear and fast for people, structured and orderable for machines. Most businesses fail the check above on their website alone.

2 weeksFrom first call to live

Structured data and /llms.txt
Booking endpoint, spec'd
Copy and structure, not just design

Where most clients end up

Agent pathways

Agents wired through the work behind the order — quoting, onboarding, invoice chasing, follow-up — so what gets booked actually gets handled.

3–6 weeksPer pathway, depending on the systems it touches

Mapping session before we quote
Measured in hours returned
Connected to your existing tools

For established teams

Internal software

When the tools themselves are the problem. A system that matches how you work, owned outright, no per-seat pricing.

Scoped after mappingTimeline agreed before anything starts

Replaces two to five subscriptions
Your data, your database
Handover and training included

The safeguard

Automation without accountability is a liability.

If you can't see what an agent did, you can't undo it. So it's built in first.

Nothing invisible. Every agent action is logged with its trigger and its reasoning.
Nothing reckless. Sensitive actions wait behind approval gates you define.
Nothing locked in. Your data stays in your tools. Synapse is the wiring, not the vault.

The process

Three steps, no long contracts.

Map

We follow one process end to end with whoever does the work, then send you the map and a fixed quote. Yours either way.

Build

Fixed scope, fixed price, agreed before anything starts. You see working software each week, not a status update.

Hand over

Documentation, training, and the keys. Ongoing support if you want it, not because you're locked in.

Questions

The ones we get asked first.

What does it cost?

A number before we've seen your process is a guess. What it depends on: how many systems the work touches, and how much runs without a person. The mapping session is free — afterwards you get the map and a fixed price, not an estimate.

Isn't this still years away?

The businesses that waited to take Google seriously never got a warning. The phone just rang less. By the time they worked out why, the competitors who'd built a website were years ahead. Doing it now costs little; doing it after your competitor has costs you the lead.

How long does it take?

A website is about two weeks. An automation pathway is three to six, depending on how many systems it touches. Internal software is longer and scoped after mapping.

What happens if you disappear?

Everything runs on infrastructure you own and control, and you get the documentation at handover. Another developer can pick it up. That's the point of owning it.

Where do you work?

We're based in Cape Town and work with clients globally. Everything runs remotely and we build against the tools you already use, wherever they are.

What if automation isn't the answer?

Then we say so. Some processes are broken rather than slow, and automating a broken process just makes it fail faster.

Run the six-point check.

Four functions, wired through the tools you already have.

Three ways in. Most clients start at the first.

Agent-ready website

Agent pathways

Internal software

Automation without accountability is a liability.

Three steps, no long contracts.

Map

Build

Hand over

If AI wanted to order from your business, could it?

The ones we get asked first.