How Premier is organized
Premier is one workspace made of modules, CRM, sales, projects, tasks, requests, approvals, workflows, files, inventory, portals and reporting. They share a single set of records, so a customer, a project and a request are different views of connected data rather than separate databases.
- 01Workspace: your company's single environment
- 02Records: customers, opportunities, projects, requests, tasks
- 03Modules: the views and tools that act on those records
- 04Roles: what each person can see and do
Decide what to turn on first
Adopting everything at once is the most common cause of a stalled rollout. Pick the two modules that remove the most manual chasing today, usually CRM plus projects, or requests plus approvals, and get them genuinely used before adding more.
- 01Week 1: import customers and invite the team
- 02Week 2: run live work through one module
- 03Week 3: add a second module and basic reporting
Model your data before importing
Spend an hour deciding what a customer, a project and a request mean in your business, and which custom fields you actually report on. Importing a clean structure is far cheaper than restructuring later.
- 01List the fields you filter or report on
- 02Delete fields nobody has used in a year
- 03Agree naming conventions for projects and stages
Set roles and permissions
Roles should reflect responsibility, not seniority. Give each role the narrowest access that lets it work, and use portals rather than internal accounts for anyone outside the company.
- 01Internal roles by function, not by person
- 02Location or team scoping where relevant
- 03Portals for clients, contractors and suppliers
Automate only settled processes
Automate a process once it is stable and written down. Workflows are excellent at enforcing a good process and equally good at enforcing a bad one, so start with notifications and task creation before automating decisions.
- 01Trigger: what starts the rule
- 02Conditions: when it should not run
- 03Actions: tasks, assignments, approvals, notifications
Measure adoption, then outcomes
For the first month, watch whether work is actually being recorded: tasks with owners, requests closed in the queue, deals moving stages. Once the data is trustworthy, move on to outcome dashboards like cycle time and win rate.
- 01Adoption: records created, tasks closed on time
- 02Outcomes: cycle time, win rate, request resolution
- 03Review the dashboard in an existing weekly meeting