The Story Behind KAB

Like many parents, I was thinking about the future and what the employment landscape looks like for young people coming into the world of work.

In particular, I was thinking about my son Kenzie and how difficult it can be to find a genuinely good opportunity. Something that offers more than just income. Something that teaches responsibility, customer service, work ethic, problem solving, and how a real business actually operates.

That became the core reason for KAB. I did not want to just talk about opportunity. I wanted to create it.

The name KAB comes from Kenzie and Barry, and that purpose is built into the business from the start.

I did not want to build a traditional small service business based around phone calls, manual scheduling, chasing payments, and constant administration.

I wanted to build something with more structure. A business that used operational thinking, process design, and technology to create a smoother experience for customers and a more scalable operating model behind the scenes.

That meant designing KAB as a modern service platform rather than just a local service.

A major part of the design came from a very real constraint. I still have a full time job that I care about and remain fully committed to.

Because of that, KAB had to be built to operate as autonomously as possible. It could not depend on me manually coordinating every customer, payment, or schedule.

That constraint became a strength. It forced me to think carefully about how to remove unnecessary admin and build a business that could run with structure, visibility, and minimal manual intervention.

To make that possible, I built the platform behind KAB myself. The aim was to create a customer journey that feels simple on the front end while the system handles the operational heavy lifting behind the scenes.

• Customers can check availability online before signing up
• New customers can register quickly through a digital journey
• Direct Debit payments are set up as part of onboarding
• Service zones and capacity are managed through structured logic
• Customers are placed into repeatable cleaning cycles automatically
• Customer and admin visibility are built into the system from day one

Everything has been designed to reduce manual administration and improve consistency as the business grows.

One of the key decisions was to avoid treating each job as a one off booking. Instead, KAB has been designed around repeatable service cycles and clearly defined service zones.

That means the business can operate with more predictable scheduling, cleaner route planning, and better visibility of capacity and recurring revenue.

It is a local service business, but it has been built with the same mindset I would apply to process improvement and operational design in a much larger organisation.

One of the parts I am most proud of is that this has been built by myself from the ground up.

That includes the concept, the brand, the website, the platform logic, the automation thinking, the customer journey, and the operational structure behind it.

For me, KAB is more than a business. It is proof that the best way to test operational ideas is to build something real and see them work in practice.

KAB is still at an early stage, but it has been built with a longer-term view.

• Expand into wider exterior cleaning services
• Refine route planning and operational efficiency
• Increase automation and management visibility
• Grow into additional service areas over time
• Create a stronger platform for practical learning and responsibility

The immediate focus is building the business properly, but the foundations have been laid with scale in mind.