hospitality technology made simple by kevin sturm Consulting

a new title for what i am

I just learned what I am...

While reading Escape From Cubicle Nation I found out about Anywired and read the post Become a Lifestyle Entrepreneur: Complete Guide and 40+ Resources.

I'm a Lifestyle Entrepreneur! What does that mean you ask? You really should read the post, but here is a great description from Skellie over at Anywired.

"If you are — or would like to be — an entrepreneur, yet you’d be happy to earn enough to live the life you want rather than becoming filthy rich, lifestyle entrepreneurship might be a good fit for you.

Lifestyle entrepreneurs will generally base their ventures around time minimalism, or something they love, even if there are more profitable (but more time-consuming, or less interesting) options available.

The goal of a lifestyle entrepreneur is not to amass a huge fortune, but instead, to achieve certain definable goals and, beyond that point,
to ensure business does not interfere too much with the enjoyment of those goals."

Now don't get my wrong, I think it would be cool to be really rich. But not at the expense of the relationships with my wife, kids, or current freedom. I spent 9 years climbing the corporate ladder and had a good position with a good salary. The next step in my plan was a VP position which would lead to a C-level position. But ultimately what I found is the stress of those positions, the time requirement, and the sacrifices I was going to make just weren't worth it.

I quit my job and started my own consulting firm to create freedom in my life. Here is my current daily schedule - which I adjust daily as I need to fit into my lifestyle.

7:15 am - Wake up to alarm clock of "DAAAAADAAAA IT'S LIIIIGHT TIIIIIME!"
7:45 am - Get breakfast for the alarm clock and take a shower
8:15 am - Make coffee and lunch for Bubba
8:30 am - Catch up on my favorite blogs and/or take Bubba to preschool
9:15 am - Blog or grab breakfast or read news
10:00 am - Work on client projects (yes I start "work" about 10:00 am)
4:00 pm - Stop work to play with my alarm clock
4:05 pm - Play with Bubba, Chrystal, and Mianna for the rest of the day.

I say this not to brag or gloat but to say it's possible. We are not getting rich and sometimes money issues are stressful, but we (my family and I) live a good life and love it. We have more freedom (though not necessarily financial) than we have ever had. Join what Tim Ferris calls the NR and break the chain!

Digg Technorati Delicious StumbleUpon Reddit BlinkList Furl Mixx Facebook Google Bookmark Yahoo

mail call...what's the scoop on SaaS solutions?

I received an interesting email a while back from Carson Mehl at Lumiere Hotels.

"I am curious to know if you have heard of any robust hotel software being developed that is web-based. Our company has started using a number of web-based software solutions such as Google Docs and Basecamp by 37signals and they have been a huge asset as far as ease-of-use, collaborative ability, and no-need for extensive/expensive hardware. The great thing about web-based software is that it all operates inside the browser so it can be easily accessible from a number of devices."


Regrettably I was not able to point to any truly web-based solutions that I felt would meet the needs of a boutique hotel group. There are a few out there but none that I have extensive experience with or have been impressed with.

What Carson was really asking is why hasn't a hospitality technology vendor come up with some true SaaS applications that fulfills the requirements for a boutique hotel or resort location? For those that are not familiar with SaaS it means Software as a Service. Wikipedia defines it as "...a software application delivery model where a software vendor develops a web-native software application and hosts and operates (either independently or through a third-party) the application for use by its customers over the Internet. Customers do not pay for owning the software itself but rather for using it. They use it through an API accessible over the Web and often written using Web Services or REST."

In our email conversation Carson was good enough to expand to what hoteliers are looking for...

"...The newest evolution of internet browsers and runtimes like Adobe AIR are really opening up the possibilities for rich internet applications. Applications like Google docs, basecamp, ZOHO, buzzword (my fav), even Facebook that are stored in the cloud and accessible from anywhere, offer such an advantage. The ease of collaboration they provide is alone and tremendous improvement on traditional software not to mention the accessibility factor, ease-of-use, elegant design, and simple hardware requirements. I do not have super-deep ranging experience with hotel software, but what I have used is far short of what is possible today.

