Premier is one operating system, not a collection of disconnected apps.
The model is simple: records connect customer context to active work. Modules expose the part of that context a team needs, while ownership, permissions and reporting remain part of the same workspace.
Platform concepts
The handful of ideas everything else in Premier is built on.
- Workspaces
- One workspace holds your company's records, people and settings.
- Records
- Customers, projects, requests and tasks link to each other rather than being copied.
- Permissions
- Access is granted by role and follows the records people are allowed to see.
- Modules
- Modules are views of connected operating data, not separate silos.
CRM
Customer context that remains connected to the work that follows.
- Contacts
- People, their roles and the companies they belong to.
- Companies
- The account view across contacts, deals, projects, requests and documents.
- Deals
- Pipeline stages, values, owners and expected close dates.
- Activity
- Calls, notes, meetings and status changes on the related record.
Work
How commitments become structured delivery.
- Projects
- Phases, owners, dates and reusable delivery structures.
- Requests
- Structured intake that creates trackable work instead of email threads.
- Tasks
- Daily execution assigned to a person with a due date and parent record.
- Files
- Documents kept with the records and work they support.
Automation
Rules and approval paths that make repeatable processes explicit.
- Workflows
- Trigger, condition and action rules for supported assignments and updates.
- Approvals
- Named reviewers and a visible record of decisions.
- Notifications
- Targeted alerts for owners and people following the work.
Data
Getting information in cleanly and keeping the operating model understandable.
- Imports
- Bring supported customer and operational records into Premier.
- Exports
- Export supported records when you need to work with the data elsewhere.
- Fields
- Use fields that match the information your operating process needs.
Administration
Running the workspace as the organization becomes more structured.
- Users
- Invite, deactivate and manage people who use the workspace.
- Roles
- Define access appropriate to internal users and collaborators.
- Audit history
- Review significant operational changes where audit history is available.