Daniel Chilcott

Yeah, well, the origin story is actually fairly mundane.

My first real job was working in a business that had a software company spun up within it.

And I became the first software engineer.

And basically, it was just a fight to survive.

So anything that came through the door, we would build.

So it was custom project, custom project.

And over time, we realized that we wanted to make some of it reusable.

And a lot of the requests that we were getting for customers were around CRM.

This is in the late sort of 2000s.

And so we realized that we could create something that was much more reusable.

And then everything else that was requested, you know, auto processing or some kind of finance backend, those were shipped as modules on this kind of platform.

ever more expensive CRM that we built.

And that was great.

And we got reusability out of that.

But every customer coming to us wanted a way to integrate what we had shipped for them into the other systems that they were already using.

And so that's kind of where the itch came from around figuring out how do we make integration reusable as well.

And the difficult thing with it is that

You can sort of build a CRM once, so to speak, and it has to have a certain level of configurability.

But after that, you can sort of sell it as is.

But integration is actually seldom like that.