The document outlines the steps to structure and implement a Salesforce CRM system for a nonprofit client. It discusses understanding the client's needs, blueprinting the necessary processes, building a prototype using standard and custom Salesforce objects, preparing and importing existing data, testing usability, training users, and providing post-launch support. The overall goal is to provide a centralized system to manage relationships and engage supporters to help nonprofits better achieve their missions.

2. Puzzling A Way To Structure
(aka “Implementing SFDC”)

3. Why CRM? Why Bother?
•A centralized record of participants
•A way to simplify complex operating processes
•A relationship diary ... a historical record
•A way to engage volunteer productively
•Data to show your leaders (board, etc.)
•Able to communicate personally with groups
•Two-way communication (e.g., surveys)
•Means to grow base of supporters

4. Best Project Environment
•Project boundaries: scope, hours, budget
•Clients eager to learn, will do assignments
•Implementation consultant is:
Organized, able to lead, reliable
Good listener, asks questions
Focused, but aware of “big picture”
Humble, able to admit “I don’t know”
Good teacher
Committed to client success

5. Step 1: Understand Client
Needs
•What is your mission?
•Who are your constituents?
•How do you serve them?
•How/when do you engage them?
•What makes you unique?
•What things would you like to do better?

6. African Library Project

7. Natl Diaper Bank Network

8. Step 2: “Blueprint” Process

9. Step 3: Build Prototype
•Salesforce standard objects
•Non-Profit Starter Pack (NPSP) package objects
•Custom apps & objects (Idealist Consulting)
•AppExchange custom applications
•Custom apex apps & objects (Idealist Consulting)

10. Salesforce Standard “Objects”
•Accounts = organizations, legal entities
•Contacts = people, profile data
•Leads = unknown/unqualified “suspects”
•Donations = financial records
•Campaigns = groups of Leads/Contacts
•Cases = service requests
•Tasks = reminders to do something
•Events = meetings

11. NPSP Package Objects
•Contacts/Organizations = NPO treatment of these
•Households = contacts w/same address, roll-ups
•Affiliations = organizational role associations
•Relationships = contact-to-contact associations
•Recurring Donations = pledges (open/closed end)
•Batch Entry = mass input of donations
•Contacts Merge = merging of duplicate contacts

12. AppExchange Apps
•Web integration
•Form submission
•Email/synchronization
•Payments/e-commerce
•Events, auctions
•Document prep
•Data management
•Mobile
•Social networking
•And more …

13. Minnesota State College SA

14. Waukesha Country EDC

15. Salish Sea Expeditions

16. 104.9 The River Radio

17. Start Small Think Big

18. Step 4: Prepare/Import Data
•Other CRMs, fundraising apps
Donor Perfect
Raisers Edge
•Other data sources
Excel sheets
QuickBooks
Auction software
SQL
Constant Contact
PayPal

19. Step 5: Usability Test
•Test against client scenarios & data
•Clarify & confirm usability
•Create useful views, reports & dashboards
•Modify as required

20. Step 6: Prepare/Deliver Training

21. Step 7: Post-Launch Support
•Emails
•Calls
•Re-train
•Additional customization
•Fixes
•Other as required

22. Q&A