Get in touch
Software Factory
Services
Software FactoryTech and DataBusinessExperienceOrganization All services
Cases
Cyberport’s journey to becoming an AI-first company−95 %, time to live per feature, planned target path10 billion euros in annual turnover through a new booking tool+€10bn, annual revenue through the booking tool, more than 30 % of it booked digitallyDigital turnaround for Vodafone B2B8 weeks, from audit to quantified impact All cases
Company
About usCareers2 openPress House of AIKassenzone
Insights
ArticlesEventsReports All insights
Network

DE

Get in touch

The Software Factory for your backlog.

A software factory builds software with AI agents. They plan, build, test and document every ticket. Your team approves at fixed points and keeps control of the code.

Find the bottleneck To the approach

For
IT teams whose backlog grows faster than they deliver
Entry
Analysis workshop on your backlog
Start
One pilot team on one technology stack
Result
Your own Software Factory in your IT environment

Bottleneck

Why your backlog keeps growing despite AI tools.

AI assistants speed up coding, while specifications, tests and releases still take up your team’s time. So the bottleneck only moves elsewhere.

  1. Stage 0

    Status quo

    Your team does every step itself. Its capacity sets the pace.

    Plan
    Team
    Build
    Team
    Release
    Team

  2. Stage 1

    Agentic Engineering

    AI agents write code. Planning and release stay with the team.

    Plan
    Team
    Build
    Agent
    Release
    Team

  3. Stage 2

    Software Factory

    AI agents work through every step. Your team approves the plan and the result.

    Plan
    AgentApproval
    Build
    Agent
    Release
    AgentApproval

Overview

Your knowledge goes in, tested features come out.

The Software Factory is a ready-built software kit on proven frameworks. The Workbench makes your knowledge usable for AI agents, and the Factory builds every ticket from it in the same way. Both run in your systems.

  1. 01

    The Workbench prepares your knowledge

    It reads code, screens, data and documentation. Your experts decide in dialogue, and every statement is backed by evidence.

    Your team approves the ticket

  2. 02

    AI agents plan, build, test and review

    Specialized AI agents work in your Jira, GitHub and pipelines. A ticket goes back until no finding is open.

    Your team approves plan and merge

  3. 03

    Tested features, ready for release

    You get code with tests and documentation, plus a monthly report with KPIs. Code, data and know-how stay with you.

    Your team decides on the release

Approach

We start with one pilot team on one technology stack.

We work alongside your team until it steers the Factory itself.

  1. 01

    We check whether the Factory fits

    We analyze the architecture, security and backlog of your system. At the end, you decide whether and where the Factory starts.

    Where the Factory startsExample

    • Features

      Checkout

      First slice

    • Interfaces

      ERP, payment

      Second wave

    • Reports

      Export, KPIs

      Second wave

    • Legacy

      Batch jobs

      Groundwork

    • Content

      Shop, prices

      With the team

    • Architecture

      Platform

      With the team

    6 ticket groups assessedUnder reviewYour team

  2. 02

    We set up the Factory in your systems

    We fit the Factory to your systems and processes. It works in your IT environment, with your permissions and security rules.

    How a ticket runsExample
    1. 1 Specify Agents
    2. 2 Ticket approval Your team
    3. 3 Plan Agent
    4. 4 Plan approval Your team
    5. 5 Build, test, review Agents
    6. 6 Merge approval Your team

    Back until no finding is open

    System 2 of 4 connectedUnder reviewYour team

  3. 03

    We build with your team

    Your pilot team works on real tickets with us from the start. That is how it learns to steer the AI agents.

    Ticket, Examplerunning since today

    T-214 Check the interface to the ERP

    • Ticket read, code and docs checkeddone
    • Plan ready, waiting for approvalYour team
    • Code and testsrunning

    Approvals at ticket, plan and mergeUnder reviewYour team

  4. 04

    Your team carries on alone

    We hand over documentation and the full source code. Your team runs the Factory itself and extends it to further systems.

    Handover

    Source code
    Complete, with documentation
    Acceptance
    By your team
    Operation
    In your IT environment

Why Etribes

We deliver speed your company can actually absorb.

Soon many providers will be able to set up a software factory. What counts for you is how fast features go live, whether your organization can carry that pace and whether your partner knows your business.

Team in a working session, a board on the screen, laptops on the table

How to measure us

Speed
The Factory is already built and runs in our own projects. The monthly factory report shows how fast your features go live.
Organization
We prepare your product team, business units and sales for more releases, so the pace reaches your customers.
Mittelstand
We know German mid-sized companies from our own projects and have founded and run companies ourselves.
Control
Your team approves ticket, plan and merge. Code and data stay in your environment.

Results

More features in less time.

Every ticket is tested automatically before release, so higher speed does not come at the cost of quality.

−95 %

Time to live per feature on the target path: 3 days instead of 8 weeks

−50 %

Duration of a legacy migration: 18 instead of 36 months

−70 %

Cost of that migration: €3.76m instead of €12.6m

+32

Developers free for the roadmap, 32 of 40

Example calculation: 40 vs. 8 developers, 36 vs. 18 months, €105,000 per developer-year, plus €2.5m for set-up and AI usage. From our projects: duration and team size drop by half and more.

You get

  • A Factory ready for use in your IT environment
  • Faster releases with tested features
  • KPIs such as lead time per ticket, cost per feature and test coverage
  • A team that runs the Factory on its own

FAQ

What clients ask us first.

Another question?

Write to us
01 What is a software factory?

A Software Factory builds software with AI agents. Specialized AI agents plan, build, test and document every ticket in fixed steps. Your team approves the ticket, the plan and the merge. The Etribes Software Factory runs in your IT environment.

02 What is agentic software development, and how is it different from AI coding tools?

Is your backlog growing despite AI tools? Coding assistants speed up writing code, but specifications, tests and releases still take your team's time. In agentic software development in the Etribes Software Factory, AI agents work through every step of a ticket. Your team approves at three points: the ticket, the plan and the merge.

03 Where do people decide when AI agents build software?

At three fixed points. Your team approves the ticket before the AI agents plan, the plan before they build, and the code before it is merged. These approvals are set in the code of the Factory and do not depend on the AI model.

04 How do I clear my backlog faster?

More AI tools alone will not clear your backlog, because specifications, tests and releases still take time. Speed up your development by letting AI agents handle the whole chain of a ticket while your team approves at fixed points. That is what Etribes built the Software Factory for. It starts with an analysis workshop on your backlog.

05 Who is a software factory for, and how does it start?

The Etribes Software Factory suits IT teams whose backlog grows faster than they deliver. We start with one pilot team on one technology stack. After diagnosis, set-up and joint work on real tickets, we hand over the Factory and your team runs it on its own.

06 How safe is software development with AI agents?

In the Etribes Software Factory, code and data stay in your IT environment. Each AI agent has exactly one task, and every step is documented in the ticket and the pull request. Your team approves three times: the ticket, the plan and the code before it is merged. We test every ticket automatically before release.

Inquiry

Let’s look at your tickets together.

Together we check which of them the Factory can take over and how much time your team gains.

Find the bottleneck

Stefan Luther CIO