Author Archives: thedoctor

You Admit You Might Be a Dumb Company. How do you avoid the fork in the road that leads to the Graveyard? Part 1

Good for you! Admitting you might be a dumb company is the most important thing to do on the yellow brick road to enlightenment.

So what do you do next? In short you:

  1. start by admitting to every mistake you are making and do something about it,
  2. look for opportunities to improve that are logical next steps, and
  3. never, ever forget the timeless basics.

Today, we’ll start with describing what you do when you identify, and admit to, one of the first five mistakes we chronicled in our re-introduction to our “dumb company” series and want to do something better. Next week, we’ll tackle the remainder of the mistakes before we move on to our eight-part series (each of which is worth much more than a piece of eight) on avoiding the graveyard if you are a dead company walking. After that, we’ll provide even more advice if you just want to be a smart company in two two-part series! In other words, SI has a lot of great helpful content lined up for you if you are a vendor that wants to successfully sail the choppy seas ahead (and not end up as another wreck on the ocean floor).

1) No More Perks

Unless you’re going crazy on perks, just leave them alone.

If a few are a bit crazy, reign them in to reasonable levels.

If they still eat up too much of your budget, find something else to cut. Start with the deadweight (and begin your search in the [micro] management suite). A useless or salary or two will go a long way to maintaining morale (and if you cut deadweight, morale will even lift).

2) No More Tech/SaaS

First, do a process time audit and figure out where your people are spending too much time on tasks that can be semi-automated to a significant extent.

Then, identify the appropriate solution to the problem and a set of potential SaaS tools to fill that solution affordably.

Then, Get SaaSy and do a SaaS audit, find the 33%+ overspend, cut it, and use that savings to get the SaaS your organization needs to be more productive and receive a return of at least $3 for every $1 spend on SaaS.

Finally, if your cloud costs are significant, Be Cloud Aware and do a cloud audit, tracking down what applications, or parts of your application, are chewing up the most CPU time. Then reign that in. Ongoing cloud costs add up faster than you realize!

3) NPD Can Wait (Sell What We Have)

Maybe heaven can wait, but hell waits for no man, and neither do the competition you don’t yet know about. No matter how good, or how bad, times are, your product must ALWAYS be improving. The minute you stop, the sales will stop as the customers will peg you as a dead company walking if you are not actively developing your product.

Segment all features into must, should and nice to have from a target customer perspective and make sure you are constantly working on the “must have” features, getting a decent number of the “should have” features that aren’t too time consuming to add into the plan, and prioritize any “nice to haves” that can swing a deal in your favour. If you have to slow down a bit because you can’t expand the team, that’s fine, just as long as you don’t stop.

Remember to keep dependencies in mind and structure development so that dependencies are always done first, to minimize release cycles.

4) No More Travel

Before you approve travel,

  1. first do an audit of all travel reasons the company has seen. Then,
  2. identify the direct and indirect ROI on past travel. Finally,
    • determine where in a marketing cycle travel actually results in actual, qualified leads
    • determine where in a sales cycle travel actually results in a selection or sale
    • determine which conferences/workshops/training events helped product management or developers

Then deny all travel that does not fall into one of those buckets.

Next, for travel that does, look at the cost vs. the projected return and how it compares to the most successful travel of the past. If a conference only results in 10 real leads, and it will cost 100K, but there’s another conference likely to result in 5 real leads that will only cost 25K, deny the first request and approve the second.

If $$$’s are tight, then restrict all travel to

  • small, focussed, cost-effective events that will generate actual leads or customer insights
  • on-sites likely to close the deal
  • low cost workshops where your product managers / developers will definitely improve their skills

5) Cut 10% Across the Board

Do a full budget review (keeping the dumb mistakes in mind) and cut the unnecessary expenses. They are MUCH higher than you think (because, when times are good, or you raise too much money, you don’t watch the small stuff and your unnecessary tail spend is just as bad as your clients).

Then, do a performance analysis (and blind peer review) of the teams across the department, especially the management teams, and cut the real deadweight.

