Twenty CRM

Twenty is our CRM and our task board. It runs on our own Hetzner server and holds our leads, deals, clients and the team's to-do list. Ben, Cam and our AI agents all work from the same records.

Every lead lands with its source

Every contact and landing-page form on this site goes through n8n into Twenty, and one form fill becomes three records:

• A person, matched on email, so someone who gets in touch twice isn't added twice.
• A deal at the New stage, ready for the pipeline.
• A form submission with the message, the page, the campaign and the Google click ID.

Leads from our Meta instant forms end up as the same kinds of record, through a separate n8n workflow built for them.

Inbound calls to our main line and tracking numbers are logged the same way: each call becomes a call record with outcome, campaign attribution, the voicemail recording link and Scribe transcript, and for the AI line the ElevenLabs summary and caller details, so follow-up does not rely on memory.

Your own objects get their own API

Form submission isn't one of Twenty's built-in objects. We added it, with the fields we wanted, and Twenty gave it an API at once. This is roughly what n8n sends:

mutation {
  createFormSubmission(data: {
    name: "Jane Smith"
    formName: WEBSITE_CONTACT
    utmSource: "google"
    utmCampaign: "brand"
    gclid: "Cj0KCQjw..."
  }) { id status }
}

Change a status, and the follow-up happens

When we mark a lead as booked, qualified or disqualified, Twenty calls a webhook and n8n moves the deal to the matching stage. The same status changes can send follow-ups through Notifuse.

It's the team's task board too

Client work, our own projects and ops jobs are all tasks in Twenty, each titled with the client's code. Actions from Fireflies meeting notes become tasks, and our AI agents read and update them through Twenty's MCP server, so nothing important lives only in someone's notes.

It's our record of who we work with

Our client roster and our network of 140+ freelancers live in Twenty, alongside records for the tools we run, so a question like "who in our network does a given kind of work?" is a filter, not a spreadsheet hunt.

Clients get their own workspace

A client can have a workspace of their own on the same install. Each workspace has its own API key, so a client's contacts never sit next to ours, and an agent working for one client can't see another client's records. We've set one up to catch website requests.