Inter Orbis
Briefings

Briefing report: Cycloid 10 November 2026

16 November 2026

Summary

These are interesting times for software tooling vendors, who can both use AI in their product development, and support their enterprise customers as they increase their own use of AI in software creation and deployment.

Software process tools vendor Cycloid has taken this bull by the horns and rebuilt its platform from scratch in under a year. It has released a Beta version of the revised product.

The rationale behind this decision acts as a template for other software tooling vendors, and raises questions for enterprise decision makers.

Market Context

Cycloid operates in the tooling space for software creation, deployment and management. If I’m honest, based on my historical briefings with the company, I think it has struggled to find its core – it started as a more generic development platform, then shifted towards FinOps as this increased in popularity.

This is not unusual for software development and management tools like this. Three things have long been true of this space.

  • A relatively small amount of tooling can go a long way – as a result, tools are often adopted and run with, even as they hit growing pains of expanded adoption.
  • Tooling and good management processes go hand in hand. Organisations that are good at what they do see tools as an enabler to best practice.
  • Vendors either go top-down with a strategic and expensive consulting play, or bottom-up with a freemium solution for developers and teams.

The challenge lies in the middle of each of these statements – the Goldilocks level of tooling, practice and strategy. It also lies with departmental and project managers responsible for, say, mobile apps or current accounts. No wonder that maturity models and adoption indices are rife.

These are the heady waters in which Cycloid has been swimming, with success not guaranteed. Meanwhile, AI has changed how we build software. As I have written in Dispatch #1, organisations can build software faster but this creates longer review cycles, or code that nobody understands. Unclear as yet is the golden path through what software development is becoming.

Every tooling provider including Cycloid faces a clear challenge: how to support the customer need for visibility, governance, efficiency and developer productivity, even as the specifics change under everyone’s feet.

The Briefing

Whilst Cycloid was keen to demonstrate its product, first let’s consider how it got to today: by rebuilding its core product offering from scratch, based on what it understood of its domain, customer needs and channel-based routes to market. The approach was:

  1. One person spent three months on a first layer of specifications.
  2. Ten people spent three months on a full specification, in collaboration with Cycloid’s ten largest customers.
  3. Fifty developers then spent six months building the product, with AI tooling support.

A big lesson learned was that the specification phase became the hardest part of the process (as I quipped, “It’s almost like requirements engineering is a thing”). Cycloid now also treats developers as architects, operating at a broader level than traditional programmers.

The resulting platform offers a flexible software composition and delivery tool, incorporating elements such as blueprint-based deployment, GitOps-like drift detection, cloud resource inventory management, access policy and approval-based build management. The product is AI-enabled (now table stakes, of course) and also offers a plugin library, such that partners and customers can quickly add their own.

Why it matters

As every software company can now create functionality quickly, functionality no longer defines competitive advantage, so how can such companies win? In Cycloid’s case, it has majored on two pillars:

  1. Speed of response to a real need. Having established a platform-based architecture, Cycloid can add functionality more quickly and easily, for example a ticketing system. Just as important is restraint: “Less is better than more.”
  2. Domain expertise. Cycloid put its largest customers inside the specification, and it knows the regulated enterprises and public bodies it serves.

Clearly these are both important, and other software companies should take note. I would add a third:

  1. Customer success should be driven by services. Getting the functionality to work in the client’s environment becomes a significant differentiator.

Depending on their business model, many vendors have moved away from services, relying on partners or letting people pick up the product and run with it. In this changing market I believe a proactive services play becomes increasingly important for longer-term client traction. In other words, if everyone sells the same thing, organisations will buy from a company that understands and adapts to their unique models.

Plus, many companies could learn from Cycloid’s own experience of rebuilding with AI. This was a big bet, which came with no guarantee of success. But the future game is about raising the probability of success through continuous re-alignment with customer needs, and Cycloid stepped up to that.

What to do about it

For enterprise users as well, this question of vendor alignment becomes increasingly important. Decision makers can afford to become more discerning, not least because AI-powered tools enable increased discernment without requiring a hugely expensive subscription to an analyst firm.

Already it is possible to run scenarios that enable you to rationalise your tooling and models, and no doubt this will reduce your tooling costs. Probably the bigger bang per buck will come from putting in place the tooling you need to reduce infrastructure costs – make those on-prem versus cloud-based decisions, or migrate from one provider to another, for example.

Ultimately though, the biggest changes are going to be in the nature of supplier relationships. The notion of “intelligent customer” has existed since the early days of outsourcing – so:

  1. Start by getting your own house in order, understanding what creates your own business advantage in this AI age.
  2. Identify suppliers and integrators with expertise in your domain, potentially over those with the longest feature list.
  3. Review your procurement processes to ensure they position vendor responsiveness as a first-class citizen.

This latter point goes to the heart of procurement, given how requests for proposals tend to be written – hard (feature-based) requirements as mandatory, and softer (agility-based) requirements as differentiators. It’s too early to say whether this model will flip, but let’s not rule it out.