Chances are, done right, there’s more than 10% that can be safely cut with no impact (whereas 10% across the board will damage morale to the point that the best talent might leave at a time they are the most critical).

Be sure to keep reading SI as Part 2 posts next week!

PROCUREMENT ARE NOT GUINEA PIGS!

Now, a lot of things grind my gears, but if you really want the doctor to fly into a rage, suggest, as this article did, that Procurement, the most critical function in the modern organization, and the one experiencing the greatest dearth of talent, should be used as a guinea pigs … and especially so for bullcr@p AI!

This is the kind of idiocy that, in olden times, would not only get you fired on the spot for suggesting it, but blacklisted by your employer and any other executive who hung out in the same private clubs. No one wants a reckless fool that could tank their business, earnings, and lifestyle … and that’s the last thing a rich, lazy, private club (and private jet) executive wants to happen. (And the last thing your team wants to happen as you put the blame on them and expect them to clean up a mess that the systems you imposed created.)

If you’re going to experiment with AI, especially if you’re just doing it so you won’t miss the bandwagon as it races by (because, as we’ve said before, it has no brakes and no steering if its the Gen-AI bandwagon), pick a function and a supporting task that is much (much) less critical where utter, abysmal failure won’t have any significant business impact … not a function where one mistake in even the most mundane of activities can halt your multi-million dollar production line for weeks (or months) and possibly bankrupt you!

Zombie Companies Exist Too!

Last week the one and only Dr. Tony Bridger, one of the world’s leading spend gurus, said that the correct term for “walking dead companies” is Zombie companies, and I had to correct him.

Historically, a person was walking dead when they had received a mortal wound, infection, poison, or radiation dose and it was just a matter of time before they died. But they weren’t dead yet, and there was always a chance (albeit not a good one) they could survive if they got medical treatment fast enough to stem the bleeding and repair enough of the damage, fight the infection with a miracle drug, get injected with the anti-venom, or get quickly decontaminated and receive enough red blood cell transfusions to have a fighting chance (although, admittedly, not a very good one).

Similarly, a walking dead company is a company that is on the path to insolvency (or acquisition on someone else’s terms if it’s lucky) because of the situation it is in, which is usually because of critical mistakes that were made in the past and still being made today. If such a company suddenly stopped making all identifiable mistakes, found a way to stem the bleeding (of cash), and mitigate some of those past mistakes, there’s still a chance it could survive. It might not be the company it wanted to be, but if it made it to break even, maybe it could find a new direction and a new chance to be great down the road.

In comparison, a zombie company is one that is already dead, and has been dead for years, but refuses to die, usually because of the stubbornness of one or two founders/leaders who believe if they make it just one more year, even though they refuse to do anything different from what they have been doing for years, the company will magically take off. They maintain a heretical, fervent belief that it just needs “more time”, just like the Gen-AI zealots believe it just needs “more cores”, and the American voters think they have a real choice (when, in a two party system, they don’t … or at least won’t until the Super PACs, which give money to both parties to ensure that whomever wins will support their core agenda, are made illegal and eliminated).

You can tell these companies because, in our space,

  • they have been around more than five years, and usually more than seven (before COVID and since the second last M&A frenzy in the late teens when money flowed freely)
  • they have less than 10 (FT) employees if they are primarily a point/module-based solution, and less than 20 (FT) employees
  • their customer count hasn’t increased significantly (i.e. has not increased by more than 10% to 20%) in at least 3 years, i.e. if they’ve managed to sign new customers, they’ve usually lost almost as many
  • they don’t do any marketing whatsoever beyond email campaigns and more often than not the copyright on their website is a year (or more) out of date
  • none of the major analyst firms or analysts have given them much attention in years

And, as any consultant, analyst, or partner who they attempted to engage or who tried to help them can tell you, the situation the company is in is unrecoverable or a non-starter.

(So while the doctor will be giving you

  • a two-part series on what you can do to avoid the graveyard if you admit to some of the dumb company mistakes and
  • an eight-part series on what you can do to avoid the graveyard if you are willing to admit you are making some of the dead company walking mistakes

he will not be doing any follow ups to this article.)

