Morettini on Management

General Management and Marketing Advice for Software and Tech Companies

Tag: Product Development

Extending Your Technology With Spinoff Products

Many software and hardware businesses, particularly smaller ones, are religiously focused on a specific vertical market. As well they should; focus is one of the most important attributes that can bring a business from startup to a strong growing business. This is often one of the key areas I concentrate on with many of my consulting clients. Many businesses just can’t turn down any sort of deal, no matter what the effect it has on their existing product development plans or other key corporate initiatives.

But there is another side to the focus issue. Many tech companies have developed excellent, mature technology bases at huge expense. If that basic technology has a horizontal appeal, it can be quite profitable to spend a modest amount of additional effort to bring that technology to other adjacent markets that the company is currently not serving.

Care needs to be taken, of course, to not spread your marketing efforts too thin. But if you’re smart about it your company can increase, sometimes dramatically, the return on its product development investments. Let’s take a look at a few potential tactics, all of which I’ve used successfully both at companies I’ve run and with consulting clients:

Customize your products for adjacent markets

As an example, maybe you have an ERP software package aimed at retail markets. It might be quite easy to customize the product for other inventory-oriented businesses, such as distribution or service/repair businesses. By doing this you’ve created a potentially large new revenue source, at a fraction what building that product from scratch might cost. The trick in this instance is often marketing the product–read below for a couple of ideas on how to accomplish that without doubling your marketing budget.

Private Label/OEM products

Private labeling or OEMing your product to another vendor can be an excellent way to extend your product development ROI. It might be as simple as partnering with a non-competitive vendor who takes your existing product “as is” or with minor modifications, as well as changing the product identity and labeling. The target partner would be a company very strong in a market segment that you aren’t successful in, have no interest in directly marketing in, or simply is beyond your resource level. If done well, this is a win-win for both companies. Your company gets additional revenues with little to no additional costs (“pure profit”), while your partner gains additional revenue in it’s target market–without any product development investment.

Integration & bundling with other products

One of the best things a software vendor is to create a “developer’s version” of it’s product, which essentially consists of creating APIs (application programming interface) to the software. This allows easy integration with complementary software applications and even hardware. Back when I was CEO of a mapping software company with limited resources, we created a developer’s version which enabled both integration and bundling with a number of complementary applications, notably in the real estate and CRM segments. Once again, this tactic required only modest product development investment and enabled us to draw revenue from a number of different markets. We would never have had the resources to pursue these markets if we tried to build a new product from scratch as a company would traditionally do.

Different price points

Using my favorite mapping software company example, we were often forced to think creatively to wring out as much revenue as we could out from our existing technology. One of the other tactics we used was “de-feature” our existing $99 high-end consumer application to create a $9.95 version, which we then sold through mass market retailers of all kinds. Not only did this create more revenue, but the high volume business also created a bunch of opportunities to upgrade these entry level customers to our higher-end core product. This is a strategy I’ve used many times; you almost can’t go wrong when creating a larger customer base for your technology. I use the simplistic phrase “the more you sell, the more you sell” to illustrate the advantages of this approach.

Business vs. consumer version

At that very same mapping software company we used one other great approach to extending your technology: creating a B2B version of our consumer product which was aimed at road warriors such as sales and service professionals (the converse works just as well). The B2B version had a few additional features and we sold it via different channels and strategic partners. It didn’t have the unit volume of the consumer version, but the margins were much higher.

So there are a few ideas on how to extend the use of your IP to increase your overall ROI. What are your ideas on creatively utilizing existing assets to create additional growth? Please post a comment with your own thoughts so we can all benefit.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

1 Comment by admin on December 5, 2011
filed in B2C, Business Models, Corporate Strategy, Distribution Channels, General Management, Product Marketing/Management, Software/Product Development, Startup/Early Stage, enterprise software, hardware
tagged , , , , , , , , , , , , , , , ,

Will Smartphones Replace PCs?

Smartphones are taking over the world–the tech world, at least. The computing buzz these days is decidedly mobile. The question is “where does it end”? Do Smartphones continue their growth until they are the dominant or sole computing platform, or does this trend stop somewhere short of that? Let’s look as some of the factors that will drive the market:

Processors

The state of microprocessors used in Smartphones will go a long way in deciding the ultimate outcome of this discussion. We’ve seen similar scenarios to the Smartphone phenomenon before, and history tells us that microprocessors will keep progressing on all three major computing platforms. History also says that applications have always grown in size and capability to take advantage of the increased level of processing power and memory available at a given cost. In addition, desktop PCs (and laptops to a lesser degree) don’t have the extreme power constraints that a pure mobile platform like a Smartphone does. If historical trends hold true, it won’t bode well for Smartphones becoming the dominant computing platform, because PCs will continue to have an inherent advantage in software capability due to more powerful hardware. If there is a leveling off in PC processor capability, Smartphones will have more of a chance to overtake them as the primary computing platform.

Screens

Screen size and power consumption are also very important to this argument. Until holograms become standard, screen size will always be an important factor is choosing where to do your computing. This doesn’t bode well for a total Smartphone takeover of computing.

Keyboards

