Product & Startup Builder

Twitter killed the developer star

Added on by Chris Saad.

Twitter’s updated Mac app wasn’t made by Twitter

The irony here is profound.

This should be a case study in modern business school.

They killed a vibrant ecosystem investing blood sweat and tears into beautiful apps for various niche and mainstream audiences ostensibly to control the experience (actually to control the eyeballs) and then ultimately outsource building the experience.

The result is a shitty app shipping years late.

Lesson: Developers rule. In today's API and software economy you must empower them and get out of the way.

Cc Chris Loic Khris Robert

Originally posted on Facebook


Get More Intentional

Added on by Chris Saad.

I’ve come to believe that we, as builders, need to get more intentional about building products that solve for the unintended consequences we’ve created. If you’re an engineer, designer, growth marketer or investor let me know if you’re interested in this.

My favorite misconception by those who fear change brought on by digital technologies is how they confuse or imbue the tools with intent or inherent value. All human tools simply magnify inherent human traits. If we weren't trolling online we'd be doing it offline.

The technology doesn't "make us" anything - it just highlights who we already are. In some cases technology actually restored old patterns like trust, helping each other get around and telling each other stories.

Of course when you exaggerate something or make it more efficient things change, but those aberrations tend to smooth out as people catch up or other tools compensate.

Originally posted on Facebook

New Opportunities

Added on by Chris Saad.

Today I'm searching for new opportunities.

Over the last 5 years at Echo I’ve lead product for the team who built the Echo Real-time Developer Platform from 0 to 85 Billion API calls a month, some 30+ shrink-wrapped consumer social products and the super slick drag-n-drop Echo Experience Studio with 100+ customer deployments.

We’ve powered amazing brands like Salesforce, AWS, WWE, ESPN, NASDAQ, USA Networks, Washington Post, Coke, Fanta, AT&T, Scripps Networks, Justin Bieber, Lady Gaga and many, many more.

It’s been an amazing journey with a passionate and dedicated team - I’m grateful and humbled to have had their trust and hard work. 

