---
# /integration/ - imported from the company-brain draft (integration.md v1,
# 2026-07-09). Optional page: answers "will this integrate with our mess,
# fast?" as METHOD, never as inventory - no vendor names, no support matrix,
# no catalogue.
title: 'Integration'
description: "How blocks connect to the systems a firm already runs - read, don't replace; build only the connectors the block needs; hand over ownership."
slug: 'integration'
noindex: false # launched 2026-07-24
---

# Integration is not the project.

The framework reads from the systems you already run. A new source is a new
receptor, never a new pipeline - and never a migration. Nothing is replaced,
nothing is moved, and no eighteen-month data programme stands between you and
the first signal.

---

## 01 · Start with the object, not the systems

Integration effort is scoped by the block, not by the estate. The block defines
what needs sensing - the signals its loop actually reads - and only the
connectors that block needs get built. A cash block does not wait for the HR
system; an account block does not wait for the payments stack.

## 02 · What we typically read from

Connectors we commonly build:

- email and calendars
- the CRM
- practice, case or policy systems
- billing and finance ledgers
- document stores
- payment providers
- screening and regulatory feeds

The named connectors - what is available today and what is coming - are
listed on [our framework](/ai-native-company/). Each is built or adapted per
engagement, around your environment as it actually is.

## 03 · Read before replacing

A signal is captured once at the receptors, typed, indexed to the objects it
touches, and shared by every block that needs it. That is why the integration
surface shrinks as blocks accumulate rather than growing with every tool: the
second block finds most of its signals already flowing, because the first block
put them on the spine.

## 04 · What's handed over

The connectors built for your engagement are part of the handover - documented,
owned by your team, yours to extend. Integration is not a dependency on us; it
is an asset you keep.

## 05 · What we don't claim

No universal schema. No zero-effort integration. The claim is narrower, and
true: the first signals flow in days, not months, because the block only
needs what the block needs.

---

**Start with the diagnostic.** It includes a signal audit - which of the
signals your first block needs already exist in your systems, and where they
live. Take [the ten-minute diagnostic](https://benchmark.somai.studio), or
write to [hello@somai.studio](mailto:hello@somai.studio?subject=The%20block%20diagnostic).