Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

A Story from My Company

Peter K1PGV
Peter K1PGV Member ✭✭✭
edited June 2020 in New Ideas

Since the community has apparently become somewhat of a replacement for WordPress, I’d like to add my own, entirely irrelevant, blog entry.

Back in 1983, when I started my current software company (my second), we focused on doing what much of the community viewed as impossible.  About five years along, we were working on a cutting-edge piece of enabling software (software that other companies use to build their products).  Now, to be clear: This project we were doing wasn’t the Manhattan Project or landing a man on the moon.  But it was still pretty innovative, very difficult, and terribly complicated.

The project was progressing, but it was way behind.  We delivered features late, and what we did deliver often was neither particular well documented nor always correct.

We had a particular client whose staff was constantly complaining and sending rude bug reports to our team.  Their management sent our management rude emails.  The VP at this client had been trying to call me for two weeks, and I had succeeded in ducking his calls.  Finally, later on a Thursday afternoon, I was in my office and I made the mistake of answering my phone.  It was the angry VP.  He proceeded to read me the riot act: Dates, bugs, how many millions of dollars of sales were on the line for his company, how we gave dates, promised functionality, etc.  He was yelling.  I got angry and started yelling back.  Instead of answering any of his questions, I told him “From this moment forward, if you or anyone at your company sends us one more, single, tiny, complaint… I’m going to walk in to my Finance Manager’s office, cut you a check for whatever you’ve paid us, and you can write this software yourself.”   That was the gist of what I said.  In actuality, I used the f-word several times. They had paid us in excess of $100K, which at the time was a significant amount of money for us.

In truth, this was one of my proudest moments as an entrepreneur. The client was out of line and getting worse.  I knew that the abuse had to stop, for my sanity and for the sanity of my dev team.  And I knew if I worked for any company other than one I founded, I would have been fired on the spot for talking to a client this way.

But… You know what?  The client’s complaining stopped.  Immediately.  He even stopped yelling on the phone.  He apologized, in fact.  Because he knew his company really wanted our software, there was no way they could write it themselves, and if we "fired them" as a client they'd be out of luck.

Know what else?  That company has been one of our best and most loyal clients from that day to this.  Just last week, almost 20 years later, we signed a major product licensing agreement with them.

And that concludes today’s blog post.

I swear this is a 100% true story.  I will fully understand if the mods lock or delete this post for being off topic.


  • Stu Phillips - K6TU
    Stu Phillips - K6TU Member ✭✭
    edited May 2020
    You are not OT at all.

    You rightly called the guy out and you were right to tell him he was about to get fired as a customer. 

    I have a lot of experiences with companies and with customer support.  Sometimes the customer passes the point of acceptable behavior and they have to be told so.

    About a year ago, there was one particularly angry individual on this community who wouldn't quit griping.  He didn't say anything new, he just kept ranting and ranting - railing abuse like so many continue to do over 1.4.

    I emailed him privately and offered to buy his radio from him at what he had paid for it.

    He blustered and the net of it was he shut up and to the best of my knowledge, still has his radio.

    Your action was 100% on target.

    Stu K6TU
  • WX7Y
    WX7Y Member ✭✭✭✭
    edited June 2020
    The complaining is what killed the open BETA back in the day when PowerSDR was being perfected. 
    Thanks for you story and the happy ending.

  • Gerald-K5SDR
    Gerald-K5SDR FlexRadio Employee ✭✭
    edited December 2016
    Bret, you are correct.
  • Gerald-K5SDR
    Gerald-K5SDR FlexRadio Employee ✭✭
    edited December 2016
    Howard, from your story you know exactly what it is like on our end.  Thank you, thank you.
  • Steve W6SDM
    Steve W6SDM Member ✭✭✭
    edited June 2020
    Deadline:  A commitment made for the sole purpose of giving someone something to complain about when you miss it.
  • Peter K1PGV
    Peter K1PGV Member ✭✭✭
    edited December 2016
    Great story, Howard.  Right on the money.
  • Ken - NM9P
    Ken - NM9P Member ✭✭✭
    edited December 2016
    The difference is that most of the time the "deadlines" were always stated, or at least understood by most of us as "we HOPE to release it in January,  "We PLAN to release it in October."  "Our GOAL is for a release in the third Quarter of 2014." etc.  I never interpreted ANY of these as a hard deadline (like tax day) or as a firm promise, only the fluid time schedules of a company pushing innovative software development.

    In fact, this increasing complexity was probably one major thing behind the move away from annual software release fees and shifting to Major Upgrade Version fees.  I am sure that many people, even those who were so hacked off at that paradigm shift, are glad that they haven't spent all of their year's fee waiting for the company to perfect what promises to be a major shift in software capabilities.  And we will get another one in v.1.5 for FREE before the shift to 2.0 brings us our first paid upgrade.  I would have already been halfway through my second year of paid annual updates on the old system!

    I have no gripes here!

    Ken - NM9P
  • Bob K8RC
    Bob K8RC Member ✭✭✭
    edited March 2015
    Huzzah! Thanks for speaking up! It is my own experience that a good number of our fellow amateurs have no real appreciation for the amount of time and effort required to produce software. I wrote one of the first software logging packages for Windows (3.0!) in the early 90s. I actually was scolded by one ham for charging $30 when, as he so helpfully pointed out, you could buy an entire box of 10 floppy disks for less than $10. To the Flex Folks, thanks for what you've already done to give me a cutting-edge radio. Bob, K8RC

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.