At each stage I’ve had the chance to mature my skills in all aspects of the product and startup lifecycle including rapid prototyping, agile/lean development, branding and marketing, growing teams/cultures, scale and security, developer platforms and ecosystems, B2B product/sales/support, and beautiful, easy-to-use B2C experiences (some lessons learned: http://bit.ly/1DNNqEV).

Today I’m announcing that my time at Echo is coming to a close. It’s time for me to look for new horizons!

I don’t yet have a specific project or company I’ll be doing next. But I know some of the characteristics I’ll be looking for...

  1. Smart, passionate and hungry people
  2. A product making (or having the potential to make) a big impact
  3. An opportunity for me to work my ass off to help the venture succeed

So if you’re working on something great and need help with…

  • Business and product strategy
  • Product management
  • UI/UX
  • Developer platforms/APIs
  • Developer ecosystems and App marketplaces
  • Open standards (adopting, creating, influencing)
  • Modern UI metaphors (Cards, activity streams)
  • Future of media
  • Working with brands

Then I want to hear what you’re working on and how I can help!

Drop me a line

You can also find out more about my experience at www.linkedin.com/in/chrissaad

How to win in Silicon Valley

Added on by Chris Saad.

I’ve been working on startups in one form or another since about 1999. I started hanging out in Silicon Valley informally in 2008 and moved formally at the beginning of 2009. When it comes to playing the basic Silicon Valley ‘game’ of building something meaningful that is validated by the market (most important), investors (less important) and ‘makes the world a better place’ I feel like I’ve had some share of big wins and great outcomes. I’ve also made a lot of mistakes.

Along the way I’ve also advised a lot of startups, as well as paid close attention to what’s worked well in the broader startup ecosystem.

What follows are some of my personal, high-level and incomplete tips resulting from this experience.

As always, there are exceptions to every rule and many of the individual things in this list are not fatal on their own, but if you start making too many of these mistakes, they will really undermine your chances for success.
 

Before you even get started

  • Be in Silicon valley - Yes you can succeed in other places, but the chances of success are so small, why start with a disadvantage

    • Some people argue that the ecosystem in their area is ‘getting better’ or ‘they’re going to help build the ecosystem along the way’. Are you f’ing kidding? It’s hard enough building and driving the train, you can’t build the tracks at the same time!
       

  • Have a big vision - a master plan for how you want to change the world
     

  • Now forget your big vision  - Or you’ll risk trying to boil the ocean. Instead...
     

  • Figure out a very specific, painful, real problem where there’s a significant number of people or companies needing a solution. It’s essential that the problem is one you are personally experiencing and/or are super passionate about solving.
     

  • Find people who are uniquely qualified to execute on this idea with you (Big question: why are YOU qualified?). They should be the best in their field
     

  • If you can’t get the rockstars with experience in the space, then at least find curious, humble, high-EQ people.
     

  • Make sure you have a technical co-founder who knows what they’re doing. If you’re doing software you can’t outsource the core technical function
     

  • You’re going to have high, highs and low, lows. It’s a rollercoaster. As the sunscreen song says “Whatever you do, don't congratulate yourself too much, or berate yourself either. Your choices are half chance. So are everybody else's.” - stay calm, focused and deal with the most pressing issues one by one.
     

  • It’s likely going to take many, many years. 5 - 10 years.

Product

  • Figure out a very specific, simple, discrete solution for a specific, well defined customer (preferably in the form of a software product). Keep in mind that…

    • If your product is B2B, it still needs an easy way for employees to onboard themselves - See Slack

    • If your product is B2C you will likely, once you hit scale, need a plan to..

      • Sell it to brands, distribution partners, advertisers (See Twitter, Facebook, Snapchat etc - in this case just note that you can’t avoid a ‘sales’ team and B2B conversations) or,

      • Charge a fee for ‘pro’ features

      • Charge transaction fees

    • Avoid propping up incumbents - Ask yourself how you might build a full stack startup

    • Building on top of someone else’s (very successful or rapidly growing) platform might be ok as a way to bootstrap - but look out for cannibalization from the platform. Ensure you have alignment, access to their team and - better - a way to syphon value to your own property

    • Mobile seems to be popular right now - consider starting there.
       

  • Avoid any initial need/reliance on network effects - Your idea will need a great ‘single-player mode’ to avoid a ‘cold start’ catch-22 problem. This doesn’t mean your product can’t benefit network effects and viral mechanics, but it must (ideally) provide enough value without them so that it’s immediately useful and sticky for your initial set of users.
     

  • Make sure you have enough money and a guerilla marketing campaign - especially if you can’t avoid the need for network effects. You will need to find and activate passionate groups of users so that they take notice in a hungry, addicted way (passing interest isn’t enough). They must come onboard in big groups so that they break their own catch-22
     

  • Your first, specific, simple, discrete solution should (must) avoid trying to be a “platform”. If you think you’re going to start by build a container into which others pour their creativity - you’re likely very wrong.

    • Platform partners (in b2c this means users, in two sided marketplaces this often means content creators, app developers etc) only pour their creativity into platforms that provide massive utility (e.g. make it 100x easier to create something beautiful) and/or provide massive distribution to an existing audience (e.g. make it 100x easier to reach or benefit from large numbers of people)

    • If there’s an existing competitor with a massive audience, even significant utility may not be enough to draw users/content creators/developers since people gravitate towards winners and audiences

    • Platforms emerge from massive companies OR from great products with passionate users who then open up part of their experience as a platform

    • If you’re idea *must* be a platform on top of which 3rd parties will play, plan on doing ALL of the initial work yourself because...

      • You need to seed the platform with great ‘content’ so that customers can start using it before you have platform partners contributing 3rd party value

      • 3rd party partners need amazing examples to be inspired by

      • Most people suck so you need large numbers of crappy 3rd parties in order to get just a few great ones

      • AirBnB had to manually go and get the initial listings. Pintrest had to create the initial pinboards. You will need people dedicated and passionate to do this obsessively well. It costs money and takes a lot of time so plan for it.
         

  • “There’s only two ways to make money - bundling and unbundling”. On mobile, however, bundling multiple features into one app is not an option unless you are somehow making a 5 step process into a 1 step process (in this case you’re bundling logistics, not features - See Uber). The current trend is unbundling features into stand-alone apps.

    • Do one thing really well

    • Do it really, really, well - design, simplicity and better ui/ux metaphors can be a big differentiator
       

  • Make it easy to adopt - really easy. Self-serve. Up-front pricing. Free-trials.
     

  • Make it easy to understand - a one page website is best
     

  • Get users to the magic moment as fast as possible - that moment where users go “Ooooh... that’s awesome!” when using your product
     

  • Wire it for metrics. How many page views, how many downloads, how many signups, how many users tried feature 1, 2 and 3.


Product/Market Fit

  • Ship it.
     

  • Get it into customers hands. Lots of them. Manually if you have to. Go meet them.
     

  • Look at the metrics
     

  • They will suck. Refine the product. Ship more.
     

  • Keep iterating until your acquisition and retention rates trend up and to the right
     

  • User support is massively important - listen carefully, look out for trends, respond quickly (both to the specific inquiries and with broader product changes).
     

  • Learn how to say ‘No’. Or ‘Later’. Because customers, partners, employees and your own entrepreneurial spirit are all going to demand you do a lot of things and you need to understand what’s inside and outside of scope for your product at this stage of its development. Focus.

  • Iterate, iterate, iterate
     

  • Have a plan (and enough money) to promote the hell out of it - Once the metrics (acquisition and retention rates especially) are trending in the right direction (and ONLY when they are), you need the resources and skills to push hard

    • PR

    • Sales

    • Bizdev

    • Content Marketing

    • Influencer outreach

    • Events (Sponsorship and speaking)

    • Social Media Marketing

    • SEO

    • SEM

    • Inside Sales

    • ALL AT THE SAME TIME - they build on each other. You can’t do them in serial.


Fundraising

  • Raise an Angel round. Don’t skip it. Angels can provide a strong foundation of contacts and peer influence. Don’t skip them unless you’re a rockstar.

    • Angels invest in great teams. At this stage your idea is just an idea - so they need to know they can bet on YOU to figure it out. So lead with your team in your pitch. Why are you uniquely qualified to do this?

    • Angels also want to be part of something that’s got early glimmers of traction that has the opportunity to become the next big thing.

    • Don’t pretend like you have it all figured out or you’ll just look like you’re full of shit

    • You just need to show that you’re asking the right questions and have concrete ways to go find the answers with their money

    • You should always raise at least 18 months of runway - because you will need to start fundraising again 4-6 months before it runs out

    • You will need more money than you think - don’t be too conservative

    • If you’re really good, a clever trick is to include Angels and Advisors in your Series A
       

  • Unless you’re a rockstar, you can’t raise an Angel round until you’ve done all of the above
     

  • YC, 500 Startups, Techstars are also great options.
     

  • Treat the Angel round like a product launch

    • Meet all the Angels you can. Get commitments. Getting a lead investor is the hardest step here.

    • Angels often invest in packs - try to find a great group of Angel friends who will make intros to each other.

    • Once you have 50%+ of your round filled in, launch on Angellist to get the rest

    • Have your existing Angels commit via the site to get Angellist’s attention and get featured (you should have spoken to them ahead of time and put yourself on their radar)

    • Make sure you agree with your Angels the metrics that matter in your business. Focus on them. Move them.
       

  • Even better, start talking to VCs about the metrics/proof points that would matter to them for a Series A.

    • Your angels can/should help make the intros

    • Talk to them early

    • Build a relationship

    • Listen to their objections carefully and find a way to address them
       

  • Make sure you have plenty of time to raise your series A (start 6 months before you run out of money)
     

  • Talk to VCs - You will need to talk to a LOT of them
     

  • Most of their objections will be around Team, Technology and Traction.

    • Team: Why is your group uniquely suited to this.

    • Technology: Why is your stuff better/faster/cheaper.

    • Traction: Can you demonstrate that this is (right now) a rocket ship of growth?


Hiring/Growing your team

  • ‘Hire slow and fire fast’ - This is a cliche/classic recommendation - but it’s serious.

    • Don’t just hire whoever’s in-front of you. Cast a wide net. Actively reach out to amazing people. Build your dream team.

    • Vet potential hires thoroughly for culture, expertise and vision alignment. Of course this doesn’t mean hire ‘yes people’ - you want people who are smarter than you who can help make big strides in their respective roles.

    • Don’t avoid firing employees because it feels bad. Fire them QUICKLY if they are not fitting. They can burn a LOT of time and capital and destroy morale if they are the wrong person for your team.    


This is, of course, not the end of the journey - but it is the end of my personal experience. Next steps involve further fundraising, IPOs, Acquisitions etc. More for me to learn!

Props to Woody Hooten, Julia French, Andrew Grignon, Jeremiah Owyang and Clara Shih for their feedback.

How telling our own stories is disrupting Journalism

Added on by Chris Saad.

It's become increasingly clear to a growing number of people that the Internet, and more recently Social Media, are empowering individuals to tell their own story... 1 tweet at a time. Victims, Terrorists, Dictators, Celebrities, Politicians, Countries and even every day citizens get to publish their message, their way, free of pesky intermediaries called 'Journalists'.

I've been writing about this, in one form or another, for pretty much as long as I can remember. Certainly since I read the Cluetrain Manifesto some 10+ years ago.

Don't get me wrong. I'm not saying there's no place for Journalists/Editorial Voice. I believe the ultimate answer is the intersection of social conversation and editorial curation.

That being said, However, I was tickled by this post on Vox today where Senator Barbara Boxer announced her retirement using the traditional TV Journalist/Politician interview format - with her grandson playing the role of journalist.

I'm sure she didn't mean it this way, but it's a stark example of how the Journalist could be seen as disposable, interchangeable or even totally unnecessary in a wide range of traditional journalism cases.

Given this accelerating trend, journalists, and media companies, are running out of time to find their (essential) place in the future of story telling and journalism.

Collaborative Works

Added on by Chris Saad.

There's been a lot of talk about the impact of social media on mainstream media, democracy and politics. It's also clear that the 'collaborative' or 'sharing' economy is going to massively disrupt traditional business models and concepts of ownership vs. access.

I'd like to propose another area of exploration. Collaborative Works. That is, work product produced as a result of a broad collaboration between loosely tied peers.

Think Wikipedia.

I struggle to think of too many other great examples. Some loosely related case studies might include...

  • Facebook Groups, for example, allow a few people to curate and collaborate to create a space for others to hang out in. You can even invite people into groups as part of the curation effort. But it's very rudimentary right now and the 'work product' is fairly simple.
     
  • The Reddit community also does a good job of covering major breaking news and producing collaborative reporting and investigative citizen journalism. While the Reddit team has made some moves to bake more support for this behavior into the product, the platform was never really designed for this kind of use-case.
     
  • Kickstarter (and other crowdfunding platforms) is also related to this, in that they ask the crowd to donate pure cash to a project. But it asks very little else of its users.
     
  • Genius.com is perhaps closest to my vision. It's a platform for crowd sourcing annotations of lyrics, news and other content.

I think there's a real opportunity to take this to another level. Perhaps by applying some new user experience metaphors on top of traditional social networks to coax/incentivize directed effort towards meaningful work product.

My personal dream would be to see collaboratively produced/curated news. News that is collaboratively produced from initial idea all the way through sourcing, writing, editing, fact checking and distribution.

Something open like Twitter #hashtags but less 'shouting into the stream' and more 'composing a collective narrative'.

In the past I've suggested that adding narrative structure on top of social media conversation was the role of Mainstream Media and the traditional Editorial Process, but, except for a few bright spots, I've increasingly become disillusioned with the attempts so far. However even if there was great traditional editorializing going on, I'd still love to see what democratizing the editorial part of the process might look like.

News is not the only 'work product' that could be developed collaboratively though. I'd love to hear your thoughts. What other work product do you think might lend itself well to Collaborative Work? Let me know what you think!

The Tyranny of Choice

Added on by Chris Saad.

For the longest time I was all about Choice. Give users flexibility, power, choice I'd say. Open ecosystems create opportunities for innovation I'd say.

I've recently changed my mind. At least when it comes to the first few stages of creating a new product/company/opportunity.

It seems that the number of people with any taste and tenacity is quite small and the opportunity (especially when you're just getting started) is not about consumer choice but about product choices. Creating great Product is all about making hard, opinionated choices based on best practices, intentionality and specific use-cases/markets in mind. The choices need to be on the design side so that the consumption side (the consumer buying your stuff) does not have to think.

I bring all this up to say this.

The Android and Windows device marketplaces are still missing the point.

It seems that every device manufacturer (with a couple of notable exceptions) is committed to creating as many phones as they can in a range of colors, sizes, variations and price points.

This one has a big lens on the back. This one has a crazy massive screen. This one comes in red. This one is the 'prime' version. This one is the Samsung Galaxy Nexus Play running Android Kitkat 4.23423 on Verizon - are you kidding me!?

I follow these things very closely, and I still can't tell you what the hell is going on. I can't imagine the confusion in the mind of the regular consumer.

The opportunity for Android and Windows is to create ONE flagship phone and iterate on a regular schedule - each time getting better and better. No forks, no variations, no changes and one distinct brand.

Then, and only then, can you start to introduce some simple variations. Black or white. 16gig or 32gig.

The current overcomplicated approach seems to stem, at least in part, from a technology mindset. Version numbers, inheritance, open source etc. The problem is that cell phones are not computing devices. They are not technology. They are consumer electronics. They are jewelry.

As far as I can tell, the only vendor+product doing this besides Apple is Microsoft with the Surface. But on the Nokia side they still have an embarrassingly large range of phones with stupid names based on numbers. If anyone can explain what the numbers mean I will give them a bitcoin.

Sure Surface is still losing money, but at least they are building trust over time that this is a stable, supported, flagship product that is a viable alternative. There is no tyranny of choice.

Of course the Surface has it's own problems of trying to be both a Tablet and a Laptop - but that's a discussion for another day.

I hope now that the Nokia acquisition is complete, Microsoft's next move is turn down the noise over there and get them to focus on one device that matters.

This post was inspired by a friendly debate with the awesome Doug Crets over on Facebook.

How Apple might compete with Google on Search

Added on by Chris Saad.

Thought experiment.

Yesterday I tweeted lamenting the fact that a report shows we now search more within Apps than Google/Web Search...

Well....

  1. Notice that on iOS 'Search' is branded 'Spotlight Search'.
  2. Notice the new 'Continuity' Features on iOS 8 and OSX Yosemite that involve lots of cross iOS/OSX interactions
  3. Notice the SMS Syncing between iMessage and Desktop
  4. Notice deep spotlight search on the OSX - showing content within an App in the search results (like recent documents etc)
  5. Apple has clearly shown they want to disintermediate Google by turning every search box on an Apple device (iOS or OSX alike) into a branded search experience "Spotlight" that a) they control b) mixes both web and native/app content.


