Skip to main content

The Dial Tone of Ops

Startups begin with hope and vision of success. That's great and important.

But when it's time to really rock--you're ready to launch (or you think so), you're mapping out strategy, and you're ready for revenue. It's time to go from zero to one, the hardest part of building your company. 

What will your dial tone of operations be?

(if you already have ops established, please take this survey thanks)

If you're young enough, you might not even know what dial tone means. So let's go to the wayback machine and see. 

In the grand Olden Days, there were these things called phones--land lines, as we call them now. When you pick up the phone, you hear this dial tone. It's always there.

If it isn't there, your phones are down in all likelihood. When you hear that tone, you know the phone works. 

As a company, you need a dial tone of operations: that reliable, steady, stable, expected performance of all of your operational processes and tools. 

So these days, what does that mean? 
  • Cloud backup of all of your data. 
  • CRM always available, and a backup system just in case Salesforce or Nutshell goes down. If they aren't available, how do you access customer data? 
  • Your accounting data and software always, reliably available so you can invoice, analyze, etc. 
  • Your phone service--and yes you need phones, because cellphone quality still sucks for business purposes. 
  • Your website
  • Your support site like Zendesk
All of this stuff is so important. Some of it has no relationship to your vision. All of it matters to the mission of serving your customers, or people who use your stuff. So get it right. 

I've been looking at all of these things for Joe and Current. And I have not found a consensus of what works for startups for half of this stuff, especially phones. 

Why phones? Sales. calls me every other day. I've told them no. They call anyway. I'm on all major social media services, but they call. They have my email address. They call. 

So what does the "No Software" company (bullshit slogan, btw) do to add customers? They call them. They have systems. Processes. A pipeline. Software (hence the bs). And a telesales force that calls every prospect, even after they say no. 

What do we need?

Well, we need to make a ton of calls. We need to be able to listen in on the calls so we can help manage the sales process. And we need to be able to transfer calls. 

So cell phones? No. Not at all. Google Voice? Nope. Pretty sure it doesn't do the job, but please correct me if I'm wrong.

At my last company, we had an in-house PBX. This time, we'll go with a hosted PBX like Ringio or RingCentral. Grasshopper is too expensive for a call-intensive operation. 

You need to figure out what that dial tone of ops will be for you. Part of that will likely be a phone system, and fortunately phone systems are now available as hosted services with little or no up-front cost. 

The dial tone of ops. Can anyone point me to what works for today's startups? 


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