Skip to main content


It's been a busy week out in the Valley--lots of meetings, a missed flight, and random encounters with investors. Throughout the week I've narrowed and refined the pitch and found my sea legs--I'm almost swaggering with confidence (not overly so). 

Earlier this week I met with 3 VCs, all of which are now tracking, which means they're intrigued, not saying no, but not whipping out the term sheet just yet. 

I've also met with the heads of a number of startups and large-company divisions. This morning I met with the founder of Keyhole (Google Maps)--great guy, and as you usually find here, very smart. It's great to get that kind of exposure and conversation level about your stuff, if only to practice the pitch, though I always learn something. 

At the end of next week I hit NYC for investors presentations there. 

I added an advisor as well--someone with deep experience in mobile search who now heads a research lab. 

This is the true beginning of the formal fundraising process. I've done this 6 times or so before. Typically the process is this:
  • Intro of some sort
  • First meeting by phone or in person
  • Follow up in email thanking for meeting
  • Follow up when something significant happens--beta release, traction, deals, etc. This is the key post-meeting trigger for future meetings. 
  • Follow-up phone call and request for next meeting. 
  • Next meeting is usually with other partners--gotta be on my game (I am already). 
  • They then make a go, no-go, or track decision. Sometimes it's hard to get a clear indication because there's internal disagreement. 
  • Term sheet. It takes 6-8 weeks to close the deal after the term sheet. 
That's the typical process, which can take 2 to 6 months, but there are angels that can write the check and get it done in a day. That's relatively new for the startup world--lots of active, cash-rich angel investors. 

In the meantime, our small amount of angel investment moves things along until we get a revenue engine going. 

It's important at this time to focus on measurable progress: quality and scalability of the app, UI, and UX, then number of active users, revenue, traffic, press, etc.

This means it's time to clean things up, stabilize, and launch the beta. I want to be code complete within 10 days, testing over the following week, and launching beta within 17-20 days. 

Every time I do this it feels like I'm making it up as I go, but this time around I'm really enjoying the process. And the weather--can't beat the weather this week. 


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