A CRM organizes relationship and sales information. A client portal is a client-facing access point for relevant information or actions. Agency management describes a broader coordination category covering client work and business processes. These labels can overlap within one product; use them to name the job and records involved, rather than assume a fixed feature list.
- CRMOrganize contacts, relationships, opportunities and next actions.
- Client portalGive clients an appropriate view of information and actions.
- Agency managementCoordinate delivery work and broader business processes.
One product may cover several jobs. These category labels do not establish a fixed feature list.
Why the vocabulary matters
Teams can use the same word for different jobs. One person asks for a CRM because lead ownership is unclear. Another uses the word to mean a place for client files. A third means the agency's whole operating system. Clarifying the noun makes the conversation easier before anyone evaluates a product.
This is a terminology guide. The operations system decision guide owns the broader question of what to keep, connect or replace. Here, the task is to distinguish the records, views and responsibilities people are describing.
Relationship records: contacts, companies and opportunities
A contact record identifies a person and relevant relationship information. A company record identifies an organization. An opportunity represents potential commercial work. An activity can record a conversation or next action linked to those records.
- Contact recordIdentify a person and relationship information.
- Company recordIdentify the organization connected to the relationship.
- Opportunity recordRepresent potential commercial work.
- Activity recordLink conversations or next actions to related records.
A returning client can create a new opportunity without becoming a new company.
Your agency should define how those records relate. One company may have several contacts and engagements. A returning client may create a new opportunity without becoming a new company. A person changing employer may require a reviewed relationship update rather than a blind duplicate merge.
The acronym CRM means customer relationship management. In practice, products vary in the record types and actions they provide. The acronym is a category description, not proof that a particular workflow is available.
Client-facing access: the portal
A portal describes an access point through which a client sees or contributes to relevant work. It may show deliverables, requests, progress or decisions, depending on the implementation.
The client view and internal workspace are different concepts even when they use the same underlying records. An internal comment might belong in the project record while remaining inappropriate for the client view. A permission model decides who can see or act on information.
The word portal does not tell you whether records are stored separately, which actions are allowed or how access restrictions are enforced. Those are implementation questions. The permission checklist defines them more precisely.
Delivery coordination: projects, tasks and agency management
A project organizes a defined body of delivery work. A task identifies a smaller action within that work. An owner is responsible for the next step or result under your process. A status describes the state of a record using agreed meanings.
Agency management is a broader category that may bring several business and delivery functions together. Different products use the term differently. Keep individual functions visible instead of assuming the label includes everything your agency does.
| Term | Concept to distinguish | What the term does not prove |
|---|---|---|
| CRM | Relationships and sales information | Complete delivery coordination |
| Client portal | Client-facing access and participation | Verified permissions or security |
| Project management | Organization of delivery work | Full relationship or commercial coverage |
| Agency management | Broader business and delivery coordination | Every specialist function |
| Automation | Actions performed under defined rules | Correct inputs or resolved exceptions |
Shared records and connected records
Two views can display one record, or two systems can each hold a copy. That distinction matters when somebody edits a field. Ask which record is authoritative and how other views or copies receive the change.
- Contact detailsIdentify which system is authoritative.
- Active projectIdentify which system owns delivery work.
- Accepted agreementIdentify where the accepted agreement lives.
- Other views or copiesDefine how changes reach connected records.
An integration label does not determine record ownership.
A label such as “integrated” does not resolve ownership. Write down which system owns a contact's details, which owns the active project and where the accepted agreement lives. The data cleanup guide uses those definitions to reconcile conflicting information.
Agree on a small agency glossary
List the terms your team uses most often, their meaning and the source record. Include opportunity, client, engagement, project, approval and completion. Resolve differences before encoding the labels into automated rules.
The glossary should explain current work in plain language. It does not need to mirror every vendor's menu. When the agency changes systems, preserve the intended meaning and map it to the new tool rather than letting a changed label silently change the process.
Evaluating a portal for your agency
Once the terms are clear, use the client portal selection checklist to test an actual client interaction, access boundary and review process. The terminology describes the category; the checklist helps you evaluate its implementation for your agency.
- Choose client interactionSelect a real client action or information need.
- Check access boundaryReview who may see or act on the information.
- Check review processTest how the agency reviews the interaction.
- Document implementationRecord how the actual portal works for the agency.
Terminology describes a category, while implementation requires agency-specific testing.
Questions and answers
What does CRM stand for?
CRM means customer relationship management. In agency software discussions, it commonly describes relationship and sales records such as contacts, companies, opportunities and next actions. The label does not establish which features a particular product includes.
Is a client portal a separate database?
It can be a separate system or a client-facing view connected to another system. The portal term describes how clients access relevant information and actions. It does not, by itself, describe the underlying data structure or prove account separation.
Is an opportunity the same as a project?
An opportunity represents potential commercial work. A project represents delivery work under your operating definitions. They may be linked, but changing an opportunity status should not obscure which agreement and delivery record the team is using.
Does agency management mean every business function is included?
No. It is a broad category label, and product coverage varies. Define the records and functions you need separately. Use the operations system guide for the actual buying decision and verify current product capabilities.