This document outlines the plan for a proof of concept project using Circuit collaboration software. It defines the participants and their roles, proposed activities including onboarding, project work, and wrap up. Success criteria are identified to measure the results, such as improved collaboration and engagement. Finally, next steps are outlined including meetings to discuss goals, review the evaluation process, conduct the proof of concept, and review sessions.

1. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.11
Circuit Proof of Concept

2. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.22
ListofActions
Item Description Owner
PoC Participants Define PoC participants, roles, and responsibilities. Ensure resources are
committed to success.
[CLIENT] / Circuit Customer Success Manager
PoC Logistics Agree on Dates/Times/Location for delivery. Need to confirm that Stakeholder’s
calendars are blocked, room(s) are reserved and a computer(s) with
camera/microphone are available.
If iOS devices (iPhone/iPad) available – download Circuit application.
[CLIENT] / Circuit Customer Success Manager
Project Selection Choose appropriate project and scenario(s). Suggested by [CLIENT], agreed to by Circuit
Customer Success Manager
Document Goals Define overarching goals for collaboration. What results are the client looking
to achieve by implementing? These should be documented through early client
conversations and validated by the Sales Director with the CSM before engaging
in proof.
[CLIENT] Executive Sponsor, Circuit Sales Director,
Circuit Executive Sponsor
Identify Success Criteria Identify the Success Criteria for the PoC. These should align to the goals defined
above. This list should contain items that will be proven, demonstrated, and/or
discussed during the PoC and will be used to determine the overall success of
the PoC.
[CLIENT] PoC Sponsor, agreed to by Circuit
Customer Success Manager
Communicate Process for Documenting
Success Criteria
Once Success Criteria have been agreed upon, it is important that all PoC
participants are made aware of the criteria and the role they play in providing
feedback to help measure/document the results of the PoC.
This should happen before the PoC begins, and should be reiterated during the
PoC kickoff meeting.
[CLIENT] PoC Coordinator, supported by Circuit
Customer Success Manager
Agree to Sequence of Events (SOE) List out the steps after the PoC is completed – this is simply an agreement on a
plan and is not binding.
Suggested by Circuit Sales Director, agreed to by
[CLIENT] Executive Sponsor

3. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.33
Contents
1. Circuit Proof of Concept Overview
2. Objective and Activities
3. Project Information
4. Planned Deliverables
5. Participants and Roles
6. Planned Activities
7. Success Criteria and Proof Points
8. Sequence of Events

4. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.44
CircuitProofofConceptOverview
• See the Software in Action
• Get Results in Real-Time
• Resolve Collaboration Issues
The Circuit Proof of Concept is an engagement where Circuit Customer
Success Manager(s) work iteratively with your team to create a project plan
for success.
• Determine Project
Selection and Scope
• Define Success Criteria
• Identify Team Structure
• Communicate expectations
to PoC participants
• Educate & Prepare Team
PREPARE EXECUTE
Sprints
Workshop Wrap-Up
Getting Started
Review & Validate
Circuit On Boarding
Review & Validate
Project Work
Review & Validate
Final Review and Approval
Generate Deliverables
CONCLUDE
• Conduct PoC survey and collect
feedback from participants
• Document results and findings
• Draft business case document
(as needed)
• Present PoC results to
Executive Team

5. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.55
ObjectiveandActivities
• Objectives
» The purpose of this document is to propose a structured plan of activities that will:
 Allow [client] to evaluate the Circuit Collaboration Platform by directly experiencing the value on real life project(s).
 Demonstrate the speed, collaboration and understanding that Circuit brings to team communications.
 Support a business case for investment & provide a low-risk way to make an informed buying decision.
 Review the people/ process fit of Circuit in the [client] organization.
» At the end of the workshop, a summary of the results and an anticipated ROI (return on investment)
will be documented for the creation of a business case that supports the adoption of Circuit within
[client].
• Proof of Concept Activities
» Circuit resources will use the Circuit Platform on a project mutually agreed to be suitable for this
evaluation.
» Circuit resources will work with project stakeholders to capture their feedback.
» [client]’s staff will be involved at all stages of the evaluation to maximize understanding of the Circuit
platform and its relevancy to the [client] team collaboration needs.

6. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.66
Project Name
Provide the project name, release information,
etc.
Project Description
Provide a brief background of the project and
the business benefits / objectives it is intended
to deliver
Proposed Use Cases
Describe the project-specific use cases that will
be included as part of the PoC
• Use Case 1 – description…
• Use Case 2 – description…
Scope Considerations
Clearly define what the Circuit simulation will
deliver, areas of focus, or any other scope
related items.
• Item 1
• Item 2
Project Information

7. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.77
PlannedDeliverables
Name Description Type
Evaluation Planning Document • Contains PoC scope and approach information Presentation
Circuit Getting Started Guide(s) • Tips, Tricks & Best Practices for using Circuit Presentation, Videos
PoC Results Document • Summary of PoC activities & outcomes
• Measurement and Results of proof points for the project
• PoC Team Feedback
• Conclusions, recommendations, next steps
Presentation
Business Case Document (DRAFT) • The value of Circuit as a collaborative solution
• How Circuit fits into the [client]’s environment
• The applicability and value of Circuit to [client] projects
• Justification for acquiring and adopting Circuit
Presentation
The Circuit team will work with [client] to produce the following deliverables as part of the PoC

8. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.88
ParticipantsandRoles
Teams Participants
Core Team
This team will spend the entire time together as they work together to
implement and adopt Circuit success.
• [TBD], Customer Success Manager, Circuit
• [TBD], [CLIENT] Circuit PoC Sponsor
• [TBD], [CLIENT]
Stakeholder Team
This team is expected to participate in the review and feedback sessions.
These sessions will be as needed.
• [CLIENT] Business Stakeholder Group [TBD]
• Business / End User Representatives
Extended Team
This team will attend the Kick-off session, monitor the progress of the
Circuit PoC, and attend the Final Review Session.
• [TBD], Account Executive, Circuit
• [CLIENT] Executive Sponsor
• [TBD], Circuit Executive Sponsor
SAMPLE ONLY – PARTICIPANTS NEED TO BE DEFINED AND DOCUMENTED WITH THE CLIENT

9. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.99
Activities
Sprint Activity Description Participants
Getting Started Circuit Introduction & Project
Overview
• Kick Off Discussion
• Circuit Introductory Demo
• Validate Scenarios in scope
• Validate Use Cases
• Validate Success Criteria
On Boarding The Fundamentals Behind Circuit • Logging In
• Setting Up “Your” Circuit”
• Conversations (Private/Open)
• Starting Conversations
• Adding Content
• Voice/Video
• Screen Sharing
• Best Practices
Project Work Using Circuit For Your Project • Integrating Circuit Into Environment
• Team Usage
Wrap Up • What Have We Learned
• Team Feedback
Deliverables • Business Case Justification
Core Team Stakeholder Team Extended Team
(Optional)
SAMPLE ONLY – FULL SCHEDULE NEEDS TO BE DEFINED AND DOCUMENTED WITH THE CLIENT
(Optional)
(Optional)

10. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.1010
[Client]SuccessCriteriaandProofPoints
During the course of the PoC, [CLIENT] & Circuit will work together to ensure that each of the
success criteria are addressed and measure/document the results
Criteria Measurement Evidence / Feedback (on completion of PoC)
Using Circuit, [client] is able to reduce the overall time it takes to organize and
facilitate a conference call.
Project Team Estimates
Circuit is able to easily capture persistent feedback and comments during a
conversation.
PoC Activity Completed
Circuit is able to deliver a realistic and intuitive conversation experience. Stakeholder Feedback
Circuit creates a knowledge sharing platform. Project Team / Stakeholder
Feedback
Using Circuit will promote higher levels of engagement and drive productivity. Stakeholder Feedback
Circuit results in improved collaboration between [client] project teams and internal
customers
Project Team Feedback
Circuit provides for: vibrant team conversations, candid dialog, frequent
contact and a personal touch.
PoC Activity Completed
SAMPLE ONLY – NEEDS TO BE COMPLETED BY [client]

11. www.Circuit.com | 1.800.556.0399Circuit Company Confidential © 2013 All rights reserved.1111
SequenceofEvents
Item Description Owner Completion Date
Meeting to Discuss current
situation, goals &
expectations.
Gain common understanding of current situation, business goals & capabilities needed. Julie/Daniel/Darin 1/8/2015
Review the evaluation
process.
Ensures we are on the same page for next steps and helps conceptualize the entire
Circuit decision process (evaluation, purchase process, deployment – etc.).
Julie/Daniel/Darin 1/13/2015
Proof of Concept Short term trial of Circuit using mutually agreed upon project. Circuit usage will be
mapped to project details, key requirements and areas of improvement will be
demonstrated (using Circuit). Findings and deliverables on completion.
Alabama Core Team/Daniel TBD
PoC Review Meetings Meetings with Core, Stakeholder and Extended teams to discuss progress. TBD TBD
PoC Review Session Findings of PoC discussed and deliverables reviewed. TBD TBD
Go/No Go Determination for the fit of Circuit within State of Alabama’s environment. Julie/Darin TBD
Order Sent Circuit order sent for approval. Julie/Darin TBD
Signed Order Received Signed Circuit order received. Julie/Darin TBD
Circuit Deployment Introductory hand-off meeting with Circuit Customer Success Manager. Access and
confirm short and long term goals. Define project plan to ensure success and expansion
Alabama Team/Daniel/CSM
Team
TBD
Customer Success Throughout Circuit engagement you will have a Circuit CSM to make sure you meet and
exceed goals and expectations.
Daniel/CSM Team Ongoing