Morettini on Management

General Management and Marketing Advice for Software and Tech Companies

Tag: SaaS

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

Selling SaaS through the VAR Channel

The move toward Software-as-a-Service (SaaS) is the strongest trend in the software business in recent memory. It changes the software business model in a number of fundamental ways. For the purposes of this article, I’m assuming the reader has a basic understanding of the SaaS business model. I’m also going to assume a basic understand of what a Value Added Reseller (VAR) is and does. I’ll focus on the fit between SaaS and the VAR distribution channel.

 The VAR channel has been a major factor in the B2B software business for a long time. There are tens of thousands of VARs, most of them now focused on specific vertical markets. While it is still possible to find a horizontal VAR, in a market of any size you’ll likely find a nice number of VARs specializing on that segment of customers. As a result, anyone who is selling software (whether via traditional licensing or SaaS) would love to have this stable of key market influencers representing their product. Let’s take a look at the situation:

 Major SaaS strengths

  •  Simplicity of startup for the customer – For many SaaS apps, getting started is as simple as signing up, obtaining a user name and password. Contrast this with the lengthy, complex and sometimes extensive setup and configuration period for some B2B apps. (This strength is a potential problem for VARs).
  • Available from any web browser - This is one of the great capabilities driving the SaaS revolution. Of course, traditional apps can have a web-based interface as well, but SaaS apps by definition are web-centric. Browser-based apps can limit functionality in some cases, but is becoming less of an issue all the time.
  •  Simplicity of maintenance for the vendor - This is a big one. With traditional on-premises apps, the vendor has to deal with “pushing” updates to the client, often into wildly varying hardware and software environments. With SaaS, the vendor presses a button and the new version is universally available to everyone. This is a huge advantage leading to reduced rollout costs for the vendor, and less pain for the client. (Also a potential problem for VARs) 
  • Less IT infrastructure required by clients - Theoretically a company could nearly eliminate their IT department by adopting all SaaS apps. As a practical matter, this isn’t happening in companies of any size, and likely won’t. But any reduction in reliance on perennially overworked IT departments is usually seen as a good thing. (Potential problem for VARs, but also an opportunity)

 Major VAR motivations

 Sell Services (not products) – Contrary to the expectations of channel neophytes, VARs are generally seriously interested in products to the extent that they have the ability to generate service revenue for the VAR. (Early SaaS models eliminate many traditional service revenue streams)

 Secure ongoing revenue – VARs don’t own intellectual property(products) to stabilize long-term revenues as a rule, so they’re always interested in ways of “smoothing out” their business with predictable, ongoing revenue streams. (SaaS eliminates much traditional service revenue, but subscriptions open up new possibilities)

 Maintain client control – VARs are very sensitive about retaining control of the relationship with their clients. They view these relationships as hard-won, and without owning the intellectual property, they are probably the most strategic aspect of their business. (VARs shy away from vendors who try to wrest account control from them, and many new SaaS vendors have this “direct-first” mentality).

 The Gap

 The problem as discussed in the above paragraphs is that the ways VARs traditionally make money (installation, training, integration, customization, support, client control) have been eliminated or severely reduced as opportunities by first generation SaaS vendors. Frankly, it’s never been easy for any software vendor to recruit VARs who are “active” with their products. The current situation sets up the typical first generation SaaS vendor as an arch- enemy to VARs. The SaaS vendors aren’t attractive partners due to the lack of potential service revenue (and often aren’t looking to partner), but are targeting the VAR’s customer base. To some, it looks like the end of the VAR channel for anyone running a SaaS-based company. Sound like a caution sign to SaaS vendors, one which makes the vendor focus strictly on direct selling? Maybe–but let’s explore a few ideas for changing the equation.

 Ideas on how to bridge the gap and attract VARs to your SaaS offering

 There are some forward-thinking SaaS who have been able to leverage the VAR channel for their companies. But at this point, they are few and far between. For many of the reasons stated in the above paragraphs, there is no established, tried and true model for attracting VARs to a SaaS offering today.

The biggest thing I’d like you to consider with respect to the sentence underlined above, is that when things are least established, there is the MOST opportunity for newcomers. Since there is no established perfect SaaS/VAR cooperative business model yet, no SaaS player is dominating in this still very influential channel. For a newcomer, this creates great opportunity and potential payback for creative approaches. Let’s take a look at a few such ideas to attract VARs:

 Design your SaaS offering from the ground up for easy customization and integration

Unfortunately I don’t see many SaaS vendors considering channel strategy when designing their first product. In the early days of SaaS, enabling customization and integration with other products was tough to do. Now the tools are there to make it very possible, but it’s a lot harder if you try to do it “after the fact”, once your architecture has been set and the first commercial release is done. This one step can be a huge asset when you are later trying to design programs attractive to VARs, and it can of course be a huge advantage with certain end users as well.

 Offer solid upfront margins, but focus on downstream revenue streams for your VARs

