Folk vs Twenty
Side-by-side trajectory, velocity, and editorial themes.
Folk wraps an autonomous AI layer around its CRM data hygiene work.
Folk is on a near-weekly cadence with two parallel arcs: AI-driven enrichment and outbound communication. Auto-fill AI in late April promises continuous, autonomous data cleanup and insight extraction. Email scheduling, send previews, and the Fireflies integration build out the relationship-management surface. Admin visibility and sender-control tweaks address compliance edges.
Folk is positioning as the CRM that keeps itself current without operator effort: AI fills records, conversation tools feed context, and scheduled outreach closes the loop. The directional bet is that small teams will pay for autonomy over data hygiene, not for more fields to fill in manually. Expect more autonomous workflows that span enrichment, segmentation, and outreach.
The next directional move likely turns Auto-fill AI into named, scopeable autonomous routines (lead-research agent, dedupe agent) rather than a single setting. Deeper Fireflies-style integrations with other meeting tools should follow.
Twenty's open-source CRM hits v2.5 while wiring AI agents and credit-metered billing into the workflow core.
Twenty is shipping fast on its v2.x line, with five releases across April and May pushing AI agents as first-class workflow nodes and rolling out a billing v2 that meters AI credit usage. The release cadence shows the cost of that ambition: a string of cross-version upgrade hotfixes, agent-node execution bugs, and modal-loading regressions has accompanied the new surface area. The team is leaning into incremental hotfixes (v2.5.0 to v2.5.3 within four days) rather than batching.
AI agents and credit-based metering are becoming structural to the product, not optional add-ons — the architecture is being reshaped to gate billing at AI entry points rather than per workflow step. Meanwhile the workspace migration runner keeps surfacing cascade-dependency bugs as the schema evolves, suggesting an underlying brittleness that will need a structural fix. The pattern is: new capability ships, upgrade paths break, hotfix lands.
Expect a consolidation release that hardens the workspace migration runner against cascading column dependencies — the recurring pattern of fixing this case-by-case (v2.5.0, then the band-aids in #20581/#20583) signals a refactor is overdue. AI agent capabilities will continue expanding as the credit-cap architecture matures.
See more alternatives to Folk →
See more alternatives to Twenty →