Initial considerations
- It should be a simple as possible initially
- Each phase should make sense to the selected group of users, so it should be complete within the area it covers
- It should provide business benefit
- It should not disrupt your ability to process business
- It should build on earlier phases
- It should minimise duplication of effort (some degree of duplication is inevitable, but we should try to minimise it)
Data considerations
- Employees
- Customers (and suppliers/resellers etc)
- Customer
- Contacts Products
- Contracts
- Projects
- Tickets
Logical functional groups
Starting
area |
In
favour |
Against
|
Subsequent
phases |
Timesheets
(up to 6 phases)
|
v Gets most of
the company using the solution immediately v Timesheets
without order integration (manual link) can be quick to get live v Drives
immediate visibility of activity |
v Commercials
are hard to model without orders v Invoicing
likely to remain manual v Timesheets
without tickets means that once tickets are added, a second bulk change in behaviour is required |
1.
Quotes and orders 2.
Contracts 3.
Tickets 4.
Invoicing & Accounting 5.
CRM (can be slotted in at any point, not critical) |
Tickets
(Up to 6 phases)
|
v Ticketing
may be run in isolation v If no
solution exists, this can really help organise work without disrupting other existing processes |
v Without
timesheets, time tracking on tickets is not useful v Without
contracts and SLAs ticket reporting is isolated |
1.
Contracts 2.
Timesheets 3.
Quotes and Orders 4.
Invoicing & Accounting 5.
CRM |
Sales Opportunities
(Up to 5 phases)
|
v Simple to
model v Only needs
data points 1,2&3 v Unifies and
cleans customer data v Replaces CRM
system v Low training
effort |
v Low user
impact and so limited benefits on day one v Can create
frustration as quote functionality not available |
1.
Quotes and orders 2.
Contracts 3.
Projects, tickets and timesheets 4.
Invoicing& Accounting |
Sales Opportunities, Quotes & Orders
(Up to 4 phases)
|
v Immediate
benefit is organising contract creation and management v Places first
delivery into the heart of the organisations revenue maintenance v Overall
fewest phases approach, shorter change period |
v Requires
product and price book definition, can be tough to formalise v Each phase
is larger and requires more coordination v Without
invoicing, double entry is required |
1.
Projects, Tickets and timesheets 2.
Contracts (populating the back-book) 3.
Invoicing & Accounting |
See also:
At what stage of my business growth should I invest in a PSA system?
How to build a business case for a PSA solution
Implementing professional services automation - where to start?
The 5 golden rules for PSA implementation success
Assessing the ROI for implementing a Professional Services Automation (PSA) solution
Beyond Professional Services Automation – Are new breed PSA systems are changing the way technology providers do business?
About the Author: CloudBlue PSA is the most complete cloud professional services automation (PSA) software on the market. Purpose-built with functionality to simplify every need of MSPs and Professional Services Organisations, CloudBlue PSA introduces a state-of-the-art PSA system built for today’s modern service provider. The platform empowers services organizations to scale recurring channel revenue and diminish operational complexity via its advanced product suite, which includes automated billing and reconciliation, an industry-leading customer support center and network operations center (NOC), real-time profitability analysis, and much more. CloudBlue PSA is available globally. Follow CloudBlue PSA on Twitter, LinkedIn or Website