Why I Build Custom Systems Now

Here’s the short version: I used to set my clients up on an all-in-one platform. These days, I build them something custom — a client portal, a booking system, automations — on modern web technology they own outright. A few of my older articles now carry a note pointing to this post, so you deserve the full story rather than a shrug.

It’s a good story, I think. It’s about a business growing up.

What changed

When I started PSOS, the job was getting small businesses over the line — taking owners who’d done most of the hard work themselves and removing the last few roadblocks. The fastest, most affordable way to do that was assembling systems from excellent off-the-shelf tools. For a few years, the centre of my toolkit was GoHighLevel, a genuinely capable all-in-one platform that let me stand up a CRM, bookings, email and automations in one place. It served my clients well.

I’ve since moved to a different approach, and I no longer use or recommend it — not because anything went wrong, but because my own model changed.

Two things happened. First, a pattern: most of my clients needed a specific slice of what any all-in-one offers — and it was a different slice for every one of them. A cleaning business needed job scheduling and review requests. A wellness clinic needed intake forms and reminders. Each of them was learning their way around a big platform to use the one corner of it that fit.

Second, my own work kept drifting custom. Whenever a client needed something shaped exactly to their workflow — a portal their customers could log into, an ordering flow that matched how they actually operate — I built it by hand. And those builds were consistently the work clients loved most, because the system fit them like it was made for them. It was.

At some point the maths flipped: the systems I could build had become a better fit for my clients than the systems I could configure. That’s the whole story. The right tool at the right time — and the right time changed.

The new approach, plainly

Instead of one platform that does everything, I now build each client a small stack of right-sized pieces:

A client portal that’s yours. Your customers log in to see their orders, project status, files and messages — laid out around your actual workflow, not a generic template. It runs on the same modern web technology that powers the big-name apps you already use, and it belongs to you.

Lead and client tracking built in. Enquiries land in your portal’s own inbox, tied to the customer’s history — part of the system, not another subscription to manage.

Automations that connect what you already use. The same automation work I’ve always done: bookings flowing into invoicing, review requests firing at the right moment, reminders that stop no-shows. The difference is the automations now connect your tools, whatever they are.

Bookings, forms and email that each do one job well. Small parts, each simple, each replaceable — so nothing you rely on depends on everything else.

This isn’t theoretical. It’s how I’ve spent this year: client portals are in final testing with real PSOS clients right now, I’m building my own back office — I call it PSOS HQ — on exactly the same stack, and I’ve built a chatbot that answers questions about my services over on my Automation & AI page. I don’t sell anything I don’t run myself.

What “you own it” actually means

“No lock-in” has been a PSOS promise from day one. The new approach makes it structural rather than contractual:

• The domain is registered in your name.
• The data lives in a database you control — export it whenever you like, it’s yours.
• The code belongs to you, not to a platform and not to me.
• The bill has no per-seat licence in it, because there’s no platform underneath charging one.

The test I use: if you and I parted ways tomorrow, what happens to your business? Under this model, the honest answer is nothing. Everything keeps running, and any competent developer could pick it up where I left off. I work hard to make sure you never want to take up that option — but you having it is the point.

If you’re a current or past client

Nothing breaks, and nothing changes without a conversation. If I set you up on a platform and it’s doing its job, keep using it — a working system is a working system, and I’d never advise replacing something that’s earning its keep. When you’re ready to move, or when something stops fitting, I’ll help you migrate properly: data exported, history preserved, no gaps your customers would notice.

If you’re shopping for an all-in-one today

Honest guidance, brand-neutral: all-in-one platforms are a genuine option, and for some businesses the right one. They suit you if you want one login for everything, you’re happy to invest in learning one big tool deeply, and fairly standard workflows fit how you operate. That’s a real set of businesses, and if it’s you, buy with confidence.

Custom suits a different set: businesses whose workflow is their edge, who want the system shaped to it exactly, and who like the idea of owning what they pay for. And there’s a third path people forget — doing less, better. If your subscription list has quietly grown past what you can name from memory, start with my plain-English guide to consolidating your tools before you buy anything new.

The short version

The values haven’t moved: plain speak, honest pricing, right-sized solutions, and telling you when you don’t need me. What’s changed is the toolbox — from configuring someone else’s platform to building small systems my clients own. It’s the same job I started with, done with better tools.

If you’re wondering what that would look like for your business, the automation service page has the detail and the pricing out in the open, as always. And if you’d rather just ask a person, get in touch — no pitch, no pressure, plain answers.

Frequently asked questions

Why did you move from an all-in-one platform to custom builds?

It was a business decision, not a verdict on any tool. All-in-one platforms are genuinely capable and suit plenty of businesses. As my own skills and my clients' needs matured, building small custom systems became the better fit for the work I do — each client gets exactly what their workflow needs, and they own the result outright.

What does owning your system actually mean?

The domain is registered in your name, the data sits in a database you control, and the code belongs to you. There's no per-seat licence, because there's no platform underneath. If you and I ever part ways, everything keeps running, and any competent developer can pick it up where I left off.

Is a custom system right for every business?

No, and I'll tell you when it isn't. If you want one login for everything, you're happy to learn one big tool, and standard workflows fit how you work, an all-in-one platform is a perfectly good choice. Custom suits businesses with a distinctive workflow who want the system shaped to it — and who like the idea of owning the result.