Keyboards are an analogous issue to screens; once voice input becomes standard in the computing world, keyboard size will seize to be an issue, tilting the field toward Smartphones. But until this happens, all but the insane will prefer typing on a PC keyboard over anything available in the Smartphone world (although there have been definite improvements in Smartphone keyboards).

Batteries

Battery life is also a major driving factor in the capability of Smartphones. While mobile processors and memory will almost certainly continue to provide greater compute capability at lower power consumption, desktops essentially have no power constraints (except for the very green-conscious). Even laptops come with an assumption of working at least part of the time where they can be plugged in. There could come a day where batteries are so powerful and hardware is so miserly in power consumption that battery life is no longer a major issue. Until that day, however, the checkmark goes to PCs.

Software

There are two aspects of software that are important to this discussion. The first is the number and breadth of applications available–the Smartphone category has already blown through this checkpoint. Hundreds of thousands of applications are already available on Smartphone platforms. Smartphones are already in the mainstream from a software assortment perspective. The second question is the sophistication/capability of the infrastructure software available, to ensure whether bleeding edge technology can be used on a platform. While Smartphone infrastructure and tools aren’t t yet as powerful and mature as what’s available on PCs, things are moving fast and I don’t see this as a major issue preventing Smartphone dominance.

New Hybrid Smartphone/Laptops

This embryonic platform holds the promise of being a game-changer in the market, tilting the advantage towards Smartphones as your primary (and possibly only) computer. What I’m referring to is a normal Smartphone “docked” into a laptop accessory shell, providing a larger screen, keyboard and maybe even bigger battery while using the same interface and software available on your Smartphone. This allows all of your files and computing occur on a single device, which would represent a major breakthrough for users. It’s the holy grail of computing. You may have seen ads for one of the early models, the Motorola Atrix “Lapdock”; or heard about the recently announced ASUS Padfone hybrid Smartphone/Tablet. It’s still very early in this segment and definitely uncertain how it will turn out. As in any early market, prices are still high, and the early devices don’t quite work as well as you’d like. But the paradigm is a powerful one. If the companies bringing out these devices stick with it, continue to innovate and introduce next generation devices that meet market expectations, this is a product that could truly be a PC killer. Only time will tell if this category will become the next generation of computing, or peter out like so many other great ideas that weren’t carried out to the required maturity.

I realize that tablets are becoming an important part of the computing ecosystem, but for simplicity I’ve considered them a next generation laptop in the context of this discussion.

I can’t say I know how this eventually works out. If I had that type of view into the future, I’d be in Vegas placing bets rather than writing this article. But using history as a guide, I think all three major platforms–desktops, laptops and Smartphones–will be with us for a long while.

I do think there will be a re-alignment in computing market share among the main platforms. I see desktops continuing a slow decline in share and eventually becoming specialist computers, used only where the ultimate in computing power is required. Smartphones have already staked their claim as the new growth platform. How far this growth goes is the only question. The wildcard is the new hybrid category. I believe that these devices could become the dominant primary computing platform if the hybrid Smartphone/laptop category takes off–which is far from a certainty at this time. If hybrids don’t take off, I believe screen, keyboard and processor limitations will prevent Smartphones from becoming the dominant computing platform anytime soon.

That’s my forecast–what’s your opinion on the direction computing will take? Do desktops eventually go away completely? Are they replaced by a Smartphone/laptop hybrid device? Do two of these three platforms survive, or will all three co-exist in the future as they do now?  I’d be interested in your own forecast–leave a comment to further this discussion.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

1 Comment by admin on June 12, 2011
filed in Business Models, Corporate Strategy, Software/Product Development, hardware, market research
tagged , , , , , , , , , , , , , ,

Starting and Growing a Software Company in a Difficult Fundraising Environment

Some would say that it’s ALWAYS a difficult time to raise funds for a startup company. In general, I’d agree. With the exception of a few brief moments, such as pre-Internet Bubble in the late 90’s where money was being thrown around like air, fundraising is hard. There are a few lucky folks that don’t sweat this startup task, like repeat entrepreneurs who hit it big the first time, or those with truly obvious ground-breaking IP. But for most it’s a grueling and soul-sucking necessity.

 Today fundraising for a startup company is tougher than every. The Venture Capital (VC) business is in disarray, with the number of active firms in the process of shrinking. The financial crisis and general economic malaise has made finding capital from nearly every source more difficult, from traditional banks to angel investors. So if you’re planning on starting a company today, it might be time to get creative.

 Most of the ideas presented here are applicable to any type of company. But for those smart about it, a software-based business is one that can be started and grown with minimal, or zero, outside capital. This has always been true in the software business, but a number of developments have made bootstrapping even a more realistic possibility today. You will need to accept upfront that it can be done, and structure everything you do with minimal financial resources in mind.

 Successfully bootstrapping is tough if you’re a first time entrepreneur, especially for those that have been working in large companies, with all the trapping that come with that. But embracing the proper attitude early on is essential if you’re going to have to bootstrap your company, at least in the beginning. Let’s examine some tactics that can increase the odds of startup success:

 Understand early-on the level of capital you’ll have available

