Chuw on this.

Read us, know us. Because knowing is nice. 

Stop the Press: Building A Startup Presskit 101

You and Your Press Kit
Post your press kits and questions on Chuwe.com, and we’ll go over it with a fine-toothed comb to help you perfect it for free. We’ll also be choosing one company to give a press-kit makeover with a PR professional in an upcoming Chuwe podcast.

What It’s For
A Press Kit (a.k.a. media kit) serves one primary purpose: to generate interest in your business. You’ll show it to press, investors, and potential sponsors, but the purpose is always to provide a powerful and actionable set of information on your company. Every business needs to put one together - musicians, restaurants, Internet websites, new companies and established small businesses. Typically, you’ll want to include

  • Some limited background information on the company and industry
  • Relevant sources that have quoted or interviewed you on your business topic
  • High-quality logos, photos, and other promotional materials for press use
  • Information for your reader to act on

Background Information
Your press kit summarizes the company; keep it short, keep it focused. Bore your audience, and you’ll lose potential press exposure.

You have a few fleeting seconds to make a strong impression, to establish credentials, and to convince them to contact you. Once they call, go ahead and flood them with your anecdotes – but your press kit stays sharp. Humor helps if you can pull it off and it’s appropriate for your industry, but keep in mind that humor is the most difficult concept to convey in writing.

Avoid looking desperate; confidence attracts press. At the same time, don’t claim what you can’t backup, says Bill Bradley at Bottom Line Communications,

“Resist the urge to use self-impressive adjectives and make specious claims.  As a startup, you may be innovative but you're clearly not a ‘market leader,’ so don't insult the media's intelligence by characterizing yourself that way. “

Use charts and graphs to objectively highlight company services and successes in the industry, adds Farrah Parker of FDP & Associates.

Industry Quotes and Interviews
Always keep your quotes and interviews section up to date with anything positively mentioning your business. Interviews are a kind of positive feedback-loop: Interviews establish legitimacy and generate more interviews, which further establishes legitimacy and generates more interviews…

Promotional Materials
Make it easy for someone who wants to write about you to put together a memorable piece. Your logo, company graphics, and founder photos should be available in high resolution and several different formats.

Useful Tips
It’s not bad to list a few necessary personal details, but remember you are not the focus. Emphasize what’s new and interesting about your business.

If you’re in a new niche that takes awhile to explain, try starting your description with a simple “X for Y” analogy.

“We started as an Olive Garden for Indian food – a reasonably priced restaurant with a comfortable atmosphere serving Indian food tailored to the American palate”

The initial introductory line might not be spot on, but it’s a practical shortcut and gives the press a feeling for how to spin your business to the public at large. One caveat with this technique is that you must be absolutely sure your reader is familiar with the object of your analogy.

Peter Gudmundsson of Priceless Legacy encourages entrepreneurs to make it easier for reporters to think of a story involving you by including a media pitch sheet with suggested story ideas and titles embedded.

Farrah Parker further advises startups to "stay consistent with your design theme - If your brochure has a contemporary design, then make sure that your kit follows suit…Graphics can truly enhance your kit but they can also overwhelm the eye." Michael Saltzman also offers tips on graphically presenting information, “Simple is better than complex… Try and use bullet points rather than long paragraphs."

Finally, a press kit is not a place to negatively mention your competition. Actually, there’s never really a good time to negatively mention your competitors. As Loic Le Meur points out, you’ll always come off as crass, and it’ll likely come back to haunt you in the future.

How To Use Your Press Kit
First, set out to develop a useful publication list, and find reporters. "A lot of people buy media lists [of press contacts] rather than creating their own, which can result in wildly wasteful mailings.” Lizzy Shaw, who runs her own PR consultant, writes, “Send your press kit to the writers and editors who can actually do something with it…don’t send a press kit about electric razors to a children's apparel trade publication!"

Once you’ve sent out your press kit, don’t be depressed at the slow responses. Saltzman continues, “Don’t assume one press kit will revolutionize the world or make ‘dramatic’ changes in the company - a race is not won on the first stride." It’s an uphill battle to gain and retain press attention; you’ll have to invest considerable energy into contacting and following up with writers.

