What implementation readiness looks like
A company is ready to implement Salesforce when it can name the outcomes the project must deliver, has one decision-maker for process questions, has its core process written down, knows where its data lives and how clean it is, has listed the systems Salesforce must connect to, and has people available for workshops, testing and ownership after launch. Gaps in two or more of these areas are the most common cause of delays and rework.
Take the assessment (20)
Close these gaps first
Your answers stay in this browser. Nothing is sent unless you choose to send your results below.
Questions about the assessment (4)
Who should take this assessment?
Whoever is sponsoring the Salesforce project, ideally with the person who will own it day to day. It works for a first implementation, a new cloud added to an existing org, or a move from another CRM. If a question does not apply yet, answer it as you expect things to stand at kickoff.
What does a low score mean for our project?
Not that you should wait. It means the gaps are likely to show up as delays or rework if nobody closes them. Most of the fixes are decisions and preparation on your side, and a good partner will help close them during discovery rather than skipping past them.
Is my answer data saved or sent anywhere?
Only if you choose to send it. The assessment runs entirely in your browser, and nothing you select is sent to us or stored on our servers. If you use the form under your results to ask a consultant for a review, your scores and top gaps are sent to our team with the contact details you enter. Use the print button if you want to keep a copy.
How is this different from the org health assessment?
This one is for companies about to implement Salesforce or add a cloud. The org health self-assessment is for companies already running Salesforce who want to know what to fix in an existing org.