Slate for Advancement is the smart and strategic choice
Use Cases and Deployment Scope
Currently, Slate for Advancement is used for gift processing, maintaining constituent and donor records, event registrations, electronic communications, territory management, and financial reporting on all of the above. It is our backbone of all things Advancement.
Pros
- Online event registrations / online data collection
- Email communications
- Gift & Payment Processing
- Very flexible configuration and customization
- Quick queries (exportable to excel)
- File or web service integrations
Cons
- More robust reporting functionality or visualization plug-ins
- More influence on when enhancements are moved into production and test environments
Likelihood to Recommend
I think you get hug bang for the buck with Slate for Advancement, From the internal user perspective, you don't need extensive or even moderate understanding of sql, html, css or javascript to create rich and engaging interactions with the general public. Of course those skills wouldn't hurt if you have them! In other words, you don't need a team of programmers to maintain your event pages or forms or customizations in general; it's typical that the IT department needn't be involved in the day to day support of the application. I'll state the obvious in that it's extremely advantageous to pair Slate for Advancement with Slate for Admissions. It's helpful to have bench strength on the platform even if the users have drastically different workflows. The only scenario I can imagine where Slate for Advancement would not be a good fit is where the culture of the institution has issue with the entire Software As A Service model. If your institution needs absolute control over all aspects of your implementation, or is reluctant to use cloud-based applications, Slate might not be for you.