Finally, keep in mind that reporters often have deadlines hanging over their head. Glenn Philips recommends making yourself available at any hour – you might get that story instead of a competitor if you include a call to action and state you’re available 24 hours a day.
 
Write One. Now.
Start with a simple outline.

  1. Company Introduction
    1. Analogy if necessary
  2. Quick summary of your company’s strengths
  3. Quotes from relevant and credible sources.
  4. Contact information
    1. Preferred contact methods
    2. Response times to press inquiries
    3. Hours available
  5. Promotional Material
    1. Logo
    2. Mascot
    3. Relevant photos and graphics, etc
    4. Be sure to include all popular formats at multiple resolutions to make life easier.

Then add, delete, and generally tweak it until the outline grows into a professional and compelling description of your business.

Finally, post it on Chuwe, and we’ll go over it with a fine-toothed comb to help you perfect your press kit. Also, we’ll be choosing one company to give a press-kit makeover with a PR professional in an upcoming Chuwe podcast.

Good Luck, and let us know if you have any additional tips!
 
> Courtney
Ninja Entreprenette

Loading mentions Retweet

Comments [3]

The Starbucks Pitch - Our Experience

When Jun Loazya interviewed Tim Young from Socialcast, they ended up discussing what I'll call The Starbucks Pitch (10:22).

The Pitching Problem
After awhile, you just can't practice your pitch with your founders anymore. You've all heard it so many times, you're numb to it. Your founder could omit 95% of the pitch, and you'd think, "Hey, that's pretty good; nice and short. And I still totally understand it!". So you've got to bring in fresh blood, people who've never heard of what you're doing, and might not even understand the industry. If you can explain it to them quickly, succinctly, and clearly enough so that they understand, you've got a golden pitch on your hand.

Enter The Starbucks Pitch
Bring your co-founders and a friend or two to Starbucks, practice your pitch on one another for just a bit, and give a few last minute critiques. Now you're ready to approach someone at another table and try to pitch them your idea. Have your friends sit nearby somewhere out of the way, watching you and (most importantly) your listener's face during your spiel. Watch for emotional changes, confusion, glazed eyes, etc. When you're finished, have everyone write down notes on your performance, and points for you to improve on. Internalize it all, practice, and try it again. Repeat per-pitching-founder.

We decided to a Starbucks to give it a shot today.

Results
I noticed a few interesting points when pitching - not a single person said a bad thing. In fact, the first pitch of Chuwe for the day, my subject only asked me to repeat my explanation once. His response afterwards was, "Hey, that sounds great! Way to go!"


"Did you have any questions about Chuwe? Is there anything unclear? What did you have a hard time understanding because of my explanation?"
"No, it all sounded pretty simple to me! I think it's great!"

Either I'm a pitching god, or an epic fail.

