AI automation consulting

Ainur

Ainur is my AI automation consultancy for B Corps, nonprofits, professional firms and cooperatives.

I help these organizations decide what to automate and put it into production. I do the work myself. Every system has explicit limits and requires human approval before it can affect people or money.

Organizations accountable to members, donors, professional bodies or communities cannot treat an automated error as an ordinary bug. We define risks and responsibilities before I write any code.

AInur Lab image

Who it's for

Ainur is designed for organizations that handle sensitive data or processes with real consequences for people.

  • B Corps
  • Nonprofits
  • Professional firms
  • Cooperatives

Three ways to work together

Process mapping

For two weeks, I map how the work is actually done with the people who do it every day. You receive an operational map covering priorities, risks and the activities that should remain manual.

Implementation sprint

We start with one process and take the first automation into production. Work happens in short cycles with the team that will use the system. Human review is included from day one.

Training

Your team learns to manage the automation and recognize its failures. By the end, they can handle ordinary changes without depending on me.

Start with a process-mapping engagement

Seven rules, written before the code

  1. 01

    Mandatory human review

    An output that affects people or money takes effect only after a person approves it.

  2. 02

    Transparency for users

    People must know when they are interacting with an automation. No bot presents itself as a colleague or human operator.

  3. 03

    No irreversible decisions delegated to the system

    The system may prepare a decision or flag a risk. It cannot exclude a person, deny a service or dismiss an employee without human approval.

  4. 04

    Control of client data

    We define where data travels and who can access it. No model is trained on client material without a written agreement.

  5. 05

    Operational continuity

    When the process requires it, we design a manual path that allows work to continue during an outage.

  6. 06

    Periodic review

    We review the system at an agreed interval. Anything that no longer serves its purpose is corrected or switched off.

  7. 07

    No surveillance or manipulation

    I do not build systems that monitor employees or push users toward choices they do not want to make.

Next available project slot: to be confirmed.

Tell me about the process you want to automate. In 30 minutes, we can decide whether it makes sense to work together.

Book a 30-minute call