Get Started. It's Free
or sign up with your email address
Rocket clouds
strbrd.com by Mind Map: strbrd.com

1. Crew

1.1. Availability

1.2. Experience

1.3. Can be assigned to an event or can assign themselves to an event

1.4. Can be a skipper (administrator)

2. Boat

2.1. Potentially stores large database of boat characteristics. Could be loaded from somewhere or built up by users. Probably built by cheap labour. This may form the basis of pricing, so need to consider further.

2.2. Yacht public page

2.2.1. App serves as the website for each boat.

2.2.2. Can use URL redirects from say www.yachtname.com to yachtname.strbrd.com

2.2.3. According to settings, public can view published items,eg results, events, crew etc

2.2.4. Visitors to boat homepages should be able to follow boat on twitter or facebook, rather than our actual site.

2.2.5. Automatically bring back results from races for that boat.

2.2.6. Heavily based around photos which should attract more visitors

2.2.7. Provides an entree to crew to become part of the boat. Displays interesting characteristics of the boat.

2.2.8. Page should have Facebook Like & Twitter Tweet on it to increase distribution / traffic.

2.2.9. News. Boats and events will often appear in the news. We should provide a link to that.

2.2.10. Provides link to home yacht club.

2.2.11. Status updates (potentially) scrolling. See www.spotify.com as a good example.

2.3. Attributes

2.3.1. Description

2.3.2. Dimensions

2.3.2.1. LOA

2.3.2.2. LWL

2.3.2.3. Beam (max)

2.3.2.4. Displacement

2.3.2.5. Ballast

2.3.2.6. Draft Standard

2.3.2.7. Draft Minimum

2.3.2.8. Water Tank

2.3.2.9. Fuel Tank

2.3.3. Sailplan

2.3.3.1. Inventory

2.3.4. Details

2.3.4.1. Builder

2.3.4.2. Country

2.3.4.3. Designer

2.3.4.4. Hull Type

2.3.4.5. Rig Type

2.3.4.6. Material

2.3.4.7. Keel Type

2.3.4.8. CE Class

2.3.4.9. Production

2.3.4.10. Engine

2.3.5. Home yacht club

2.3.5.1. URL

2.3.5.2. Address (Google maps)

3. According to settings, update to yacht's page get posted to Twitter with URL. See tripit or Runmeter. The idea being more widely distributed info with links back to the site.

4. Regatta Management

4.1. Races

4.1.1. Race Type

4.1.1.1. Pursuit

4.1.1.2. Standard

4.1.2. Results

4.1.2.1. Provisional

4.1.2.2. Final

4.1.3. Scoring

4.1.3.1. Pursuit Races

4.1.3.1.1. Start Time

4.1.3.1.2. Finish Time

4.1.3.1.3. Additions & Subtractions

4.1.3.2. Standard Race

4.1.4. Protests

4.1.4.1. Notification Engine

4.2. Entrants

4.2.1. Data

4.2.1.1. Sail #

4.2.1.2. Skipper

4.2.1.3. Contact Details

4.2.1.4. Yacht Club

4.2.1.5. LOA, etc.

4.3. Staff

4.3.1. Regatta Director

4.3.1.1. Contact Info

4.3.2. Roles

4.4. Awards

4.5. Divisions

4.6. Data

4.6.1. Dates

4.6.2. Places

4.6.3. Documents, eg NOR

4.7. Handicaps

4.7.1. Handicap Type

4.8. History. All information for an event and/or a race should be locked. That is to say if a boat changes skipper between events, then the skipper for that event should be recorded, not changed. Same goes for handicaps, contact details, etc.

5. Event

5.1. Races

5.1.1. Dates

5.1.2. Type

5.1.2.1. Social Race

5.1.2.2. Serious Race

5.1.2.3. Delivery

5.1.3. Crew

5.1.3.1. Min

5.1.3.2. Max

5.1.4. From

5.1.5. To

5.1.6. Time Required

5.1.7. CAT Rating

5.1.7.1. Default Crew #s

5.1.8. Part of a Series

5.2. Accomodation

5.3. Travel arrangements

5.4. Crew Attending

5.5. Print off checklist for today's race with crew attending, race start, each to-do list etc.

5.6. Download map for nav software for particular race.

5.7. Download NOR when loading event.

5.8. Be notified when supplemental notifications are posted to a subscribed event.

5.9. Be notified when results are posted and updated. Post 'status update' when results are posted.

5.10. Link to Top Yacht Software

5.11. News. Boats and events will often appear in the news. We should provide a link to that.

5.12. Skippers (administrators) should be able to create events

5.13. Skippers (administrators) should be able to add and remove crew to events

6. Web application

6.1. UI

6.1.1. Web 2.5+!

6.1.2. Pre-populate wherever possible

6.1.3. Everything designed to reduce friction

6.1.4. Likes

6.1.4.1. http://letsfreckle.com/

6.1.4.2. http://xero.com

6.1.4.3. http://www.yammer.com

6.1.4.4. http://www.nicereply.com

6.1.4.5. http://www.supereightstudio.com

6.1.4.6. http://dribbble.com

6.1.4.7. http://outright.com

6.1.4.8. http://flavors.me/

6.1.4.9. http://www.assistly.com/

6.1.4.10. http://www.flowtown.com

6.1.4.11. http://swipely.com

6.1.5. Patterns & Techniques

6.1.5.1. Progressive Disclosure

6.1.5.2. Lazy Registration

6.1.5.3. Forgiving format in search

6.1.5.4. Clear Primary Actions

6.1.5.5. Breadcrumbs

6.1.5.6. Hover Controls

6.1.5.7. Calm Separation of Elements

6.1.5.8. Treat text as User Interface

6.1.5.9. Simple and Usable Forms

6.1.5.10. Real-Time Updates

6.1.5.11. User-Centric User Interface

6.1.5.12. Advertise features of the application

6.1.5.13. Use contrast to manage focus

6.1.6. Allow feedback

6.2. Social

6.2.1. Blog

6.2.1.1. Integrated

6.2.1.1.1. Twitter

6.2.2. Photos

6.2.2.1. Integrated

6.2.2.1.1. Facebook

6.2.2.1.2. Flickr

6.2.3. Videos

6.2.3.1. Integrated

6.2.3.1.1. Vimeo

6.2.3.1.2. YouTube

6.2.4. Automated twitter

6.2.4.1. So when the skipper updates a status on our site it feeds out through the twitted account of the boat

6.2.4.2. Users should be able to create account through twitter

6.2.5. Automated facebook

6.2.5.1. Users should be able to create account / login through facebook

6.2.5.2. According to settings, update to yacht's\rpage get posted to Facebook. See tripit\ror Runmeter.

6.2.6. Status updates

6.3. Support

6.3.1. Assistly

7. Objectives

7.1. Increase the likelihood of crew organisation through the use of social networking.

7.2. Make the life of a yacht owner easier than ever to campaign a yacht over a season

7.3. Create a database of events of yacht races to make management of a series easier

7.4. A better organized boat is more likely to be successful. The primary objective is to make strbrd boats winning boats

8. Sales & Marketing

8.1. Free trial for 30 days. No credit card required.

8.2. Preferably use SecurePay as payment Gateway, however Paypal might be the quickest way to deliver MVP

8.3. All registrations are populated back in to Microsoft CRM. Activity always logged in CRM.

8.4. Pricing based on length of boat in US Dollars. 31 - 40 foot $39. 41 - 50 foot $49. 51 foot - 60 foot $59. 61+ $69

8.5. Use Chargify for subscriptions and billing

8.6. Use Payment Express for merchant gateway

8.7. iPhone App

8.7.1. Look up crew for events

8.7.2. Update boat status

8.7.3. GPS for events like Runmeter

8.8. Sailing websites for PR

8.8.1. Sailing anarchy

8.8.2. Sail World

8.8.3. Yachtloop

8.8.4. My Sailing

8.8.5. Sailing Magazine

8.8.6. Valencia Sailing

8.8.7. TP52 Class site

8.8.8. Sail Karma

8.8.9. LuvMyBoat

8.9. Exhibitions

8.9.1. US Sailing Boat Show

8.10. Regatas

8.10.1. http://www.coastalclassic.co.nz/

8.10.2. http://www.regattadates.com/

9. Public Website

9.1. Sign up using Twitter or Facebook by default. See www.hunch.com as an example

9.2. Keywords

9.2.1. Crew management

9.2.2. Crew organisation

9.2.3. Yacht management

9.2.4. Yacht website

9.2.5. Yacht homepage

9.2.6. Yacht organisation

9.2.7. Yacht organization

9.2.8. Yacht website templates

9.2.9. Yacht ownership management

9.2.10. Yacht social networking

9.3. Metrics

9.3.1. Kissmetrics

9.3.2. Ginzametrics

10. iPhone Application

10.1. Take a photo of your boat, register name and email and post immediately to sign up.

10.2. See new photo sharing application with filters for example

10.3. Similar to RunMeter, if the application is on during a race, you can use it as a timing device, it can track your course using Google Maps

10.4. Add and delete crew from an event

10.5. Send reminders and reminders to crew about races

10.6. Event results are posted via push notification.