I recommend offering competitive upfront-sale margins, but going overboard here can be a waste of resources. Remember that VARs don’t build their business on upfront product sales revenue. Focus on finding ways VARs can make money dealing with you after the initial sale is complete. As an example, how about sharing downstream subscription revenue–but only if the VAR creates X amount of new sales revenue for the year? This is an example of a win/win which could lead to great loyalty to your offerings, tying the VAR’s interest to your business in the long run.

 Instead of building a large in-house consulting team, use VARs to help fill IT gaps for your customers

VARs have a lot of capability to offer services that your end users might require and demand. Rather than competing with VARs (and using scarce capital that could be deployed elsewhere), take a look at creating programs to utilize the best of your channel partners as your outsourced consulting team.

 Create a program to enable the outsourcing of upfront product training to your VARs

Initial product training is a great example of a “consulting service” to outsource to your channel. Most product groups see training as a necessary evil and an afterthought, often giving it away for free–while providing it with insufficient attention from the end user’s perspective. With the right tools, a VAR could turn this into a profit center for their business, reducing your utilization of key resources on a non-core activity, while tying the VAR tightly to your products.

 Be careful to allow your VARs to continue to lead in account management activities

In everything you do, keep in mind that the VAR is paranoid about account control (with good reason, unfortunately). Remember, you are in a business partnership with the VAR, and you need to trust them to do the right things for your joint business interests in the account. If you don’t feel like you can trust a particular VAR in this regard, don’t change your program to wrest account control from your channel. Stop doing business with that VAR.

I’m optimistic that adopting a few of these ideas can give you a leg up over the competition in building a productive channel business. I hope that you’ll find this article provocative, if not accurate in your view! This is an emerging, rapidly changing environment. Please post a comment with your own thoughts to expand the 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

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.

Cloud Computing, SaaS and Such–Have We Read This Story Before?

I have this incredible feeling of déjà vu.

Cloud computing and Software as a Service is all the rage. In my practice at PJM Consulting, I am very involved in software startup activity. Nearly every new software company that I see today is being built on the Software as a Service business model. It’s all the rage–so much so that it appears that any self-respecting software entrepreneur would be embarrassed to start a company using the traditional software licensing model. Even if an entrepreneur was so inclined, good luck finding a VC who would even consider funding such a company. No one wants to look like a dinosaur.

It’s all well and good–there is definitely a real trend toward SaaS and Cloud Computing, with many good reasons for it. But most high technology trends are initially a bit over-hyped, and tend to get ahead of themselves. In addition, this particular story seems ever so familiar to a tech veteran that’s been around for a few of these cycles.

The first bit of history this reminds me of is the old terminal/mainframe model from the early years of computing. There were some real advantages to this model, but also some big disadvantages as well–which opened the door for the golden age of PCs and networking.

The second era that the current SaaS wave reminds me of is “Web 1.0″, when Web-based hosted software (then called ASP rather than the modern SaaS terminology), was first going to take over the world. The current trend seems so very similar because it was around the Web 1.0 years of the late 90s/early 2000 when the traditional software license business model was first proclaimed dead. At that time nearly every new business plan was based upon an ASP model.

So some of this fast-moving Cloud Computing or SaaS trend is new–but much of it could be viewed as recycled from past trends. Let’s look at the Pros and Cons of this computing model:

ADVANTAGES

* Enables “Utility-Style” computing – variable expense instead of. capital investment
* Allows an end run around overwhelmed IT departments (like PC networking did)
* Supposedly “On-demand”–use only what you need, when you need it
* More efficient use of compute resources by time-slicing large farms of cost-efficient computing resources
* Web-based allows anywhere, anytime availability
* Off-site storage of data assists disaster recovery preparedness

DISADVANTAGES

* Immature and inherently more difficult Security
* More difficult integration with other applications
* Internet latency
* Internet reliability
* Data resides outside the company firewall
* Costs over time aren’t necessarily lower for customers
* Lower margins for software vendors–aren’t always accounted for in current pricing

SUMMARY

I believe that the trend toward computing in the cloud will continue, but there will be some stumbles and pullbacks along the way. Cloud Computing and SaaS has some inherent strengths–but also some under-publicized weaknesses. Many software vendors are overlooking the weaknesses at this time, as is typical of any new and hyped technology. Traditional licensed software hosted by the user still has its strengths and a definite place in the market. Like many mature technologies and business models, the death of traditional software licensing has been greatly exaggerated. Once the early hype passes, decisions on whether to computer within the firewall or in the cloud will once again be made on the individual merits, costs and user needs for a particular application within a particular company. That’s how I see it–post a comment with your opinion so we can look at all viewpoints.

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

Business Models in the SMB Market

