OBJECTIVE        3

BACKGROUND OF THE BOOK        3

BACKGROUND OF THE PROJECT        3

DEVELOPER SCOPE
OF WORKS        3

CMS SPECIFICATION        4

PAGES AND POSTS        4

NAVIGATION        4

COMPONENTS        4

RESPONSIVE TEMPLATES        4

WORDPRESS PLUGINS        5

SEO specification        6

PLUGIN REQUIREMENTS        6

ANALYTICS REQUIREMENTS        7

STRUCTURE REQUIREMENTS        7

DUPLICATED CONTENT        7

MOBILE EXPERIENCE        7

RUN_FRICTIONLESS
SCOPE OF WORKS        7

MESSENGER + SOCIAL MEDIA        7

Account access        8

Email addresses        8

Hosting        8

Budget        8

OBJECTIVE

Create a Wordpress site to drive reservations of a book during pre-launch. 20 percent of reservations are expected to convert to a book sale. Target 5,000 reservations.

BACKGROUND OF THE BOOK

Run_frictionless was created to help founders from internet startups and leaders of sales organizations from enterprise, scale sales operations. The book focuses on the concepts required to design and build sales systems. The text is written in an easy to understand language so technical founders find it easy to grasp. The title run_frictionless was derived from the idea that the more friction points removed from a sales system, the less the marginal cost of each sale.

The brand has a scientific, non-sales look and feel. The logo, visual language etc are designed to appear frictionless. This is an important attribute of the brand, which has to make its way into the experience of the website.

BACKGROUND OF THE PROJECT

The primary focus of the website is to entice visitors to register their name and email address and reserve a copy of the book at 50% of the retail price when the book goes on sale 2018. There will be many pre-launch activities designed to draw traffic to the site before the book goes on sale. The more reservations, the more copies of the book and reviews we capture the day the book goes on sale on Amazon.

The sale of the book is key to building the credibility of the author as an authority on the subject of sales systems, and ultimately the brand. The book lays down the concepts on how to design and build a sales system. In addition to book reservations, the purpose of the website is to drive pre-launch engagement with readers (events, videos, and articles on the book), and offer visitors an opportunity to attend workshops and purchase consulting hours.

• Set up a dev environment and recommend hoster
• Create an instance of WordPress (as per specification)
• Install plugins
• Create a holding page with a web capture form, built using the same WordPress installation as the website.
• Build a Wordpress website (/main, /shop, /blog)
• 10 variant HTML component templates
• Implement an SEO specification
• training on the use of CMS

CMS SPECIFICATION

A holding page has been built here [hidden] There are several pages we will need to be created to support our pre-launch of the book.

We will need to be able to edit 95% of words and pictures within CMS. This includes the main navigation, footer navigation, and the components in between. So we need a template is easy to add rows and columns, new sections, anchor html tags etc. Our preference is to build the site in Visual Composer for WordPress to allow easy drag and drop edits on the website.

Our preference is to use frameworks (ex: Bootstrap 4 for CSS and a skeleton WordPress theme) instead of a full WordPress theme to keep the site running like a lean, mean machine.

PAGES AND POSTS

●      Add, delete, modify and clone

NAVIGATION

●      Add, delete and modify links

●      Main nav, footer navigation and social media links

●      Add, remove or modify anchor links to components

COMPONENTS

●      Add, modify or remove a component from a page

●      Reorder components on a page

●      Suppress or ‘turn off’ a component ie draft mode

●      Add an anchor link to a component such that the anchor link can be added to the navigation

Example site built using components: https://pamwayfinding.com/ 

RESPONSIVE TEMPLATES

The site must be ‘mobile first’. That means our priority is display and user experience on mobile, then PC.  We prefer in the interest of time we not build a template from scratch. Site navigation is required to be flat and no more complex than the microsite found here http://klbtheme.com/onepager/

As you can see it is one long scrolling page that uses wordpress 'components'.The template needs to behave responsively across PC desktop, tablet and mobile. We do not mind if you buy an existing theme and modify or modify a template you have.

