Skip to content
gitogi
Book

AIRA Method

The method that builds autonomy

AIRA is the method we use to bring Odoo, AI integration and custom software into your company. Not a theoretical framework: an operational path with defined deliverables, mandatory measurements, and a clear goal — helping you become self-sufficient.

What is the AIRA method?

AIRA is the method we use to structure Odoo implementation, AI integration and bespoke software projects. It has four phases — Assessment, Implementation, Results and Autonomy — each with defined deliverables and completion criteria. The aim is to enable you to move forward independently of us, with the code and documentation remaining with you.

AIRA

4 phases. Clear deliverables. Measurable exit criteria.

AIRA — Assessment, Implementation, Results, Autonomy

A

Assessment

1-2 weeks
Clarity in 1-2 weeks: processes, systems, priorities and a 90-day roadmap.
  • Process and systems map
  • Priorities and use cases
  • Value Scorecard (baseline)
  • 90-day roadmap
I

Implementation

2-6 weeks
The first workflows in production, built with the people who use them every day.
  • Configured and developed workflows
  • Data migration and integration
  • Operating procedures
  • Role-based training
R

Results

2-4 weeks
We measure before and after across 4 quadrants and correct course if we miss our targets.
  • Before/after report
  • Optimisations
  • Scaling plan (use cases 3-5)
  • KPI dashboard
A

Autonomy

1-3 months
Internal playbook, documentation, coaching. Success is when you no longer need us.
  • Internal playbook
  • Technical documentation
  • Periodic reviews
  • Trained internal lead

method · 6 verbs

What we do, in 6 verbs

  1. We listen

    Your problems first, our solutions second.

  2. We map

    Every process to digitise, every available data point, every place where AI creates value.

  3. We implement

    With the people who do the work every day, not instead of them.

  4. We measure

    Before and after. KPIs, not opinions.

  5. We transfer

    Skills, playbooks, tools. You continue on your own.

  6. We exit

    When you're autonomous. That's our measure of success.

value scorecard

We measure impact across 4 dimensions

Every AIRA intervention produces a scorecard with baseline and measured results. The KPIs below are examples of typical targets.

Efficiency

Less time on repetitive tasks
  • Hours saved
  • Order-to-delivery cycle time
  • Cost per process
  • Error rate

Growth

More sales capacity
  • Margin per project
  • New clients
  • Upsell
  • Quote-to-order

Customer Experience

Faster response times
  • NPS/CSAT
  • Response time
  • First-contact resolution
  • Retention

Governance

One record, traced
  • Data quality
  • Traceability
  • Incidents
  • System adoption

AIRA vs.

AIRA vs alternatives

AIRA (Gitogi)

Strengths

  • Structured method with defined deliverables
  • Integrated governance
  • Skills transfer
  • Before/after measurement

Limitations

  • Requires team involvement

Generic consulting

Strengths

  • Recognised brands
  • Large teams

Limitations

  • Enterprise costs
  • More strategy than execution
  • No skills transfer

DIY

Strengths

  • Zero consulting costs
  • Initial speed

Limitations

  • Disconnected tools
  • Maintenance falls to you
  • Unmeasurable ROI
  • Time away from operations

Frequently asked questions

The questions we are asked most often about the AIRA method

What does AIRA stand for?

AIRA stands for Assessment, Implementation, Results and Autonomy. These are the four phases Gitogi uses to structure a project: understand the need, carry out the work, check the outcome and prepare you to operate independently. Each phase has defined deliverables and completion criteria.

FAQ 01 / 6

Will we be able to manage the system without Gitogi once the project ends?

AIRA aims to leave you able to move forward without depending on Gitogi. The code and documentation stay with you to support whoever manages the system. Achieving that independence means identifying who will have the skills to use and maintain it.

FAQ 02 / 6

How do we know whether a project has been successful?

Success means checking the outcome against clear, testable objectives for the process you want to improve. AIRA includes a dedicated Results phase and completion criteria for every phase. For example, you might check that information moves between systems without anyone having to enter it again manually.

FAQ 03 / 6

What do we need to establish before starting a software project?

Start by identifying the process you want to improve, the outcome you need and the constraints the project must meet. In AIRA, this work belongs in Assessment, the opening phase. To prepare, gather concrete examples of how the work is done today and identify who can assess the outcome.

FAQ 04 / 6

Who from our business needs to be involved?

You need people who can set priorities as well as people who understand the day-to-day work. The people who will use the system help explain the process and check that the result works in practice. Whoever will take technical responsibility after handover should also be involved.

FAQ 05 / 6

What happens if our requirements change during the project?

A change needs to be assessed against the planned work before it is agreed. AIRA gives each phase defined deliverables and completion criteria, which provide a basis for reviewing changes to the scope. Any revisions need to be agreed in light of their impact on the project.

FAQ 06 / 6

Go deeper

Case studies

Illustrative scenarios showing how AIRA applies in business, rather than actual client projects.

Services

Odoo, AI integration and bespoke software: our services delivered using the AIRA method.

Transformative intelligence

Autonomy has a name and some conditions: what has to evolve inside a company for the method to leave a lasting effect.

Let's talk about your project

Tell us where you want to take your company with Odoo, AI and custom software. We'll honestly tell you where to start — and with which method.

Book a free call