Twenty, a modern CRM alternative to Salesforce

Original Article ↗ Hacker News Discussion ↗

An open-source CRM called Twenty is drawing interest as a modern, customizable alternative to Salesforce and other incumbents, but users note it is still early-stage, with gaps around permissions, automation, and integrations. Commenters debate how hard it really is to replace Salesforce, arguing that its true power lies less in core CRM features and more in its ecosystem, programmability, and deep lock‑in at large organizations. The thread also surfaces broader themes: many smaller teams still get by with spreadsheets, niche groups such as academic or nonprofit teams struggle to fit traditional sales-focused CRMs, and licensing choices like AGPL can deter commercial adopters despite the appeal of open source.

Overall reception & positioning

  • Many welcome a modern, open‑source CRM and like the UI and ease of setup.
  • Some feel marketing as a “Salesforce alternative” is premature; they see Twenty as a promising CRM, not yet a full platform.
  • Several say it fills a gap vs older open‑source CRMs that look and feel dated.

Non‑traditional and personal use cases

  • Atypical organizations (academic groups, nonprofits, consortia) want contact/relationship tracking not centered on sales funnels.
  • Desired capabilities include: longitudinal tracking of careers, research interests, engagement history, and funding discussions.
  • Some suggest this is closer to association management software or personal contact managers than classic CRM.
  • Personal users with ADHD or relationship‑tracking needs look for calendar‑integrated “personal CRM” tools.

Features, maturity & limitations

  • Early users report alpha‑level rough edges and missing basics like granular permissions and role‑based access; anyone can currently alter data models.
  • Lack of clear support for custom automation and complex workflows is seen as a major blocker for many business use cases.
  • Questions arise about email/calendar provider support beyond Google.

Salesforce comparison, value, and lock‑in

  • Multiple comments stress that competing with Salesforce means matching the “last 20%”: compensation, billing, contracts, reporting, etc., plus its vast ecosystem.
  • Salesforce is chosen for integration, platform capabilities (Apex, LWC, AppExchange), reliability, and strong admin/rev‑ops community, not just basic CRM.
  • Others note Salesforce’s limitations (slow UI, governor limits, complex contracts, lock‑in) and see room for 80% solutions without those constraints.

Licensing & self‑hosting (AGPL)

  • AGPL raises concern for companies that might embed proprietary business logic into a self‑hosted instance; some fear “viral” obligations, others argue this is misinterpreted and only applies to modified AGPL code.
  • Some note big companies often avoid AGPL entirely to dodge legal complexity.

Extensibility and programmability

  • Strong sentiment that a serious Salesforce competitor must offer a hosted programming layer (triggers, scripts, workflows), not just an API.
  • Others counter that many smaller customers just need a flexible CRM, not a full low‑code platform, and that enterprise‑grade programmability can come later.

Roll‑your‑own vs buying

  • Building a simple, single‑org CRM is considered easy; the difficulty is supporting many orgs, diverse workflows, and integrations.
  • Several warn that rolling your own quickly becomes an internal ERP project; off‑the‑shelf CRMs exist largely because of this complexity.