One of my favorite things about having worked on Silicon Florist for more than two years is watching the progress people are making. And watching how things change. I’ve been lucky enough to watch ideas, events, and companies come and go—and I’ve had the chance to document their stories. It’s never something I intended to do. It just kind of happened.
Sometimes those stories are happy. Sometimes they’re not. But they’re always good stories. The latest story I’ve had the pleasure of documenting as it went full circle? The story of Shizzow.
What’s Shizzow, you ask? Well, it was Portland’s own foray into the world of sharing location information. Back in the day where there was Brightkite and a couple of others. It was a strong competitor to the location sharing services. And a way to be more social by knowing who was where when. Or as it was described in the first post:
Shizzow provides the technology for you to notify your friends of your location, with as little effort as possible, so you can spend more time hanging out with your peeps and less time trying to coordinate bringing them together through phone, email, SMS and IM.
I liked the idea. And I really liked the folks who were working to put it together and make it into something. I can still remember sitting down with Ryan Snyder and Sam Keen when they unveiled the idea. And then hearing Dawn Foster was going to help. And later with Mark Wallaert.
It was just a good group of people trying to build something that had a ton of potential.
I liked them so much, in fact, that I invited them to share their idea with the folks at the Silicon Florist hosted Portland Lunch 2.0 at CubeSpace.
And I wasn’t the only one who thought so. The entire Portland tech community embraced them. And Shizzow, little by little, became a community pursuit. And the Shizzow folks knew it.
I’d like to give knucks to Scott Kevton and Ray King, who served as fabulous advisors; bows of gratitude to the publicity given by Rick Turoczy at the Silicon Florist, Cami Kaos and Dr. Normal at Strange Love Live, Marshall Kirkpatrick at Read Write Web, and Adam Duvander of MapScripting; pint glass clinks to Sue Brown, Matt Gifford, Reid Biels, Bill Jackson, John Nastos, Don Park, Sam Grover, Ken Baer and the other developers who pounded on the Shizzow API; and high fives to Sam Keen, Gus Torres, Carolynn Duncan, Aaron Hockley, Ryan Buchanan, and the countless number of others who have helped along the way.
But it wasn’t all champagne and roses. Like any startup, Shizzow suffered some bumps and setbacks.
For as quickly as Shizzow took off locally, it struggled to find a following in other areas. At the time, that didn’t seem to matter. We loved it. We used it. We knew where people were. And things kept getting better and better. From our perspective.
But then the market changed a bit. Competitors got funding. Platforms grew more prominently. New people and companies began to enter the race with new ideas—and then the game changed.
And then the economy changed. And suddenly it wasn’t so easy to bootstrap a startup and work on some side gigs. And with little capital, there simply weren’t enough hands to get everything done.
New shiny objects came along. Shizzow remained a strong product, but some of the lustre began to fade.
We’ve seen the writing on the wall for some time now, with services like Foursquare and Gowalla pushing forward and securing funding, that the outlook for Shizzow and its future was dim. We’ve had to admit to ourselves, after each of has suffered periods of burnout while attempting to juggle full-time jobs and this startup, that we simply cannot continue to push Shizzow forward with our current lack of resources.
So Shizzow will continue. But not with the speed and effort it once had. And it will return to the realm of side project for Mark. Not shuttered. But maybe a little mothballed.
So what did we learn from Shizzow?
It was a great effort. With many lessons learned by the founders. And many more lessons for all of us to take away for our own edification.
And yeah, it’s a little sad having to write this. But it happens. These are startups.
And while Shizzow didn’t skyrocket to the levels of some of its counterparts, it did manage some things that were far more important. It captured our imagination with its potential. It built community. And it built connection. And it did all of that at a time when those things were desperately needed.
And honestly—quite honestly—Portland is better for it—and the startup community here is better for it—for having had the opportunity to go along for the ride.
Here’s looking forward to the next startup that manages to accomplish as much as Shizzow did.
For more from the source, read the post on Shizzow’s future from Ryan Snyder. And if you appreciate what they managed to accomplish as much as I did, please leave them a comment.