Imagine taking this further in a series of incremental steps that would eventually lead the app developer community along towards a powerful end goal...

  1. Introduce 'Deep App Search' on iOS. An API that App Developers can use to allow spotlight to index their contents so they can appear in iOS search results and/or Siri or more often
  2. Introduce 'Continuity' for Search Results... When I get a result on OSX Spotlight, why can't I 'launch' it on my iOS Device and vice versa.
  3. Introduce Search Sync so that OSX Spotlight can return results from my iOS devices/Apps (and vice versa). Content that can only be seen on my phone will only allow that option in the search results
  4. All of this would presumably be via iCloud... 
  5. Apple could provide a WEB Interface to all this.. say at Spotlight.com
  6. BOOM! Apple would now have a differentiated Web Search Interface that rivals Google using...
  • A well known search brand (Spotlight)
  • Bing for Web (at least until they decided to build their own)
  • Deep/personalized results from your iOS app data. They might even be able to reach into FB if FB played along with the FB iOS App.

The challenge of developing Open Standards

Added on by Chris Saad.

A lifetime ago I created something called the DataPortability Project and, separately, proposed my own standard called APML. I also co-authored the Backplane standard. The first two were not very successful in achieving their mission. The latter is currently enjoying a medium amount of success.

During these experiences, and while observing other standards efforts (particularly in the social media and web space), I've come to be quite jaded about the Standards process