The designs and page grids for both desktop and mobile device will be provided.

WORDPRESS PLUGINS

Here are our  suggested plugins to be used. The choice of plugin is at the agency discretion. It is important the chosen plugins render on mobile. Free or paid plugins are acceptable. As much as possible use features within Visual Composer to carry out the tasks.

SEO specification

PLUGIN REQUIREMENTS

Yoast SEO.

ANALYTICS REQUIREMENTS

Google Tag Manager installed on all pages in header.php, Google Analytics and other codes added within Google Tag Manager, individual “thank you” pages created for each form so goal tracking is reliable. We have approximately 5 forms of which goal conversion needs to be set up for each.

STRUCTURE REQUIREMENTS

We need to keep in mind from an SEO point of view a one page scrolling website and subdomains are not the best approach. It would be much better to use a subfolder, for example http://www.[hidden].com/shop, than a subdomain version as it holds the authority in a single domain.

With a one page scrolling website we are limited in what we can target keyword wise, and Google uses content as an indicator of authority. Google has been known to dislike single page websites because they are essentially too thin. I would recommend structuring the website to have multiple pages.

DUPLICATED CONTENT

Where text is duplicated on the landing page and a dedicated page example blog and event pages, we would like to index the landing page solely. Set the SEO of the duplicated pages like /events and /faqs to noindex.

MOBILE EXPERIENCE

We are building our html email templates to be mobile-first. We would like the website to follow. The template for mobile will be different and include functions available exclusively for mobile users. These include being able to share content via telegram and whatsapp.

https://medium.com/@uiuxlab/the-most-used-responsive-breakpoints-in-2017-of-mine-9588e9bd3a8a 

• Purchase of a hosting plan, plugins and templates under the Developer direction

• Customer flows
• Website designs
• Downloadable PDF
• Brand guideline, page grids, images and logos
• Social share image
• Final copy deck, terms of use and privacy pages
• Upload images and copy
• User acceptance testing

MESSENGER + SOCIAL MEDIA

Account access

[hidden]

Email addresses

For any plugins/accounts which need to be setup, please register the accounts to: [hidden]. For all inquiries, notifications are to be directed to [hidden].

Hosting

A holding page has already been created and is hosted with a company called [hidden] on a shared package called Basic. We will continue to use this service unless the developer instructs otherwise. We estimate site traffic at 5,000 unique visitors per month in first 6 months.

Budget

Disclaimer

None of runfrictionless, any of its affiliates, providers or their respective officers, directors, employees, agents, independent contractors or licensors (referred to collectively as the runfrictionless Parties) guarantees the accuracy, adequacy, timeliness, reliability, completeness, or usefulness of any of the content and runfrictionless disclaims liability for errors or omissions in the content.

The Document and all of the content is provided “as is”, without any warranty, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose, non-infringement or title. The Document could contain technical inaccuracies or typographical errors.

Runfrictionless Parties do not warrant as to the results of your use of the content or that the Document is free of viruses or other harmful components. Use of this Document is at your own risk. This does not affect those warranties which cannot be excluded or restricted under the applicable laws.

We may discontinue or make changes in the content and the Document at any time without prior notice and without any liability. Any dated information is published as of its date only, and runfrictionless Parties do not undertake any obligation or responsibility to update or amend any such information. We reserve the right to terminate any or all Document offerings or transmissions without prior notice.

Third Party Documents

This Document may contain links to websites controlled, owned, or operated by third-party entities, organisations or people (the Third Party Documents). Links to Third Party Documents on the Document are provided solely for your convenience. If you use these links, you leave the Document. We have not reviewed all of these Third Party Documents and do not control and are not responsible for these websites or their content or availability. Runfrictionless therefore does not endorse or make any representations about them, or any material found there, or any results that may be obtained from using them. If you decide to access any of the Third Party Documents linked to the Document, you do so entirely at your own risk.

Copyright © runfrictionless 2018