About

In most small businesses, a person is the integration between two pieces of software. This site is for that person.

What we do

We take a specific repetitive task, build the automation that addresses it, run it, record what it costs and how it breaks, and publish all of that — including the cases where the honest answer is that you should not automate it at all.

Who writes this

What we have and have not done

Being specific about this matters more than sounding impressive:

• We have built and executed automation workflows against a local test stack, measured what they consume, and deliberately broken them to document their failure behaviour.
• We have not yet run a workflow on Make, n8n or Pabbly themselves. Their pages say so.
• We do not run a small business that uses these automations, so we make no claims about hours saved or revenue recovered.

When that changes, the pages will change, and the change will appear in the corrections log.

AXORD is the chosen name for this publication. The site is publicly available and independent: we take no paid placement, and where the best answer is a free or non-affiliate option we say so. Every claim is labelled by how we know it — tested by us, documented by the vendor, or unverified — as set out in our editorial standard. Preliminary trademark searches found no live exact AXORD mark in the sources reviewed, but no professional clearance has been obtained.