Showing posts with label business. Show all posts
Showing posts with label business. Show all posts

Tuesday, October 8, 2013

Guess What? Your Customer Does Matter

So this weeks blog post comes with a recent experience.  I booked a trip on Booking.com and made sure to make every reservation refundable as I knew my trip was subject to change.  Sure enough, I ended up having to change one of my five reservations.

Upon visiting the site I was unable to cancel the reservation.  When I contacted them, the reply was that it was non-refundable, but they would see what they could do.

To make a long story short, after having to follow up several times over a month, and getting no real answer, I finally got the response that is summed up by "It is not our problem."

I have had to run my own customer service, managed customer service teams and know the damage that can be done by a customer that is not taken care of.  I had thousands of dollars in bookings on the site and that was treated with a "sorry for your frustration, good luck."

Here is where companies always seem to make a huge mistake.  Now if they were to get my trip refunded, let's say it costs them the entire $800 for the reservation.

Now, I don't know their fees, but what will it cost them when I never book on their site again, and I make sure everyone I know stays away from their site.

You NEED to take care of your customer.  There are times when you want to strangle the person on the other end of your emails.  Complaints can seem unreasonable, refunds hurt, but nothing can hurt your company more than bad public relations.  The moment you have people walking around talking about what a scam you are, and not to trust your brand, you are losing WAY more money than a few customer issues here and there.

Regardless of being motivated by profit, you need to look at the long term affects on your company.  Are you in this to see a big number this week, or this year?

This may be redundant to a lot of you.  I once heard the number used in the restaurant industry is for every one bad experience, 205 people hear about it.

Imagine that! and this was before social media and the power a voice has now.  All it takes is one person with enough frustration to want to spread the word and it can crush even a large brand.

hasan syed

Above is a tweet promoted by an individual that was not compensated for lost luggage.  He spent $1000 to promote this tweet and it got the attention of the world.  News stations, websites, bloggers, influencers all spoke about him around the world.

Do you think British Airways should have just handled his situation and been done with it?

The power of your customer is larger than it has ever been.  Everyone has a huge voice now and it is your job to make sure they do not use it against your brand, even if you may not feel they are always in the right.


Tuesday, October 1, 2013

Building a Brand versus Getting Direct Response

Marketing has become extremely easy to track.  Measuring your ROI from your marketing spend, especially online, is available to everyone.  I have seen this cause a shift in the way people market.  Most brands I speak with are looking for their CPA.  How much do they spend, and how many customers or how much revenue does that bring in?

The issue is, the long term goal of brand building is suffering more and more.  Here, I will outline the benefits and tactics of building a brand versus driving direct response.

Brand Building
Building a brand is the backbone of any long term, consumer facing business.  What is the lifestyle around your products?  Why do I want to give your company money? The most important questions consumers ask and the only way to answer is with a strong brand.
If you want to:
  • Build long-term customer engagement
  • Bring in evangelists
  • Create a long-lasting company
  • Increase long term revenue
  • Engage your customers on an emotional level
Then you need to focus on building a brand identity.

The issues with focusing on building a brand are:
  • Lower immediate ROI
  • Higher risk (with the results being more long-term, you are generally going to spend more money before seeing results)
  • Hard to track response

Direct Response Marketing
Direct Response is marketing done to make the the largest immediate ROI.  It is extremely tempting for companies to focus on these marketing channels because they can see the affect to their bottom line immediately.
If you want:
  • To increase revenue in the short-term
  • Show immediate growth
  • Closely gauge your financials and ROI
  • Lower your risk
then direct response is the way to go.

The issues are:
  • The long term benefits of direct response are much less
  • Customers are generally driven to purchase your product, but are less emotionally engaged, which means less likely to return or share
  • Does not create an identity for your brand, which hinders long term customer engagement
Conclusion
When deciding whether to build a brand or get direct response, make sure you understand the value of both.  Most companies can benefit from a mix, but if you are in it to create a long lasting product and company, do not sacrifice building your identity, for your immediate returns.

For any questions or comments, please feel free to email erik@hawkemedia.com

Tuesday, September 24, 2013

5 Ways to Build your Network

We all know the cliche "It's not what you know, it's who you know," but how do you get to know those people?  Here are my 5 tips to building a great network.

1. Be great at explaining your value
A lot of networking is done through people talking about you and introducing you.  The best way to get this done is to make it really easy for someone else to communicate who you are and what you do.

If you do a good job of concisely explaining your talent or career, then others feel confident speaking about you, and are also able to identify situations where you should be introduced.

People love to connect each other.  Just make it easy for them to do so.

2. DON'T go to networking events
Networking events are generally places for people with no connections to meet other people with no connections.  Mark Cuban does not go to "networking events."

Parties, benefits, dinners etc. are fine, but anything that calls itself a networking event is generally not a good place to build a solid network.

3. Offer something first
Once you initially make a connection with someone, offer them something.  Most good connections are used to hearing what they can do for other people, but offer them something in return.

If you are good at marketing, maybe shoot them a decent idea about marketing their company.  If you are good at building technology, give them something technological that could really help them.

Once someone sees that you have smart things to say, they are going to want more.

4. Keep in touch
Do not be afraid to stay in touch.  Check in through email regularly, follow up about setting that face to face, people don't mind hearing from you.  Be confident that you have something to offer and stay in contact.  Most well connected people are busy, and it is usually helpful if you follow up.  Don't take no response as a sign of a lack of interest, they are probably just swamped.

5. Don't be afraid to ask
Tell the people around you what you need and what you are looking for.  People seem to always be afraid of looking like they are "using" someone or that they shouldn't ask for help.  When was the last time someone asked if you could introduce them to a friend and you were bothered by it?

Always remember, people inherently love to help.  Do not be afraid to tell people around you what help you need.

If you want to discuss this further please feel free to email me at erik@hawkemedia.com or visit HawkeMedia.com

Tuesday, September 17, 2013

4 Perils of Hiring Developers

Hiring a developer in house, or outsourced can be one of the most difficult tasks when getting into the tech industry.  As someone that has no tech background, I have made my share of mistakes that have cost me dearly.  Here are 4 big things to look out for when hiring a developer.

Not Skilled Enough
Many developers seem to think they can do everything and anything.  I have rarely heard a developer tell me that they don’t think they can accomplish a task.  Given unlimited time, they may be right, but if you have hopes of seeing your project complete any time soon then this can be a problem.

Make sure when hiring a programmer, that they have done a similar project.  You can even take it a step further and ask for a recommendation from that former client and see if they dealt with any problems.

Not Fast Enough
A CTO for one of my past companies said it best “when managing developers, your job is to have a number that sits above each developers head.  That number is a multiple.  If they say the project will take a certain amount of time, you need to multiply it by the number above their head.”

When working with any developer, understand that their time frame is rarely accurate.  It is hard to know what that multiplier is, but assume there is one and always assume the project will take significantly longer than you have been told and allow for that when planning your time line.

Business Savvy
This is a developer, not usually a businessperson.  Never assume that a developer understands the logic of what you are trying to do.  You need to hammer out every little detail of the project.  Get as basic as mentioning that “Home Button” actually links to your “Home Page.”  Do not leave anything left to assumption, that is where you don’t get what you want and your bill starts to increase.

Transparency
I have heard MANY horror stories about programmers when there wasn’t transparency.  Recently, I had a company approach me who had a developer “working” for 2 months and then quit.  Turns out they had done nothing and now their hopeful launch date was a month out with no development work done.


To avoid this situation, when you hire a developer, take the opportunity to learn a little and ask for them to use project management software and monitor what they are doing along the way.  It may take a little time, but you will save a TON of potential headache later.