In the early days of your startup, you might have heard you should have a hacker, a hustler, and a hipster on the founding team. That makes a lot of sense in the initial stages of your company due to the experimental nature of the business. Remember what Steve Blank says: a startup is not a “real” business but rather “an experiment searching for a business model.”

Once you start to move out of the coffee shop and build your initial team, you’ll have to make some careful hiring decisions. I’ve seen founders hiring for new “formal” positions right out of the gate when all they need are operators to validate the business and find product market fit. Instead of finding your next VP of whatever or Chief whatever Officer, you should have no titles until you have paying customers and a product market fit.

I advise all the founding team to call themselves “product” on slide decks and email signature (if you do that sort of thing). Early stage team members should not be going to conferences and don’t need business cards, so the title doesn’t matter.

Here are a few other ways to manage the early stage hiring processes, and run your startup more effectively.

Maintain Equilibrium

Last year, I wrote a piece called “The Holy Trinity of Product Development.” I argued that it’s important to maintain balance in a company. Often, a startup’s first hires (besides the founders), tend to skew either to the technology side (we need 5 developers!), or the marketing side.

Generally, if the founding team is more marketing-minded, they overhire engineers, and vice-versa. Instead, a company should be customer-centric. To achieve this “holy grail,” the company needs both technology and marketing expertise.

Be Well-Rounded

In another article, “Why CTOs Should Know Accounting,” I suggested that CTOs also need to understand the business side of your company. It’s important for all of the high-level employees in a company to be able to converse with the rest of the employees.

Just like the CEO of a company should be able to at least pronounce the word “kanban,” (con-ban not can-ban) and know the difference between Java and JavaScript, a CTO should be relatively familiar with balance sheets, income and cash flow, annual statements, and budgets.

How to Hire

I’d argue that it’s better not to even bother with interviews. Rather, have coffee first. Discuss why they want to work at such an early stage company and review their skills there.

If that goes well, then have the potential employee give a presentation to the entire team. It can be on any topic (Was “The Force Awakens a remake or not?” is a perfect choice), and it gives the team a feel for the candidate’s analytical skills, seriousness about the position, and ability to do something different, while it also provides a unique experience for the candidate.

If the person is successful on their hiring presentation, I’d suggest the “can we have a beer with them” final check. This one’s really complicated – take them out for a beer with the team (or another social engagement if team members don’t drink). Get to know them on a personal level. When companies scale to be over 25 people, it is much harder to do this with the whole company, but each functional area (marketing/sales, tech, backoffice) can do it with their group and a select few members from other functional groups to join.

Avoid Founder Disputes

Early stage companies sometimes have no cash and bring on someone as a “co-founder” with little to no pay. It’s also crucial that you do your best to avoid founder disputes. I wrote a piece on this called “Dynamic Founder Agreements,” but I’ll give you a short summary. I described this agreement like a typical IF/THEN/ELSE.

IF:

The CTO works full-time and performs all of coding and technical duties of V1, his equity is 50% vestedover 4 years, 1 year cliff.

ELSEIF:

The CTO works part time, is disengaged, or we need to hire developers sooner than expected, his vested equity is reduced by half and he forfeits his unvested equity. Loses board seat.

ENDIF:

The CTO has to leave the company because he needs a job or a family emergency: if the CTO built V1 then the buyout is a one time payout of $50,000 USD cash or 2% vested equity, if the CTO did not build V1, the buyout is 0.5% vested equity. Loses board seat.

While you might not avoid all disputes, this agreement will go a long way.

Hiring for Bigger Companies

Once your company grows and matures, deliberately hire slow. "Scale" and "move fast" does not mean "hire crazy fast." Rather, hire for a role only when it is obvious the company is suffering without it.

There is a Silicon Valley secret that dictates that “you make a decision to join a company ONLY if they are resource-constrained. Once they have enough people, time to move on.” The idea behind this secret is that creativity needs constraints. Translation: if your plan calls for ten people, see what you can do with five.

