Skip to main content

Startup Mechanicsburg

Last night I drove out to Mechanicsburg for the first Startup Mechanicsburg.

Josh Smith attended a few of the Startup Lancaster meetings and was determined to identify and gel the ecosystem in Mechanicsburg, so he cloned it and bam--9 people attended, a good start.

Startup Lancaster has about 35 members now, after 11 months of existence, but about half of the meetings had around eight or nine founders, and only two had over 20.

I arrived late, and they had already done introductions, decided the topics for the night and were about to create breakout groups--Josh had it down pat.

There were at least 3 viable startups there; one of them is already at $14,000/month of revenue. They're going to do very well,  I'm certain.

It's so encouraging and exciting to see this. Hopefully others will follow Josh's lead and start their own groups throughout PA.

Here are the guidelines as I see them:

  • Who: Founders only. That means no employees, friends, spouses etc unless they are truly co-founders.
  • Who II: Founders of technology product startups only. This might feel limiting, but the issues tech product startups face are different from services companies, hosting companies, and non-tech companies. 
  • No vendors, attorneys, investors, etc. Have an Open Meeting maybe 6 to 12 months down the road and invite outsiders in, maybe hold a showcase. But keep most meetings closed to all but founders. It matters--outsiders truly dilute the quality and focus. 
  • Place: Pick a restaurant or meeting space that's quiet. Don't assume noise levels--you really have to go check it out and see if you can hear someone 12 feet away across the table from you. I like choosing places that have some character, and are locally owned so we support other founders. 
  • Running the meeting: 
    • after brief networking (15 minutes or so),  
    • brief intros
      • who are you, 
      • what does your startup do
      • what stage of startup life are you in (pre-product, product but pre-revenue, revenue but not yet sustainable, sustainable)
      • biggest current challenge
    • After intros, choose a challenge for people to discuss. A good one is pain point you're trying to solve; another is explain your business model (what are you selling, who is buying it, etc)
    • Break into groups of 3 or 4, and have each person discuss the challenge. Participants should just listen and not try to solve problems. If you have a solution, hold onto it for later. 
    • After everyone's gone, offer each other advice, solutions. 
    • Choose one startup to share with the group. Have someone other than the founder talk about it. (this is'll see why)
    • Group gets back together, shares stories from the breakouts
    • General discussion and wrap up. 
  • Use Meetup. It works well and is relatively cheap. 

Reading, York, Allentown, Paoli, Scranton, Erie, Pittsburgh--this really could be a statewide thing. All you have to do is call the meeting and let people know,  just like Josh did.


Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

The Real Jobs Problem

It's the economy, stupid.  Well, yes, it always has been, if you're in the distortion field of politics.  But whose economy? The pundits, the White House, the Republican candidates all miss the mark. They keep talking about debt, taxes, and monetary policy. None of those things tell the real story behind today's economy.  The Old Economy Keynes was right--in the old economy. Economy gets weak, pump some money into the economy through public works projects, which  1) puts people to work, which  2) boosts the economy and  3) generates new tax revenue, while  4) leaving us with another generation of reliable infrastructure to support  5) more growth (for growth's sake, which is another post).  The Beach Ball Imagine a beach ball, partially deflated to represent a recession. Got it? Now imagine the govt pumping that beach ball back up through sensible public investment (which we haven't seen for decades). The New Economy Same beach ball, same pum