From an hotelier’s point of view, I see a demand for a well designed software platform that is easy to use and is far reaching ie: pos, pms, booking, web-booking, reporting, etc. What is currently available in this regard is very expensive and complicated from both a hardware and software standpoint. The existing platforms work well for companies with deep pockets, IT experts and central reservation departments...


I guess the dream software would provide seamless connection between web reservations, pms, and the gds. It would allow an administrator to provide different levels of access to employees. It would automatically create and update guest profiles. It would show activity feeds for a property (similar to a facebook newsfeed, but showing reservations made on the web, pms, or gds, and more). It would be dead simple to use. It would look elegant. Training would be obvious and intuitive. It would be a subscription based service or maybe annually licensed. The system would be complete so there wouldn’t be any interfacing problems between disparate types of software. All the data is indexed and searchable. Reports are automatically generated and distributed. Data is backed up securely. The software works in multiple languages. Software updates are seamless, because it is web based. Housekeeping could carry around a tablet pc or iPod touch and update their room list. Guests could check out from their tv or laptop. The list goes on and on. It may seem like a pipe dream, but I think it is a possibility especially as we are reaching the age of ubiquitous internet connectivity.


From a software company stand point I think there is demand for such a service. It might be a long long time before a large hotel company would make the switch but there are so many independent and small hotels for which this service would be a blessing. In addition, if the service was successful the access to data would be invaluable."


I thought the question was a good one and the desires well stated. So the question stands to why are there not more SaaS applications for hotel/resorts?

In my experience the main reason has been a data access issue. For pure web based applications the data is held (and often owned) by the vendor. Data security standards and PCI regulations make it difficult for vendors to effectively and affordably deliver on the needs of a hotel/resort. PMS, POS, and GDS solutions are generally considered mission critical to the business. If you don't have immediate access to the data then you cannot run your business successfully which often means inconveniencing the guest. And unless a company like Google with an almost infinite budget for infrastructure redundancy and fail-over brings a solution to the table the costs of effectively delivering a solution like this appears to be too high for a start-up looking at what is really a limited market (unless some of the larger brands like Hyatt, Hilton, and Marriott joined in).

Ultimately I hope I'm wrong because I believe we need this. A corollary could be made to what people thought about CRM solutions until Salesforce.com rocketed to uber-status of success and took over that space as the darling of the market.

If you know of a SaaS POS, PMS, GDS or other hospitality technology solution leave a comment as I'd be interested to find out more about them. Or if you have other thoughts on this topic post a comment and share your wisdom.

Digg Technorati Delicious StumbleUpon Reddit BlinkList Furl Mixx Facebook Google Bookmark Yahoo

confidence and humility are not mutually exclusive

In the last week of my full-time employment a co-worker (and former consultant) told me she thought I would find consulting harder than I expected. I didn't know her very well but I knew her well enough to know she was referring to the selling side of consulting, and I could tell by the way she said it she didn't think I had the "selling side" in me.

I told her I agreed that most consultants struggle with the selling side of the job, mainly because you are selling "you". What you personally bring to the table is all there is to sell, and part of what you bring to the table is confidence. But many consultants struggle with the concept that confidence and humility are not mutually exclusive. The opposite of humility is not confidence but rather cockiness. Cocky consultants are annoying, irritating, and often difficult to do business with.

When I talk with any customer I know I bring confidence to the discussion. Confidence that I know what needs to be done or that I don't.

Cocky consultants always know the answer, regardless if they really do. Confident consultants are humble enough to know when they don't know the answer, but instill confidence they can find it.

She was right that I'm not naturally a sales person. I have friends who are and they could convince you to buy the dirt off your own floor. As a consultant that is not the type of sales person you want to be. You want to be an evangelist.