I still believe deeply in the vision of Open Standards. A world where independent parties can interoperate with each other without prior negotiation means that there's free and rapid iteration for the benefit of everyone.

Most of life as we know it is enabled by standards of one kind or another. From which side of the road you drive on to the shape and power coming out of your wall socket. The Internet itself is a miracle of technical standardization - from TCP/IP to HTML5.

The reality, however, is often times far messier and more frustrating than one would expect and hope. It's caused me to rethink some of my earlier, perhaps naive, points of view.

So, despite my love and admiration for the work and many of the individuals, I'd like to indulge in a post about the frustrations with standards and the standards community...

  1. The standards writing community tends to be mired in politics divided along minutia like HOW to organize yourself and WHICH technical approach is the most elegant and WHO is running what clique. You have to approach it in exactly the right way or risk offending someone (this post likely wont help).
  2. The community tends to be fairly academic resulting in commercial applications and/or ease-of-use taking a back seat.
  3. If any commercialization does happen, only the 'losers' in the market tend to participate so it never becomes dominant or particularly useful at solving the end goal (which is not openness, but interoperability). Even when big players participate they tend to send people who do not have the political capital at their company to adopt what's been developed in any meaningful way.
  4. For some reason engineers/implementers would rather create a proprietary format or protocol over an open standard just because the latter sounds like more work. Unfortunately often times they're right.
  5. it's easy to write a technical spec and propose it as a standard. The problem is getting consensus amongst the technical community and adoption by companies that matter. Unfortunately most standards efforts get stuck on the first part and never even begin to tackle the second and most important part. Adoption is far more important than getting every technical detail correct.
  6. As a result the standards often die on the vine or shortly thereafter.

