CRM

The people behind the tickets, the deals and the hours.

Contacts and companies, a sales pipeline, and everything said and done with each of them: notes, calls, meetings, email and follow-ups on one timeline. It works on the records the rest already has. A company is the customer your helpdesk serves and your invoices go to, a deal is a ticket on a board, and a won deal becomes the contract your hours are logged against.

Contacts and companies

One record for a person and one for a company, whichever part of the work they turn up in.

Contacts

A name and a job title, any number of email addresses, phone numbers and postal addresses, a company, an owner and a stage, with notes in Markdown.

In the guide →

Companies

An organisation with its website, industry, size and domains, a customer or not yet one. Its page lists its contacts, its deals and its open tickets.

In the guide →

The same people as your helpdesk

A helpdesk customer, and anyone who sent a public request form, is a contact already, with the requests they raised on their page.

In the guide →

Fields of your own

An administrator adds custom fields to contacts and to companies, as to tickets.

In the guide →

Who sees it is yours to say

Seeing, editing and managing the CRM are three permissions held on roles, for one company or for every company. Customers never see it.

In the guide →

Bring your CRM with you

Companies, contacts, deals and their history from a HubSpot, Pipedrive or Salesforce export, with every row kept whole beside the record it became.

In the guide →

A pipeline that is a board

A deal is a ticket in a sales project, so everything a ticket has, a deal has: history, comments, files, a workflow and a board.

Stages as columns

Qualified, Proposal, Negotiation, Won and Lost on a kanban board, each card showing the company, the value and the expected close.

In the guide →

The deal's own fields

A value in its own currency, an expected close, a probability, the company it is with and the people there, each with their part in the decision.

In the guide →

Won, or lost with a reason

Losing a deal asks why, so the reports can say what deals are lost to.

In the guide →

Quotes

Lines with quantities, prices, discounts and tax, on the same sheet as an invoice, sent to the deal's people from its page.

In the guide →

From a won deal to a contract

A won deal offers the contract and the first invoice from its quote, and the hours that follow are logged against it.

In the guide →

Sales reports

The pipeline by stage, the weighted forecast, won and lost with the win rate, and how long deals spend in each stage. Amounts are never added across currencies.

In the guide →

Everything said and done

A note, a call, a meeting, an email or a task is logged once and shown on the timeline of the contact, their company and the deal.

One timeline

Interactions beside the requests a contact raised and the deals won and lost, newest first, on the contact, the company and the deal.

In the guide →

Follow-ups

A task with a due moment and an assignee is on their home page until it is done, and they are reminded when it comes due.

In the guide →

Email, by BCC

Each member has a logging address: BCC it, or forward to it, from any mail program and the message is on the timelines of the people it names.

In the guide →

Write from the contact's page

A message written there goes out under your name, and the answer comes back to the same timeline.

In the guide →

Your calendar, both ways

Connect Google Calendar, Microsoft 365 or iCloud: a meeting a contact is invited to is logged, and a call you schedule here is put in your calendar. An event with no contact is never read beyond who is invited.

In the guide →

The time it took

A call or a meeting records its time as an activity in the same step, on the customer's contract.

In the guide →

Their data stays theirs

A CRM holds data about people who never signed up to anything. The workspace answers to them, and has what that takes on every contact's page: a record of what they agreed to, a copy of everything held about them, and their erasure.

Consent, purpose by purpose
Every answer is kept with when and how it was given, and never changed.
No marketing without a yes
A message sent for a purpose goes only to a contact whose latest answer is yes.
A copy on request
One person's data as a ZIP of plain files, kept for 24 hours and deleted.
Erased when they ask
Their details, interactions and email go; the requests they raised stay, under no name.

Everything is included

The CRM is not an extra, and the people in it are never a seat.

Keep the relationship where the work is.

Every module is in every workspace, at one price per seat. A workspace takes a couple of minutes and asks for no card; an installation is one container image and a compose file.