If you are selling on the basis that you offer a service you're selling on cockiness: "Buy me because I'm here." You should be selling on the basis of a business problem that you personally can help solve: "Buy me because you have this problem and I have experience and knowledge to offer multiple solutions on solving that problem."

Seth Godin had a great post today on Self Promotion that spurred this thought. Thanks Seth!

Digg Technorati Delicious StumbleUpon Reddit BlinkList Furl Mixx Facebook Google Bookmark Yahoo

the most important decision as a consultant

The number of decisions you have to make when starting your own consulting business are numerous. Decisions like choosing your niche, how much you charge, where you will spend money are all important. But one of the lesser discussed but possibly most important decisions is what business will you NOT take.

I have found this to be the most difficult decision because knowing when the next job will be is usually unknown. You are always in need of the money (lets be honest here), but every opportunity that comes your way has the potential to grow or limit your business (read income).

  • will the contract increase your specific skill or expertise that makes you valuable?
  • will the contract lead to on-going future business with a client?
  • how sure are you that the project will end successfully?
  • how likely is it that the potential client will provide you with a good reference?
  • is the potential client the type that would recommend your services without request?
These are all important questions to ask when deciding what kind of projects you do or do NOT take. But I'm going to focus on one question where many consultants make the wrong decision.

Will the client pay you what you are asking?

This is an important question because it brings up two equally important questions. First, how much are you worth? And second, what type of personal life do you want?

The temptation to take a contract at a reduced pay is great, especially when the pipeline is small. But one of the most important decisions you will make is sticking to your guns and turning business away. Consultants are generally willing to take these jobs because they come with a promise of lots of work or because of nervousness that nothing else will come along.

But if you take a contract for either of these two reasons you are both decreasing your perceived value to current and future clients and sacrificing your lifestyle. You should be confident that you are worth your rate and your current and potential clients must see that. Taking a contract for a lower fee says that you believe you are not worth your stated rate. And if you do not believe you are worth your fee then you should not be charging that fee.

The second reason you should not accept a reduced fee is based on simple math. Let's say your normal fee is $100 per hour (just to pick a round number). If you take a 20% fee reduction at $80 per hour then you have to work more hours and harder to make up the difference.

Most likely you have a revenue goal for your company (if you don't it's time to get one). The more projects you take at a decreased rate the more you have to work to achieve that rate.

If you are still not convinced then look at it this way. Let's say your goal is to bill 30 hours per week at $100 per hour with four weeks of vacation. That means there are 48 billable weeks in the year. This is pretty aggressive goal if you are just starting out.

48 weeks x 30 hours x $100 = $144,000

NOTE: $144,000 may look like a lot (or may not), but when you factor in taxes and business expenses your take home quickly begins to fall.

If you take a 12 week contract at your 20% fee reduction there are only 36 weeks left in your "goal year".

12 week x 30 hours x $80 = $28,800
36 weeks x 30 hours x $100 = $108,000

Now your total revenue is $136,800. In order to make up the difference of $7200 to meet your goal you have to work 72 hours at your $100 rate. That equates to 2.5 weeks of work which leaves you with 1.5 weeks of vacation time.

But the better scenario is that you would only need to work 45.5 weeks at your normal rate to achieve the $136,800 revenue number. This means that you either have 2.5 more weeks of vacation time (imagine a job with 6.5 weeks of vacation), 2.5 more weeks to market and build the business, 2.5 weeks to blog and share your knowledge, or 2.5 weeks to try and find a small contract at your $100 per hour rate.

Be worth what you say you are worth. It will be better for you in the long run and you'll do business with the type of customers you want.

Digg Technorati Delicious StumbleUpon Reddit BlinkList Furl Mixx Facebook Google Bookmark Yahoo

best-of-breed or one-stop-shop...what's best for me