This is crucial. Most get going on their business, moving ahead and worrying about funding once they have a business plan, prototype/beta, etc. Only then do they put together an investor pitch and think about how much money to raise. But it can be really helpful to have a realistic view as early as possible how much money will be available to you in the early days. No question this is hard to do and by definition the result will be inaccurate. In reality, a number of things will dictate how much money you’ll have available: Management team reputation and track record, investment contacts, dilution philosophy, local investment resources, business model, IP, etc. The key point here is to do your best to understand how much money you’ll realistically have available at startup and early on….

 Structure your business accordingly

….then design your business model to fit your prospective available funding. In reality, this rarely happens. Most design their business, and then try to raise money to fund it. As a result, for example, I see people start enterprise software companies, with complex products at high price points that demand a team of outside sales reps and field engineers with $150-250K comp plans. Most startups won’t be able to attract the funding to support this sales model. Or adopting a Software-as-a-Service (SaaS) approach, without planning for the added operational expenses required with a SaaS model, essentially taking on the role your clients IT department. If you can match your business model to your expected capital resources from the beginning, your chances of success go way up.

 Start while you’re still working

One of the best things a startup entrepreneur can do is to start working on your business while you still have a job. This is especially true of the technically-skilled software company founder. Many software companies have been started by a sole programmer, writing the initial product on his or her laptop while sitting at home in the kitchen. It’s one of the beauties of the software business; you can create a product with very little capital investment. Of course, care needs to be taken that you don’t use any of your employer’s resources or do anything on company time. Make sure that you aren’t violating any of agreements signed with your employer. But once you stop working to start up a new venture there’s no telling when your personal income will start flowing again. So do as much as you can, before cutting the cord with your steady income.

 Do it yourself and don’t be wasteful

Entrepreneurs often find that they can actually do things they never dreamed they could. When dealing with scarce capital, it’s critical to make sure that you actually NEED to pay someone else to accomplish a particular task before parting with your cash. This will lead to personally doing a lot of mundane activities that you don’t really want to do. But it’s important to take those duties on early on to conserve cash. Also try not to waste money on ANYTHING, not just labor. Count those paperclips! The corollary to this is when you really do need outside help, DON’T SKIMP and just do an unacceptable job internally. Bad marketing is an example of this for the technically-oriented founder. This can be truly penny wise and pound foolish, and can cost you much more money in the long run than you save in the short term. Recognize what skills you just don’t have that are absolutely critical to the business, and save money elsewhere so you can afford outside assistance in those crucial areas.

 Don’t reinvent the wheel

I referred earlier to it being easier than ever to build a software company with minimal capital. Development tools have matured to make development quicker than ever. Many target platforms have much less memory constraints, reducing the time needed to produce code that is extremely memory-efficient. There are many pre-built modules for standard functions available for a modest cost. Ten years ago it might have taken a half million dollars to build a quality website that you now can replicate for a few thousand dollars. As a software startup, make sure that you scour all pre-existing resources for things that you can use, before you build them yourself.

 Outsource and off-shore, if appropriate

Another area responsible for much lower costs in starting a software business is the potential for outsourcing/offshoring. This isn’t for every company or every situation, but where it makes sense, it can both reduce your costs significantly and expand the availability of critical development resources. While everyone would prefer the developers under their own roof, in many cases there just isn’t the right talent where the company is located–or the budget to fully staff with full-time, onsite employees.

 Don’t ignore international markets

A big area which most software companies ignore initially for their products is international sales. It’s natural to want to focus on your domestic market first. But doing this exclusively can cost you some excellent growth opportunities, even from the very beginning. This is particularly true for US-based companies. The US is the toughest market in the world. It’s the biggest, and the bulk of the software industry is located there (all looking at the US market first….). As a result, the competition is almost always less in non-US markets. So there is low hanging fruit to be had, plus you can partner in many markets with distribution partners whom have existing market presence, and can take on much of the marketing investment required to gain traction. All of this can mean an excellent return on a modest investment. Once you’ve invested so much to create valuable product IP (which is very “perishable”, by the way), don’t limit your return on that investment by focusing on a narrow geography, if at all possible.

 Don’t give up and enjoy the journey

Don’t ever give up prematurely. The most important thing is to keep grinding until you start to gain traction. Starting up and growing a software company is an exciting–and difficult–endeavor. Above all, I believe you need to be able to enjoy the journey, in addition to having your eye on the end prize–success. There will be difficult times where you need the willpower and stubbornness to push through. Often startup success is found by staying alive long enough for good fortune to find you.

 That’s my advice on starting up a software company and growing it in relatively tough times. Post a comment if you have your own experiences to add.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

3 Comments by admin on August 8, 2010
filed in Business Models, Corporate Strategy, General Management, Startup/Early Stage, enterprise software
tagged , , , , , , , , ,

Growing from a Startup to a Mid-Market Software or Hardware Company

Every stage of a company’s growth holds unique challenges. In my opinion, startup to about $2M in revenue for a software company, and startup to $10M for a hardware company is the hardest phase of all. But growing a business is almost always hard, and there are several natural revenue levels where companies tend to “get stuck”.

 As in the hardware/software contrast above, revenue levels for different business models can be quite different. So it’s hard to generalize strictly upon gross revenue levels. But undoubtedly there are stages that every company goes through (startup to profitability, profitability to stable small company, stable small company to midsized company, etc.) which represent points of inflection in terms of the way a company operates. For example, you need quite a bit more formal process to operate a large company than a very small one. The methods of capitalizing a large company are very different from a bootstrapped or VC-backed startup. There are many more possible examples; I’m sure you get the picture. For this article we’ll focus on growth into the Mid Market stage.

 First of all, there is no perfect definition of a “Mid-Market” company. People have defined it many different ways: by number of employees, revenue level and many other factors. For the purposes of this discussion, we’ll define a Mid Market company as one having between 100 and 999 employees. . Let’s take a look at some of the major changes required to successfully grow from a startup to a mid-market sized company:

