a red truck with a yellow stripe on the side is on a black background

We have a number of clients in the transportation industry. Given the number of claims to which trucks and truck drivers are susceptible, we’re always eager to help our clients manage, track, and settle their claims as quickly and efficiently as possible.

Two of our client companies — Long Haul Cowboys, Inc. and Big Rigs Amalgamated — recently had separate incidents at roughly the same time. Since each of those incidents produced multiple claims, we asked the CEOs of those companies — Tiny Littlestone of Long Haul Cowboys and Duke Waslewski from Big Rigs Amalgamated — if they would talk to us together. They said yes.

What follows is a cleaned-up transcript of our conversation, with all the bad truck-driver words taken out. Tiny is represented as TL. Duke is represented as DW. And we, as always, are represented as CE (Claims Expert):

CE: Thank you for joining us today, gentlemen.

Burt and his new rig.

TL: It’s good to be here.

DW: Speak for yourself, Tiny.

CE: Well, great start there, men. Let’s start with you, Duke. It seems you had a man who was refusing to drive. Is that right?

DW: Yeah. Burt Sniglitz said he just wanted to stand and admire his new truck.

CE: Did you file any insurance claims on Burt?

DW: No. But we did file claims against Burt for professional liability, property damage, and errors and omissions.

CE: Can you be more specific?

DW: Sure. The professional liability was because he was loitering on company property. The property damage was because he was kicking the tires. And the errors and omissions was because he omitted his job, which was supposed to be driving.

CE: And what was the incident to which you tied those claims?

DW: Burt was an accident waiting to happen. And he did.

CE: Okay, Duke. That’s quite the story, indeed. Tiny, I understand one of your drivers was involved in a crash caused by faulty equipment.

Ernie gets busted on the road.

TL: Yep. But it wasn’t exactly one of our drivers.

CE: Who was it?

TL: That was Ernie Bilge, our head mechanic.

CE: He got pinched for faulty equipment?

TL: He said he was taking it for a test drive to see if the tires were really flat and to determine if the engine was emitting excessive exhaust.

CE: And what were the charges?

TL: Driving with flat tires and emitting excessive exhaust.

CE: And what types of claims did you have to file for that incident?

TL: Well, we had two property damage claims — one for the flat tires and one for the blown engine.

CE: Uh huh. Anything else?

TL: We filed a negligence claim against Ernie.

CE: For what?

TL: Driving with a suspended license.

CE: Why was his license suspended?

TL: Because he had a prior arrest for driving with flat tires and emitting excessive exhaust.

CE: Thank you, gentlemen. We need a drink.

Claim Management For The Transportation Industry

Is that story made up? Well, yes. Is it deliberately absurd. Well, yes. But the fact of the matter is you can manage almost anything — and all of your liability-related incidents — if you have the right claim system. If you’re in the transportation business, you likely don’t have to deal with people like Burt and Ernie. Nevertheless, we’re here to show you how Cloud Claims can transform your claims operations, whenever you’re ready.

In the meantime, be careful out there.

a man in a suit and tie is throwing money in the air

No. The title of this post isn’t a typo.

It occurred to us as we were thinking about crowdfunding, which Wikipedia defines like this:

Crowdfunding is the practice of funding a project or venture by raising money from a large number of people … typically via the Internet.

Then we thought about the time, the effort, and the money (not crowdfunded) we put into developing Cloud Claims. We wondered why no one had ever thought of calling the investment in developing software, the functionality of which is delivered from the cloud, as cloudfunding. We still don’t know. But we decided to use the term anyway.

The Value Of Cloudfunding

Aside from coining the term, cloudfunding, we decided to engage in it because we believed it was a better way to deliver value — more flexibly and less expensively — to the claims managers and risk managers who depend on our software to get their jobs done efficiently. We undertook the conversion of our old, on-premise claim product — IMS — for cloud delivery because we believed the cost savings, the increased productivity, the speed and efficiency, the performance, and the security would constitute valuable assets to our customers. We haven’t heard anything yet to suggest we were wrong.

We also think there’s value in playfulness, in having fun, in engaging in a little word play to come up with a term like cloudfunding, and in deliberately making life a little lighter. We take our work seriously. We take our commitment to our customers — their business and their loyalty — very seriously. But we like to believe we don’t have to take ourselves seriously all the time.

One More Thought On Cloudfunding

We’re a product company. We develop and sell software. But we’re also a service company. We provide the services that enable our customers to get the most out of the software they buy from us. And we’ve come to realize we derive at least as much satisfaction from supporting and interacting with our customers as we do from developing software. If we were inclined to coin another term, we might call that interaction cloudsourcing.

But we don’t want to get ahead of ourselves.