For many this debate is a philosophical versus empirical one, but it is worth a discussion I think. It is almost impossible to set aside the philosophical side of the debate (i.e. those that hate strongly dislike big business), but I'm going to do my best based on my experiential side of the debate. In starting this post off lets take a moment and clarify what we are talking about.

best-of-breed

"Best-of-breed" vendors generally provide one or two technology solutions. They are 100% focused on these products and are thus considered to have more expertise in the needs of their customer (a debatable concept). Generally they are also considered to be more agile because of this focus (or so they say), allowing them to respond to development requests in a shorter time frame or at least with a more predictable software release schedule.

one-stop-shop (aka integrated systems)
(Pretty self explanatory I think) The Wal-Mart of technology vendors. They can fulfill most of your major technology needs and some of your minor ones as well (or so they claim). Generally they are very large organizations that offer products to a wide range of vertical markets. For this reason they are considered to have less knowledge of your specific operation (a debatable concept). Their release schedules tend to be further apart, but they also tend to perform custom work more willingly (possibly because of a larger resource pool) (also a debatable concept).Now that we are all on the same page lets talk about how to sort through the question, "What's best for me?" First, for the purposes of your time and my own sanity I'm not going to attempt to categorize all the vendors for every technology solution. It's almost impossible given the new companies that pop up semi-regularly and more importantly with the disappearing act by many of the formerly named best-of-breeds recently gobbled up by the one-stop-shops. And that quickly then brings me to the point...best-of-breed or one-stop-shop labels are a useless and very stupid business requirement when selecting your technology solution. It might have been a semi-meaningful requirement five years ago (of even two years ago), but not anymore.

Now, I'd like to just end here and have you believe me because I say so...but the probability is some of you reading this are staunch believers that best-of-breed or one-stop-shop is an important requirement when selecting a technology vendor. The rest of this post is dedicated to you. If you agree with me I'd love you to post a comment on what experience led you to the same conclusion. Below are some of points based on my experience, and why they are pointless when made as general statements.

ease of integration
This is one of the biggest points in the debate, and is often touted by the one-stop-shop as a major reason to chose them. But before you buy look closer, talk to existing customers, and make sure that this is really true. As with anything in technology your plug-and-play solution may leave you hanging. At face value it seems logical.


A single company can get their products to interface and integrate easier/better than different companies.

But changes in technology, the ever shifting product road map, and the acquisition engine proves in reality they most likely are not so integrated.

Most one-stop-shops did not start development of their products at the same time, which can mean the technology platform between the solutions is different (sometimes drastically). This can lead to some interface challenges that are often only overcome with limitations (and you end up with multiple technology platforms). The number of products gained through acquisition and the time frame of those acquisitions is also a good identifier for how seamlessly integrated a one-stop-shop is. My experience has led to the conclusion that the integration capabilities post acquisition is about the same as when they were different companies. Existing customers have lived with the limitations before the acquisition for years, so it is easy for a vendor to rationalize not making it a priority to enhance integration.

The willingness of one-stop-shops to work with other vendors is also a point to consider here. Where generally best-of-breed vendors thrive off partnerships with other vendors, the one-stop-shop may create integration road blocks. After all, it is in their best interest for you to purchase all of their products.

Now in fairness to the one-stop-shop I suppose I also need to point out that best-of-breed vendors also make this claim by touting their agility to enhance the product quickly. In some cases this is probably true. But do not be easily mislead. As a customer you want to be wary of this promise, because if it is being made to you it is also being made to someone else. You want a vendor that has a well established software development life cycle (SDLC) so they already (or at least should) have the next two to three versions of the product planned out. First, this means that new development probably cannot make it into the next scheduled version. Second, it means that your requested enhancement can easily be trumped by promises to the next customer. The temptation for best-of-breeds to "follow the money" is often too tempting and promises become easy to break.

