Developer-Led CRM: What Engineers Actually Want From Customer Software
In developer-led companies the CRM is chosen by people who will build against it, not click through it. That flips the evaluation criteria.
What developers look for
A real data model. Companies, people, deals, tasks and activities with stable identifiers and clear relationships.
Clear, versioned APIs. A versioned REST API for your own code, and MCP tools with defined inputs for agents.
Predictable errors. Conflicts, denials and rate limits as distinct, structured responses, not a 200 with a warning buried in the body.
Safe retries. Write operations that accept an idempotency key so a retry cannot create duplicates.
What developers avoid
- Seat pricing that makes service accounts expensive.
- Permission systems that only make sense in the UI.
- “AI features” that cannot be replaced with the team’s own agents.
- Programmatic access that bypasses the controls the UI enforces.
Why governance is a developer feature
The most dangerous code path is the one nobody tested. A narrow agent write surface is a testable invariant. Row-level security in the database is a testable invariant. Governance is not a compliance checkbox; it is the system being designed properly.
How AI PRO CRM approaches it
- REST API v1 for humans. Create, read, update and archive companies, people, opportunities, tasks and activities, plus search, agents and audit events. Access follows the user’s workspace role; tokens are personal, with no per-token scopes, and cannot currently be created in the product UI.
- Optimistic concurrency. Updating a record that someone else changed first returns 409 with a stale_record error, so a stale edit cannot silently overwrite a newer one.
- MCP for agents. A remote Streamable HTTP endpoint with ten read tools and one write tool, activity_note_create, which adds an internal company note and requires an idempotency key.
- Per-agent credentials. Bearer tokens shown once, stored as a hash, expiring and revocable.
- Forced row-level security on every tenant table in PostgreSQL, which the runtime database role cannot bypass.
- Stated rate limits. 120 MCP requests per minute per credential, 600 per workspace, and 120 REST requests per minute per user.
It has no SDKs, webhooks, CLI, sandbox or import and export. Plan around plain HTTP and MCP.
FAQ
Is there a CLI?
No. There is no CLI or official SDK. The REST API is plain HTTP with a personal token, and agents connect over MCP.
Can we self-host?
No. AI PRO CRM is a hosted service.