Today we released two premium services for SlideShare. (see venturebeat, techcrunch, om malik, and our blog). One product (LeadShare) helps you use your documents on SlideShare to collect contact information from potential customers. The other (AdShare) helps you get more targeted traffic to your documents. We’ve been working on this for six months now, so I’m really happy that we can finally talk about it! Here’s a quick overview of what we’ve built, and why I think it’s cool.
This service lets you put a “contact me” form on and around your document on SlidSshare. It appears next to the document, on download, inside the document, and inside any embeds of the document: so basically everywhere. ;-> We let you collect not just contact information (like address, phone number, etc) but arbitrary survey questions (e.g. “What size company do you work for”, or “When do you plan on buying a new CRM system”). If you’re a business and already have documents on SlideShare, you can turn this feature on and immediately start adding new potential customers to your sales funnel. Pricing starts at $1 per lead, and goes up as high as $22/lead if every single option is enabled (you probably won’t need every option though).
Here’s the cool thing: we’re inverting the standard process of “tell me your name, rank, serial number, and underwear size and I’ll let you read my promotional business literature”. I think that process is broken, and isn’t a friendly way to begin a relationship with a potential customer. With LeadShare, you share your document and THEN ask for contact information. People only fill out the form if they legitimately WANT to get in touch with you. This fosters trust, leads to higher lead quality, and gives you access to a much broader audience of potential customers (because your documents can be found using search engines, and can be shared viraly using platforms like twitter and facebook). I think it’s a more open and friendly way to do b2b marketing.
The other service we’ve built helps you get more views for your documents on SlideShare. We use the text of your document to promote it against similar documents in a special “promoted” area on the document page. Sometimes it can be hard to get noticed on SlideShare. AdShare will help you get more views from the kind of people that are likely to be interested in your content.
Here’s why I think this is an interesting new form of advertising. 1)It’s a very high level of engagement. On average people spend 3 minutes looking at a document on slideshare. When was the last time you spent 3 minutes looking at an ad?
2)It’s very highly leveraged. You’re not just buying a single view, you’re buying social and search engine traction for your content. Popular traffic becomes more popular on SlideShare as people bookmark it and forward it and blog about it, so if you give your documents a “boost” by promoting them they’re likely to be embedded, bookmarked, tweeted, and search indexed, leading to continual “free” views. Of course, if your content sucks this is unlikely to happen. Like every form of advertising, the quality of the creative matters. ;->
AdShare costs only .25 per document view (.35 per document if it is geo-targeted). And if you’re using LeadShare, you can use AdShare to drive more targeted views to your lead-generating documents. Whoa!
I’m sure you can tell how excited I am about us launching these new services. Please take them for a spin and let me know what you think. Is this a useful way to connect with your customers? What features should we ad? What do you think of our pricing model? The comments area below is where you can have your say.
We just released something really cool! It’s a.plugin for PowerPoint that lets you do pretty much anything that you can do on the website … from within PowerPoint.
As Keanu would say, whoa. Using PowerPoint to browse a site for sharing PowerPoint. Very meta.
We call it the “SlideShare Ribbon”. The best part IMHO is that you can search for PowerPoint files and download them directly from slideshare into PowerPoint. Also, uploading is really convenient, so if you’re working on a presentation, once it’s ready you just click one button and it will upload in the background.
The best BEST part, though, is something we really should have built into SlideShare (don’t worry, it’s coming soon). It’s a console that shows you how many views, comments, and favorites each of your presentations has received. If you’re using SlideShare to market your business, this is a really handy way to see, in one screen, exactly how many people you’ve been able to reach.
Major props to the Microsoft crew over in Seattle … they were incredibly helpful to us over the course of this project.
Now it’s time for the second meeting, and I’m proud to say that SlideShare will be hosting the event.
The techcrunch article lays out the details. We are really happy with how things worked out! Many thanks to everybody out there who played a part in making it happen.
We could have made a press release, of course, but press releases are kinda boring. So we made a meet henry style presentation instead.
“Meet Henry” is a presentation style that evolved on slideshare, and is a great way to describe the value of any good or service (through a simple, predictable narrative arc). In our case, we used Dave McClure (who’s an angel AND an advisor) as our “Henry”.
We’re really grateful to our community for taking us this far. We love you guys and all the cool stuff you do, and can’t wait to see what you upload next! We promise to work really hard to make the SlideShare experience as useful and pleasurable as possible.
As I wrote in my last post, we’ve been going through the process of adding a content delivery network (PantherExpress) to SlideShare. Since there isn’t a lot of information on the net about how to use a CDN to accelerate content that is hosted on S3, I thought I’d publish it here.
The way you integrate with any CDN is pretty much the same.
1) Create a subdomain (e.g. static.slideshare.net) for your domain.
2) Point that subdomain to your CDN (e.g. 132.pantherexpress.com) using a CNAME entry in your DNS.
3) Configure the CDN to know that the “origin server” they should use is your amazon S3 bucket.
4) When the CDN gets a live request for a piece of content, it serves the content if it has it in it’s cache. Otherwise, it fetches the content from the origin server and then serves it.
This is great if you’re starting out. But what if you’ve already launched? You NEED to be able to try out your CDN integration, and then quickly back it out if it isn’t working. There’s two ways to go here.
1) If you’ve thought ahead, you’ve named your s3 bucket after your subdomain (e.g. static.slideshare.net) then you can point your CNAME entry to to bucket. To switch to your CDN, change the CNAME entry. If there’re a problem, switch back. The switch will take however long your “time to live” is set to in DNS.
2) OTOH, you probably WEREN’T forward thinking enough to name your s3 bucket after your subdomain. In this case (the normal case), you have to make sure your webapp is written so that you can quickly change the location where it expects to find external content. We didn’t do that (we had hard-coded the s3 bucket url into the code), so we had to externalize that into a property file that could be easily edited.
One thing I’ve been working on in the last month is accelerating the serving of SlideShare content using a “content delivery network” (or CDN). You use a CDN so your content can be cached in RAM, in a place that is geographically near your customers, instead of on disk, in a place that is far away from your customer. This makes a BIG difference in terms of page load time. There isn’t much on the net about hooking a CDN up to Amazon S3, so here’s what I learned:
Frankly, the process of shopping for a CDN vendor is *really* annoying, especially for someone who has become used to buying these cloud-based services like S3 that are priced openly and on the basis of usage. The process is very “enterprise procurement”: lots of high-pressure salesmen trying to get you to sign two-year contracts, and with no price transparency. One way to win is to get them to bid against each other. But the whole thing feels like an unnecessary amount of work.
Fortunately, we found a company that had transparent pricing that seemed fair to us, and that wasn’t about locking us into a long-term contract: PantherExpress! Their pricing is standardized, is per-gigabyte, and gets cheaper the more you use it. Given that Amazon doesn’t provide a CDN, this is the next best thing for serving up content fast. It costs $.28/GB for the first 8 TB/month, $.24/GB for the next 8 TB, and so on. More expensive by Amazon, but a decent price for global content delivery.
Hooking PantherExpress up to S3 was pretty easy, and I imagine the same procedure would work with other CDNs. I’ll cover that in my next post.
I’m really pleased to announce a new member of the SlideShare advisory board. Edward Tufte, author of such seminal works as “The Visual Display of Quantitative Information”, has agreed to join the SlideShare team.
Tufte’s work on presentation design is obviously especially relevant to us. His critique of current approaches to presentations (The cognitive style of PowerPoint) was a major driver of the new styles of presentation that have cropped up in the last few years.
This will result in some changes to the SlideShare experience as you currently know it. Most importantly, we’re implementing some filters that will block the most egregious examples of PowerPoint abuse from our system. You can read the official announcement for the whole story.
Sergey Chernyshev just released a much-needed piece of code last week: an extension that makes it easy to embed slideshare slideshows into MediaWiki, the open-source wiki software that powers wikipedia.
This is pretty huge: for an organization trying to build a knowledge repository, easy integration between wiki content and social document sharing is a really important. A good example of how this can be used can be found on Sergey’s site TechPresentations.org , which archives presentations from all tech conferences worldwide.
A company that wanted to run a private mediawiki could even upload slideshows to slideshare, not share them publicly, and embed them into their corporate wiki. This would provide a wiki that supported embedded office documents, which would be a killer knowledge-management tool.
Just like Chris Hellman’s slidehare ego widget, this mashup does it’s work without using our API. I’m reminded that RSS and embed codes are powerful integration points with any system. It’s easy to forget that a lot of the time, a formal REST API isn’t even necessary in order to build a mashup!
Hey peeps! We’re having some difficult-to-troubleshoot problems with our server cluster right now. The primary problem seems to be with file uploads: I’ve taken the site down into maintenance mode while we scramble to fix this. Will keep y’all updated via this blog, blog.slideshare.net, getsatisfaction.com, email, and carrier pigeon as we work to fix this.
Chris Heilman published an article where he described how to make a slideshow widget that has ALL your slideshows from slideshare in it. The article was recently profiled in the Ajaxian.
The result looks totally bad-ass. In fact, we’ve been working on a similar widget, but this one totally blows ours out of the water. The only downside is that his current solution required server-side scripting (with php). We’ll definitely take inspiration from this design and try to put something out in the near future that does something like this from a simple embed.
It’s interesting that Chris chose NOT to use our APIs for doing this, relying instead on our RSS feeds and embed codes to get the information he needed. Chris writes:
I had a look at the API of slideshare but I am always a bit bored with having to go through a developer ID and then do everything on the server. That’s why I put on my “ethical hacker” hat and took a look at the RSS feed of my slides and found everything I need there!
Sounds like making our read-only API calls usable without a login would have helped here. What else would make our API more accessible or useful to developers?