MightyData

FileMaker and WordPress Consultants

  • Company
    • About
    • Contact
    • Team
    • Artists
  • Services
    • Consulting
    • Development
    • Our Process
    • Coaching
    • Training
  • Results
    • Customers
    • Success Stories
    • Testimonials
  • Blog

Poker Analogy Blog Re-hash

October 3, 2012 by David Weisiger 1 Comment

I will be the first to admit I struggled with my last blog post, using poker as an analogy with respect to the sales/prospecting  process. There were some outside factors that were in play there–procrastination, tons of new leads filling up the pipe, procrastination again. But there was something else that was going on there as well. Poker analogies don’t work with respect to sales!

I could not put my finger on it at the time I was writing it, but something wasn’t quite gelling with the whole story I was trying to tell. I wanted to talk about how the ability to read other poker players at a table is similar to the technique you need when talking with new potential customers. You know, being able to get the “real story” that the potential customer isn’t giving you.

The problem is when you use poker as an analogy for sales you set up a “zero-sum game mentality”. Here is a video from the VeraSage Institute that helped me with this realization. Read the comments below it. In other words, there is a winner and a loser. And in any successful sales transaction there should be two winners, the customer and you.

Ultimately when you play poker you are trying to knock out your opponents. Unless it is a cash game, you want them to keep buying back in. But with sales, you are hoping that the conversation between the two of you leads to a point where you are shaking hands and smiling ear-to-ear because you both got what you want. This would never happen in a poker game.

Another point I was trying to make is that sometimes you win and sometimes you lose. Using skills that I honed while playing poker seemed to be a useful metaphor for getting to the decision of whether we want to “play” with this customer (read qualify). And really that is what you need to figure out early on in the process.

So the analogy only works in the sense of whether or not you want to have the initial conversation. It is used in the sense of the introduction. Do they like your “game”? Do they think your “rules” are fair? In the long term of the sales cycle, poker does not make sense as an analogy.

Another way to look at it would be like this. Poker is an individual game. You are looking at increasing your chip stack while decreasing your opponents. That fact alone shows it is not a good comparison for sales. If you presented a proposal to a customer that said the cost is $20K and never said what they would get for it other than spending $20K, you would most likely not get the business. If you have not shown the customer the value of what they would receive, they will never buy it.

Sales is a team effort. You and the customer must work together in order to come up with a fair proposal that both parties agree on. Now maybe if there was “team poker” this analogy might work. Then again, probably not.

Filed Under: Sales Tagged With: Customer service, Sales process

Outstanding Support from BaseElements

April 22, 2011 by Kirk Bowman Leave a Comment

Recently, we were engaged by a customer to provide consulting and coaching to their team of three in-house FileMaker developers. As part of the initial review, we created a DDR of their database and tried to import it into BaseElements. Shortly after starting the import, BaseElements displayed an error message saying the file may be corrupt. The error dialog also had a link to a support article on the Goya web site.

Per the article, I validated the XML using a trial version of TextMate. The second error TextMate found sounded suspiciously like the layout error described in the BaseElements article. Since I could not quickly determine where the missing XML tag was, I opened a support case with Goya and uploaded the DDR for review.

The next day, Nick Orr at Goya responded. Over the next 48 hours, Nick and I determined the root cause was a tab control in the Footer part of a specific layout. Once this tab control was removed and the DDR recreated, BaseElements was able to import the DDR with no problem. We suspect for some reason FileMaker Pro Advanced was creating invalid XML in the DDR. Nick submitted this as a bug report to FileMaker Inc.

The reason for retelling this story is to say thank you to Nick and Goya for outstanding customer service. In my mind, looking at a problem DDR and helping to identify the issue is going above and beyond. Being able to process a DDR with BaseElements was critical to being able to help our customer. Nick showed what type of company he runs and I appreciate working with a vendor who “gets it”.

Thanks Nick!

Filed Under: Sales Tagged With: Base Elements, Customer service

Let’s get started on your project.

It will be more fun than you think.

Get in Touch

  • Company
  • Services
  • Results
  • Blog

Copyright © 2023 · Parallax Pro Theme on Genesis Framework · WordPress · Log in