Beyond the backlog

Software houses, IT services firms and the consultancies that build and run systems for everyone else: 965 000 firms in Europe. What they all have in common is that the hours worth selling are the ones an engineer spends building.

The trouble is how few of those hours there are in a week. Before anyone can build anything, somebody has to triage the overnight tickets, keep the documentation in step with what shipped, and chase the client for the access that has been missing for three weeks. None of that is the work, all of it is required, and most of it lands on the people whose time is the most expensive in the building. Agents are unusually good here. For example, reading the night's tickets and coming back with the six that are the same bug. Drafting the release notes from what was actually merged. Asking the client for the missing access every Tuesday until it arrives, which no one enjoys doing and everyone forgets.

These firms could build an agent themselves. The question is whether they should spend their engineers on it, and on keeping it running once it is built, rather than on the work their clients pay for.

To that end, our embedding process puts the person at the end of every chain. For example, your agent proposes and never merges. Everything it asserts is traceable back to the ticket or the commit it came from. And it works from a copy, so the system it read is the system that is still there afterwards.

If you're interested in the advantages an agent can give your business, click here to let us know more about your business.