Hiring

As a startup or smaller company, you’re often restricted by resource realities with respect to who you can hire. Startups are often forced to hire people with less direct experience than they’d like, and pay them less than the going rate in cash compensation. You often can’t fill every hole, even all the ones that you think are critical. People have to wear two or more hats, and the type of people you can attract might be those that really prefer the small company environment, or are dreaming big dreams based upon the stock options. In short, it’s continuous compromise. As you grow into the mid market you have more resources to pay market rates, and are generally more attractive to a larger pool of employee prospects.

 But please, be careful–just because you can hire differently, doesn’t mean you should. I’ve seen folks get drunk on hiring at this phase, and get loaded down with overhead that makes running the business to optimal profitability much harder. There is also a tendency to go after people with big, blue chip company resumes, which can be very dangerous. If these candidates don’t also have experience in smaller companies, you’re setting yourself up for a very premature and inappropriate culture change. It’s important to guard against building a big company bureaucracy in a middle market company.

 Business processes

Much like in hiring, there is often a tendency to want to add too much process, too soon. In fact, I believe this is the absolute biggest danger executive management needs to guard against during this transition. The CEO and senior team are usually very aware that the business is outgrowing its current level of checks, balances and controls. Inevitably there is a need for additional and more formal processes. The typical mistake I see is that instead of adding carefully and gradually, folks want to radically change the business overnight. The result is often a still-modest-sized business operating like one with 20,000 employees: Meaning operating VERYSLOWLY. Guard against this! Mid Market companies still need to rely on speed and agility to compete with the corporate giants, who have many more competitive advantages that you can’t yet replicate.

 Scope of target market

Around the mid market stage, a single-product or single market segment company may be running out of room to grow at the rates it has historically enjoyed. This is a day of reckoning and a danger point that stops many promising companies in their tracks. If you need to expand into new products or markets, make sure that you do so rationally. Don’t go out and acquire a company in a complete different business, because your investment banker thinks it’s undervalued and a great buy. Do “diversify” into “adjacent” markets, taking one of your existing technologies into a different market, or introducing a new technology or product category to your existing market segment.

 Capitalization

This is the stage where you absolutely need to hire a serious CFO with financial market savvy and connections. Many startups have someone with a CFO title whose background is really accounting and financial controls. Or possibly and outsourced, part-time CFO. This usually is fine up to this stage. But once you are talking about opening new offices, funding a new market focus or new line of product technology, the game has changed. The skill set of controlling the company’s simple expenses, dealing with angel and VC investors now becomes inadequate. The company needs someone that understands raising money in institutional financial markets, along with the contacts that go with that knowledge. Budgeting and controls will also start to become more decentralized, requiring a different financial management style, as the company continues to grow into the upper end of the mid market phase.

 Distribution and regional offices

As your business grows into new markets and product categories, your distribution system must often change and grow with it. This might be the time that you begin to open offices in all the key geographic markets of the world. But don’t do this “just because it’s time”. It should be done only for good business reasons, such as increasing marketing in countries where a distributor won’t or can’t do what’s necessary. It might also be the time that a single distribution channel business needs to become multi-channel. For example, a direct-only company adds retail or VAR channels. Again, avoid the temptation to do these types of things because your business has grown to a certain stage. It adds complexity and overhead to your business, so make sure there are sound business reasons for the change.

 Product Development

Moving to a different customer set or new base technology can have a profound effect on the product planning and development process. It is often at this stage that you must stop relying on a single set of market veterans or insiders, who have been successful in bringing out products due to deep, long-term domain knowledge in your original market/product focus. Now is often the time where there needs to be a bit more standardized product planning and development process, as you broaden both the number and scope of development projects.

 The bottom line is that as you grow out of the startup phase, the way your business operates necessarily will need to adjust to continue strong growth. The biggest danger here is trying to “get big” before your time. While the big blue chip companies are often envied, trying to duplicate their current mode of operation while you’re just entering the mid-market stage is probably the best way to ensure that your company will never reach that blue chip status. “Get big” in the way you operate cautiously–because once you’ve bureaucratized your business, it’s very difficult going back.

 That’s my take on going from a startup to mid-market. Share your own growth stories with us to start a discussion.

 Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

No Comments by admin on June 8, 2010
filed in Business Models, Corporate Strategy, Distribution Channels, General Management, Operations, Startup/Early Stage
tagged , , , , , , , ,

Will SaaS Lead to the Death of Software Product Management?

There is a lot of talk in the software business these days about changing business models, particularly the trend toward SaaS (Software as a Service).

Will SaaS business models dominate the software business?

Many consultants, pundits and other industry figures are proclaiming that SaaS will very soon take over the world; saying if you’re not on the bus soon, you’re going to be out of business. I believe this is a bit overstated, but the strong trend toward the SaaS business model can’t be denied.

