Case study

Khirby CRM

Our product · sales and customer service

Proof we can build and run a CRM from the inside: contacts, correspondence and next steps in one place, including on the client’s own server.

CRMOpen sourceOwn serverNestJSVue 3PostgreSQLRedisDrizzle ORMDockerTypeScriptVisit product ↗

Khirby CRM - product screenshot — Product screenshot

Problem

Conversation history stays in individual inboxes, and status has to be pieced together from emails and spreadsheets.

Solution

The team sees what was agreed and what comes next - even when someone else takes over the account.

Why we built Khirby

Customer history often stays in one person’s inbox or a spreadsheet. We built Khirby to give a team shared access to contacts, correspondence and tasks.

How it helps

Companies define their own sales stages. Conversations and tasks sit alongside the customer, and website forms can send enquiries into the CRM. Another team member can pick up a case with its history intact.

A Bearly product

We develop Khirby as an open-source CRM under the MIT licence. Companies can run it on their own server, and we also help with implementation and maintenance. We agree any customisation around how the team works.

Need something like this?

Tell us what you are dealing with. We start with a conversation and a clear brief, not a quote in the dark.

Tell us where you lose timeWe reply within one business day