Get in touch
Axon Model
FRAMEWORK

The Axon Model™ — your product, your team

The Axon Model™ is a Scrum-based delivery framework built for long-term product partnerships. Applied by Axon Active across every engagement — named engineers, dedicated squads, continuous product ownership. Now extended by the Axon AI Operating Model for the AI era.

17+Years in business
100%Swiss owned
40+Long-term clients
650+Employees
80+Dedicated teams
The model

What is the Axon Model™?

The Axon Model™ is based on Scrum — a framework for developing products and adaptive solutions to complex problems. Built for the way modern software is actually shipped: continuously, securely, and close to the business. Since 2024, it is extended by the Axon AI Operating Model, which governs AI-augmented engineering across every squad.

Software today is continuously developed and rarely offline. The constant connection to the internet, and the security posture that requires, has reshaped how products get built — and who builds them.

Since 1970 — the end of Taylor’s bathtub — we’ve transitioned into the knowledge and information age. Global market density keeps climbing. Customer needs keep splintering. Competition keeps tightening. Each step compresses how fast a product has to move and how quickly business value has to land.

The Axon Model™ is our answer: flexibility you control, security you don’t have to bolt on, and direct access to skilled people you can talk to. Real names, real standups, real continuity — wrapped in our operating philosophy:

Axon Model
Axon Model

The traditional model, and where it falls short

Most offshore engagements still funnel everything through a bridge engineer or project manager. They translate, they plan, they promise — and the actual people writing the code stay anonymous behind the contract.

You pay for capacity, not for individuals. Names change. Standups don’t include you. Security and scalability decisions get made out of sight. The thing that ships fulfills the contract — not necessarily the problem.

The Axon Model™ inverts that. The team is who they are, by name. You meet them. You talk to them daily. The engineering decisions that shape your product are decisions you’re part of.

Working together

Direct, end-to-end — the team is the team

Two operating principles shape every engagement: you talk to the people who build your product, and the channels they talk back through are short.

01 · Working together

A real team, not a capacity

To stay aligned with a fast-growing market, you need to work quickly and directly with your team. In traditional outsourcing and most "dedicated team" arrangements, the team is built around capacity — not around the specific people who own the work. The Axon Model™ flips that: each engagement is a stable group of named engineers, the same week to week, year to year.

AI governance training for enterprise software development teams
02 · Fast communication

The channels are short

Successful products are built on efficient, effective communication. In the Axon Model™ every member of your squad is someone you can call, meet, or share a whiteboard with. We actively encourage in-person time at our offices in Can Tho, Da Nang, and HCMC — it shortens the loop on every product decision and makes the next sprint faster than the last.

Axon Active meeting room
Product-based vs project-based

Same idea, different result

Two engagement models can take the same starting brief and ship two completely different things. Here's how the philosophies diverge — and what each one actually delivers.

Axon Model™ · product based

You work as a Product Owner. You own your product

Close to the business. Excellent business understanding.

Your squad is a stable group of engineers you know by name.
Daily communication, no bridge in between.
The team identifies with your product — and brings it to success.

Axon Active takes care of your development team so you can focus on the business and the vision. The team stands behind you, communicates with you every day, understands your problem space, and ships things that solve it.

Traditional offshore · project based

You work with a bridge engineer. They translate and plan everything for you

Anonymous capacity. Everything filtered through one channel.

You don't know who works on your product.
Security and scalability decisions happen out of sight.
Promises are easy; ownership of the result is not.

Your offshore partner is always ready and always promising — but the people in the room change, and what ships is whatever fulfills the contract. The thing arrives. The problem stays.

Why choose the Axon Model™

Three roles, one team

Inside every Axon engagement, three roles share a clear remit. The lines between them keep the right work in the right hands — and keep you accountable to the part that only you can own.

PO

Product Owner

You, the customer · close to the business
  • You are close to the business and have the best understanding of why something should be built.
  • You are responsible for building the right things — the strategic "what" and "why".
  • You know, as the customer, why this product needs to exist in the first place.
Responsible for: building the right things.
DEV

Developer

Your team · daily contact point
  • They are your daily contact point — solving your problems, building your product.
  • A real, physically stable, dedicated team you can meet in person.
  • They take care to build things right — engineering, security, scalability.
Responsible for: building things right.
SL

Squad Leader

Axon Active · working as Scrum Master
  • Helps the developers focus on high-value Increments that meet the Definition of Done.
  • Finds techniques for effective Product Goal definition and Product Backlog management.
  • Establishes empirical product planning for a complex environment.
  • Works as the Scrum Master.
  • Facilitates stakeholder collaboration as requested or needed.
  • Supports the administrative work so the squad stays focused on shipping.