My opinion on SaaS adoption: When bandwidth is unlimited and close to free, all IT systems are totally secure, the Internet is as reliable as old AT&T; and every customer in the world decides they want to rent everything and own nothing–then I’ll agree that SaaS is heading toward 100% market share. As I said above there’s a strong trend in this direction, but we’re a long way from there.

Is software product management dead?

I’ve written about SaaS a number of times before, and since it has become very important in the software business I’ll continue to do so frequently. What I want to address today is another opinion some “experts” are also espousing: that the trend toward SaaS means the end of the Product Management function in the software business.

I find this statement to be downright silly.

When following this debate, it’s important to take notice that many of the folks proselytizing these opinions have businesses whose success is based upon these predictions actually coming true. It’s always important to consider conflicts of interest among the debaters.

In one recent webinar they trotted out a SaaS software company that was growing briskly every year with no product managers in the company. What wasn’t said is that it was always possible to find software companies (of the traditional sort) who didn’t have a product management function. Software companies are often founded by programmers, and they haven’t always seen the need for Product Management. There are very successful companies where the developers talk directly to the customers, with no product managers at all. However, the facts are that a very small percentage of companies that do business this way are successful, and its usually based upon special circumstances: the rare developer who understands markets and customers as well as he does coding, markets where the developers themselves are perfect customer proxies, etc.

So while software companies without Product Managers have always been out there, it just hasn’t been a broad formula for success. Trotting out one SaaS company successfully doing business this way (incidentally, I saw some big holes in their model long-term) doesn’t impress me much.

I’m not defending the status quo–I’ll say it once again, there is a huge move to SaaS in the software biz. Many (and maybe most) will be doing business this way in the near future. However, like most over-hyped trends, this are some pretty big overstatements being thrown around.

SKILLED product management will always be important

The argument being made is that many of the functions Product Managers currently perform are obsolete under the SaaS model. With continuous development more practical using SaaS, there may be fewer (or no) new version introductions. So the old waterfall chart with MRDs being created for the new version may go away along with new product introductions. I’m sure you get the picture. SaaS is a pretty fundamental change to the software business model, so you wouldn’t expect a product manager’s job to be stagnant under such change.

But those predicting the death of product management are focusing on the more mundane aspects of Product Management. The essence of this critical function is the ability to understand markets and match widespread, aggregate customer needs to the technical skills and IP of your company–creating a PRODUCT which can be sold to these many people. It doesn’t matter whether you deliver this PRODUCT over the Internet in a hosted manner using monthly subscriptions, or in the more traditional on-customer premises, licensed model. Product Management is about creating a profitable PRODUCT well-matched for a market segment. It matters not whether you are engaged in customer facing marketing/promotional activities, or upfront product planning–the product manager’s understanding of market needs and how your company can fulfill those needs is crucial in a product business. Otherwise, you’re just selling custom software–one-off’s for every customer. That’s a different business–not a bad one–and one you which doesn’t require product managers.

Can Social Media replace Product Management?

Another thing being bandied about by my favorite pundits is the impact of communities and other social media for its potential impact on product development. The thinking goes that there will be much more direct interaction with the end customer, leading to tremendous amounts of data available to ISVs. While SaaS is very well suited to communities (although not exclusive–they can be well utilized by traditional licensed software vendors), the ability to more easily obtain direct customer comments, and maybe take votes on potential new features doesn’t eliminate the need for product management. To the contrary. While communities and other forms of social media are very powerful tools, don’t mistake more data and customer access with actionable market intelligence. Data needs to be interpreted, and skilled marketers are best positioned to discern who’s telling you what and why–the underlying motivations behind any customer feedback. So all of this added customer access and resulting data will only put a premium on good product management, to use these powerful new tools and data for quicker action and to allow better product planning decisions. Remember, SaaS competitor down the road will have access to the same tools and data that you do.

It is rare to find a developer who has truly exceptional product management skills. That’s not a knock on developers; as a whole they are an extremely sharp bunch. But specialization in life happens for a reason–very seldom is someone the best at everything. Developers are trained to write code and build applications, not understand markets or extract the “truth” from customers. Different types of people’s brain’s work differently, and a good developer and good product manager are an example of this.

I find that it’s when a talented, open-minded development manager teams with a market-savvy product manager, that most great software applications are made. So no, I don’t believe that the Product Management function is going away anytime soon in the software business. There are many important changes going on in the business, the SaaS business model not the least of these. With any change in business model, functional roles will evolve and change. But I believe strongly that Product Management is a fundamental, important role that will remain critical in software businesses far into the future.

That’s what I think about SaaS and product management–what do you think? Post a comment to start the discussion! Follow Phil Morettini and Morettini on Management via Twitter, Facebook, RSS, or the PJM Consulting Quarterly Newsletter.

3 Comments by admin on October 12, 2009
filed in Corporate Strategy, Product Marketing/Management, SaaS, Social media, Software/Product Development
tagged , , , , , , , , , , , , , ,

Integrating the Marketing and Engineering Functions at Technology Companies

In most tech companies, Product Marketing and Product Development/Engineering are managed separately. There is usually a VP over the Product Development function and another over the overall marketing function, which usually includes future product marketing/planning.