As far as I can tell real standards tend to emerge only after proprietary innovation is created and commercialized by a first mover who wins big. Part of their competitive advantage is they get to control the implementation and iterate on it quickly. This forces competitors to fast-follow (read: copy) the conventions and models of that market leader.

This results in a kind of rough, market led convention that, while not open and interoperable, lasts for pretty much the entire cycle in which the particular technology is relevant, interesting or rapidly changing. This can take many, many years. Decades even.

Once that layer/component in the technology stack becomes conventional (read:boring) and the battle (read:unique value prop and lock-in) has moved up the stack, then standards groups can get together, figure out the common cases (which have now stabilized and been fully figured out), sand the edges and create true interoperability.

Said another way... you can't standardized the innovation before it's played out in the market and had a chance to run its course. Then you can retroactively write down what happened.

Let the hate mail begin :)

Confessions of a Startup Founder trying to get Press...

Added on by Chris Saad.

I just read a great post by Bekah Grant about the pain and suffering that tech bloggers go through dealing with the continuous onslaught of startup founders trying to get press for their startups.

I thought it might be fun to give the startup founder point of view so we can each understand each other's world a little better.

IMPORTANT DISCLAIMER

First let me say that many of my close friends are tech journalists/bloggers both past and present. I know (second hand) many of the frustrations they go through every day trying to do their best to stay on top of the stream of news, balancing priorities and serving the page view master. This post is not meant to be an attack on anyone - just a fun counter-balance to Bekah's post.

