AI integration for ERP, CRM and the tools in between.
Connecting AI to the systems you already run — CRM, ERP, accounting, internal tools — without breaking them.
The problem this solves
An AI feature that cannot read your CRM is a demo. Integration is the actual work: authentication, data shape, idempotency, rate limits, and what happens when the other system is down.
How the work runs
- Inventory the systems, their APIs and their limits.
- Define the data contract: what is sent, in which shape, with which key.
- Build the connector with retries, backoff and idempotency.
- Add monitoring so failures are visible before the client notices.
- Hand over documentation and a runbook.
Systems I connect
Proof
Intake service connected to Postgres with an outbox pattern: every message written to an outbox first, retried with jittered backoff, moved to a dead-letter queue after four attempts, replayable with one endpoint.
How to engage
Process Assessment — $249: one process analysed, bottlenecks and cost identified, proposed architecture and a written plan. Then an Automation Pilot from $999, or an ongoing technical partnership. Card via Creem or contract with an invoice.
Questions people ask
Our ERP has no API. Can you still integrate it?
Sometimes via database access, file exchange or RPA-style automation. The assessment says which option is realistic.
How do you handle outages of the other system?
Queue and retry with backoff, dead-letter after N attempts, and an alert. No data is lost silently.
Is our data used for model training?
No. Client data is not used to train models, and can run on local models where required.
Dejan Milošević · Independent AI Systems Architect · Belgrade, Serbia · Privacy