Dimitri Goikman

No, I was a geek, basically.

And, you know, software development, electrical engineering seemed like real work.

So I kind of slid into consulting for large retailers.

I used to work for digital equipment, which then was like the size of IBM, and they had a lot of big accounts.

And so I started doing that.

And then at some point, I decided to jump off the career ladder and do my own thing.

And basically slid into it sideways.

I think I wrote the first prototype in 93, but it was for a custom system for a company called Waccamo Pottery.

They sold a lot of Mikasa and Lion King blankets in North Carolina.

And sizable then.

And then five years later, we decided that it was worth...

you know, doing a product.

At the time, there weren't any planning systems on PCs.

It was all mainframes.

No, no, no.

It was all traditional sort of, you know, first custom development, then systems development, client-server.

We became software as a service really over the last three or four years, you know, because...

uh you know because the clients wanted to go that way and because i wanted to stabilize the cash flow on a subscription basis rather than on a project basis you know projects you know starve or eat right uh sas has been much much much better for us and i think that's definitely the way we're staying okay so you okay so that's helpful context i guess before we dive deep into the backstory here tell us an example of a customer that pays you today and what they're paying for

So we have basically retail chain customers.

The better known ones might be like Puma or Zoomies, but there are lots of smaller ones.