Founder story

Built by an operator who knows what happens when the system is missing.

I have spent ten years inside real operations, not consulting theory. Fleets on the street, a P&L to defend, projects running across three continents, and an ecommerce brand built from our kitchen table. Different industries, different scale, same job: make the work run without heroics.

The pattern held everywhere. Teams do not break because people stop caring. They break because ownership is unclear, success is undefined, reporting is too slow, and the founder or manager becomes the only person who can connect the dots.

The System Folks exists to fix that, in that order.

Ten years inside real operations, not consulting theory.

At Bolt I scaled driver operations. At Neuron Mobility I managed city-wide operations with a $12M P&L. At Askable I lead global project delivery across APAC, EMEA and the Americas. In between, my wife and I built Puggle Adventure, an ecommerce brand, from zero to $70K in its first year.

At Neuron and Bolt, performance came down to four things: visibility, ownership, cadence and fast decision loops. When those existed, hundreds of vehicles and dozens of people ran smoothly. When they did not, everything escalated upward. Every exception landed on a manager's desk, and the people closest to the work waited for answers they should have been able to reach themselves.

That is the difference between a team that performs and a team that is merely busy. It was never talent. It was never effort. It was whether the system around the work made good performance the default.

Chapter 01

Bolt

Scaled driver operations. Learnt that growth exposes every unclear handoff.

Chapter 02

Neuron Mobility

City-wide operations with a $12M P&L. Hundreds of vehicles, dozens of people, one operating rhythm.

Chapter 03

Puggle Adventure

Ecommerce brand built with my wife. Zero to $70K in year one, and every decision ran through us.

Chapter 04

Askable

Global project delivery across APAC, EMEA and the Americas. Production AI systems in live workflows.

Lorenz Villalba

Founder, The System Folks · Australia

At Puggle, founder dependency stopped being a concept.

Running someone else's operation teaches you the pattern. Running your own makes you live it. At Puggle, every decision, every quality check, every customer issue ran through us. Supplier problem at 7am, ours. Refund question at 11pm, ours. The business grew, and our capacity to hold it all did not.

That is what most founder-led SMBs live every day. Not a lack of effort, not a lack of tools, just a business where the founder is the routing layer for everything. I know exactly what that costs, because I have paid it.

AI sharpened the lesson. It did not replace it.

At Askable I built production AI systems, including a feasibility agent that compressed a multi-week bottleneck into a 2 to 5 minute check. Real workflow, real users, measured result.

Here is what that work actually taught me: the best automation did not start with a tool. It started by understanding the workflow well enough to know where the real bottleneck lived. The AI was the last step, not the first. Point automation at unclear work and you get faster chaos. Point it at a well-defined workflow and it compounds.

So the order matters. Operator first, systems builder second, AI practitioner third.

Why The System Folks exists.

The System Folks helps founder-led teams install the operating layer first, then automate what is actually ready. The operating layer is five things:

Roles. Every outcome has one owner. No dot-connecting through the founder.

Scorecards. Success is defined in numbers, so "good" is not a matter of opinion.

Workflows. The way work moves is written down, not remembered.

Dashboards. Reporting is fast enough to change decisions, not describe last month.

Cadence. A rhythm of reviews that keeps the loop closed without you chasing it.

Once that layer exists, automation has something solid to attach to. That is the whole premise: performance systems first, AI where it is ready. It is what I wish someone had built for us at Puggle, and it is what I build for founder-led teams now.

Built by an operator who knows what happens when the system is missing.

Ten years inside real operations, not consulting theory.

At Puggle, founder dependency stopped being a concept.

AI sharpened the lesson. It did not replace it.

Why The System Folks exists.

See what your business looks like from the outside.