Built from the operator's side of the problem

Before OnComply, I spent years building and running businesses of my own. I’m not someone who came out of the compliance software industry. I came into this from the other side, as a business owner dealing with the same day-to-day operational problems our customers deal with.

Running businesses means keeping up with vendors, contractors, insurance, accounting, payments, documents and a lot of paperwork. The bigger the operation gets, the harder it becomes to keep everything organized. Important information ends up scattered between email threads, spreadsheets, folders and different software systems, and somebody has to constantly follow up when something is missing or expires.

That’s where the idea for OnComply came from.

I wanted a simple way to send a vendor one link, collect everything we needed from them, keep it organized, and know whether they were actually cleared to work and be paid. If a document expires, the system should catch it. If something is missing, it shouldn’t take digging through emails to figure that out.

So I built OnComply around the way I believe this should work as a business owner.

I’m still directly involved in the product and in working with our customers. We’re going to keep improving OnComply based on what businesses actually need.

If you’re considering OnComply and have a question, want to see how it would fit your business, or think there’s something we should be doing better, I’d be glad to hear from you.