Responsible for: keeping the system working.
Governance

The governance cycle

Three nested forums keep value flowing in both directions — between your business and the squad shipping your product. Each cycle has its own pace, its own participants, and its own concrete decisions.

Governance cycle diagram
Tier 1 · innermost

Product Owner Cycle

The forum for product development with the Product Owner and the customer's business manager. Here, priorities get negotiated and budgets get tuned to maximize the customer's product-value delivery.

  • Product stakeholder management
  • Product-value delivery management
  • Software development lifecycle ownership
Tier 2 · middle

Squad Leader Cycle

aka Executive Action Team (EAT)

The forum for our Head of Department, Squad Leaders, and other Axon Active stakeholders — focused on continuous improvement and removing impediments so your squad keeps shipping.

  • Continuous improvement
  • Impediment removal
  • Cross-squad coordination on service quality
Tier 3 · outermost

Business Cycle

aka Executive Meta Scrum (EMS)

The forum for the Branch Director, Head of Department, and other senior stakeholders to negotiate priorities with the PO team, alter budgets, or realign teams and business to maximize value delivery.

  • Strategic prioritisation across engagements
  • Budget and team realignment
  • Long-horizon value optimisation
Frameworks referenced

Based on the official Scrum Guide™ 2020.

Based on the official Scrum@Scale® Guide 2022.

THE AI LAYER

Extended for the AI era — the Axon AI Operating Model

The Axon Model™ defines who builds your product and how you steer it. The Axon AI Operating Model — formalized in 2024–2025 — governs how those same squads use AI, under the same rule that runs everything else here: a name on every decision.

The Axon AI Operating Model is the AI layer of the Axon Model™. It defines the tools, autonomy levels, and governance under which our squads apply AI across the SDLC. The delivery model underneath dates to 2009; the AI layer on top is refreshed continuously as the tool landscape evolves.

Inside your squad, nothing changes about who you talk to — and that’s the point. Your developers work as AI Engineers, running the same AI coding tools the whole market uses — GitHub Copilot, Claude Code, Cursor — plus Axon-built Spec, Test, and Monitoring agents. Every AI-assisted task runs at one of four autonomy levels, human-in-the-loop throughout: production work defaults to L3 Supervised, and nothing merges without explicit human approval. Every AI-enabled change stays traceable — which model, which prompt, which engineer reviewed it.

Traditional offshore had a problem: anonymous capacity. The AI era has its own version: anonymous code. The Axon Model™ answered the first with named teams you can meet. The Axon AI Operating Model answers the second the same way — AI-native software engineering practices, with a human name and a review gate on everything that ships. See how the model runs in practice →

Extended for the AI era — the Axon AI Operating Model
Axon Model
Etymology

The name "Axon"

Axon comes from cell biology. It's the long, slender projection of a nerve cell — a neuron — that conducts electrical impulses. The Axon's function is to transmit information between neurons, muscles, and glands. Communication is what it exists for.

Today, with software complexity and market density growing at the rate they are, exactly that kind of communication is what separates a successful product from one that just got built.

Hiring "capacity" for software development and shipping ideas at it, hoping that a fully functional product comes back, is not enough. What works is the right communication with every member of the team — every day. At Axon Active, with the Axon Model™, that's the standard. Like an axon in your body.

From cell biology to product engineering
FAQs

Frequently asked questions

How does the Axon Model™ use AI?

Since 2024, the Axon Model™ is extended by the Axon AI Operating Model — the layer that governs how our squads apply AI across the SDLC. Engineers run AI coding tools and Axon-built agents at defined autonomy levels, with human review on every change that ships. The model itself doesn’t change: you still steer a named team as Product Owner; AI changes how fast that team moves, not who is accountable.

Is the Axon Model™ the same as hiring a dedicated development team?

A dedicated development team is what you get; the Axon Model™ is how it runs. The model defines the roles (Product Owner, Developers, Squad Leader), the governance cycle, and the working principles that keep a dedicated squad steerable and accountable. Every Axon Active dedicated team operates under the Axon Model™.

Do I need Scrum experience to work as the Product Owner?

No. The model is based on the official Scrum Guide 2020, but your Squad Leader — working as Scrum Master — coaches you into the Product Owner role and handles the process mechanics. What you bring is knowledge of your business and your customers; the framework is designed so that expertise, not Scrum vocabulary, is what steers the product.

How much of my time does the Product Owner role take?

Enough to steer, not to manage. You set direction through sprint ceremonies and stay reachable through short daily channels; the Squad Leader absorbs the administrative and process work so your involvement concentrates on decisions only you can make — what to build and why.