CrmLeaf, PSA and the Service Lens in This Manual
All editions. This article explains how the manual layers general platform documentation with professional services context, and how to read the two together.
Availability: All editions. This article explains how the manual layers general platform documentation with professional services context, and how to read the two together.
Overview
CrmLeaf is a broad business management platform. It serves several product types, business functions and industries, and this manual documents it that way. Alongside that, professional services is the primary industry lens for depth: where a capability matters to a service organisation, the article explains the business context as well as the mechanics.
The positioning is deliberate and worth stating plainly:
| Layer | What it means |
|---|---|
| CrmLeaf | The broad platform. Everything documented here is a CrmLeaf capability, available to any customer whose edition and plan include it. |
| PSA | Professional Services Automation - the flagship service-oriented solution, assembled from CrmLeaf capabilities rather than sold as a separate product. |
| Professional services | The primary industry lens for documentation depth. Service organisations receive the fullest business context; other product types remain documented in parallel. |
The governing principle is service-first, not service-only. No article has been narrowed to a service audience, and no general functionality has been removed to make room for service context.
How It Works
Every article documents the capability itself first. Where the capability has genuine service relevance, an additional block follows the core instructions.
Core capability → Service value → Other applicable use cases
You will find that block after Expected Result, visibly separated and labelled as a service lens. It never changes the instructions above it. It answers a different question: not "how do I do this", but "why does this matter to a service business, and what does it connect to".
Of the 190 articles in this manual, 112 carry a service lens. The remaining 78 do not, because the connection would be forced. That restraint is the point.
The Same Capability, Different Purposes
Most CrmLeaf capabilities serve more than one kind of business. The table below is a reading principle, not a claim that every capability exists identically in every edition - availability is always stated in each article's own Availability block.
| Capability | General CrmLeaf | Service / PSA emphasis | Other product types |
|---|---|---|---|
| Projects | Project management | Client service delivery and engagements | Internal and operational projects |
| Tasks | Work management | Service delivery activities | Operational work |
| Time tracking | Work and effort recording | Billable and non-billable delivery time | Internal time tracking |
| Timesheets | Time recording and approval | Client and project effort | Workforce management |
| Expenses | Expense management | Project and client-rechargeable expenses | General business expenses |
| CRM | Customer and lead management | Client and engagement management | Sales management |
| Resources | Team management | Resource planning, availability and capacity | Workforce planning |
| Reporting | Business reporting | Delivery and effort analysis | Operational reporting |
Article Classification
Each article carries a small classification label beside its article code. It exists to show how much service context to expect, and to let the documentation team see coverage at a glance.
| Label | Meaning |
|---|---|
| Core CrmLeaf | General platform functionality, applicable across editions. May still carry a short service context note. |
| Service / PSA | Significant professional services relevance. Carries the fullest service lens. |
| Industry / Solution | Explains how CrmLeaf supports a particular industry edition, such as Solar or Construction. |
| Other Product Type | Primarily relevant to another CrmLeaf product or business model, such as manufacturing or inventory. |
A full list of all 190 articles with their classification is in Article Classification and Service Lens Coverage.
Which Service Organisations This Addresses
The service context in this manual is written for project-based service businesses, including consulting, IT and software services, engineering and architecture services, marketing and creative agencies, accounting and advisory firms, implementation and managed services, and business consulting. These are used as illustrative contexts. CrmLeaf is not certified or purpose-built for any named industry beyond the editions listed in Understanding CrmLeaf Product Editions.
Where a concrete example helps, the manual prefers the four industries for which CrmLeaf ships project templates - IT Services, Marketing Agency, Creative Agency and Legal Services - because those templates are real and inspectable, carrying estimated hours, rate per hour, estimated cost, owner role and a billable flag for every task.
Terminology
Interface terminology is never changed to suit the service lens. If a screen says Client, the manual says Client. Service vocabulary - engagement, consultant, utilisation, billable hours, delivery performance - appears in explanation, with the mapping made explicit where it helps. For example, a CrmLeaf Client record usually represents the client organisation an engagement is delivered for, and a CrmLeaf Project often represents a single engagement or assignment.
Expected Result
You can tell, for any article, whether it carries a service lens, where that lens sits, and that the instructions above it apply to every CrmLeaf customer regardless of industry.
Important Notes
- A service lens never asserts a capability the platform does not have. Where a service reader would expect a measure CrmLeaf does not store - a utilisation target, an employee cost rate, a backlog figure, a project margin report - the manual says so and records the question rather than implying the feature exists.
- Competitor PSA platforms informed how deep and well-structured this documentation should be. They never supplied a CrmLeaf capability. Nothing in this manual describes a competitor's feature.
- A lens block is additive. If your organisation is not a service business, you can skip every one of them and the manual remains complete.
Related Articles
Our support team answers on business days. Reference FM-05 so we can jump straight in.