Professional Documents
Culture Documents
Example Scope
Example Scope
Venuiti
Reinventing Customer Engagement.
Contents
1
Scope of Work............................................................................................................................................. 2
Development & Production Services........................................................................................................... 3
UX, Design & Build – Mobile / Desktop Tools.......................................................................................... 3
Analytics.................................................................................................................................................. 7
Backend Development............................................................................................................................. 7
UAT / Launch........................................................................................................................................... 7
Maintenance Phase..................................................................................................................................... 8
Project Timing.............................................................................................................................................. 9
Project Costs............................................................................................................................................. 10
Terms & Conditions................................................................................................................................... 11
Acceptance................................................................................................................................................ 12
Scope of Work
CLIENT Sciences (“CLIENT”) has engaged Venuiti, Inc. (“VI”, together, “The Parties”) to review existing
sites for Website 1 (www.Website1.com) and Website 2 (www.Website 2.com) which CLIENT has
expressed concern over relative to existing designs, look & feel, and overall functionality (prior produced).
The Parties are aligned that timetables will incorporate the development of functional requirements, UX /
UI, design & development for Website 1 first, followed up by Website 2 (once Website 1 is live launched).
Resources will be prioritized to each project group based upon the site in process (no resources will be
employed simultaneous to one another where hours are not accountable). VI will make recommendations
for improvements across the following:
1. User Experience
As noted, CLIENT has expressed frustration with existing site performance among a variety of issues
example of which include: a) customer accounts & ecommerce capabilities; b) mobile optimization; c)
data accessibility; and d) overall ease of update for its tools as key examples. VI’s key mission will be to
deliver best practices for both sites in three ways:
2
Principal tactics will be implemented with the intent to expand / increase traffic, gain optimization-based
data about user journeys, and sales through e-commerce. Customer subscription options, as noted
above, have been discussed and are currently considered “nice to-have’s” and are addressed for the
feasibility of delivery in scope below. CLIENT will benefit from extensive VI experience in developing
robust retail websites that are optimization rich and maintenance friendly. It is imperative to VI that
entering in to this project scope, the Parties align that VI effort is intended to insure long-term
effectiveness of CLIENT tools and that a standing partnership will be developed as a result of efforts
made on CLIENT’s behalf. VI enters in to all agreements with the desire to collaborate, cultivate and help
partners re-invent and improve / succeed. This SOW will identify all elements to be completed, split in to
two separate timelines (one for Website 1 and one for Website 2) during the balance of 2018 calendar
year. The specifics of the SOW will be prioritized herein including plan, timing, manpower, and costs to
implement for CLIENT.
As noted during initial discussions, in each case, VI will utilize its significant category expertise to
establish a framework from which to approach development for CLIENT properties. This framework is
based in a fundamental belief that tools will best be served in creating refined sites which function
according to expectation and which are surrounded by e-commerce and other data feeds important to
best practices for CLIENT’s business requirements.
Further, given e-commerce requirements, it is essential to properly integrate CLIENT business
processes into a Product database that can be easily updated and centrally controlled by the
CLIENT stakeholder members.
The parties are aligned that this SOW will prioritize a mobile optimized site as step 1 for each site.
Overall deliverables are to include:
3
Site 1 (First build and launch) Website 1
Privacy Policy
Privacy
Policy
o Site design strategy will be aligned to during the initial work session meetings. This strategy
will encompass Stakeholder guidance for both sites (Website 1 first, Website 2 second).
The deliverable on approach will be a one-two page brief that must be Stakeholder
approved prior to creative work-start (per site).
CLIENT Stakeholders will provide all Website 1 and Website 2 style guides (if
available), brand guidelines and examples of competitive / non-competitive
messaging that are deemed, directional ideals.
Site design will commence once the creative brief is approved by Stakeholders. VI
will engage best-in-class design team to develop a set of design options (2 each for
Website 1 first and Website 2 second) which best articulate the guiderails of the
approved brief. Initial round of concept presentation will feature main page (desktop
& mobile), product page (desktop & mobile), and blog page (desktop & mobile)
Site design reviews will take place in PDF format only and once approved, PSD
/ InDesign files will be implemented.
Round 1 Review:
o Designs will encompass the UX noted above.
o CLIENT Stakeholders will select one (1) direction for each channel from
the options provided.
o ------ Stakeholders will provide input / guidance on the selected designs. VI
will continue refinement and adjustments to the winning directions. The
Parties are aligned herein that timetables will require review and
refinement rounds to be kept to two - three (2 – 3) in total for each site.
o Approved design elements will be moved to development steps are each is
secured (The Parties agree this does not have to happen all at once. Where
pages are approved, CLIENT authorizes VI to implement to the already in
process development stage).
o VI will collaborate with Project Stakeholders on SEO but will defer to Project Stakeholders to
lead this process. VI will apply all required / agreed to SEO practices in to site builds.
Analytics
o Analytics creation is critical to optimization of the tools once launched. VI will be prioritizing
best-in-class analytics leads to manage these steps on behalf of CLIENT from the get-go.
Initial deliverables for analytics will include the following:
During work sessions, The Parties will align on all key performance indicators (KPI’s),
for both sites, that will serve as the success metrics for the program for the balance
of 2018 (post-launch). VI will, however, engage in 2019 planning support up to and
through December 2018.
With KPI’s established, VI will customize Google Analytics tools for both Website 1
and Website 2 sites, creating a dashboard for each site.
Post-launch, under the maintenance umbrella noted herein, VI will monitor
performance and provide the following :
o Monthly reports
o Quarterly optimization recommendations / action plans
Backend Development
VI will work with CLIENT to identify integration points for the sites including (but not limited to)
o SKU databases including description, META data, images and other attributes
o Pricing data
o Rebate data
o Availability / stock levels
o Ecommerce / order taking / Promo Code (includes ability to pay through paypal)
o Existing CRM / Marketing automation systems
o One time purchase / subscribe (includes auto-allotment for month-to-month product
shipments, cancel at any time, auto-reminder for pending shipment)
VI will work with CLIENT to determine the most efficient and complete way to move
data throughout the system and use this information to integrate into product
engines.
This SOW assumes that there is a single backend system used for pricing and
order fulfillment.
Backend development will be completed concurrently to UI / UX and once both systems are
completed they will be integrated into a single unified web experience for each brand.
VI will work with CLIENT to recommend and implement a suitable content management
and ecommerce platform taking into account
UAT / Launch
o UAT / Soft-Launch Program
As stipulated within the timetable herein (below), the Website 1 and Website 2
sites will be considered substantially completed once soft-launch is ready in each
case based upon each sites respective timetable (Website 1 to be first).
VI will maintain the soft-launch within its staging environment. CLIENT Stakeholders
will provide the link to a variety of employees, partners, necessary team members
who will actively utilize the site and address any pertinent areas of refinement for the
aligned to soft-launch period.
VI will engage its UAT team to work in conjunction with dev.
The Parties will align on refinements, updates, alterations and engage in a maximum
of two (2) rounds of update prior to live launch (this will likely take three to four weeks
to complete). The site will not be considered “complete” and ready for live launch until
all UAT refinements, updates, and alterations are complete and the site is fully
functional and de-bugged (this will include spell check and broken / dysfunctional
links that are discovered during testing).
o Live Launch
VI will complete all refinements identified during soft-launch and secure final
CLIENT Stakeholder approval that issues have been rectified.
With final approval, VI will move the staging site to identified live URLS, as
identified by CLIENT, and bring the sites live to the public.
Maintenance Phase
In the 30 days immediately following launch VI will complete the integration, test the performance of
backend systems, identify bottlenecks, complete training and undertake tasks typically done in the period
immediately after launch as well as start the month to month maintenance activities (hours noted will be
split between the two sites as directed by CLIENT). This includes (but is not limited to):
Verifying user engagement & workflows are working as anticipated in the UI / UX stage and
adjustments as necessary.
Training staff for the management of the site and products.
Performance testing and identifying bottlenecks.
Mobile site performance optimization (this is not a visual optimization – but a performance
optimization which can only be done after the engines are fully enabled).
Establishment of reporting framework and key KPI’s to ensure they are reporting as designed
using actionable and tangible data.
Putting in place workflows and processes to facilitate backend updates.
Identifying high value / volume targets to address during month to month maintenance.
Putting in place the monthly maintenance process and integrating with CLIENT’s existing
business framework.
Project Timing
Project milestone dates will be provided once the SOW is approved and signed. Given that both sites will
operate on separate timelines vs. simultaneous, VI needs to review plans and align resources
accordingly. Full timetables by site and decision dates will be required within three (3) working days of
scope approval.
Note: Timetables represent the general order of process and go-to-live dates. Once fully aligned and
approved on SOW, The Parties agree that an initial planning session will be implemented where a
detailed project plan will be assembled. Given that there will be significant requirements of time for
CLIENT to allocate to this program, it is essential that full project plans are worked on collaboratively to
insure all milestones that require input / approval from CLIENT can be met once established. Further,
given that the build will be an on-going process, The Parties are aligned that the timetable may morph
from time-to-time based on need and learnings from within the process. VI will be responsible for
notification to CLIENT of any pertinent changes to final timetables as it relates to completing all assets
where CLIENT informs VI of potential changes. Where delays are the direct result of CLIENT review or
updated input requests, CLIENT will allow for work stop until such time that activities are rectified.
Staff Jun Jul Aug Sep Oct Nov Dec Total Allocation
Hrs
Account Lead 0.00 0.00 5.00 5.00 5.00 0.00 0.00 15.00
UX & Wireframing 5.00 0.00 20.00 15.00 0.00 0.00 0.00 40.00
Designer 0.00 0.00 10.00 25.00 0.00 0.00 0.00 35.00
Analytics Set-up & Reporting 5.00 0.00 10.00 15.00 5.00 5.00 5.00 45.00
Sr. Engineer 0.00 0.00 12.50 12.50 0.00 0.00 0.00 25.00
Developer 0.00 0.00 25.00 25.00 20.00 15.00 15.00 100.00
Project Management & UAT 0.00 0.00 40.00 10.00 10.00 10.00 10.00 80.00
Totals 10.00 0.00 122.50 107.5 40.00 30.00 30.00 340.00
Design / Build
Maintenance
Initial build and design encompasses a simplified e-commerce structure whereby each site will have the
following abilities:
a. Buy now feature – allows for one-time purchases to be completed and data monitored for
VI understands that there is more desire for comprehensive e-commerce systems that allow for a variety
of features. Given overall scope necessary to achieve all of the above in budget shared, VI would
require additional scope to incorporate the following abilities:
a. Subscribe
b. Member login (sign-up)
c. Manage my subscription (including modify orders, set notifications, cancel subscription)
d. My Account
These additional elements will require additional UX, Design & Development time to incorporate in to the
e-commerce construct. The estimate for these additional features is approximately $ (which would
increase initial build scope to $ VI is highly sensitive to delivery of the sites with an e- commerce engine
in place and recommends an initial focus on the “buy now” feature only at the outset. Where traction
builds to significant levels, the add-on features can easily be implemented but it is believed now that
early stages will incorporate a greater level of trial vs. running subscription.
10
Additional keynotes:
1. Design assumes all content / copy is provided by CLIENT team (this includes images). No
allocation within this scope is provided for writers or editors. The parties are aligned that once
maintenance stage launches design requirements will end (outside moderate / reasonable review
of work updates). Therefore, design time ends once both site designs are final approved (relative
to each site’s final aligned timetable)
2. Maintenance timing is considered engaged once UAT is completed on each site as they become
ready to push live from staging. This phase is considered an estimated block of hours and covers
the low-end in terms of hours to cover tasks. Monthly hours reconciliation will be provided as
requested by CLIENT and included with invoicing where desired. Actual hours will be billed out
and not billed at higher totals than estimate shown without prior written approval from CLIENT to
do so. Where CLIENT requires work which exceeds the hours applied herein, VI will notify
CLIENT of overage danger to monthly estimate and secure necessary approval before work start
on said elements. Maintenance hours should be utilized in the month identified. However,
minimal tasks may roll over month-to-month.
o Website 2
25% on SOW signature date
25% on UI/UX Presentation
25% on staging/UAT
11
VI will work with CLIENT to manage timelines. It is understood that building a project such as
this requires rigorous project management skills and most importantly delivering and approving
work on time. The Parties agree to work collaboratively and vigorously to deliver on these
defined timelines to ensure that the project will not extend past the original timeline. VI will
insure that appropriate resources are available throughout the entire project lifecycle based
upon the project scope detailed herein. In the event of potential delays and scope changes The
Parties will need to make each other aware of the delay and reason for it and will possibly need
to allocate additional resources in order to make a best effort to reach the agreed upon
timelines. No such additional scope or change work will be initiated, started, or acted upon
without express written consent of CLIENT.
All work will be delivered in electronic format unless required otherwise.
In-person check-ins and production steps that are identified above or which are identified as
the project continues forward will be considered expensible travel. The Parties will align to
expense allocation for meetings / production and must have approved documentation to
support with signature, solely from CLIENT identified Stakeholders. At no time will VI submit
expenses to CLIENT that have not been authorized in advance, in writing.
Post-Launch Maintenance and Reporting can be cancelled anytime on 30 days written notice
This agreement does not cover any products or services not detailed and quoted in herein
Any significant changes to the scope of the specifications herein require an amendment to
this agreement executed by The Parties.
The content of this agreement is confidential and may not be shared with any 3rd Party
without prior written consent from either Party. VI agrees in total to sign all NDA and non-
compete clauses as identified by CLIENT prior to work start.
VI represents and warrants that it has all rights necessary to grant the rights to
Customer contemplated by this Agreement.
CLIENT agrees that VI may use the process, outcome and imagery of the scope herein for use in
case studies or company credentials but only upon CLIENT’s prior written approval, which
CLIENT may withhold in its sole discretion. VI warrants that all such utilization will be provided to
CLIENT prior to submission and that CLIENT has right to modify or refine documents prior to
release or use by VI.
CONFIDENTIAL INFORMATION
o Obligation of Confidentiality. In performing consulting services under this Agreement, VI
Please indicate to the undersigned your acceptance of this agreement by signing two copies of this
agreement and returning by email to @venuiti.com. Venuiti will sign this agreement and return one fully
signed original to the Client.
We are delighted to be able to work with you. Should you have any questions, do not hesitate to
communicate with the undersigned at 000-000-0000. Please note that Venuiti will begin working on the
project only when the Client’s acceptance has been received.
CLIENT
Date:
“I have the authority to bind the Company”