The hungry, hungry employees

As founders of startups we have asked other people to risk their livelihood (wives, employees, families, investors and so on) on our crazy idea. Not only are we desperate to see this idea succeed so we can make our own little dent on the universe, but there's also the constant fear of letting those who've bet on us down and having them and their families go hungry!

In any given day you're dealing with product development, business development, fundraising, marketing, family issues, competitors, personal grievances between various stakeholders and the worst enemy of all - time.

You don’t have any visibility

It's hard to explain the sheer terror one feels after you've poured your blood, sweat, tears and money into a project, that, on launch day, it wont get covered... or... just as bad... it will get covered and no one will care.

The reality is, of course, that even with coverage, launch day is often not the big 'build it and they will come' miracle moment most green entrepreneurs think it will be.

In any case, get covered they must and trying to walk that fine line of diligent follow-ups without being annoying with a blogger who is spread too thin to give you a clear response is a nightmarish process.

One would think it would be easier if you're friends with the blogger (as I sometimes am) but in truth it's even harder because you don't want it to ever seem like you're leaning on your friendship to get something written (because that is, of course, NOT the point of your friendship) and you don't want to upset your friend for some announcement.

Bad Perspective

Another mistake that's easy to make as an Entrepreneur is that you are so intimately aware of every facet of your product and all of the underlaying assumptions and market dynamics that it's very, very easy to screw up your pitch.

