Built for the Small Guy

Most software companies don't know you exist.

They build for the enterprise. Fifty users. Department heads. IT teams that evaluate software for a living. Then they strip features out, call it a "Starter Plan," and act like they built something for you.

They didn't. They built for someone else and gave you the leftovers.

If you run a business with one, two, maybe five people. If you're the owner, the salesperson, the bookkeeper, and the one who answers the phone. If you close your laptop at 11pm because invoicing still isn't done.

You already know the tools weren't built for you.

There's a gap in business software that nobody talks about.

Enterprise tools cost too much, do too much, and assume you have staff dedicated to running them. Free tools break, don't connect, and lose your data when you need it most.

In between? You're patching things together. An invoicing app here. A booking tool there. A spreadsheet to track what the other two don't talk about. Maybe a CRM you signed up for, used for a week, and never opened again.

That's not a system. That's a workaround.

You spend your mornings serving customers and your evenings doing admin. You enter the same client details in three places. You can't answer "what do I owe or what am I owed?" without checking two apps and a spreadsheet.

And the worst part? You think this is normal. Because nobody's shown you anything different.

My name is Anton de Villiers. I've spent 26 years in IT and 15 of those building software platforms.

For most of that time, I sat across the table from business owners. In client meetings. In project sessions. In those honest conversations that happen when someone is frustrated enough to say what's actually wrong.

The pattern was always the same.

Five, six, seven tools. None of them talked to each other. Every handoff was manual. Sales would close a deal and operations wouldn't know. A quote would be accepted but nobody would raise the invoice. Stock levels lived in one system. Orders in another. And the owner was the human bridge between all of them.

I saw this in retail. In service businesses. In medical practices. In accommodation. In trade. Everywhere.

Every time, I thought: someone should build the thing that just does all of this. One system. Connected. Where a quote becomes an invoice becomes a payment becomes a line in your books. Automatically.

So I built it.

Not for enterprise. Not for teams of fifty. For the person who runs the business.

Here's what most people don't understand about BX1X.

It wasn't designed as a big system and then simplified. It was built from the ground up with the small operator in mind. Every module was designed for someone who doesn't have an IT department. Someone who doesn't have time to read a manual. Someone who needs it to just work.

Billing. Bookings. Inventory. CRM. Accounting. Communications. E-commerce. Project management. They're all there. But they're modular. You switch on what you need. You never see what you don't.

Run a plumbing business and don't need bookings? You'll never know the module exists. Run a physio practice and need clinical records on top of scheduling? Switch on the medical module and it activates inside the same system you're already using.

One login. One place. Everything knows about everything else.

When a customer books, the system knows. When you send an invoice, the books update. When a payment comes in, the statement reflects it. You don't bridge anything. You don't re-enter anything. You don't spend your evening reconciling.

That's not a feature list. That's your evening back.

The software industry gets this wrong constantly.

A solo GP with one receptionist is a small business. A physiotherapist with two rooms and a part-time assistant is a small business. A dentist running their own practice is a small business.

But medical software treats them like hospitals. Complex. Expensive. Separate from everything else.

So these practices end up running two systems. One for clinical records. One for billing and operations. Half the admin time goes to making the two agree with each other.

BX1X treats the medical practice as what it is: a small business with an extra layer. Clinical records, treatment tracking, and medical aid processing sit on top of the same billing, bookings, and CRM platform that every other small business uses. One system. Not two.

I should be honest about this.

If you have 200 employees and need role hierarchies five levels deep, BX1X probably isn't the right fit. If you need to plug into legacy ERP systems from the 1990s, you'll need something bigger.

BX1X was built for the owner who runs the show. The one who wants one system that handles everything, set up by someone who actually talks to their customers. Not a chatbot. Not a help article. A person who built the thing and knows how it works.

I redesigned the architecture seven times to get it right. Not because a committee asked for it. Because it wasn't right yet.

That's the difference between software built by a company and software built by someone who cares whether it works for you.

Book a demo. I'll walk you through the platform. Not a sales pitch with slides. An actual walkthrough, tailored to what your business does.

You'll see the billing, the bookings, the CRM, the accounting. All connected. One login. And you'll have a clear picture of whether this fits.

If it does, great. If it doesn't, you'll leave knowing more about what you need. Either way, you're talking to the person who built it.