Blog01–09

Writing.
On the work, and the market around it.

Articles on applied AI, digital strategy and what actually changes when a system goes in. Every figure quoted carries the organisation that published it and a link to the publication.

A cyanotype architectural blueprint of a foundation plan, annotated by hand.
Method4 min read

What a diagnostic actually looks like

Two weeks, a map of how the work really moves, and a costed shortlist. What we look at, who we speak to, and what you are holding at the end of it.

Articles

02–09
  1. 02Strategy3 min read

    Buying a tool versus building a system

    A tool is bought once and bent to fit. A system is shaped around how the business already runs. The distinction decides most of what happens afterwards.

  2. 03Practice3 min read

    Why most automation automates the wrong thing

    The visible bottleneck is rarely the expensive one. On where the time actually goes, and why the obvious candidate is usually a symptom.

  3. 04Market3 min read

    AI adoption in the GCC: what the numbers miss

    Personal use in the region is among the highest measured anywhere. Business adoption is not. On the gap between the two, and what sits in it.

  4. 05Governance3 min read

    Human-in-the-loop: where the loop belongs

    Approval placed at every step slows everything and is ignored within a month. On putting the checkpoint where a wrong answer would be expensive, and nowhere else.

  5. 06People4 min read

    What AI actually does to the people using it

    Not what it does to headcount. What it does to the working day of someone who uses it, measured by an organisation with no product to sell.

  6. 07Skills3 min read

    Almost nobody using AI thinks they are good at it

    The majority of people using AI at work do not believe they have the skills for it, and more than seven in ten want to learn. The constraint is not willingness and it is not access.

  7. 08Search3 min read

    Being findable when the answer is written for you

    Search is splitting in two. On what a peer-reviewed study found actually gets a page cited inside an AI-generated answer, and why it is not what the SEO industry is selling.

  8. 09Evidence3 min read

    The AI statistics that survive checking

    We tried to source every number on this site. Several of the most-quoted figures in the industry did not survive the attempt. Here is what happened to each of them.

New writing, when there is some

A short note when something is published: what it is about and a link. No more than a couple a month, and nothing else.

Start with
the diagnostic.

A scoping conversation costs nothing and ends with a straight answer about whether there is enough here to be worth doing. If there is not, we will tell you.

Book a scoping callinfo@skaiyon.com

Questions. Asked before every engagement.

Your data is yours. You can export it at any time, and it is exported to you in a documented format before any engagement closes. The software itself is licensed: we build it around your business, host it, and run it, and you pay monthly for that. If you'd rather own it outright, that's possible. It's a different kind of engagement and it's priced accordingly. Licensing keeps maintenance our problem rather than yours, which is why it is the default.

Two weeks' notice, either side. Your data is yours. You can export it at any time, and it is exported to you in a documented format before any engagement closes. The system stops running. If you'd rather keep it running, the ownership option is available at that point as well. Ending the retainer doesn't force you to lose what was built.

Typically four to eight weeks from signing to a working system, depending on how many tools it connects to and what state the data is in. A scoping conversation and a written plan come first, so the timeline is agreed before anything is committed to.

Access to the tools and data the system will work with, one person who can make decisions, and a few hours in the first two weeks while we map how work actually moves through your business. After that, very little. The point of the engagement is that it runs without your attention.

Usually. Most business software exposes an interface we can build against, and where one doesn't there's normally a way around it. Which connections are viable is settled in the scoping conversation, so you find out before committing rather than after.

Hosting region for a system we build for you is decided at the start of the engagement, not inherited from a default. If data residency is a hard requirement, raise it in the first conversation and we will tell you plainly whether we can meet it. This website is separate and its processing is already fixed: enquiries, quote requests, bookings and chat are handled by Supabase in Tokyo, Resend in Tokyo, Cloudflare, cal.com and Moonshot AI, which the privacy policy names individually along with where each one processes. Nothing from a client system is ever sent to the chat assistant.

That's the normal starting point, and mapping them is part of the work. Automating a process nobody has examined just makes the confusion faster, so we don't start there. The first phase establishes how things actually happen, as opposed to how they're supposed to.