Skip to main content

Going All In: Part II

Last night we held the 9th meeting of Startup Lancaster, a group of 30 tech-based startup founders from the region.

We got into a conversation about going all in, and I think there were varying definitions of what it means to do that.



One person had just quit their job and will be consulting three out of four weeks per month.  The fourth week is his free week. Not a bad way to live, but I wondered whether he could really have a free week, and if that's enough to move things forward.

Another person worried that his product wasn't ready for him to be full time yet, and since he can't code, how would it make sense to go full time?

It's a good question--what does a full-time non-technical founder do before the product's ready for show and tell?

I feel there's plenty to do--talk with prospects, develop relationships with press, keep dev focused on the mvp, research more, develop surveys, talk with prospects again, etc, etc. It's a great time to ramp.

Most people had different levels of pain tolerance, or rather, risk tolerance. One works 2 days a week so she can spend 5 days a week on the startup. That's a smart idea if you can pull it off.

At some point you have to pull the trigger. People that might want to work with you need to see it. Investors need to see it. They all want to see that you're fully committed and figured out how to make that jump.

But it isn't easy without capital. I admire the people who are able to make it happen without external capital--it's entirely possible.

And recently I've thought of expanding my consulting, adding to the team, and leveraging that to create a buffer big enough to have another team working on product.

And then I remember how hard it is to serve two masters. One is always stealing from the other. It's very hard to advance your product when your services team has a lucrative deal that needs your product guys.

Very nice conversation--we have a great group of founders and they all seem like they are getting close to going all in. It's a joy to see.


Comments

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