Use these tips when building out your initial team. Don’t fall into the hiring trap.

There has been an explosion of hardware startups over the past few years led by the Maker Movement and startup programs like Hax (where I’m an advisor). I’ve seen and worked with well over 100 hardware companies in the past five years. In that time, I have observed that hardware startups think differently than software startups. They shouldn’t. All hardware companies are software companies. The sooner they realize it, the sooner they’ll become successful.

Photo by flickr user chefranden

Look at today’s most successful hardware companies. Apple and Tesla build amazing, innovative hardware. And at its heart, a Tesla is an iPad on wheels.

It’s okay if you don’t believe me. But I just upgraded to version 7.1 of their software, which includes self-parking and summon features. It means my car self-drives in parking lots. It’s not even software in disguise. It’s just software. They didn’t send me any new hardware, just an update over WiFi.

Software isn’t Second Priority

It’s tied for first. Obviously a hardware company needs an amazing design and has to worry about manufacturing. The economics of a hardware startup are different. But a great hardware solution needs great software.

If you were going to build the connected camera (as if your iPhone didn’t suffice), designing and engineering a perfect, beautiful camera wouldn’t be enough. People want to frame their pictures, or share them online. Your camera has to have a user-friendly social element or you’ve missed the boat. And if you don’t want to design your own social software, it needs to integrate deeply with Instagram, Facebook, and Twitter.

People, including me, are spoiled. We expect a great software experience wherever we go. If you’re building an IoT product, it’s not enough to connect something to the internet. Users need utility from your software too.

Software can never be an afterthought.

This area is where hardware companies miss out. If they don’t prioritize software, they’ll be unsuccessful. I saw this happen with a company in the pet space. After their successful Kickstarter campaign, they delivered an awesome hardware solution with so-so software. Once they upgraded their software and then built an app that augmented the experience, they were able to draw in new users to their hardware as well as keep the existing customers who purchased their hardware more engaged. Lastly, the additional software opened up way more monetization opportunities besides the hardware. (Nobody besides Apple makes money on hardware.) Only once the company realized that software was the key ingredient did their hardware solution become successful.

What Separates Leaders from Followers

Most fitness trackers do the same thing. They count steps, measure progress, and suggest goals. But if you use a tracking device, I’ll bet it’s a Fitbit.

It should be. Fitbit has the best solution for helping you stay fit and lose weight. It’s simple to compete against your friends (and yourself) as you work towards fitness goals. I find myself walking more so I can catch up with my competitive friends. I take particular pleasure (and taunt them) when I beat my friends on the the leaderboard.

Products are supposed to get a particular job done. The job isn’t to count steps, or else there’d be little distinction between the trackers. Fitbit has invested time, energy, and resources into building a data analytics solution to solve the real job: helping people lose weight. And why are they so successful? Because they invested in software that accompanies their hardware.

In my experience, I’ve never invested in a hardware company. I’ve only invested in hardware or IoT companies that are software or big data companies in disguise. It’s a massive differentiator.

Hardware’s Maturation

Consider this: Intel, a global hardware leader, has more software developers than Facebook. Intel is a software company that happens to produce hardware.

If it’s good enough for world-shaking market leaders, it’s good enough for your hardware startup. Go become a software company as well.

Meet The Connected Dishwasher

Put yourself in the shoes of Philips, consumer products manufacturer. Philips makes dishwashers. One day, they’re going to throw a sensor and wifi chip into the newest dishwasher model and call it a “smart” appliance.

We’ll have the thing we never knew we needed: the connected dishwasher. (But trust me, I will buy one.)

It’s not so simple though. Philips can’t put some chips into an appliance and call the project complete. They need to design an app that consumers could conceivably use. Then, they need an API so that Smart Things or some other home automation software can control it.

Philips was a consumer hardware manufacturer. But with the connected dishwasher, is it still?? Or is it a software company? Is it an App and API company? Of course not. Philips will continue to build appliances and outsource that kind of work to someone else.

