Guide to success for this project. Invoicing, Stable/pre-release, automation, Messaging.

[Novapixel1010]

I made this so I can have a place to come back to see what is in the works and done. Also to give my input from other projects that have been around long time and are successful.

Features (in order that I think matter most for business clients)

1. • Stable and a pre-release to test new stuff.
2. • Good Docs
3. • automation via n8n
4. • Invoicing via stripe
5. • Messaging
6. • Roles & permission
7. • In-house automation (in the works via workflows)
8. • Calendar to keep track of meetings with clients

Stable

Currently, I am tagging my Docker container manually, but it would be tremendously helpful to have an official section on the website that clearly distinguishes stable releases from pre-releases. This would allow production users to confidently rely on the stable build, while beta testers and early adopters can explore the latest features without confusion.

Automation

Automation should be a core focus so that businesses can dedicate their energy to higher-value tasks. I strongly recommend considering n8n, an open-source workflow automation tool. A great example of its power can be seen in how ERPNext integrates with n8n, enabling simple workflows such as:

• Converting a form submission into a lead, and
• Automatically generating an invoice once an appointment is booked.

This kind of integration provides immediate, practical value and reduces repetitive manual work.

Invoicing

It’s surprising that invoicing isn’t already built in, considering that most CRMs are centered around sales. In my experience, invoicing is a standard expectation, as businesses don’t just want to manage customer data they need to generate revenue. Industries like trades (plumbing, framing, HVAC), photography, and hair salons would all greatly benefit from a built-in billing system. Without it, the platform risks missing a core requirement for everyday use. The project cal.com use stripe so could get examples their. I made a vary rough draft what it should look like

Massaging

If customer information is being collected, there needs to be a way to maintain communication. At a minimum, the system should support basic email messaging, with the option to expand into templates later. Beyond email, support for messaging via Telegram, Matrix, or even bulk SMS through Twilio would make the platform far more versatile for businesses looking to engage their clients directly.

Docs

Good documentation cannot be overstated it often determines whether a project thrives or struggles. For example, ERPNext could have been significantly more popular if its documentation had not been outdated for so long. Even now, some parts remain inaccurate, referencing features that no longer exist or no longer function.
Transparency matters: if a feature is broken, such as the Stripe integration for ERPnext (which has been unreliable for years), that should be clearly stated. Acknowledging limitations builds trust, while leaving outdated or misleading documentation creates frustration. For a project of this scope, accurate and well-maintained documentation is just as important as the code itself. I might even make a pull request to fix some of the docs for this project when I get some time.

Thanks to the Twenty team

Overall, this project is heading in the right direction, and I truly hope the momentum continues. One thing worth noting is that the repository has already earned more GitHub stars than ERPNext, which is a much larger and more mature project in the same space. That’s a strong signal that the community sees real promise here.

[BOHEUS]

Hi @Novapixel1010, thanks for such detailed feedback! About all mentioned items:

• versioning - every version is stable with new features are available in Lab (Settings > Lab) in beta so if someone wants to try a new feature, they just have to enable it there
• automation - as you've already mentioned, in-house automation is currently in progress with more and more features being slowly added to it, I guess end-goal is to have everything in one place so users won't have to jump between providers, there's community n8n library if you want to use it (https://github.com/shodgson/n8n-nodes-twenty) but making your own integration with n8n isn't that hard, just be aware that for some things you may want to use GraphQL API instead of REST (e.g. if you need roles of workspace member, REST API doesn't expose them)
• invoicing - never heard of someone missing invoices before but integrating it isn't that hard with Zapier since it has already a native support for both Twenty and Stripe (https://zapier.com/apps/stripe/integrations), I guess most people made integrations on their own with payment providers
• messaging - until core team abstracts everything, more integrations are out of options unless someone from community does them which may make rewriting later more difficult (as per comment from here Whatsapp Business sync #7296 (reply in thread)) some of them are already planned but mainly for workflows aka in-house automation 🔌 First Integrations (Nodes & Triggers) core-team-issues#219
• docs - while documentation isn't really outdated, I agree with you that docs could be improved, for example there are no information regarding AI features about which there are many questions from community, if you want, you can list missing things in docs and someone will take care of them in nearest future
• calendar - similar request appeared few months ago (Calendar View #10906 (comment)) but I haven't see it on roadmap, I think the hardest part in implementing this is ensuring that permissions are working properly so there won't be a situation where unauthorized person can see someone else's calendar

If you want to mention something else, feel free to do so!