Trip Hop Records
Web Site and E-Commerce
Creation Plan
Presented by:
Kaylah Pavlicek
Web Site and E-Commerce Creation Plan
Developing an e-commerce presence in the online marketplace for
Trip Hop Records is an important part of creating residual profits and opening
new avenues for increased visibility and production networking opportunities. The
following will detail the proposed e-commerce implementation project.
Planning the site
Research
Research and scheduling
Does Trip Hop Records really need a web site with e-commerce capabilities? Yes! Every competitor in the music industry has a web site for various reasons. Artists who have record contracts not only have an online existence through the record label company but many of them also have their own private web site as well as fan sites that they maintain and update.
If we start with the first stages of the
e-commerce project in November of 2007, we should have the web site ready to
advertise by mid-February of 2008.
Vision and purpose
The vision and purpose of creating a web site with e-commerce capabilities is to bring original music to the masses, to produce profits through e-commerce technology, and to generate network connections with the music industry and other artists.
Strategic objectives
Create an e-commerce shopping cart environment so that fans and visitors can purchase Trip Hop gear and CD’s (and other accessories in the future as the budget allows)
Produce a collaboration network base with the industry, artists, and fans
Offer music preview downloads and other media (graphics, logos, screensavers, wallpapers)
Establish an added alliance between the crew members and their fans
Critical success factors
This project must be handled with a strict chain of command while at the same time utilizing the teamwork skills of each member on the project. Members are encouraged to think creatively in their assigned tasks but to ultimately keep the bigger picture in mind.
Weekly meetings are to be scheduled and attendance mandatory for everyone.
Technology
ISP server hosting will be provided by
Mid-Continent Communications located in
Risk and pain factors
General cost of deploying the web site will be minimal as it is going to be an FTP to the server. The budget allows for downtime and upgrades as mentioned in the budget portion of this plan.
Plan
Competitive landscape
|
|
Trip Hop Records |
NoFace Records |
RedLight Productions |
Sonny |
|
Sales |
$31,000.00 |
$26,000.00 |
$24,005.00 |
$45,560.00 |
|
Net profit (loss) |
$24,640.00 |
$21,212.00 |
$20,015.00 |
$31,125.00 |
|
# of Employees |
6 |
8 |
7 |
11 |
|
Market share |
20% |
12% |
15% |
21% |
Brainstorm
Create overall look and feel
Create graphical elements
Establish e-commerce environment
Write content
Develop calendar
Program contact form
Create wallpapers and screensavers
Develop forum/chat area for fans and crew
Plan
Look and feel
Color Scheme: black, white, purple
Deliverables
Need a marketing plan and an IT plan to present to stakeholders and employees.
Building the site
Discovery
Team structure
|
Role |
Resource name |
Reports to |
|
Project Manager |
Austin Lewis |
Owner of Site & Web Developer |
|
Marketing manager |
Isaac Roberts |
Project Manager |
|
Graphic designer |
Jaime Randolph |
Marketing Manager & Web Developer |
|
Web developer |
Kaylah Pavlicek |
Project Manager |
|
Content Writers |
|
Project Manager & Web Developer |
Content
The content will consist of artist biographies with photos, upcoming show information (a calendar needs to be created and a form for requesting a show performance), songs to download (a portal needs to be implemented), lyrics (create links to a PDF doc or use inline frames), contact information (a contact form needs to be created), gear to purchase (online shopping interface needs to be implemented), and a show gallery (a selection of photo albums needs to be created).
Project plan
Page 1: Home – contains quotes from various
artists as well as a large logo image
Page 2: Artist bios (to be completed by Elizabeth Brander by December 1st,
2007)
Page 3: Upcoming shows (to be completed by Sue Bines by December 1st,
2007)
Page 4: Contact information (to be completed by Elizabeth Brander by December 6th,
2006)
Page 5: Show gallery (to be completed by Sue Bines by December 6th,
2007)
Page 6: Songs/lyrics (to be completed by Sue Bines by December 10th,
2007)
Page 7: Gear (to be completed by Kaylah Pavlicek by December 10th,
2007)
Design
Conceptual design and prototype
Basic design of each page
|
Top Navigation Bar (graphical) |
|
Logo
Content |
|
Bottom Navigation Bar (graphical) |
|
Text
Navigation Bar |
Technology architecture
The Trip Hop Gear page will house the e-commerce environment hosted by PayPal, at this point. An upgrade to a customized shopping cart with a complete product catalog is scheduled to be in the summer of 2008. All secure information such as credit cards is through the PayPal system which uses SSL in its processing.
Implementation
Content development
Content will include: artist bios (personal web site addresses, email addresses, photos); gear items (T-shirts, Sweatshirts, CD’s); single song downloads; contact information; company logo; artist quotes; business plan; upcoming show calendar; song lyrics in PDF format; gallery of photos.
Graphic assets
Gallery of photos – photographs of artists
Fonts – all Verdana, Arial,
Helvetica
Animated objects – navigation bar Flash buttons
Stabilization
Testing
Testing will take place once each week until deployment has occurred. There will be 3 browser tests – IE, Netscape, and FireFox. The tests will consist of how quickly the site loads in each browser, the overall look and feel of the site, and how it comes up in various Web search engines.
Bug fixes
The development software will be utilized in identifying bugs and will be fixed ether immediately upon detection or within a specified period of time – to be determined on a per case basis depending upon the issue at stake.
Deployment
Deployment will take place after all of the content and graphical elements are approved by all project members. Deployment will commence with an upload to the server after which a testing period will be put into effect.
Maintenance plan
Maintenance will be done on a monthly basis by the Project Manager, Austin Lewis. Regular backups will be performed on a weekly basis by the Web Developer, Kaylah Pavlicek. The hard copies will be kept her office for reference.