Why I Started Verity

Verity started, in a way, because of my wife.

She had a WordPress website for her business, but she didn't really know how to use WordPress. And honestly, she had no reason to.

Whenever she needed to change something or add some functionality, she had to contact a developer. Not even the person who had originally built the website, just the person managing it at the time.

At one point, she needed a way to manage people signing up for her Pilates classes. The solution was to install another WordPress plugin, configure it, connect things, and once again depend on somebody else whenever something needed to change.

And that was only the website.

Invoices were handled somewhere else. Email was somewhere else. Hosting was somewhere else. The domain was somewhere else. Every part of the business had its own platform, login, settings and way of doing things.

None of this was impossible to manage.

It was just unnecessarily complicated.

I've always been obsessed with making processes simpler. If something takes five steps and I think it can take two, I will probably spend an unreasonable amount of time figuring out how to make it take two.

So watching all of this made me think about something I had already been thinking about for a while: what could I build myself?

I had studied web development, and eventually the idea started taking shape.

What if instead of giving small businesses another tool to learn, I could build something that removed some of those tools altogether?

That became Verity.

The philosophy behind it is pretty simple: **technical things should feel simple for the person using them.**

The complexity can exist behind the scenes. Domains, hosting, DNS, deployments, email infrastructure, integrations, all of that still has to happen somewhere.

But the person running the business shouldn't have to care about most of it.

They shouldn't need to understand WordPress plugins because they want customers to book an appointment.

They shouldn't need to know where their DNS is managed because they want a professional email address.

And they shouldn't need four or five different platforms just to run basic parts of their business.

That's what I'm trying to build with Verity.

Today, it brings the website and business email together in one place. Appointments are the next part of that, and over time I want the different parts of the platform to work together more and more.

Not because I want Verity to have hundreds of features.

Actually, quite the opposite.

I want fewer things for the customer to think about.

My instinct when I build something is always the same: there has to be a better way to do this.

Sometimes there isn't.

But very often there is.

And that's probably the simplest explanation for why Verity exists.

I want to make running the technical side of a small business less annoying, especially for people who aren't technical and have absolutely no interest in becoming technical.

They already have a business to run.