Twenty

What is Twenty?

Twenty is an open-source CRM. Teams run it in the cloud or self-host it, and shape it around how they sell: custom objects, custom fields, relations between records, and workflows on top. People, companies and opportunities come standard, and everything else is defined by the team.

Teams that choose Twenty usually care about owning their data and their model. They build objects for what matters to them, such as sites, contracts, competitors or bid requirements. Then the proposal gets written in a document tool that knows none of it, and the structure they designed stops at the edge of the CRM.

Let the model you built in Twenty shape the documents you send

Cobl reads people, companies and opportunities in Twenty, along with the custom objects, fields and relations your team defined, and the notes and tasks attached to them. That context sits inside a deal workspace next to the proposal, the deck, the questionnaire response and the technical memo.

Custom objects are usually the most specific description of how a team sells. Built on them, a proposal reflects the team's own sales process rather than a generic template's idea of one. Because Twenty is open source, teams often extend it in ways no packaged CRM supports. Those extensions are exactly the context a template would ignore and a good proposal should use.

What Twenty and Cobl look like on a live deal

A software company runs Twenty with a custom object for technical requirements, linked to each opportunity. A prospect in healthcare has eleven requirements recorded after discovery, three of them marked critical. The opportunity moves to the proposal stage. The account executive opens a deal workspace in Cobl, which reads the opportunity, the company, the linked requirements and the notes.

The proposal comes back structured around the three critical requirements, with the answers drawn from the Shared Drive. When the prospect sends a security questionnaire, it goes into the same workspace. Nothing is sent without review. The team's custom model pays off in every document, not only in reporting.

Key features of the Cobl Twenty integration

Standard and custom objects as context

Cobl reads people, companies and opportunities along with the custom objects and fields your team defined. The document works from your model, not from a fixed schema someone else designed. Reading your model means nothing needs remapping before the documents work.

Relations followed, not flattened

Records linked to an opportunity, such as requirements, contacts or sites, inform the same document. The structure your team built survives the trip from the CRM to the page. Linked records keep their meaning, so a requirement stays attached to the opportunity it belongs to.

Every document for the deal in one workspace

Proposal, deck, questionnaire response, technical memo and business case sit on the same deal and share the same context, so nothing gets re-explained between them. A late questionnaire starts from everything earlier documents already established.

Works with your knowledge base, chat and inbox

Twenty context combines with documentation in Notion, internal discussion in Slack and buyer threads in Gmail. Together they give the proposal both the structure of your CRM and the detail of the conversation.

Frequently asked questions

Does Cobl integrate with Twenty?

Yes. Cobl connects to Twenty so opportunities, companies, people and your custom objects can feed proposals, decks and RFP responses.

What Twenty data does Cobl access?

People, companies, opportunities, custom objects and fields, and the notes and tasks attached to them, read through the access the connected workspace grants.

Does it work with a self-hosted Twenty instance?

The integration connects through the Twenty API. Whether your instance is cloud or self-hosted, it needs to be reachable through that API for Cobl to read it. Your team controls what the connection can access.

Does Cobl work with custom objects?

Yes. Custom objects and relations are often the most useful context a team has, and Cobl reads them alongside the standard records.

Can I edit before anything is sent?

Yes. Cobl produces a draft. Precise changes go through the inline editor, exports are editable Word and PowerPoint, and approval stays with your team. More on data handling sits on the security page.