Why are they zombie companies? There are a lot of reasons the doctor can point to, and he’ll include a few examples in this article, but it all boils down to this:

  1. most of these companies are owned by one to three founders/partners who control the company and
  2. the refuse to admit that they need help, or if they admit they need help, they refuse to either do what is necessary, and often won’t even admit they need to do something different to get help

And since I know THE REVELATOR loves details, some examples include, but are definitely not limited to:

  • their messaging will be awful and their marketing strategy non-existent, and even if multiple people outright tell them that, including analysts and (potential) partners who want to help them, the founder/partner will either insist it’s just fine or that they need to keep it in house
  • they couldn’t sell a space heater to a freezing American stuck in Alaska, but won’t hire a full time sales person on salary because “a great salesperson should work only on commission and want to sell our product because it’s so great”, even though a sales person would need to sell a deal a month to make a decent salary on the commission on a 50K modular sale, and since it takes about a year to build a solid pipeline, that sales person is apparently supposed to starve for the first year (with zero stake in the company) … because of future potential
  • they admit they need help tweaking the product to be more appealing to a wider audience, but won’t pay for consulting because the budget is too tight — unless the consultant works on “referrals” … but that’s presales, not product, and not what the consultant they need is going to be any good at, so they don’t get any help … ever!
  • etc.

the doctor could go on, but he won’t, because there’s no point. At the end of the day, these zombie companies desperately need help, and even if they admit it in some capacity, they won’t get it because they don’t want “IP” to leave their “4 walls” (even though they have very little they need to protect as the core of most solutions that implement a core function is about 80% the same), or, usually don’t want to pay for it (because that would either require investment, a loan, and/or ownership dilution … and sales, which they are not getting and haven’t gotten in years, should pay for everything).

The founders/partners are the problem, they can’t be removed, and they’ll stubbornly keep sailing on the edge of the massive whirlpool that’s sure to swallow their ship to the bottom of the sea until they lose that one key customer (that accounts for a significant part of their revenues or referrals to replace the customers they keep losing) or one of the partners becomes unable to continue, at which time the helm will be unmanned and the whirlpool will win. It’s unfortunate for all involved, and it is even more unfortunate that, since they are private, you can’t do hostile takeovers of the ones with good tech that will soon be lost to time.

So that’s it. Zombie companies exist and they can’t be helped and you want to steer further from them then dead companies walking. At least in the case of a dead company walking, if that company admits it and charts a turn around course, it could end up being an okay bet, especially if they can reach profitability or are likely to get acquired intact by a new investor. But the only future for a zombie company, unable to acquire the brains it needs to survive, is to eventually shrivel up and fall apart and return to the dirt from which it came.

Don’t Fall for the Buzzwords!

In fact, as per our 10 words or phrases to ban from an RFP response last year (Part I and Part II), you should ban all buzzwords from not only your RFPs but from your communications with potential vendors. They should be counted as strikes against the vendor and the baseball rule applied (3 strikes and you’re out).

Even though you might be attracted to “social”, “green”, “(Gen-)AI” (which you shouldn’t be, since it’s been proven that all the emergent property claims are false), “autonomous”, “intake-to-“, “discovery”, “multiplier”, and “insights”, etc., you need to remember that the vendors know this and are using as many of these terms as possible to lure you to them and convince you they have the best solution, even if all they have are the best buzzwords.

After all, they know that you are under pressure by your consumers, colleagues, and CEO to be “social”, “green”, and “autonomous” and that, to do that, you need “insights” and “discovery” and that you are all getting swept up in the “intake-to” and “(Gen-)AI” hype-cycles and that you believe it will get you “multipliers” and “delightful” experiences.