But there’s more work left. The dishwasher needs to communicate to the power grid if it’s going to be “smart” and cycle at the most opportune times. Does that make Philips a data communication company?

And what happens when the dishwasher needs servicing? Luckily, its sensors can determine when repairs are needed before something breaks. The dishwasher “calls” a service provider and tells them what part it needs. Or better yet, a technician could log in remotely and fix the problem with software. No in-person visit required.

Philips is now solving problems the same way Tesla “repairs” my car! Doesn’t that strike you as a big leap for a consumer appliance company?

Dishwasher-as-a-Service

I say “DaaS” only partly tongue-in-cheek.

Because when Philips walks down this path, it will transform how the company does business. Its existing models aren’t compatible with its business needs. The dishwasher company will become a service company.

Not only that, but Philips isn’t competing against its old peers anymore. The company enters a field where it doesn’t have any core competencies: home automation.

The consumer isn’t buying a dishwasher. In their mind, they’re buying another home smart device, no different from a new Beats Pill in their mind. Besides every other consumer appliance manufacturer, Philips now has to compete with Apple, Bose, and Samsung for the same top of mind and share-of-wallet.

The other dishwasher companies don’t seem like a big threat anymore.

Where Do We Go Now?

History repeats.

Today, we’re in a mobile-focused world. Before that, it was the web. Then PC, and then Mainframe. Right now, people think IoT is geeky. They believe it can change “infrastructure,” whatever infrastructure means to them. But what they don’t realize is that IoT is probably the driving force of the next era of computing. We already have more IoT sensors connected to the internet than people In the next five years, the number of sensors will outnumber people by a factor of 10.

Philips and companies like them will have their business models disrupted. They’ll walk down new paths, completely unprepared for the risks that they’ve introduced.

But that’s where the massive opportunities lay. Startups can fill the gap. Investors can finance them. Someone will profit from the demise of the Old Guard.

The next era is coming, and it will either be the IoT era or an era driven by it.

A few years ago I was sitting in a classroom at the London School of Economics debating unemployment with my nobel prize winning professor. The conversation was centered around another LSE nobel prize winner, Ronald Coase, who in 1937 observed in his scholarly paper, The Nature of the Firm, that firms exist in order to reduce transaction costs and take advantage of economies of scale. Barring external forces, firms will tend to grow larger and larger over time. This is the fundamental economic framework powering the world economy since the industrial revolution, driving corporate behaviors such as: corporate structure, the rise of M&A, and 20th century management theory.

A few weeks later, Ronald Coase at 101 years old, would go on a podcast and declare his 80 year old nobel winning thesis obsolete. No longer do you need to scale the size of a firm just to obtain efficiency, with modern technology and today’s demographics, you can capture the same value with much smaller firms. Companies will still grow to be larger over time, however, they won’t grow as large as they have in the past.

Since then I have been thinking deeply about what has broken down Coase’s theory which was the fundamental underpinning of the world economy since the Industrial Revolution. After several years of reflection on this, I have come up with four forces:

The rise of the freelancer economy

Millennials’ behaviors and impact

IoT and lean hardware

SaaS economics and the democratization of IT

The Rise of the Freelancer Economy

According to a report by Intuit, by 2020 approximately 40 percent of the U.S. workforce will be working as freelancers. Another study predicts 50% by 2025. As more members of the workforce decide to freelance, the number of marketplaces to facilitate them will proliferate. In the past you would hire the reputation of a Brand. Tomorrow freelancers will build a reputation on a marketplace and the marketplaces will build a brand.

This trend will lead to more commodity based and strategic outsourcing. Commodity based outsourcing will consist of outsourcing HR, legal, accounting/finance, manufacturing, and software development. Strategic based outsourcing via the freelancer economy will outsource product development, design, and even management.

Millennials’ Behaviors and Impact