While this is certainly an appropriate way to organize a tech company, there is a great danger in one are when it comes to these separate operating “silos”: the planning of new products.

I have a particularly strong opinion on this topic, with an extensive product marketing background and also having worked as a product developer earlier in my career (albeit in a non-tech business).

With respect to current products, the silo approach isn’t much of an issue. The day-to-day activities of the marketing and engineering departments are very different, and can be managed separately quite successfully.

It’s in the future product area that things can get messy. Product Marketing and Product Development both have a key role to play here, if the company is to optimize the process of planning, developing and introducing the best new product possible. The problems is that at every level, from the VP-level down to the engineering project managers and marketing product managers, the product marketing and engineering functions are often staffed by individuals with very different world outlooks when compared to their direct counterparts in the other department.

Inevitably, if care isn’t taken, these very different personality types can lead to some pretty intense conflicts. I’ve been a soldier, captain and general in this war–and let me tell you, it isn’t pretty. The battlefield often is a company’s strategic plan, which ends up in a trampled mess. I have seen this battle play out regularly in the companies that I have worked for as an employee, as well as at many of my clients in eight years as a consultant at PJM Consulting. It sometimes gets so ugly it paralyzes a company, putting it at a severe disadvantage vs. competitors who have less of a conflict.

THE “WRONG” WAYS TO HANDLE THIS POTENTIAL PROBLEM

Unfortunately, most CEOs that I meet are not all that in tune to how damaging these conflicts can become.

Often they will ignore or deny the problem, thinking it is a responsibility to be handled at the VP level.

Another strategy that I have seen companies put in place is to extract the product planning function from the marketing department, and put it under engineering. This will often greatly reduce or eliminate the conflict, but it akin to throwing the baby out with the bathwater. As I said earlier, both marketing and engineering have a key role to play in product planning. This strategy effectively removes the voice of the customer, which is a key role that the marketing department should be playing in any successful software or tech company. As much as product developers think it looks easy, they almost never have the mentality or experience to accurately read markets or customers. Almost no one is great at everything; monitoring and reading markets, and technical product development, are two very different skill sets. Having both mentalities involved in a positive way leads to far better products in the end.

Finally, if they happen to have come from one side of the battle or the other, CEOs sometimes “take sides” in the battle–predetermining the winner. The problem is there is never any real winner in this battle–and the only certain loser is the company and its shareholders.

A CEO can choose to let Marketing have the upper hand–and this may work out adequately in commodity products where there is very little engineering differentiation. In any other circumstance, results will likely be sub-optimal.

Or he can let Engineering win and dominate the planning process–which is a very common occurrence in early stage, technically-driven software and tech companies. But this generally only works well for products made by engineers, built for engineers (the early days of Hewlett Packard are an example of this strategy working successfully). For every company that has used this approach successfully, there are probably hundreds or even thousands that failed in large part because of it.

Ultimately, to make sure that this conflict and its dire consequences are to be avoided, there is one key thing that needs to happen:

IT IS THE CEO’S RESPONSIBILITY TO PREVENT, RECOGNIZE AND FIX THIS PROBLEM.

So what steps can a software or tech CEO take to be on the lookout for this problem–and more importantly, what can they do to prevent it from developing?

*It’s all about relationships: closely monitor the personal relationship between VP-Marketing and VP-Engineering
*Make sure that the VPs are monitoring the relationships below them
*Make sure they are both VPs are open and honest with you about the relationship between departments
*Plan activities which allow engineering and marketing counterparts to get to know each other as “people” outside of their project activities
*Be careful that you don’t inadvertently make decisions or set up policies that reward or tolerate politics
*Design goals and MBOs to reward the two departments for working together
*Don’t ever allow one department to “get ahead” by blaming the other–tie them together as much as possible
*Hire marketing personnel that can talk the language of engineers
*Screen product development hires who will interact with Marketing for the not uncommon attitude that engineers are “superior” human beings
*Encourage the marketing department to get product developers in front of customers
*Watch out for arrogance when screening potential new hires for either department that will interface with the other –arrogance is usually the trigger which starts the battle rolling

SUMMARY

Marketing/Engineering conflict over the product planning process is a common problem that is often overlooked by tech company CEOs. A certain amount of creative tension can exist between the two departments, and be totally healthy. All too often, though, this tension turns into a bloody fight which is destructive to the company’s prospects. It is not “fait accompli”, however. It can be minimized and even prevented by a watchful and proactive CEO.

That’s my take on a common issue which is rarely discussed out loud. Have you had your own issues in this area? Post a comment to add to our discussion.

Phil Morettini
PJM Consulting
www.pjmconsult.com

No Comments by admin on July 8, 2008
filed in General Management, Marcom, Operations, Product Marketing/Management, Software/Product Development, hardware
tagged , , , , , , , , , ,

High Tech Market Research for New Products

One of the biggest problems in High Tech businesses is the “technology-driven” approach that tends to predominate, especially among startups. Much of this occurs due to the fact the many founders of software and technology companies tend to come from an engineering, programming or other technical background. While a strength in creating a flow of technical innovation, this can be a real problem when companies are planning new products which they hope to find a real market for.

Everyone has a tendency to focus on what they know best; that’s just human nature. Folks spend more time on the issues that they enjoy, are more comfortable with, and are more confident about their ability to make good decisions on. Things that don’t fit into this category tend to be put off, or given short shrift.