So they are preying on your pressures, your desires, and your fears of missing the hype-cycle and being left-behind, even though these “hype” cycles are often literal — all “hype”, no “substance”. Social value is a buzzword, nothing more. Social value is not in applications, it is in awards and actions. The same with “green”. At the end of the day, all SaaS platforms are equally green (unless they use Gen-AI, because then they use ten time the computing resources to do a simple task), they all minimize the need for on-site hardware, but they all eat up cloud compute cycles. The green comes in the decisions you make with them.

Automation is important, but “autonomous” is only useful for tactical e-paper pushing, not for strategic decision making — good computational algorithms can compute odds (and make recommendations) based on the data presented, but it cannot make decisions, and the odds are only as good as the data. “Insights” are only achieved on good data … and if you don’t have that “good” data, you can be damn sure the vendor doesn’t. “Discovery” is always limited to data at your disposal or the vendor’s disposal. If you don’t have the supplier in your database and the vendor doesn’t have the supplier in its community database, there’s no way it’s going to be “discovered”. Also, “intake-to-procure” is useless if you don’t have the solution in place to actually “procure”. As we pointed out in our piece on marketplace madness, intake-to-orchestrate on its own is useless, and a real, modern procurement solution actually has “intake” built in. (So if yours doesn’t, maybe upgrade it to a better solution instead of paying six-figures a year for a view into your data that doesn’t actually add any value.)

Which brings us to the (Gen)-AI hype-cycle. It’s all hype, no substance. There are no valid uses for Gen-AI and even less uses than none in Procurement and it’s all a fallacy considering that even in a decade it won’t even have a 50/50 chance of being truly dependable at the expected rate of improvement. (And if a 200M investment into a new model culminated in the great insight that we should eat one rock a day, maybe it’s time to bury this failed offshoot of AI now before more Billions are wasted. After all, if those Billions were invested in the public school system, that would more than double the current national budget — think of how much better educated your children would be with that increase in funding. Despite the bullcr@p, the future lies in Human Intelligence (HI!), which needs to be nurtured, not abandoned.)

In other words, don’t get led astray by the buzzwords. Value comes from real products that solve real problems whose solutions provide real value to your organization. If the vendor can’t explain that in plain English, then you can be fairly certain the vendor doesn’t have anything truly valuable and you should move on.

Why Do Successful Solution Providers Ruin Everything By Becoming Tech Companies?

Jon THE REVELATOR asked this very important question in a article over on Procure Insights in the spring.

And, of course, the doctor answered.

Simply put, the reason they ruin everything is because they fail to understand that, in Finance and Procurement, no one wants tech or software … no one. This is true from a professional and a personal point of view.

Professionally, they want whatever will make their jobs easier. They don’t care if its software, a physical tool, outsourced labour, or an intern. They want to get the job done, fulfill the requirements of the business, make money, and do it with as little effort on their part as possible. If that’s software, great. If the money is there and it’s outsourcing everything at an affordable dollar value that will generate a return, they’d be just as happy (if not happier) to do that (as then they wouldn’t be stuck fighting with a tool when it didn’t do exactly what they wanted it to do exactly the way they wanted it done).

Personally, and this is what software companies don’t get, Finance and Procurement people want software EVEN less. 140,000 people don’t flock to CES (Consumer Electronics Show) for the software — they flock for the cool new gadgets that will entertain them. The gadgets may be software powered, but they don’t care about that. It’s the fun factor. And, let’s face it, Finance and Procurement software IS NOT FUN!

Has anyone ever wanted a word processor? A piece of tax software? A scripting tool? NO. Writers want an e-type writer, they don’t care what that is. People don’t even want to do their taxes, so they definitely don’t desire software that will help them do other people’s taxes too. Coders like scripting, but they are usually doing it to get a job done more quickly or elegantly or to have (sometimes illegal hacking) fun as it’s their version of entertainment. They don’t want your tool — they want what it does.

Gamers want video games, but they want the experience, they don’t want to see the “software”. The game console sells, not the code that powers it.

That’s why successful solution providers, who forgot it is all about solutions that deliver ROI to the business, ruin everything when they become tech companies. Tech is for consumers, not for business. Valuable ROI-generating solutions are for business.