By 2020, Millennials will consist of 20% of the workforce, and by 2025, 75%. Millennials were born mobile and digital; their behaviors will change the way companies interact with their customers as well as how companies interact with their employees. Everything changes from preferred methods of communications (messaging) to marketing (social media) to commerce (mobile first). Traditional management models start to break down with Millennials managing Millennials and selling to Millennials.

IoT and Lean Hardware

At the same time the Millennials are taking over the workforce, we will have 26 billion IoT sensors in production and connected to the internet by 2020. Cheap sensors and widespread availability lead to more big data driven analysis about everything from the lighting in your office, self-driving cars, the temperature of your home, to how your dishwasher runs. Abundant sensors combined with cheaper and small batch manufacturing will drastically change business models, pushing them to be more service oriented. Robotics and AI will eliminate most unskilled jobs, driving employment to be more skilled and knowledge based.

SaaS Economics and the Democratization of IT

While the move to the cloud has already begun, over the next few years, it will be massive. The economics of SaaS software has shifted the decision making power to the line worker from the management and IT. Since you can swiftly deploy cloud-based software within your organization with a free trial, cheap monthly credit card payment, and no physical installation, employees are now making the purchasing decisions, not the IT department. This is breaking down siloed data, enabling remote/distributed teams, and creating more capital efficient companies.

The Next 10 Years

As we enter the post-Industrial era, the dynamics of the firm and the workforce are going to change radically. As the forces that are breaking down Coase’s model only grow stronger, many companies are remaining stagnant. The success of a company no longer depends on growing larger, but now depends on being the optimal size in order to fend off the disruptive smaller companies. Google figured this out when it broke the company into smaller pieces and formed the parent holding company, Alphabet.

The larger this gap between big and optimal sized companies grows, the less chance there is of survival for companies trying to grow by growing bigger, opening up great opportunities for disruptive startup companies. Even more interesting is that this transformation will happen in the next ten years. How tomorrow works is radically different than it is today.

No one talks about how important it is for your CTO to learn the business side of things. That needs to change. If you’re a co-founder or senior executive at a startup or growth stage company, you need to be more than just an expert in your area.I know that’s asking a lot. Becoming an expert is a massive task. But it’s not enough. Each senior leader needs to be familiar with engineering, marketing, sales, and accounting if you want to maximize your chance for success.

This concept has been popularized for non-technical founders for some time, through efforts like Mayor Bloomberg’s Learn to Code and Business Week’s magnum opus What is Code. But I’ll wager if you’re a CEO, you suck at social media. You probably don’t understand it, even though it’s the future of customer engagement. That needs to change. And this change needs to extend beyond giving non-technical founders technical skills. We need to help CTOs get business savvy.

Image by Flickr user foam

Perform a Self Assessment

If you had to take over any of your company’s functional roles (marketing, sales, etc.) for a short period, would you be able to lead effectively? If the answer’s yes, great. Proceed. But if not, you’ve identified a major need.

Things happen, and you need to prepare for contingencies. Not only that, how can you screen and hire the right person if you can’t speak the same language?

Non-technical CEO’s should code so they can:

Understand how the sausage gets made

Talk to their team with the right vocabulary (i.e. Agile, Scrum, and Kanban)

If you’re the CTO, don’t you want to be relevant in business meetings? You won’t be as strong in marketing as your CMO, but you can add value and influence decisions.

If you outsource business decisions to your non-technical co-founder, there will be consequences. Best case scenario? You disengage from the business side.

Worst case: your disengagement leaves your CEO to feel lonely and stressed. And then one day, you wake up to a phone call from that person saying, “Hey, we’re out of money.”

Don’t let that happen to you.

Jump into the Business Side

I love founding teams comprised of engineers because:

Less technical risk

Solve their own problems

Shared background with me

I’ve been a CTO many times in my career, and I’ve exited multiple companies. But heading back to grab my MBA still made me a better CTO.

I don’t think all developers should get an MBA even though, unlike many of my peers, I think there’s value in one. Instead, I’d suggest creating your self-study MBA.

Design Your Personal MBA

Here are my suggestions for a practical education that will make you a better leader in every functional area.