The result is often products are well thought out from a technical viewpoint–but much less well so from a “meeting market needs” perspective. While both are important, the market perspective is absolutely critical initially. So what’s the right approach to product planning-oriented market research?

When Should The Research Should Be Conducted?
The answer to this is early, often and forever. The earlier you start prior to design or coding, the more time you will have to obtain the most accurate picture of the market that’s possible. Sometimes there are practical limitations to how early you can start–Trade secrets and patent filings, for example, or the lack of a prototype which may be considered crucial to receiving realistic market feedback. Within these limitations, get out and begin interacting with the marketplace as soon as practical. And don’t ever stop. Markets, especially the software and technology variety, are like living organisms. They are constantly growing and changing. What may be true in the early phases of a market could change dramatically over even a short period of time. Companies tend to develop an internal “common sense” that is used in making decisions, which is based upon past inputs. When doing Product Planning this can very dangerous in a dynamic market.

Who Should Do The Research?
The best way to do this research is what I often refer to as the “two-headed monster” approach: one marketing person, and one technical person. Not a lone wolf if you can help it, and please–no committees. Most often, this would be a Product (Marketing) Manager along with the Engineering Project Manager who will lead the actual development of the project. In the smallest startups, it might be the technical founder and the “business” founder, for example the CEO and CTO, or CEO and VP Marketing. The Business/Marketing manager should be in the lead for this task, but it’s important to note that both camps have a role to play in this endeavor. There are two different perspectives on market feedback, and well as two different priorities in questions to ask. Having both parties involved (assuming there isn’t a dysfunctional relationship) usually leads to the most complete and risk-reducing result. In addition, it often eliminates arguments over priorities later in the process after coding starts (and schedules inevitably begin to slip) If only one can be available, it should be the Marketing side–working closely with the Product Development/Engineering lead to make sure their input is included in the process.

How Should The Research Be Conducted?
This is a really broad question which of course depends heavily on the situation. How much do you have available to you in terms of money and other resources? If you’re in a big company, you may be able to commission some objective research. If you are a startup with modest resources, it usually is an ad hoc exercise of visiting and interviewing potential customers.

What’s most important to keep and open mind, and eliminate your own biases and pre-conceived notions. This exercise needs to be a search for the truth, not an attempt to validate your own theories. Also, make sure that you are talking to the right people. If you are planning a market-creating breakthrough product, you really need to be talking to Early Adopter types, not the guy or gal that only buys after everyone else they know. If you are introducing a product that is very similar to other products in an already large market–but maybe at a lower cost–by all means, talk to those mainstream buyers and even the late adopters. Use the current market phase to guide who to get input from.

It’s great if you have the money to do some formal secondary research, but be careful about confusing formality with accuracy. For example, I know of large companies that spend huge amounts of money on Focus groups, while their Product Managers only reluctantly talk to actual potential customers directly. I find this very dangerous (you might say stupid!). Particularly with breakthrough technology, you tend to find a “garbage in, garbage out” phenomena with professionally managed focus groups. But there is that formal, professional looking report that appears very convincing in the aftermath. They can be great if constructed properly, but I have seen a lot of money spent for a very bad result. If the focus group wasn’t run properly, or the technology is very revolutionary, the results can be total garbage covered in a beautiful wrapper. I always advise that there is a good amount of old-fashion ad hoc research–talking directly to customers–to be used as a sanity check, if not the main research technique. There are exceptions, of course. If you are doing incremental product research, where the product is well-understood and the changes are evolutionary, objective research methods such as surveys may be a great way to get a quick and definitive read on the market’s reaction.

How Do You Know When You’re “Done”?
This really depends on what you are doing, but my general answer is that “you will know when you are done when you get there”. It’s important to not put an absolute time limit on the research, if it is at all practical. In some cases in the real world, this isn’t possible, of course. Sometimes you just have to go with the information that you have gathered up to a set point in time, along with your market common sense, intuition, and gut feel. With incremental product releases, waiting may not be possible or necessary. But if you can avoid it, especially if starting a new company, division, or business area, resist the temptation to “go with what you have”, if it just doesn’t’ feel right. In my experience, when you’ve “done enough” research to begin serious product planning–it’s obvious. You will feel very comfortable with regards to the clarity of the current market snapshoot, and feel you’ve really nailed the wants and needs of the market as it relates to the new product opportunity. Try not to get “antsy” and move forward because you’ve reached the original market research end date on your theoretical timetable. Resist that temptation and keep working until you are CONFIDENT that you are there, unless other factors just won’t allow it.

Summary And Conclusions
Make sure that you do sufficient market research before you begin building products; product development on a developer’s gut feel is most often a prescription for failure. There are a few high profile companies which have entered our folklore that were lucky enough to start that way, but usually this approach will quickly empty your pockets, rather than make you rich.
Include both Marketers and Technologists in the Research if at all possible. In summary:

*Marketing should take the lead on market research for new products
*Always make sure you talk to at least some customers directly and informally
*By wary of formal market research results, if not supported by an informal research “sanity check”
*Make market research a continuous company function
*Don’t stop an individual product-oriented market research project until y
ou are comfortable that you’ve got the correct answer.

