Case study

Custom CRM

A CRM that tracks relationships, not pipelines.

Custom CRM
Case 1 / 1

Custom CRM

A CRM that tracks relationships, not pipelines.

1
Source of truth per client
7→1
Separate tools collapsed
Live
Mail, invoices & planning linked
Before
  • Sales, support, delivery, finance in separate tools
  • Relationship knowledge stuck in individual heads
  • Client context reconstructed from email threads
  • No way to connect a phone call to a deal or a ticket
After
  • One searchable note history per client
  • Email, call notes, invoices all linked automatically
  • Tickets, deals, deliveries inherit the same context
  • Nothing falls through the cracks when someone leaves

The problem with conventional CRM

An IT networking and support company whose work spans sales, support, delivery, and finance — all against the same clients — needed a CRM that could keep up. Standard CRM systems organize client data around pipelines and deal stages. That works for tracking sales opportunities, but it doesn't capture the full picture of a client relationship. Support interactions, delivery milestones, strategic notes, invoice statuses, and phone conversations all end up in separate systems — or in people's heads. When someone leaves, the knowledge of that relationship leaves with them.

The architecture

We designed a note-based CRM where the base unit is a timestamped note, a record of something that happened with a client. Notes are flexible. On its own, a note is institutional knowledge. Link it to a ticket and it becomes part of a support workflow. Link it to a deal, a delivery, or an invoice, and it inherits that context.

This means the system captures the full picture of a client relationship in one searchable interface. The support inbox is wired directly into the CRM: every incoming email lands as a note on the right client and can automatically open a support ticket. Phone calls are logged as timestamped notes on the same client timeline — entered by hand today, with AI transcription scoped as the next addition once call volume justifies it. Invoice data flows in and connects to the financial side. The planning system integrates directly, so CRM notes can link to specific tasks and their outcomes.

The result

Instead of a contact database with some activity logs, the company has a complete, living history of every client relationship. Sales, support, delivery, and finance aren't separate views — they're connected parts of the same story. Nothing falls through the cracks, and nothing depends on one person's memory.

Common questions

“Could you do this for us?”

Probably — though “similar” rarely means “identical.” Every company has its own processes, data, and team structure. The architecture principles stay the same; the specifics are yours. It starts with a conversation to see if we’re a fit.

A typical shop builds what you ask for. We push back until we are sure what you actually need. Most of the value gets created before any code is written: deciding what to build, what to skip, and how it all fits together. Getting that right is what makes the code worth writing.

We integrate with all of them. For some companies the answer is “keep what works, build around it.” For others it’s “migrate to something you own.” We tell you which — based on your situation, not on which one earns us more work.

If you’d prefer an NDA before the conversation gets into the details of your situation, mention it when you reach out and we’ll work it out. For most exploratory calls it isn’t needed, but it’s something we can sort out when it matters.