I recently recommended a friend for a PM job at a hot Silicon Valley startup run by another friend. The startup recently raised a big Series A and was looking to scale. I know the risk of linking up two friends in an employment scenario, however, my friend was more than qualified for this job and my founder friend really needed the position filled.

While my friend was more than qualified, interviewed well, and the team loved him, etc, the founder decided to pass on my friend. The reason: another candidate with the same skills and experience came along that they hired. The difference between the hired candidate and my friend? The candidate that was hired had the same PM experience but all at big companies like Facebook, Amazon, and Google. My friend has spend his entire career at startups.

My question is: was this the right move? If you had the choice between nearly two identical candidates and one had all their experience at big successful companies and one had their experience at successful startups, isn’t it safe to choose the candidate that worked at the bigger companies?

Put yourself in the founder’s shoes. You just raised a big Series A. You are being pressured by your investors to “go big or go home.” You have aspirations to be a big company. This is Silicon Valley, shouldn’t you hire the absolute best talent we can find? Shouldn’t you hire people who worked at Facebook and Amazon since you want your company to be big like them one day?

PMs that only worked at companies such as Facebook and Amazon are super qualified PMs. Huge plus. They also know next to nothing about building a startup. Huge negative. People from larger companies bring the bigger company process, procedure, and culture with them. This leads to premature scaling of your business. The problem is that your startup is not a smaller version of a bigger company. As Steve Blank says, a startup is an experiment looking for a business model, not a smaller version of a larger company. Facebook as over 10,000 employees and billions in profits. My friend’s company has less than 15 employees and no profits. Hire people comfortable working in that environment, who know how to bring a company from 15 people to 150 people. When your startup has 1000 employees and is super profitable you should start to hire PMs from Facebook. In between, you have to hire people who can not only do the job, but also help you grow the business, shape the culture, and constantly evolve the process.

I made this mistake several times at my past startups. At one startup we realized that we needed an HR manager. Since we had plans to “go big” we wanted to hire an HR manager who came from a big company. Big mistake. We were a team of 12 but all of a sudden we were doing 360 reviews and had to fill out a form in order to take a day off. At another startup we wanted to enter the “enterprise” space, so we hired some “enterprise” software people from a large enterprise software company and gave them fancy titles. The problem is that people who work as executives at big companies usually don’t roll up their sleeves and build a product. Nor do they know how to scale a company, they know how to keep a big company big, but don’t know how to build a big company. In addition they wanted to fly business class and have personal assistants, things that did not jive with our startup culture.

Avoid premature scaling at your company and hire not only the candidates with the best skill set, but also with experience in working at and building a startup. Later on when you are bigger and more mature should you hire the people with bigger company experience.

Here in Silicon Valley, it is commonly said that it is “easy” to raise $1m in seed funding and $100m in Series C/D growth funding, but impossible to raise the $5-7m in Series A funding. This has been called the Series A Gap, or the lack of funds for startups looking to break out of angel and seed funding.

There is no Series A Gap

Over the past year as a VC in Silicon Valley, I’ve worked with Fresco’s portfolio companies and met countless other startups looking for funding. I’ve seen good companies left for dead when trying to raise a Series A and some raise a Series A in just a few weeks. I’ve rolled up my sleeves and worked with the founders on their deck, valuation, strategy, and ultimately their pitch. Along the way in the trenches of Series A fundraising, I've learned something: there is no Series A Gap.

Pitchbook and other sources have confirmed what my gut has been saying for the past year: there has been a modest rise of Series A capital over the past few years, but there is a glut of seed funding in the market today-as much as 4x higher in the past 5 years. So it is comparatively easy to raise a Seed round creating more and more startups looking for the same amount of Series A funding.

Startups have little problem raising seed funds these days. They string together $500k-$2m from many different people on an open source convertible note, typically $100k at a time. (AKA the “Party Round.”) Then they go out and try to find the right product-market fit and business model. Some make it and go on to raise a Series A pretty quickly. Most do not.

