Skip to main content

Business development

CRM: organisations, contacts, leads and deals

The commercial side of the business, in the system that already knows your projects and your people. No second login, no separate user directory, no copying a won deal into a project tool by hand.

What the CRM holds

Each item below is functionality in the product today.

Organisations

The companies you sell to and deliver for, as records rather than a column in a spreadsheet.

Contacts

The people at those organisations, linked to the organisation they belong to.

Leads

Early interest, captured before it is a deal, so nothing depends on somebody's memory of a conversation.

Deals

Track every opportunity through your pipeline, filtered by organisation, contact or stage so a forecast conversation starts from the current picture.

Documents on the record

Proposals, statements of work and anything else attach to the CRM record itself, stored under the same tenant-owned file boundary as the rest of your data.

Product demos

Record the demos you have given, so the pre-sales history of an account is on the account.

Team resumes

Keep the CVs you send with a proposal in the same place as the deal they support.

Service types and business domains

Two catalogues you define, used to classify what you sell and the sectors you sell into.

Why sales and delivery in one tenant is worth something

The handover from "we won it" to "we are building it" is where most agencies lose information. The scope discussed in the deal, the documents that were sent, the person who promised the timeline — all of it lives in a CRM the delivery team does not open.

In Matrix the deal and the project are in the same workspace, under the same permission model, referencing the same people. What was promised is a click from what is being built.

Pre-sales artefacts belong on the account

A product demo and a set of team resumes are not incidental — they are the two things a prospective client actually saw. Recording them against the account means the next conversation starts from what was already shown, and the next proposal reuses the CV that was already prepared.

  • Product demos recorded as records, not calendar entries
  • Team resumes stored alongside the deals they support
  • Documents attached to organisations, contacts, leads and deals

Access is separate from delivery access

CRM is its own set of permissions — organisations, contacts, leads, deals, products and team resumes are each individually grantable. A delivery lead can see the project without seeing the commercials, and a business-development user can work the pipeline without access to HR records.

Business development: common questions

Is the CRM a separate product or login?
Neither. It is part of the same Matrix workspace, using the same users, the same roles and the same permission catalogue as projects, HR and reporting.
Can we restrict who sees commercial data?
Yes. Organisations, contacts, leads, deals, products and team resumes are each their own permission, granted through a role, so CRM access is independent of project access.

Related

Or go back to all features.

Try it against your own work

A workspace takes a couple of minutes to create. Put one real project in it and see whether this shape matches how your team already works.