Rather than basing your decision on claims to ease of integration do your research to document your requirements with order of priority. Select a technology solution based on your clearly defined and documented integration requirements versus claims to ease of integration.

small size = better relationship
I'm going to pick on best-of-breed vendors here. One of the claims made by best-of-breed vendors is their smaller size lends to a better vendor-client relationship. They claim to support their product(s) better and establish better relationships with their customers because of their size. Who made the rule that to be nice to work with you have to be small? In my experience a good vendor relationship is grounded in the type of people versus the size of the company.

As a side note it is too easy when choosing a technology solution to let your sales person do all the selling. And that seems logical...but your sales person is not who you will be talking to on a daily basis. You should be meeting with the group of people you will be working with regularly. If you will be assigned an account manager then meet that person. You should also speak with installation, support, and the person that handles billing disputes. Interview them because how they respond will give you a very good idea of what it will be like to be a customer. This group will often not have the skill or desire to "sell you", so they will act just how they act every day.

Nice dinners and golf outings are great, but I bet you would give that up for a support team that is knowledgeable on the product and a finance team that is pleasant to work with. Select a vendor based on their reputation in the industry and the people that you meet, not on the assumption because they are smaller they will be better to work with.

single support entity (aka one person to yell at)
The "one person to yell at" claim is generally made by one-stop-shops and it has some validity. It can be very useful to have a single point of contact for resolving problems with your technology solutions. But this is only a reasonable point if the vendor is responsive and helpful when you yell. If you already read the comments under ease of integration and small size - better relationship you should foresee the coming point.

Having multiple vendors that are very helpful and nice to do business with will always be better than a single vendor that is difficult to do business with. Base your technology decision on who you believe will offer the better support not based on the number of 800 numbers you have to tape by the phone.

in your back yard
This is one of those funny requirements that venues seem to think is a great benefit when choosing a technology vendor, and that technology vendors tout as a major benefit to the venue.

If the vendor's corporate office is close they will be more helpful and technical support staff will be available to swing by your property on a regular basis!

Unfortunately this is usually not accurate whether your vendor is a best-of-breed or one-stop-shop. If you yell loud enough and long enough they will send someone, but that is true if you are around the corner or across the country.

The vendor is not staffed to be at your beacon call and you will often get the freest resource (read least experienced) when you do need someone. If there is a big enough problem they will send someone regardless of where you are. In my experience your vendor's proximity to your physical location has very little to do with the quality of support you will receive.

Additionally, as a venue be wary of the in my backyard vendor. You have expectations but so will your vendor. You're site will become a frequent stop for sales calls, sales meetings, prospective customers, prospective partners, and bleeding edge technology solutions.

In summary if you choose to do business with a technology vendor because they refer to themselves as best-of-breed or one-stop-shop you will stand to be disappointed at some point in the future. It is naive to assume that your best-of-breed company is not looking to expand their product suite through "build it' or "buy it" plans. Even more likely your best-of-breed company is continuously being courted by one-stop-shops and will eventually marry for money (a poor relationship foundation by the way...in life and business). But for many that is goal. Build a company so that it is attractive enough to a potential suitor to sell and retire in the Caymans? Can you really blame the owner(s) for doing what almost every entrepreneur dreams of doing? I think not, so stop treating your vendors as if they were different than any other company with a different goal than your company. And for the one-stop-shop vendor the reality is they are generally not quite as seamlessly integrated as they proclaim.

The bottom line is hospitality venues did not coin the terms best-of-breed or one-stop-shop. They are terms creating by the vendor's marketing departments and ultimately should have little bearing on your technology decision.

Comment if you agree or disagree, I would love to hear from you. And as always, if you'd like to find out more about kevin sturm Consulting please visit my website or email me.

Pictures courtesy of DWQ, Crawfishpie, Dzwjedziak, Extra Medium, katiebate

Digg Technorati Delicious StumbleUpon Reddit BlinkList Furl Mixx Facebook Google Bookmark Yahoo