A Proof of Concept (POC) can be helpful in assessing technical fit. While not always necessary, you might consider it if you have:
Complex source data
Sophisticated customer hierarchies
Diverse user populations
Variable workflows
Desire to launch on a rapid schedule
POCs can help you see beyond the demos, delve into the platform details, and understand how the system works and can work best for you. If you conduct a POC, there are different levels of commitment depending on your needs.
1️⃣ After copying this doc and sharing it with your team, have each team member add potential POC types to assess. Then have your team click Vote to vote for their favorite POC (most votes rises to the top).
Add POC
Proofs of Concept
Type
Need
Time Commitement
Considerations
Author
Vote
Upvoters
Type
Need
Time Commitement
Considerations
Author
Vote
Upvoters
1
Product Experience
Simulate platform engagement
Access to real dev environment
Experience a full feature set of platform including multi-channel experience.
5-15 hours of POC participant’s time depending on data requirements
Who will run the process
Use cases to test
Chrome plug-in (engagement simulation only)
Tag installation: either on Dev/QA, Mobile, or Production applications
Success criteria
👍
3
2
Customer Success
Want to “click around”
See how your organization would leverage the platform
Understand user experience and functionality configuration.
3-15 hours of POC participant’s time depending on data requirements
Who will run the process
Use cases to test
Sample data needed
Success criteria
👍
1
There are no rows in this table
2️⃣ Decide if you want to get POCs from your list of vendors and which POC to request: