This our complete mail-out pitch deck as of 22 Sept 2012. For specific pitches we often use a subset of these slides.

1. Neil LaChapelle Seeking Seed Capital to Expand App Suite
David de Weerdt and Develop a Platform for Future Apps
Co-Founders In Silicon Valley Sept 3 - 15
100-151 Charles St. W. Kitchener-Waterloo, Ontario, Canada

2. Have you ever been invited
to a nice dinner party…
(CC) Flikr User Iwona Erskine-Kellie (iwona_kellie)

3. …that turned out to be a
multi-level marketing “sales party”?
(CC) Flikr User Tris Hussey (tris)

4. ick!

5. social networks
are icky contexts
for commerce

6. and this
explains the
Web 2.0
paradox

7. There’s a HUGE demand for social networks,
but when you try to monetize them…

8. You piss people off!

9. It’s not nice
to monetize
people’s
online
living rooms

10. But there are social groupings that
naturally amplify commerce.
Bond Buy
Contexts where people happily
both bond and buy.

11. They’re called…
Bond Buy

12. Scenes
Bond Buy
Art Scene, Fashion Scene, Startup Scene, Foodie Scene, Classic
Cars, Surf Scene, Gamers, Yoga Scene, Punk Scene, Quilters…
Scenes are real, they’re vibrant, and there’s lots of them!
(Notice boards like this are one way to spot scenes.)

13. Scenes are:
Bond Buy
Not just social networks. Your scene depends on people
you’ll never meet, who’ll never meet you.
Not just interest networks. Like-minded people can interact
without igniting scene dynamics.

14. Scenes Naturally Entail Commerce
Bond Buy
Look above! Most of these posters involve buying/selling.
You have to consume scene stuff to build your scene cred,
relationships and identities.

15. What about consumers?

16. What about consumers?
Consumers also face a
painful Web 2.0 paradox

17. There are lots of apps consumers can use
to make things happen on scenes!

18. Lots and lots and lots and lots and lots of them…

19. And each service covers lots and lots of scenes
(kind of indiscriminately – all your contacts get networked together)

20. and this
explains the
Web 2.0
paradox
(for consumers)

21. Pain Point 1: Excessive Fragmentation – social functionality
is scattered across too many web services: no itegration.

22. Pain Point 2: Inadequate Segmentation – diverse friends
get pulled into each network. Audiences get mixed up

23. This pain
and paradox of
(over/under)
differentiation
exists because

24. Each web service
covers only part
of a consumer’s
social scene

27. Co-Founders
We (Sceneverse Inc.) will prove 3 things:
1) Scenes, not networks, are the right
contexts for amplifying natural
cycles of bonding & buying.
Neil LaChapelle David de Weerdt
Design Leader
Past Creative Dir.
Business Leader
Past CEO &
1) Scene dynamics are universal enough
3 Startups Business Dev. that you can build a platform that
Advisors gets, crunches and serves scene data.
1) Context-aware apps can use that data
to help scenes rock harder.
David Orban Robert Kozinets Renee Lloyd We’re starting by launching our own app
Fellow, Berkman
CEO dotSUB
Singularity U
Chair, Marketing
Schulich Business Center for Internet suite for the indie music scene.
Humanity + Global expert in & Society, Harvard
Lifeboat Found. tribal marketing. Project VRM
Later, we’ll help other companies build
Sceneverse-enabled apps.
They’ll get the APIs, SDKs, data, analytics
Doug Cooper Alan Cross Ladan Tahvildari and insights they need to rock their scenes.
Exec in Residence
Communitech
Professional Music
Geek - Creator of
Professor at U of
Waterloo, Dept of
We’ll crunch and serve.
Co-Founder “Ongoing History Electrical and
Splintir of New Music” Computer Eng.

29. A data-processing Context-aware
platform that apps that enhance
understands scene your scene
context. experience.

30. Scene Contexts Consist Of…
Groups of people, in specific places & times, invested in topics with high intrinsic value for them.
Social Place Time Topic
$
Value
(We call these “Sceneverse dimensions”)

31. Social Place Time Topic
$
Value
By tagging each data point with scene metadata, we can derive scene
structure, and assemble scene views as users and app developers require.
Social Place Time Topic
$
Value

32. Place + Topic Tuples are Primary
E.g Silicon Valley Startup Scene.
Our code-name for them is “shrines”.
Places devoted to topics.
Place Topic
Participant Relationship

33. Our Test Case: The Indie Music Scene
“Kickstarter for Shows” (In Closed Beta) “Yelp for Scenes” (Working Prototype)
They both look at the same “elephant”
the same scene data/metadata
on our back-end platform

34. Go-To Market Strategy
Analytics
Driver Data Farm
Revenue App Store
API
Apps
Product Scenes Scene App Builder The Sceneverse
Phase Launch Scale Hyper Growth
First we make money from scenes we build apps for ourselves. Then we ramp up growth by enabling other companies to build SV-enabled app
for their own scenes, using SV data and functionality. Finally, as our data about scenes gets very rich, we leverage that data for more revenues.

35. Market for Our First App Suite
(cc) Flikr user Nick Sherman
(cc) Flikr user steve loya
500K Bands x 24 shows/year x 15 fans x $10 ticket = $1.8B Merch & Sponsorship
0.5% share = $90MM Modules to Come…
Is big enough to sustain significant upside even with conservative estimates

36. Currently We Are Seeking
• $2MM Total
• Launch First Scene: Indie Music App Suite
• $1MM to develop back-end scene-data
platform
• Series A readiness by Q3 2013