About CinchFox

You hire someone to take work off your desk. Six months later they finally know the job. Then they hand in their notice, and the job comes back to your desk, along with the training, the mistakes, and the wait for the next person to get good.

If you have run a small business for any length of time, you have been round that loop. So have I, more times than I planned to.

This site exists because I eventually found a way out of it, and the way out was not the one I expected.

Where I am writing from

Fifteen years ago I started a distribution business in Vietnam from nothing: no staff, no warehouse, no customers. Cutting tools and tooling accessories for CNC machine shops.

For years I was every role in it, because there was nobody else to be them. I sold, I bought, I counted stock, I drove deliveries, I chased the money. I sell cutting tools. I have never sold software, run an agency, or taken consulting work.

Hiring solved one problem and created a bigger one

One person at a time: warehouse help, then salespeople, then an accountant. Then a logistics company for delivery, a website, SEO because buyers had stopped phoning suppliers and started searching for them, then social because the website alone stopped being enough.

While I did everything myself, the limit was my own hours. Once other people were doing the work, the limit became consistency. Two salespeople quoted the same customer two different prices. The stock record and the shelf disagreed, and both were confident. Nobody could tell me what our process was, because the process was whatever I happened to do that day.

So I wrote things down. Company rules first, then a documented procedure for every function: quoting, purchasing, goods receipt, delivery, collections. Then I trained people against those documents instead of against my mood.

That work was slow, unglamorous, and unpaid. It is also the part almost every article about automation skips.

Then the resignations taught me what it was really for

Good people leave. They get married, they move city, they get a better offer. That is normal and it is nobody's fault, and it still costs you the same thing every time: months of training, and a job back on your desk while you find the next person.

What I noticed on the second and third time round was that the departures I documented my way through cost far less than the ones I did not. A procedure that lives only in somebody's head leaves the building when they do. A procedure that is written down survives the resignation.

And a procedure that is written down is the only kind a machine can take over.

Automation was the last thing I built, not the first

That sentence is the whole reason this site exists, and it puts me at odds with most of what you will read about business automation. I did not start with tools. I got to them years in, after everything else had already been built and broken and rebuilt, and after enough people had walked out of the door for me to see what the real cost was.

Why the order matters more than the tools

You cannot automate a process you have not written down, and you cannot write down a process you have not done yourself. Every automation I built after the procedures existed survived. The handful I tried earlier quietly rotted, because there was no agreed version of the task for a machine to hold to.

Which is why this site is organised around what a task costs you and how clearly you can describe it, rather than around what a tool can do. A tool cannot rescue a process nobody has defined. It will automate the confusion faster.

What that eventually bought me

Once the procedures existed, automation and AI tooling could take most of them over. Quoting, purchase orders, goods receipt, delivery handoff, chasing overdue invoices: work I used to do by hand, then trained other people to do by hand, now runs largely without either of us. It also makes fewer mistakes than I did, because it never gets to Friday afternoon and stops checking.

The part I did not see coming is what it did to hiring. The work that runs itself does not resign. When somebody does leave now, they take their judgement and their customer relationships with them, which is a real loss. They no longer take the process with them, which used to be the expensive part.

I am not going to put a percentage on that yet. I am measuring it properly, task by task, and those numbers will be published here with the raw data behind them when I have enough of it. A site that demands a source from every tool it reviews does not get to skip the requirement for its own claims.

Why I write this instead of selling it

Almost everything published about business automation is written by someone with a stake in your answer. Agencies want the retainer. Vendors want you on the annual plan. Developers writing about self-hosting already own a server and already know how to patch it, so their arithmetic does not transfer to you.

I was the customer. I still am. I pay for the tools I write about here, out of the same budget that runs this site.

What that means for what you read

Every review starts with a paid account and a workflow I used to run by hand: turning a supplier price list into a quote, keeping stock counts honest, chasing purchase orders, chasing money.

Every comparison table names at least one thing my recommended tool loses at. Every review says who should not buy it. When the honest answer is that no software is worth it at your size, the page says that. Several tools recommended here pay me nothing, and they stay recommended.

Who this is for

• You run a business of roughly 1 to 20 people
• You do not write code, but you are not afraid of tools
• You are losing 5 to 15 hours a week to work a machine should be doing

It is not written for developers self-hosting for free, agencies reselling automation services, or companies with an IT department. Those readers are served better elsewhere.

About the fox

My name is real, the company is real, and the code is public. The face is a fox.

A photograph proves nothing that could not be faked in a minute. A dated test file, a recorded build session on YouTube, and a repository you can clone from GitHub prove considerably more. I would rather spend the credibility there.

How this site pays for itself

Affiliate commissions, disclosed on every page that carries one and explained in full on the affiliate disclosure page. No sponsored posts, no vendor previews of drafts, no paid placements. The way tools get tested is documented inhow I test, and the way they get scored inmethodology.