Compare
Not a feature war. A job-to-be-done map.
Search loves “vs” pages. Operators need honesty. Here is when Craft11 should be on the shortlist - and when you should pick something else.
| Job | Usual category | Craft11 position | How to choose |
|---|---|---|---|
| Full marketing & sales cloud | HubSpot-class platforms | Narrower: service ops spine + memory + controlled AI for small firms. Not a GTM suite. | Pick the cloud if marketing automation breadth is the job. Pick Craft11 if operational chaos is. |
| Flexible docs & wikis | Notion-class tools | Enforced Client→Inquiry→Offer→Project→Invoice + acting co-pilot. Not a blank canvas. | Notion for writing gardens. Craft11 for commercial continuity. |
| Sales pipeline only | Pipedrive-class CRM | Full service path through delivery and invoice, with compounding memory. | CRM if deals are the whole product. Craft11 if delivery + memory matter. |
| ERP depth (finance, stock, manufacturing) | Odoo-class ERP | Not an ERP. AI operations layer for service SMEs. | ERP for module depth. Craft11 for service-ops clarity. |
| General AI writing & chat | ChatGPT / Claude alone | Company-grounded path, private memory, structural human approval on binding steps. | General models for open work. Craft11 for running the firm’s spine. |
| “AI CRM” checkbox on old software | Legacy CRM + bolted chat | Structure + act + memory + gates designed as one system from day one. | If AI only drafts text next to dead fields, you still rebuild context by hand. |