Comp AI's agentic CRM, or an approval boundary the agent cannot cross?

Where Comp AI's CRM wins

It proved the demand is real, and has since proved more than that. The research file this page reads — docs/strategy/COMPETITOR_MAP.md — recorded 4.4k GitHub stars on August 4, 2026; a re-check dated August 20 records 8.7k stars, 1.0k forks and 211 commits, under an MIT licence, TypeScript end-to-end on Next.js, NestJS and Prisma. Its thesis is an autonomous background agent with a work queue, evidence-based facts and a sandboxed design the file calls genuinely novel. If what you want is a CRM in which the agent is a worker inside the product, that is its entire thesis — and nothing in this framework attempts it. No autonomous sales agent ships here. Durable jobs, a transactional outbox and scheduled asks exist for self-hosted applications that explicitly start a worker. Nothing autostarts; a timer opens an ask, never makes a decision, and no managed worker service or recurrence is included (L-04).

It is also far simpler to stand up. The file records deployment as three Vercel deployments. This project's hosted form is the managed Cloud, limited to Blueprint-configured workspaces unless a paid Dedicated Cell runs custom code (L-07) — with no authentication ships, and a deployment must supply the verifier (L-01), SQLite or dedicated-database PostgreSQL persistence (L-02), and an npm scaffolder shipping the dated 0.1.0 source snapshot or a current-checkout bootstrap; upgrading means merging source (L-08).

Where this is different

The direction of the agent. The file's sentence is exact: the agent is in the product, not building it. Here it is the reverse. The application is generated as code in your repository — a module manifest becomes a migration, a service, a REST resource, an SDK method and Admin screens (C-01) — and the runtime surface an agent gets is refusal-shaped rather than autonomous. Commercial policy is deterministic code, and a renewal at or above the threshold stops and waits for a named human (C-03). An agent actor asking to approve a discounted quote is refused with a 403 and code HUMAN_APPROVAL_REQUIRED, and only a human user actor can decide (C-21). The refusal is asserted by a test, so the boundary is a property of the system rather than a promise in a README (C-04), and every mutation leaves an audit event and a step-level trace behind it (C-16). Autonomy is not the pitch here; the approval boundary is.

Ownership shape. The file records Comp AI's customization as none meaningful — fixed schema, single-tenant, Vercel-coupled — with no MCP and 18 internal agent tools. Here the schema is whatever your manifests declare, generated into source you own and evolve through explicit revisions (C-01), and the lock-in the file records for this framework is none by design — a framework as dependency, though today that means copying source rather than installing one (L-08).

The measurement caveat cuts both ways, and on the August 20 re-check it cut against this page. An earlier version of this paragraph reported 81 commits behind those stars and called the project a manifesto rather than a platform. The file now records 211 commits, working authentication, a durable scheduler and live providers — three things this framework does not have (L-01, L-04, L-05) — so that verdict is withdrawn here rather than quietly edited away. What the file does still record is that it ships no MCP server. The same file warns that stars in this category are marketing-inflected, citing Krayin at 23.6k stars with modest activity, and says to measure forks, usage and benchmarks instead. Held to its own standard, this project's benchmark has not been run, so no measured comparison exists in either direction and none appears here (L-03).

How to choose

Choose Comp AI's CRM if you want an autonomous CRM worker inside a product today; if MIT licensing, a TypeScript-end-to-end stack and Vercel deployment fit; and if the fixed schema and single-tenant shape the file records are acceptable for what you are running.

Choose this framework in the narrow case: the deliverable is a bespoke commercial process as reviewable code in your repository, where the agent does the writing and a human owns every approval — and you can supply deployment authentication, hosting, connector mapping and complete personal-data operations; dedicated PostgreSQL and bounded customer imports already exist (L-01, L-02).

If the question is which agent should touch revenue decisions, the two answers differ in kind rather than degree: theirs works the queue, and this one is stopped at the approval and told to wait for a person. Choose by which failure you would rather explain afterwards.

What this comparison does not cover

No hands-on evaluation. Nothing from Comp AI was installed, configured, benchmarked or run in producing this page. Every fact traces to docs/strategy/COMPETITOR_MAP.md, researched on August 4, 2026, and this environment has no network access to re-verify any of it.

No review of the evidence model or the sandbox. The file records the design as genuinely novel and does not describe how it works, so this page cannot and does not.

No feature matrix and no pricing. The file carries neither for Comp AI, so no statement about its CRM features, data model or cost appears here.

The commit and star figures are a snapshot from one date, in a category where the file itself says stars are marketing-inflected. Check the current repository before drawing conclusions from either number.

No build-rate or speed comparison in either direction — the benchmark has not been run (L-03). When the competitor research is refreshed, this entry must be re-read against it.