Professional Services
›
Professional Services & Outsourcing
›
Systems Implementation
CRM Implementation
Advisory, implementation, and operational engagements where trust, alignment, and execution governance determine outcomes.
Example organizations in this space:
Slalom
Deloitte Digital
Accenture
Cognizant
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome Discovery
Align on the current CRM state, data quality gaps, adoption blockers, stakeholders, and measurable success criteria.
Discovery Questions
Start: A quick snapshot of your CRM today
- Which CRM platform does your team use today?
- How long has this platform been your primary system?
- Who on your team owns day-to-day administration for the CRM?
- Roughly how many frontline sellers on your payroll actively use the system?
- Estimate the number of account and contact records in your primary CRM
- Does any contractual or technical constraint prevent your organization from making significant CRM changes or migrations in the next 6 months?
Where your sellers actually stop using the system
- If your sellers could wave a wand and fix the CRM's single biggest pain, what would it be for your team?
- Tell me about the last time a rep on your team avoided using the CRM, what happened and what did they do instead?
- Which core selling activities take the most time in your CRM, and how many minutes per activity on average?
- How often do your reps skip required fields or use placeholder values to move deals forward?
- When incomplete or inaccurate data appears in a report, who on your team notices first and what is their usual response?
- Describe the most common workflow in your system that creates duplicates or broken account hierarchies
- What single CRM behavior or data issue in your environment would make you cancel a migration project before it starts?
Which numbers would actually move the needle for leadership
- Fixing which metric's accuracy in your reports would change hiring or quota decisions this quarter?
- Over the last six months, what has been your typical percentage variance between forecast and actual?
- Point to the pipeline stage in your process that consistently under-represents true opportunity value, and why
- Who in your leadership team reviews forecast accuracy weekly, and what action do they take when it deviates?
- If a single data cleanup could deliver a 10% improvement in forecast accuracy, who in your organization could sign off to fund that work immediately?
Stakeholders and the hidden vetoes
- Pinpoint the person on your leadership team whose withholding approval would stop the project, and explain why
- Walk me through your approval chain for data access, sample exports, and integration credentials
- Point to the stakeholder group in your company that will feel the biggest operational impact during the first 30 days
- Tell me about any internal champions in your organization who will drive adoption, and what influence they have with reps
- Assuming your executive sponsor withdraws mid-project, what immediate impact would that have on timeline and budget?
The other options you are weighing
- List the alternatives your team is actively considering right now, including 'do nothing' or an internal-only fix
- For each alternative you're weighing, what would have to be true for you to choose it over an external implementation partner?
- Has anyone inside your company proposed solving this without an outside partner, and who would run that work?
- Name the incumbent solution or internal team your organization has typically fallen back on
- What single condition would make your organization stay with the current approach instead of switching?
Data, integrations, and gating criteria for go/no-go
- Highlight the integration or data dependency that would stop your work immediately if its API or access is not available
- Do you have named data owners and a single source of truth for accounts and contacts in your organization?
- List the external systems your team must integrate before go-live, and the team that owns each
- Is there an internal technical resource in your organization committed to the project, with weekly capacity and a point of escalation?
- Rate the cleanliness of a representative pilot segment in your data on a 0-100 scale for duplicates, missing fields, and broken hierarchies
- Are there regulatory or compliance approvals in your industry or company that could delay access to contact or customer data?
- Should API access to a critical endpoint be unavailable after 4 weeks, which option would your team choose?
What success looks like and who signs off
- Assuming a pilot for your team delivers a measurable reduction in rep admin time, what organizational decision would that unlock?
- Identify the top three success metrics your organization will use to judge the engagement in the first 90 days
- Within your target window, what minimum improvement in forecast accuracy or pipeline velocity would make the project a clear win for your leadership?
- Please indicate who on your team signs acceptance that the deployment met the success criteria, and list the evidence they require
- On the condition the pilot proves the stated metric for your team, what remaining approvals or budget items would block signing this week?
Adoption, training, and early sustainment
- Identify who in your organization will be responsible for achieving 85% rep adoption in the first quarter, and describe the authority they have to change incentives
- Select the training format that has historically driven the best behavior change for your sellers
- Describe any incentives, scorecards, or performance plans your organization will tie to CRM usage
- Explain how your organization will measure sustained adoption after go-live, and who owns that measurement
- Should adoption stall at 60% after launch at your company, which remediation options would be acceptable to you?
- Specify the person or role in your organization that must commit to a compensation or process change within 30 days to make adoption achievable
Next steps, timeline locks, and potential deal killers
- Flag the single risk in your view that would make you stop the project, and describe the contingency that would allow your team to continue
- Select which of these timeline constraints apply to your organization
- Estimate the earliest possible start date for a pilot for your team, and the latest acceptable start date
- Would your organization be open to a phased pilot limited to one region or product line to prove value quickly?
- Finally, who else from your organization should we involve in the next meeting to either unblock approvals or provide technical details?
-
Solution Experience
Translate the buyer's needs into concrete configuration, data, and workflow changes using real sales scenarios to show expected outcomes.
Solution Experience
- Solution Experience Session
- Confirm the current state and its cost
- You confirm the restated current state and agree the identified costs to forecasting, rep time, and leadership trust are accurate.
- Provide a representative sample of 25 current deals and their related account/contact records for a migration trial.
- You confirm the demonstrated configuration and data changes produce the expected outcome on the sample deal.
- Map a real sales scenario to configuration and data changes
- Run the migration trial on the provided sample and deliver a deduplication and account-hierarchy mapping report before the follow-up session.
- Document decision criteria and the evidence list that will be required by the buying committee for approval.
- You agree that the shown migration approach resolves duplicates and preserves account hierarchies for the provided sample.
- Demonstrate migration and deduplication handling
- Walk the rep workflow and adoption touchpoints
- You confirm the rep workflow shown reduces manual steps enough to drive adoption in the first quarter.
- Schedule the follow-up technical review to lock field mappings, pipeline stages, and automation rules based on trial results.
- Validate the future state
- Agree on evidence and next acceptance criteria
- Solution Experience Session
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define deliverables, responsibilities, migration boundaries, integrations, training, and acceptance criteria for the engagement.
Scope Configuration
- Migrate CRM Records and Deduplicate
- Migrate and Reconcile Activity History
- Configure Sales Process and Pipeline Stages
- Customize Contact and Account Fields
- Configure Account and Territory Hierarchies
- Implement Role-Based Permissions and Sharing
- Integrate Email and Calendar Sync
- Integrate ERP and External Systems (API Connectors)
- Configure Lead Routing and Assignment Rules
- Deploy Automation for Tasks and Notifications
- Build Sales Pipeline Reports and Dashboards
- Deploy Lead Scoring and Qualification Rules
- Enable Mobile CRM Access and Offline Sync
- Train Sales Reps on CRM Workflows and Shortcuts
- Execute Post-Launch Data Health and Adoption Optimization
Scope Questions
Migrate CRM Records and Deduplicate
- How many account records need to be migrated from your source CRM?
- Which matching keys should we use to detect contact and account duplicates (select all that apply)?
- Do you require preserving original record IDs for back-reference to the source system?
- What acceptance criteria will confirm record migration completeness and acceptable deduplication (for example: record count parity within 1%, duplicate rate <1%)?
- Name the authoritative system we should treat as the master when conflicting account attributes appear (for example billing system, ERP, marketing database).
Migrate and Reconcile Activity History
- How much activity history should be migrated per contact (90 days, 6 months, 2 years, full history)?
- Which activity types must retain attachments or recordings during migration (emails, calendar events, call recordings, tasks)?
- Do you require preserving original timestamps and participant lists exactly as they appear in the source system?
- What acceptance criteria will confirm activity migration and reconciliation (for example: sample-account parity, attachment retention >95%)?
- Provide up to three sample accounts with representative activity volumes we can use to validate migration mappings.
Configure Sales Process and Pipeline Stages
- What are the pipeline stages your sales reps currently use and the typical win probability you assign to each stage?
- List any separate sales motions that require distinct pipelines (for example: new business, renewals, expansion, reseller channel).
- Describe the milestone events that should trigger stage progression (for example: proposal delivered, demo completed, legal approval received).
- Indicate which required fields must be completed before a deal can advance from each stage (for example: close date, decision maker identified, estimated ARR).
- Who in your organization will approve final pipeline stage names, probabilities, and gating rules?
Customize Contact and Account Fields
- Provide a prioritized list of custom contact and account fields required for segmentation, quoting, or reporting (for example: account tier, buying center role, contract type).
- Identify which fields must retain historical values for audit and forecast variance analysis (for example: ACV, contract start date).
- Confirm whether any fields contain personally identifiable information (PII) that must be masked or redacted in the CRM export.
- Indicate who will own the canonical data dictionary for custom fields and where it will be stored.
- State whether you require calculated/formula fields for ARR, TCV, quota attainment, or other financial measures.
Configure Account and Territory Hierarchies
- Estimate how many levels of account hierarchy (parent, regional office, subsidiary) must be modeled.
- List the rules that determine account-to-territory assignment (for example: geography, ARR, industry vertical).
- Provide the format of the authoritative territory map you can supply at kickoff (CSV, spreadsheet with account ID to territory code, API feed).
- Confirm whether account merges should preserve historical opportunities, activities, and parent-child relationships.
- Who will be the ongoing owner of territory governance and periodic rebalancing decisions?
Implement Role-Based Permissions and Sharing
- Provide the list of user roles or profiles to create and the minimum object permissions required for each (read, create, edit, delete, transfer).
- Name the roles that must have access to pricing, discounting, or margin fields.
- Confirm whether you use account teams, queue-based ownership, or territory-based sharing rules today.
- Outline any compliance-driven audit logging requirements for permission or sharing changes (retention period, report cadence).
- State the maximum number of permission profiles that should be configured for license planning.
Integrate Email and Calendar Sync
- Which email and calendar provider(s) must be integrated for two-way sync (for example: your corporate email and calendar platforms)?
- Provide the domain allowlist and mailbox patterns we should include for automatic email tracking.
- Do you require shared mailbox and team inbox mapping into the CRM for coordinated response tracking?
- Specify whether calendar events must sync bi-directionally and whether meeting updates should auto-update related opportunities.
- Indicate any API rate-limit or security constraints for the email/calendar integration (for example: API keys, service account, OAuth2).
Integrate ERP and External Systems (API Connectors)
- Which external systems must be integrated at go-live and which primary objects are required (orders, invoices, product catalog, customer master)?
- Provide the available connector type for each external system (REST API, SOAP, flat-file export, database replication).
- Do you require real-time synchronization or scheduled batch updates for each integration?
- Specify authentication and security expectations for each endpoint (API key, OAuth2, service account certificate).
- Identify the top three ERP data objects to prioritize for initial integration and why.
Configure Lead Routing and Assignment Rules
- Describe the lead routing logic you use today (for example: geography, product line, round-robin among SDRs).
- List the fields that must determine lead assignment (for example: territory code, lead source, product interest).
- Do you require SLA timers for new lead response and escalation rules if unclaimed?
- Specify fallback assignment behavior when the primary owner is unavailable (queue assignment, manager escalation, manual handoff).
- Who will own day-to-day changes to lead routing rules after launch?
Deploy Automation for Tasks and Notifications
- List the task automation scenarios you want at go-live (for example: follow-up reminders after demo, overdue task alerts).
- Provide the trigger events for each automation (for example: stage change, lead created, opportunity closed-won).
- Do you require mobile push notifications for high-priority tasks or escalations?
- Specify escalation recipients and SLA windows for missed tasks or unacknowledged notifications.
- Indicate the maximum expected daily volume of automated notifications to estimate throttling needs.
Build Sales Pipeline Reports and Dashboards
- Which KPIs must appear on executive dashboards (for example: weighted pipeline coverage, forecast accuracy, average deal size)?
- Provide a list of named dashboards and the intended audience for each (for example: CRO, Sales Ops, regional managers).
- Do you require row-level data security or per-role filters on dashboards to restrict views by territory or team?
- Specify the required data refresh cadence for each dashboard (real-time, hourly, daily) and acceptable lag times.
- What acceptance criteria will validate report accuracy against source systems (for example: 99% match on closed deals for a weekly sample)?
Deploy Lead Scoring and Qualification Rules
- Describe the lead scoring model you want at launch including behavioral and firmographic factors.
- Indicate the behavioral signals from activity history that should influence score (for example: email opens, meeting attendance, trial usage).
- Do you require manual override or adjustment of lead score by SDRs or managers?
- Specify the score thresholds that should convert a lead to MQL and MQL to SQL.
- Who will own tuning and periodic review of lead scoring logic after launch?
-
Mutual Commit
Finalize commercial terms, timelines, data-access approvals, roles, and the acceptance criteria that will verify success.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Payment and Invoice Schedule
- Acceptance & Success Criteria Sign-off
- Project Timeline & Milestone Schedule
- Roles & Responsibilities Matrix
- Data Processing Agreement (DPA)
- Data Access & Authorization
- Integration & Third-Party Access Authorization
- Change Order Agreement
- Service Level Agreement (SLA)
- Termination & Exit Plan
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm concrete readiness facts — environments, named data owners, access, timelines, and rollback plans before work begins.
Pre-Deployment Questions
Environment and access
- Which environment(s) will we deploy into? (choose all that apply; we'll ask for environment names and availability in the next question)
- Provide the environment name(s) and the date each will be available for work (so we can schedule cutover and test windows).
- Are admin-level accounts with API or equivalent deployment access already provisioned for each environment? (required—'No' pauses the schedule)
- Are there network controls, IP allowlists, or vendor approval steps required before integrations can connect? (so we can request allowlisting in advance)
Data and configuration
- Which source data categories are in scope for migration or synchronization? (select all that apply; this determines sizing and mapping work)
- Who is the named data owner for each source category above? (Format: Category — Full name, role, email; we will contact them for mapping and quality decisions.)
- Has an approach to field mapping and canonical values been approved, or will the seller propose mappings for buyer approval?
- Are there existing data-cleaning or deduplication jobs we must preserve or avoid during migration? (name the process owner in the next question)
People and ownership
- Who is the primary deployment owner on the buyer side (Full name, title, email)? This person will be the single point of contact for scheduling and decisions.
- Provide named owners for these workstreams: Data migration, Configuration, Integrations, End-user training, and Final acceptance. (Format: Workstream — Full name, role, email)
- Are the approvers for go/no-go and acceptance criteria identified and available during the planned cutover window? (we need availability to schedule final validation)
- Who will participate in the pilot or validation group (team name, number of users, contact person)? (we run pilot verifications before broad rollout)
Timing and constraints
- What is the target deployment start date and the hard completion date (if any)? (these dates bind resourcing and release sequencing)
- Are there blackout windows, peak business periods, compliance freezes, or other dates we must avoid? Please list dates and the reason they block work.
- Has a rollback/backout plan been approved that defines trigger criteria and who owns the rollback decision? (If yes, name the owner.)
- List any external dependencies that must be completed before work begins (third-party vendor approvals, data extracts, license purchases) and their expected completion dates.
-
Configuration Details
Capture exact configuration values the deployment team will use — field mappings, pipeline stage definitions, automation rules, and integration credentials.
Configuration Details
Environments & Endpoints
- Enter the production environment exact instance label to configure (used verbatim in deployment; Default: 'prod')
- Enter the staging/sandbox environment exact instance label to configure (used verbatim in deployment; Default: 'staging')
- Select the production instance region (Default: 'US-East')
Options & Feature Variants
- Select the pipeline staging model to create for the sales process (Default: 'Standard 5-stage')
- If you selected 'Custom' above, enter the pipeline ID to apply (leave blank if not applicable; format: alphanumeric, max 32)
- Select the lead-to-account matching strategy the deployment should enable (Default: 'Exact email match')
Field & Object Mappings
- Provide the path or URL to the field-mapping CSV to consume (format: s3://... or https://... or /path/to/file.csv). The CSV must follow the platform mapping template.
- Enter the target Account external ID field API name (exact field label to map to; e.g., 'External_ID__c')
- Enter the target Contact external ID field API name (exact field label to map to)
Integrations, Automation & Verification
- Primary external integration endpoint category to configure (select one)
- Enter the integration endpoint label to use in configs (exact name to create; e.g., 'email_sync' or 'erp_orders')
- Credential owner and secrets exchange method for the integration (DO NOT paste secrets). Enter as: 'Owner Name / SecretsManagerName / key-name' (example: 'Alice Smith / your-secrets-manager / crm-connector-key')
-
Deployment
Execute the migration, configuration, integrations, and adoption activities with clear owners, sequencing, and verification checkpoints.
-
-
Success
Validate adoption and data-quality targets, review pipeline accuracy, and maintain a shared backlog for issues and enhancements.
Success Reviews
- Go-live Health Check
- First Measurement Review
- Acceptance Gate Review (Day 90)
- Quarterly Success Review
Issues & Enhancements
- Produce the quarterly metrics snapshot and distribute it as the standing record for the next review.
- Restate acceptance criteria and targets
- Produce a documented acceptance decision by the buying owner and record pass/fail per acceptance criterion.
- Agree a remediation plan with deadlines for any failed criteria and place remediation tasks into the shared backlog.
- Confirm the incumbent system decommission or archive plan and its timeline to avoid dual-system usage.
- Publish the acceptance decision, including metric evidence and pass/fail outcomes, to the shared workspace.
- Create remediation tickets for each failed criterion with target resolution dates and verification steps.
- Execute the agreed incumbent wind-down or archival tasks and publish proof of completion or the retention plan.
- Review current metric trends and dashboard snapshots
- Confirm whether forecast accuracy percentage and CRM data completeness rate are meeting targets or require remediation.
- Prioritize the shared backlog for the next quarter with clear acceptance criteria for each item.
- Close resolved issues and escalate any persistent blockers with a defined next action.
- Update the shared backlog with agreed priorities and acceptance criteria for the next quarter.
- Schedule focused remediation or enablement work for items that threaten metric targets and publish verification plans.
- Re-confirm success criteria and ownership
- Confirm the deployment completed per the migration checklist and that core integrations are functional.
- Identify the top launch issues with clear remediation tasks and target dates.
- Set the date and data requirements for the first measurement review.
- Run and circulate the full data integrity and duplicate-detection report for the migration.
- Publish the list of launch blockers with remediation tasks and target verification dates.
- Prepare adoption activity baseline reports (logins, workflow completions) for the first measurement meeting.
- Present first measurement data
- Determine whether rep adoption rate and CRM data completeness rate meet or are trending toward the targets recorded in Solution Scope.
- Agree a set of corrective actions with verification dates to close any gaps before the acceptance gate.
- Confirm the evidence package and deadline for the acceptance gate review.
- Deliver targeted enablement sessions and updated quick-reference guides for the low-adoption cohorts.
- Execute deduplication and account-hierarchy fixes identified in the migration integrity report and document completed fixes.
- Produce the evidence package for the acceptance gate, including metric dashboards and migration validation artifacts.
- Deployment and migration validation
- Backlog review and prioritization
- Root-cause diagnosis for gaps
- Present outcome data vs each criterion
- Agree corrective actions and verification plan
- Document pass or fail per criterion and acceptance decision
- Blocker burn-down and recent remediations
- Early adoption signals and usage patterns
- Confirm timeline to acceptance gate
- Blockers and open issues
- Remediation plan and incumbent wind-down confirmation
- Action sync and next quarter checkpoints
- Close and record next steps
- Agree immediate remediation actions