Who writes here.
Everything on this site is written by the partners who ship the work, not by a content desk.
Kartik Anand
Partner, Axonari
Kartik works on the regulated end of the practice: automation in healthcare, financial services and manufacturing, where the compliance frame decides the architecture before the model does. He writes the vertical guides, including the NHS and HIPAA playbooks and the cost breakdowns for AI agents in the UK and US markets, and maintains the compliance research behind the location pages.
22 articles
Joseph Glanville
Partner, Axonari
Joe works on the systems side: multi-agent orchestration, internal tooling, lead operations, and the question of what to build versus what to buy. He writes on where automation actually pays, why most AI projects fail before the model is chosen, and how to move from scripts nobody owns to runbooks a team can operate.
25 articles
Harshita Agarwal
Employee, Axonari
Harshita works on how Axonari and its clients are found, across both search engines and answer engines. She writes on answer engine optimisation and on why well-built websites still get ignored by the systems that now sit between a business and its buyers.
3 articles
How we write
Practitioners, not a content desk
Everything published here is written by someone who has shipped the kind of system it describes. That is a deliberate constraint rather than a boast: it means the guides are narrower than a research firm's, and it means the numbers in them came from delivery rather than from a survey.
Where a piece describes a workflow, assume we have built that workflow. Where it describes a failure, assume we have hit it.
Claims are sourced to the primary document
Regulatory and statistical claims link to the body that published them, not to a secondary article about it. NHS England rather than a trade write-up of NHS England. legislation.gov.uk rather than a law firm's summary. The ICO, FCA, SRA, FINRA, and the Electronic Code of Federal Regulations rather than an aggregator.
Pieces that carry that kind of claim end with a numbered source list, so you can check the reasoning rather than take the number on trust.
Regulation changes, so the pieces change
Compliance guidance ages badly. UK GDPR Article 22 was replaced by Articles 22A to 22D on 5 February 2026, which quietly invalidated a great deal of automation advice written before that date, including some of ours.
Articles carry a published date and, where they have been revised, a revision date. When the underlying rule moves, we update the piece rather than leaving it to rank on a stale claim.
What we will not publish
Numbers we cannot attribute. Vendor statistics repeated without a source. Predictions dressed as findings. Case study results that a client has not agreed we can print.
If a figure appears without a citation, it came from our own delivery data and the piece says so.
Found something wrong in a piece? Tell us and we will correct it and say so on the page.