Solutions
Matrix for IT services and software delivery companies
The problems this actually addresses
- Nobody can say what a project has cost until someone builds a spreadsheet
- Hours are logged against a project and a specific issue every day, so Hours Per Project and Effort Allocation are reports you open, not artefacts you assemble.
- The scope discussed in the deal is invisible to the people delivering it
- Deals, documents and product demos live in the same workspace as the project and the board, under one permission model.
- Client hours and internal hours blur together
- A project record carries client hours, internal hours and a monthly estimate as its own fields, so the distinction survives past the kickoff meeting.
- Attendance and leave live in a different system to delivery
- Attendance imports from your attendance machine's own export, leave runs end to end with approvals, and both sit next to the projects those people are on.
- Equipment goes missing when someone leaves
- Hardware is allocated to the same employee record HR maintains, and allocated packages are a list rather than a memory.
- Everyone can see everything, or nobody can see anything
- One permission catalogue, per-screen and per-report, plus per-project access on top — so a client-facing lead and a recruiter can share a workspace without sharing a view of it.
Built around the way a services business actually keeps score
A product company measures a roadmap. A services company measures time against engagements, and everything else follows from that: what to invoice, who is over-committed, which project is quietly consuming a month it was not budgeted.
Matrix puts that measurement at the centre. The Daily Status Report is not a compliance exercise bolted onto a project tool — it is the record from which the hours reports are built, which is why it asks for the issue as well as the project.
One tenant, one directory, one set of roles
Your delivery leads, your recruiters, your business-development people and your finance user are all in the same workspace, seeing different parts of it. Adding a person is one invitation, not four accounts across four vendors.
It also means reports can cross what would otherwise be a system boundary: the person on the project, the leave they took, the hours they logged and the laptop they hold are the same record.
- Projects, portfolios and an enterprise view for multi-engagement teams
- CRM for the pipeline that feeds them
- Attendance, leave, documents and the org chart for the people who staff them
- Hardware allocation tied to the same employee records
Configurable where your business differs
Stages, leave types, holidays, document types, hardware types, departments, job titles, service types and business domains are all catalogues you maintain. The product adapts to how your firm is organised rather than asking you to adopt someone else's vocabulary.
A month in Matrix
- 1
Win the work
An organisation, its contacts, a lead and then a deal — with the proposal and the team resumes attached to the record.
- 2
Stand the project up
Create the project with its client, hours budget and owners, choose its stages, grant access, and fill the backlog under epics.
- 3
Run the fortnight
Plan a sprint, work the board, discuss on the issues, and let mentions and change notifications keep the right people informed.
- 4
Record the days
Everyone files a DSR against the project and issue they worked on. Missing DSRs shows the gaps before month end rather than after it.
- 5
Close the month
Hours Per Project, Effort Allocation, Project Analytics, the Attendance Report and the Monthly Leave Summary — all reading the same records.
Common questions
Does Matrix replace our project tool, HR tool and CRM?
Can we keep client hours separate from internal hours?
Related
Reports and analytics
The month-end reports this workflow produces
CRM and pipeline
The commercial side, in the same workspace
Matrix vs spreadsheets
What a workbook stops being able to do
Back to all solutions, or see every feature in detail.
Find out in a month, not a quarter
Create a workspace, run one real project and one reporting cycle through it. The reports will tell you plainly whether the picture matches what you believed.