Napkinv1.2

Title: <Short title> (CRM plan, from needs to rollout)

Audience: <Who will see this> (Sales leaders and RevOps)

Goal: <What the visual should do> (One page plan for the CRM decision)

Company: <Name> (Acme Robotics)
Region: <Where you operate> (United States, Canada)
Team: <Size and roles> (12 sellers, 2 managers)
Motion: <How you sell> (Inbound SDR to AE, renewals by AMs)
Budget: <Per user budget> (30 to 60 USD per month)
Deadline: <Target date or window> (Go live in 10 weeks)

Must haves: <Key needs, comma separated> (Email and calendar sync, mobile offline, custom objects, SSO, MFA)
Nice to haves: <Extras, comma separated> (Call transcription AI, deal scoring, pipeline flow)

Shortlist: <Vendors, comma separated> (Salesforce Sales Cloud, HubSpot CRM, Microsoft Dynamics 365 Sales, Zoho CRM, Pipedrive)

Steps:
1) <Step name> (Collect needs)
   - <One action> (Write must haves and nice to haves)
2) <Step name> (Shortlist and test)
   - <One action> (Run a simple pilot script)
3) <Step name> (Review and decide)
   - <One action> (Compare scores and cost)
4) <Step name> (Rollout)
   - <One action> (Train team and import data)

Success metrics:
- <Metric> (Time on task under 12 minutes)
- <Metric> (Activity capture above 85 percent)
- <Metric> (Forecast accuracy within plus or minus 10 percent)

Timeline:
- <Phase> (Month 1, discovery)
- <Phase> (Month 2, pilot)
- <Phase> (Month 3, decision and training)

Risks and fixes:
- <Risk, Fix> (Data quality, add validation and weekly dedupe)
- <Risk, Fix> (Adoption, in app tips and manager dashboards)

Visual:
- Type: <Diagram type> (Flowchart)
- Layout: <How to place blocks> (Four columns, left to right)
- Style: <Look> (Clean, light background, readable text)
- Footer: <Optional note> (Ask RevOps for the full scoring sheet)

This document outlines a one-page plan for selecting and implementing a new CRM solution for Acme Robotics. It is intended for sales leaders and RevOps to provide a clear roadmap, covering key needs, vendor shortlisting, rollout steps, success metrics, and potential risks. The plan aims for a go-live within 10 weeks, with a per-user budget of $30 to $60 per month.



Company Overview







Company: Acme Robotics



Region: United States, Canada



Team: 12 sellers, 2 managers



Motion: Inbound SDR to AE, renewals by AMs



Budget: $30 to $60 USD per user per month



Deadline: Go live in 10 weeks



Requirements



Must Haves:







Email and calendar sync



Mobile offline access



Custom objects



SSO (Single Sign-On)



MFA (Multi-Factor Authentication)



Nice to Haves:







Call transcription AI



Deal scoring



Pipeline flow visualization



Vendor Shortlist







Salesforce Sales Cloud



HubSpot CRM



Microsoft Dynamics 365 Sales



Zoho CRM



Pipedrive



Implementation Steps







Collect Needs





Write must-have and nice-to-have requirements.



Shortlist and Test





Run a simple pilot script with each shortlisted vendor.



Review and Decide





Compare vendor scores and costs.



Rollout





Train the team and import data.



Success Metrics







Time on task under 12 minutes



Activity capture above 85 percent



Forecast accuracy within plus or minus 10 percent



Timeline







Month 1: Discovery (Gathering requirements, vendor shortlisting)



Month 2: Pilot (Testing shortlisted CRMs)



Month 3: Decision and Training (Selecting CRM, training team, data migration)



Risks and Fixes







Risk: Data quality issues






Fix: Add data validation rules and implement weekly data deduplication processes.



Risk: Low adoption rates






Fix: Implement in-app tips and create manager dashboards to monitor usage.



Visual Representation (Flowchart)



Layout: Four columns, left to right



Style: Clean, light background, readable text



Column 1: Collect Needs







Start



Define Must-Have Requirements (Email sync, mobile offline, etc.)



Define Nice-to-Have Features (Call transcription, deal scoring, etc.)



Document Requirements



Column 2: Shortlist and Test







Identify Potential CRM Vendors (Salesforce, HubSpot, etc.)



Develop Pilot Script (Key sales tasks)



Execute Pilot with Each Vendor



Gather Feedback from Pilot Users



Column 3: Review and Decide







Score Vendors Based on Requirements and Pilot Feedback



Compare Costs (Implementation, subscription, training)



Evaluate Integration Capabilities



Select CRM Vendor



Column 4: Rollout







Data Migration (Clean and import existing data)



Team Training (CRM functionality, best practices)



System Configuration (Customize fields, workflows)



Go-Live



Monitor Adoption and Performance



Flowchart Arrows:







Connect each step sequentially from left to right.



Use decision diamonds where necessary (e.g., after pilot feedback to determine if a vendor meets requirements).



Footer: Ask RevOps for the full scoring sheet.