The SMB market is typically a very popular topic for hardware and software companies. Every one wants to sell to the Enterprise market; as a result, competition is fierce and standards are very high. If you get to the Enterprise market early, with an innovation that creates a new category, you can find success if you are truly making a contribution to the market. But late entries into a market segment, as well as early stage companies competing with larger, established companies, often have a very tough go of it. In these situations, attention often turns to the Small and Medium-Size Business, or SMB, market.

And why not? At first blush, the SMB market appears to be huge, as well as underserved. It looks like a perfect haven for an early stage or turnaround company with a solid product, but not quite enough differentiation, brand name, or marketing muscle to push out the big boys in the Enterprise space. So the decision is made to focus on SMBs.

What’s Wrong With This Decision?

There is nothing wrong with this decision, per se–if it’s done with eyes open, for the right reasons. But too often, it is done to run away from a problem (the inability to penetrate enterprises), rather than run to a great opportunity. A lot of times, companies see the SMB market as easier turf; simply a larger, less competitive market than the Enterprise market. Major problems can result from this type of mentality, and I see it quite often in my consulting practice. Companies that enter the SMB market from this perspective usually aren’t fully prepared to do what it takes to be successful, in what is a very different type of market than they may be familiar with. So where are the land mines in the SMB marketplace?

What’s Not Obvious in Marketing to SMBs

The first thing to consider is that customer needs are often quite different. A lot of this depends upon what technology and market segment you are in, and whether your product is aimed more at the “S” (small) segment, or the “M” (medium) segment of the SMB space. For example, if you are selling a single user productivity tool which is useful staff accountants, you may not see much difference. If on the other hand you are marketing a company wide, networked application of some complexity, the differences may be huge. Like everything in technology marketing–the devil’s in the details. Every situation needs to be evaluated closely, and treated differently on its individual merits. The most important thing is TO NOT ASSUME THAT THINGS ARE THE SAME BETWEEN SMBs AND ENTERPRISES IN YOUR CATEGORY. Do the work, evaluate the situation–don’t assume. Assumptions, without verification, are what get you burned in this transition. Below is a list of some of the major differences in the SMB market:

IT Departments are small and less of a factor–if they exist at all.–In Enterprises you may be dealing with persnickety CIOs that want thing just so. In SMBs, if there is a CIO at all, he will be looking for an off the shelf SOLUTION that will “just get the job done”. Or you may end up struggling to figure out how you can sell your complex solution, to a company that has NO IT DEPARTMENT AT ALL.

There is less money to spend–It’s harder to make money with big ticket hardware and software, let alone customization and expensive services. Your products better have value – and margin – right out of the box.

Ease-of-use is even more critical–There probably is no training department or other corporate staff, and people are busier overall. If they can’t figure out how to use it quickly, you’re going to have a hard time selling it.

There is much less time available to purchase products–Even the sales process may be compressed, in terms of how much time the prospect spends reviewing your marketing literature, or talking to your sales people. The actual TIME ELAPSED during the sales cycle could be EVEN LONGER due to lack of time available to the prospect, but the INTENSITY of the purchasing engagement is often much less.

How Do You Need To Structure Your Business Model Differently?

Lower prices– They just can’t, and won’t pay the same prices that you can get in the Enterprise space, in most cases. So you’d better come into this segment with a price and value proposition that makes sense to these price-sensitive customers.

Marketing vs. sales–The SMB market is more marketing intensive, with respect to marketing/sales ratios, than the Enterprise market. There are many more customers; the average sale amount is much lower, and much less face time available for direct sales. While in many respects Enterprises are the most demanding customers in the world, you’ve got to be a better marketer to succeed in the SMB space than you need to in the Enterprise world.

Low cost sales force– With much lower average sales amounts, and much less time available on the customer side, it is usually impractical to have a large, high-cost field sales force. Inside sales forces are the general rule in this market. If you have a product that demands customization and hands-on support, VARs are a good adjunct to consider. The more they are taking orders generated from marketing, and the less they are cold calling prospects, the better.

Better usability and reliability– You’ll need many more units being sold to get to the same level of Enterprise revenue, across a much larger customer base, with much less (if any) maintenance revenue to fund a large support staff. Your product better work when it’s installed and better be very easy to use over time. Unless you have a highly customizable solution and are using VARs as a channel, SaaS is a great platform for delivering software to this market.

Little or No IT support–The good news is that there is no prickly IT committee or staff that you have to “go through” to sell to the real users. The bad news is that if even the littlest thing goes wrong, there’s no one internally at the customer to pick up the slack–you’re going to hear about it directly from the user–over an over again.

Summary

The SMB market is actually a simplistic catch-all phrase for a large, heterogeneous group of markets. But it is a useful abstraction, as a starting point for understanding how to penetrate and thrive in B2B marketing to smaller companies. I hope this short introduction is useful–feel free to pitch in and post a comment adding to this topic.

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