tobto.Book a demo

Integrations

Data comes in from the systems you already run. Work goes back out to them. What happens in between is recorded, with the source attached.

In

Your existing systems, and third-party enrichment, keyword, and advertising data. Everything imported arrives as an observation with its source recorded — never as a decision.

Out

Work written back into the same stack it came from. Nothing is sent on your behalf: the write-back is data, not outreach.

What enters as what

The useful question about an integration is not which logos are on the page. It is what happens to the data once it arrives — and whether a machine can change what your company believes.

Imported from your systems
Observed
Contacts, content inventory, past performance, existing copy.
Third-party data
Observed
Market facts, volumes, competitor moves.
An agent, reading either
Inferred
Proposals — for the customer definition, the positioning, the voice. Proposals only.
A person
Decided
The decision itself. This is the only row that can produce one.

An agent can propose. Only a person decides. That is a rule about who holds the pen, and it is enforced in the system rather than promised on a page.

What an assistant can reach

The store is plain markdown under version control, not a database behind a proprietary API. Reading it is a property of that shape rather than a feature anyone had to build — whatever can read a repository can read the state.

The ceiling is the one every agent already works under. Something reading the store can read it, and it can propose. It cannot decide. There is no read path that becomes a write path.

The connected list

No integration is listed here yet. A tool appears on this page once it has been checked against its own documentation, on a dated review — not when a connection is planned.

See the system running on itself

We read your website to get started.