After being so close to something its often difficult to see the forrest from the trees in terms of the high level message or newsworthy angle.

Getting outside advice and pitching it to friends first is often a good idea to help with this.

Worse than a lack of personal perspective, though, is the difficulty in knowing what the journalist will actually care about or resonate with. Even if you research what they've written about before there's no guarantee that they still care about that space on the day of the pitch. They may have written about it once as a favor, or written about it endlessly and they are now sick to death of it such that they feel like your 'related app' is just a 'me too' copy. On the other hand If you come in with something fresh it might appear as outside their beat or simply too offbeat.

There's obviously no excuse for pitching a B2B story to a B2C Gaming blogger though!

PR People

Again I am very fortunate to work and play with many in the blogger community so I don't need PR people to 'get introductions', but many green entrepreneurs can be utterly lost as to how to get attention for their precious startup.

PR firms, like many other firms in the ecosystem, can often come promising a panacea solution to startup troubles and, more often than not, fail to deliver on lofty goals - particularly if you don't have real money and a strong guiding vision over the process from in-house people.

I definitely feel like reaching out and telling your own story is the best possible approach if you can do it, but often times first time entrepreneurs simply don't have a choice - and it's very easy to find bad service providers.

Commenters are Jerks

I agree most comments are garbage and unfortunately it's pretty clear that female tech bloggers have it much worse than male bloggers. I could write a whole book about this though so let me move on.

Entrepreneurs are people too

Relationships in Silicon Valley, in general, can feel very one sided. Everyone is so busy and moving so fast that it's easy for people to ask for what they need and then forget to reciprocate or touch base at other times.

I've felt this in all kinds of relationships though - not just between Entrepreneurs and Bloggers.

It can also often times feel unfair that bloggers get to pass judgement on your startup or project when they themselves have not been an operator. I've seen this kind of resentment fester - particularly when the coverage is unfavorable. 

At the end of the day, though, we're all people, and we're all trying our best to do our jobs to the best of our ability.

We need to remember that each of us is carrying our own personal burdens (both professionally and personally) and each of us is striving to be the hero of our own story.

We should also remember that we're some of the luckiest people on the planet because we get to complain about all this abundance while many are struggling just to survive.

I love all my Entrepreneur and Blogger friends!