The Rise of the Second Seed Round

The companies that don’t find the product market fit or develop their business model try for a Series A and fail. Typically they are competing against companies that have already found their business model and are executing against it. Eventually they run out of money.

If you run out of money during your seed round and you can’t raise a Series A, in the past you had three choices:

Fold the business

Raise a “down” round

Keep struggling along on nights and weekends

Now what founders are doing is going out and getting a second seed round. Typically more money than the first seed and almost always at a much higher valuation. Some people call these rounds “pre-A” and “super seed.” I’ve seen a ton of them, some that should be a down round but have a crazy high valuation. (I've walked away from two of them in the past month alone.)

For example consider this funding for startup NewCo;

Angel funding $200k @ $2m cap

Seed funding $1.3m @ $7m cap

Seed funding II $2.2m @ $12m cap

NewCo now has 20 or more note holders and an insane valuation. If you have a $12m cap on your convertible note and you raised $2.2m on it, chances are your valuation at the Series A will be near $30m. The problem is that now your revenue and growth trends have to justify that $30m valuation. Unless the business model is really strong and the company is progressing nicely, raising a Series A will be all but impossible. There is no Series A Gap, but rather a glut of seed funding and a self-inflicted wound of raising too many seed rounds with little or no growth to show for it.

What to Do?

Founders are better off trying to raise one larger seed (with a lead!) and using the round to focus like a laser beam on finding the right product market fit while keeping the burn low. If you need a second seed round, try to keep the valuation under control and have very specific metrics as what you want to accomplish in order to position yourself for an A.

Being an early stage investor, I see a lot of MVPs. I mean a lot. The problem is that most people don’t build real MVPs, but descend into building a prototype, then beta, then an actual product and still call it an MVP. Remember an MVP is your most important Customer Development tool. It is an experiment designed to test your value proposition’s assumptions by measuring a behavior and learning from the results. MVPs should be used for a short while in order to validate your learning and then help you develop the plan for the actual product. After you have built a few MVPs and measured the results, what are the top three signs that you are done with your MVP and can start building your real product?

Sign #1 That You’re Done With Your MVP: You are getting diminishing returns on your learning

Typically when you start doing the Customer Development/MVP process, it is pretty brutal. Your ideas are shattered when they come into contact with real people. It can be long, hard, and painful at times. But when you stick with it you usually go through three stages of MVPing:

Shattered expectations

Hearing the same thing over and over

Diminishing returns

Usually after your first round of MVPs, you go back to the drawing board a little and make adjustments to your Business Model Canvas and test your new assumptions. Typically you get into a zone where everyone is saying the same thing: this is good. After a while you adjust the MVP some more based on that feedback and the feedback and behavior you are measuring is only giving you a very small incremental gain. This is when it is time to stop MVPing and build an actual product.

Sign #2 That You’re Done With Your MVP: You’ve been doing customer development for a really long time

I’ve met countless startups that were working on their MVPs for months or years. Typically a single MVP should last a few hours or a day. After that time, you process the data, apply the learnings, and then make another MVP that should only last a short time as well. In a perfect world, you would only be MVPing for a month or two at most since the results of all of your MVP experiments gave you enough data to build a product.

If you have been MVPing on the same idea for over six months, you need to reevaluate what are doing. Some startups clearly have a product (see #3) and some clearly do not. If you have not seen traction in a long time and have been grinding away on the same idea for several months, it is time to ask yourself some hard questions.

Sign #3 That You’re Done With Your MVP: You are actually making money

Sometimes I’ve seen startups that are still MVPing when they are actually making money on their product or service. Typically the startup doesn’t have a clear indication of what the pricing model should be or what the right customer segment is. Once you have enough “validating revenue” (typically around $250k ARR), stop MVPing and start A/B testing and using other tools (typically sales tricks) to figure out the best pricing and customer segmentation.

As you start your next venture, think about these three tips when you start your Customer Development so you do it effectively, but don’t do it too long. Good luck!