Andy's ability to listen made him an invaluable asset. I could give him tasks, he would ask questions till he understood exactly what I wanted. Often his questioning helped me to better define what I wanted too.
Roadmapping
How can you build a CRM well without a clear blueprint?
The truth is, you can’t— at least not without wasted effort, a lot of “figuring it out as you go,” or projects priced high just to cover that uncertainty.
Understanding the key goals and subsequent feasibility of them is essential to avoiding excessive costs and poorly planned projects. CiviCRM is powerful, but flexible. Discovery exists to identify the right approach before time and money are spent building the wrong one.
And yes, there likely is a best option.
Discovery defines how it should function for your staff and members resulting in a blueprint you can act on. Slow is smooth, and smooth is fast.
What you'll get
At the conclusion of the discovery period, a written summary will be delivered outlining the implementation approach, along with an estimated timeline and costs. This blueprint becomes the foundation for your CiviCRM project.
- Defined implementation scope: a clear outline of what would be included in a potential build
- Prioritized user stories and requirements: functional needs organized using a MoSCoW framework to make tradeoffs explicit
- Recommended CiviCRM configuration: guidance on core features, relevant extensions, and data model mapping.
- Technical ecosystem alignment: how the CRM would interact with your website, email tools, and related systems
- Custom development assessment: identification of any extension development needs
- Fixed-price implementation options: estimated cost ranges and timelines for implementation phase
3 types of CiviCRM requirements
When project requirements are known, they need the general approach defined and put into 3 main buckets of work along with a prioritization method like MoSCoW. By maximizing what’s possible out of the box, you save loads of time and money all while avoiding creating technical debt and the need to refactor down the road.
Configuration
Realizing this is a configuration issue that is possible out of the box.
enhancement
Requires an extension or advanced configuration.
development
Requires significant custom coding as no existing options exist.
How it works
Review of your existing materials
Existing database, spreadsheets, workflows, forms, membership processes, reporting requirements, etc.
Stakeholder conversations
Structured discussions (3) with staff and key volunteers who will use the system, for user story development.
Requirements mapping
Translating each user story into clear, functional requirements for the build.
MoSCoW prioritization
Categorizing those functional requirements as Must Have, Should Have, Could Have, or Won’t Have to right-size the scope and budget.
Opportunities
Identifying where CiviCRM can save time, eliminate manual steps, and improve member and program experience.
Implementation approach
Outlines the CiviCRM architecture, configuration, and workflows needed to support your organization. Results in up to 3 proposal options for your consideration.
Plan for success
Build a CiviCRM blueprint to start on the right track.
This blueprint becomes the foundation for your CiviCRM project and significantly increases success for any sizable CRM project.