Scott Kveton

Update: Bac’n has been acquired. Look for the book “Makin’ Bac’n: From Idea to Startup in 21 Days” coming to bookstores in April 2010.

I’ve been in the technology space for awhile now. I started as a system administrator/engineer almost ten years ago and that morphed into a novice developer then open source participant/helper then open web evangelist then leading an engineering team building great products and finally, to selling bacon on the Internet.

“Wait, WTF?!” you say? “You sell bacon on the Internet?!”

Yes. Yes I do.

Its really hard to explain but selling bacon is honestly one of the most interesting/fun things I’ve ever done. Its not just technology-for-the-sake-of-technology. Jason, Michael and I created something out of nothing using off-the-shelf tools to make a solution that delivers real things to real people. And we did it all in less than a month.

While meeting with one of our Bac’n advisors (and hopefully future partner) this past week she summed it up best. After years selling and building technology, she was kind of over with it. “I’m tired of technology. I like solutions and business models that can be affected by technology.” You can see why we’re talking to her.

In any case, for about the last two weeks I’ve been flying solo. Doing Bac’n and putting a few feelers out to close friends and colleagues to see what there is to see that better fits my new found love of technology and a business model. I’ve been astounded by the response and there are quite a few interesting opportunities out there.

I’m still going to participate in open web work and helping to develop technologies that keep data free and put the consumer at the center. That’s something that I think is just too much a part of me not to do. However, my journey henceforth will be rooted in figuring out how building a community can be a good thing for your business.

(Note: I resisted the urge to title this post “Ship it” because I knew there would be some serious twitter hate happening – and rightfully so … hahaha)

Its amazing what you can accomplish with a bunch of people in a room … :-) I’m at the Data Sharing Summit and I just led a discussion on “What is the (stinkin’) problem?” The gist is this; what is the problem we’re trying to solve with all of these formats, protocols and solutions we’re hacking up and presenting here this weekend.

Fortunately, we had a great group and got a nice list of use cases that we think describe the problems we’re trying to solve:

• Profile and registration data: How do we quantify and manage profile data across lots of different sites. This is your first/last name, email address, avatar, etc. All of these create your profile.
• Profile update push: I’ve updated something in my profile and now I would like to push it to all of the sites that use this data. New email address? Great, push it out to all of the sites (or IMHO – get it from on place all the time).
• New friend on A, update on B: If I have a new friend in my entire social network, it should now be available to me on any site I visit. New friend on site A, it should update that onto site B. Yes, there are oodles of issues with this; what if I only want to be friends with this user in the context of site A … well, we don’t have an answer for that yet … you’ll have to wait for v2.0 … :-)
• eVite problem: In what can only be deemed really poor brand mojo, we have the eVite problem. Let’s say I want to invite a friend to an event. I have to give the event site, let’s say eVite, the email address of my friend. My friend might not want me to do that or trust the site I’ve given it to but its out of their control. This falls under management of your personal assets and quite honestly, would be like your friend posting your phone number to a sex chat discussion room … you might not want all of *those* calls.
• Share resources once, available everywhere: When I post a video on one site, my friends should see that where ever they are. I shouldn’t have to post on YouTube, Blip or Yahoo! … post it once and people should see it where ever you are. The same is for basic status information (Twitter, Pownce), birthday notices, etc … any resource you might want to share.
• Where did I put that?: The majority of users just use the Internet. Its a mash of a whole bunch of sites and users put content all over the place. How do I quickly and easily see where I put what that I touched, edited, added, uploaded or modified? This is a toughy in my opinion but there was general consensus its a good one.
• Consolidated messaging: This could possibly fall under the ’share once, share everwhere’ category but I do think this merits a separate entry. I don’t want a gazillion messaging systems on every site. I have a Flickr inbox, Yahoo, Gmail, Zooomr, you name it. I don’t want to visit every one. Let me get to a site, any site, and see my messages. This is akin to my belief that you shouldn’t go to social networking sites; social networking (the one that you have) should be a function of every site.
• Friend decay: I dated this girl once … it was a one night stand. She added me as a friend on Facebook. Years later, we don’t talk and probably never will.* How do I decay that relationship so it doesn’t show up as prominent or even valid in my social network? * – I made up that bit about the one night stand and Facebook but you get the idea.

Alright, so its not much but its definitely a start. Lots and lots of work to be done here folks but clearly once we know the problem, its that much easier to start working on the solution … :-)