There you have my thoughts on market research for product planning purposes. I’d love to hear yours as well.

Phil Morettini
PJM Consulting
http://www.pjmconsult.com/

1 Comment by admin on March 10, 2008
filed in B2C, Pricing, Product Marketing/Management, Social media, Software/Product Development, market research
tagged , , , , , , , , ,

System Integration vs. Product Development

I’ve recently engaged on assignments with two new clients. Both of them have businesses selling to large, blue chip customers. Customers of the size that are used to “having it their way”; as a result, getting a deal with them often includes the need for a lot of customization.

The interesting thing about these two clients is how they perceive and approach that need to customize.

A Tale of Two Companies

Company A views customization somewhat as a pain and distraction, something to be controlled–I am assisting them with creating a standard solution offering menu outlining the “Base” offering, with a list of options available at an added cost. They really want to discourage certain customizations, absolutely won’t do some things that will be asked, and want to make sure that they charge dearly for items that they find painful. They have the classic mentality of a product company; they want to do the amount of customization necessary to make a large sale to this important customer–but NO more than they have to.

Company B, which also considers itself a product company, has a very different mentality about customization. They welcome it, pride themselves on it, and position themselves to these potential large clients as someone that can quickly bring solutions to the client, customized to their desires. They want their big account reps to be scouring the big accounts for unique pain points or opportunities, which might fall within the company’s core capabilities, enabling them to propose a customized solution. In fact, up till now, their product development approach has really been to find out what individual accounts want–and build it for them.

So which of these two business models is the best way for technology companies to go?

System Integration Business Models

Advantages:
*More flexible and able to change with shifts in the marketplace
*Not as capital-intensive due to less “betting” on upfront product development
*Easier to grow business organically with internally-generated capital than in a product business

Disadvantages:
*Less risk due to lower upfront investments
*More competition; System Integration is an “easier-entry” business
*Generally lower operating margins
*Growth is less scalable than a product-oriented company

Product-Focused Business Models

Advantages:
*Provides greater opportunity for strategic advantage and resulting fast growth
*Less competition if a product/brand/technology differential advantage is created
*Can scale much quicker if a hit product is developed
*Higher operating margins if product is successful
*Usually more marketing-driven and less labor-intensive
*If creating a very large company is the goal, much easier to raise outside capital

Disadvantages:
*Much more risk of “crib death”, resulting in complete capital loss if first product has problems in development or marketing
*Harder to “get over the hump”; success is harder to come by, and success often happens as a step function after a difficult startup period

First of all, I want to emphasize that there isn’t necessarily a “wrong” approach with either of these business models. You can make a lot of money pursuing either model. Both of the companies I have used as models have managed to attract blue chip customer which would be the envy of any company. What we are really talking about here is the difference between a classic product-driven company and a system integrator.

Company A is that classic product-driven company. They customize when they have to, but also have a point where they will say “no”.

Company B also self-identifies itself as a product company, and in fact they have built their business around a small number of standard offerings. But as their core strategic advantage they really are utilizing relationships, the ability to customize beyond what standard product companies (especially larger ones) are willing to do, as well as to react very quickly to customer requests. They’ve built a very nice business doing this, but have some frustrations as well. They are highly dependent upon a small number of major accounts for virtually all of their revenue, and have the major revenue/profit swings that are associated with this type of business–up one year, back down the next. They also are in constant fear that a larger company will come along and “take away” their marketplace, because they’ve continuously failed to create new products which build upon a core offering which is very dated technologically. The core offering appears long-in-tooth and vulnerable. This company is very account-focused, and the lack of a market focus has kept them from being able to create additional, broadly marketable products which provide them with a strong proprietary advantage (and causes a lack of sleep at night!)

Company A understands who they are and what they want. That doesn’t guarantee success, but it makes it much easier to build a plan that everyone agrees on. At that point success or failure usually depends upon execution, unless the plan is awful. If failure ensues in this scenario, more times than not, the problem is in execution. Company B’s biggest problem is that they are floating right in the middle between the two business models. They are trying to leverage both of these business models, and struggling with execution, in some ways with both.

SUMMARY
It isn’t impossible to combine these two business models successfully. I’m sure that many of you can’t point to several examples of such a very successful compromise. In fact, many technology companies combine both of these models to some extent, with good success. But I find that usually, a company identifies itself primarily as a product company first, or a systems integrator. That identification is their strategic focus, and takes precedence when prioritizing the use of always scarce assets.

The secondary business model is usually utilized on an opportunistic basis. Product companies integrate and customize as needed to get a big deal. Integrators create “products” to fill the needs of a big account, and sometimes happily find they are saleable to other accounts. Occasionally, these “products” prove so widely saleable that they are spun off into a separate product company, or the integrator changes its focus into becoming a full-blown product company.

The most important thing, in my opinion, is to understand who you are, and what you are trying to accomplish strategically. It’s the company’s that are trying to leverage both business models at once, without one model taking the lead, that gets itself in a heap of trouble. That’s my opinion–what’s yours?

Phil Morettini
PJM Consulting
www.pjmconsult.com

1 Comment by admin on September 21, 2007
filed in Business Models, Corporate Strategy, Financing, Operations, Software/Product Development, Startup/Early Stage, VARs
tagged , , , , , , ,