I returned to the table for  feedback. It was gentle at first, but snowballed into some pretty "open dialogue" about my failings. "Speak louder, add some humor, smile, don't fill pauses with 'uhm', and for god's sake SLOW DOWN!" (I rarely notice when I'm speaking too quickly). After that feedback, I'm guessing it was an epic fail. Ego deflated ever so slightly, I adjusted the script and internalized it, made it natural - made it mine. I practiced once over.

Time for the second round.

I approached two elderly gentleman, and explained that I was doing a project for my business class. I had to give an elevator pitch for a business idea I had, and would they mind giving me a bit of feedback on what I had so far? (People are a bit kinder if they think you're a student rather than an nosy salesperson). I spoke slowly and assuredly, smiling as I looked each in the eye. I made sure not to stutter or mumble. And yet their reaction was much less kind than the first:

"What's in it for you?"
"Why are you qualified to do this?"

And so on. But after I answered their questions honestly and openly, the two elderly gentleman looked at one another, smiled broadly, and said "We love it!". Right then, a friend of theirs came and sat down at the table, and they excitedly explained my pitch to him. And they may have done a better job than I did.

Seems like I made some progress with my pitch today.

Share your thoughts and techniques on perfecting pitches with the Chuwe community. We love great advice!

> Sean
Rockin' Code Monkey
www.chuwe.com

Loading mentions Retweet
Posted by Sean Grove 

Comments [5]

Thoughts on our hn "soft-launch"

I thought I'd jot down a few notes about our experience posting to hn. I always like reading about other's experiences when launching new things, so I thought I'd share mine as well. There's no real purpose to this other than that.

Anyway, I had just finished "an acceptable code base" for chuwe.com (our Q&A site for the startup/smallbiz community) and decided that Sunday was the day. Actually, we decided Friday, but personnel issues pushed it back until Sunday.

Our goal was simple - it wasn't a "real" launch per se. We wanted to open the site, get mass feedback in one big jolt, then close it and continue with our original invite-only model.

A Short Crisis
In any case, we posted to HN - my first time showing personal code to so many people. It's difficult to tell if there will be any big problems ahead of time. To minimize the possibility, I followed BDD - we had functional-tests, unit-tests, etc. In fact, we had about a 1:1 code-to-test coverage ratio (whether that's meaningful or not, I don't know). Testing made refactoring fly by, it reassured me that things still worked, and just made me feel like a good little developer. In the end though, tests are just tests, and things will unexpectedly break.

One source of problems cropped up in that our development environment was ever so slightly different from our production environment. All the tests passed locally, but we hadn't set the tests to run on the production server. Accordingly, it turns out our sign up code was broken. Easily one of the most important items, I had worked to make sure that it was very smooth (username and password only - email optional). However, the site still sent out a confirmation email even if the field was blank. While the local mail server didn't have a problem with this (it quietly failed and went along), the production server was a much more stern mistress.

I signed up as a user on the production site, but I gave my email, so there was no problem. Shortly after posting however, my partner signed up without an email and we were greeted with four frightening words: "500 internal server error". After 20 minutes trying desperately to track it down with nearly no support from the error logs, someone recommended hoptoadapp.com. 5 minutes later the problem was fixed, tests re-run (even though I didn't feel quite so optimistic about them anymore), and the site updated immediately . Crisis averted.

Well, nearly averted. I had to go through and find the users who had tried to sign up, and email them an apology letting them know that things were fixed now, and thanking them for their interest and patience. I let each of them know in a custom email (no form letters) that we're real people, and if they had any problems we'd be all over them.

A few other minor things were broken as well, but they were mostly design related and I was able to push out updates without any big issues. 

Feelings
Showing code so publicly felt like standing naked in front of a crowd. No more time for testing, no more time to polish. Any ugly bits I had were going to be seen.

What if something was wrong? What if something broke?

Easy. End of the world.

But "launching" so publicly tempered me. Things did break (as mentioned above), and people mentioned things they disliked in no uncertain terms. I took each as a problem to be solved. I worked as quickly as possible to update the site. And the world didn't end.

Results 
A little less than 600 visitors came from posting to hackernews. A paltry amount for a tool I thought would be highly attractive to the hn community, but still enough to thrill this inexperienced team. Traffic dropped off accordingly each day thereafter, but that was expected and we got the feedback we had aimed for.

Area for improvement
I enjoy the "Ask HN" posts asking for feedback the most, and always check out each one (even if I don't comment). Also, I hate "linkbait" titles that polarize or mislead for clicks while inhibiting thoughtful discussion. Accordingly, I posted a boring title, "Ask HN: Review our startup (www.chuwe.com)".

That was a mistake. There's no information in that title, no hook. A much better title would have been "Chuwe.com: A stack overflow for the startup and smallbiz community." Immediately engaging to the kind of entrepreneur/programmer hybrids at hn.

Take away tip: Make your title catchy and targeted, without being gimmicky.

Also, the timing could have been better. I'm not sure exactly, but I believe the usage data for hn is available (in one way or another). I should have used that to post at a time that it would get maximum exposure. Although I'm just speculating, Sunday afternoon is probably one of the slowest times on the site.

So in the end, we got the feedback we needed, I passed through the trial by fire and feel confident about things breaking in public (and my ability to fix them). We even struck up some good partnerships in the process. Thanks to the experience, our next foray into the world of social media should be a bit more successful.

> Sean
Rockin' Code Monkey

Loading mentions Retweet
Posted by Sean Grove 

Comments [2]

The three I's of startup blogging

I've been meaning to write down my notes from our "mini-launch" day. I'll get around to it, I'm sure, but I've put it off nearly 5 days already. 

But this Wednesday I was listening to the BBC Newspod, and they had a small bit about successful political diaries. Gyles Brandredth mentioned four (well, three really) brilliant points that he and Alan Clarke came up with:

The four I's:
Immediate - Write it the day of.
Indiscreet - Chips Chanon: There's nothing more dull than a discreet diary; you might as well have a discreet soul.
Intimate - Intimate details are very important
Indecipherable - If someone chances upon, make sure they can't quite understand what you said.

Immediate: I was struck by the relevancy to writing startup and business blogs. Immediacy is everything - a hindsight view offers a lot of well-selected, edited, abstracted lessons, but it's boring. Tell us how you felt, what you thought when you made decisions, when you faced challenges and lost, and when you succeeded. I suffer from always trying to appear rational in my actions, so I spend too much time trying to analyze the underlying motivations about why I did something when I should simply write about what I did and the short, simple thoughts that brought me there.

Indiscreet: I think over the past four to five years we've seen more large-scale companies dropping this veil of decency, and talking about their flaws. Amazon is amazing about this - they discuss and show exactly why something failed, how they're going to fix it, and they don't clean up the language in the slightest. There's no excessive sanitization. Nothing is more dull than a sanitized press-release that says nothing; you might as well have a sanitized product that does nothing. Adobe (just to pick one big offender off the top of my head) is amazingly bad at this. Refusal to openly discuss failings comes across as hubris and cold. And boring. 

Intimate: I like hearing about people and the systems they work on. I like feeling as though I'm part of the story I'm reading in some way, and personal details / minute observations help that. 

Indecipherable: This one I disagree with. I see the value for politicians in fuzzing the meaning, it gives them latitude to maneuver if opinions or actions seem unfavorable. But for startup blogs, if you're filling your writing with words instead of meaning, I'm going to leave very quickly with a bad taste in my mouth. I'll subconsciously catalogue you as a disingenuous writer, unlikely to ever return. Focus on contributing to the startup culture, and helping others along the way with their problems.

They mentioned one more aside: Don't take yourself too seriously. Most of the points listed above stem from not being able to relax, to have a good time and engage with people because you're too worried about appearing "proper". It's not proper for companies to talk about mistakes. It's not proper for employees to detail their personal experiences with the company.

And that may be true. But it's a hell of a lot more interesting.

What do you think? It's our first question: http://chuwe.com/questions/1

> Sean
Rockin' Code Monkey

Original Podcast (Diary section at 30:06)

Loading mentions Retweet
Posted by Sean Grove 

Comments [5]

Chuwe.com part 1: Stack Overflow for startups/small business.

Programmers have stack overflow, but what about more general startup-questions? Or question regarding running a small business in general? That's Chuwe.
 
You can probably figure out the rest from there, but I'll add one more bit. To make it a little more interesting, there's a community-funded pot that'll be dished out to the most interesting question and answer (according to an open vote count) at the end of each month. We'll always start it at $30, so that'll be the minimum.
 
We have a pretty solid plan for where we're going, but this seemed like a good place to start and get some feedback from everyone.

www.chuwe.com


Thanks for checking it out.
 
Feedback welcome. Questions even more welcome!

Loading mentions Retweet
Posted by Sean Grove 

Comments [0]

Design Series, Site mocks organized

A collection of mocks before implementing...

     
Click here to download:
chuwemocks1.zip (147 KB)

> Sean
Rockin' Code Monkey

Loading mentions Retweet
Filed under  //   design   mocks  
Posted by Sean Grove 

Comments [0]

Design Series, Site mock 2

Further color-scheme tweaking...

> Sean
Rockin' Code Monkey

Loading mentions Retweet
Filed under  //   design   mock   user-driven  
Posted by Sean Grove 

Comments [0]

Design Series, Site mock

Feedback more than welcome! Give it to us, good or bad. We can take it.

> Sean
Rockin' Code Monkey

Loading mentions Retweet
Filed under  //   design   mock   user-driven  
Posted by Sean Grove 

Comments [0]

Design Series, Question mock #3

> Sean
Rockin' Code Monkey
www.chuwe.com

Loading mentions Retweet
Posted by Sean Grove 

Comments [0]

Design Mockups Con't: Question options, #2

> Sean
Rockin' Code Monkey

Loading mentions Retweet
Posted by Sean Grove 

Comments [0]