Ibis Flow

24/05/2026

GitHub has landed at Ibis Flow 🚀

Only last week I wrote about solid architecture being the basis for scale.

After two weeks of building, testing, refining workflows, and tightening the setup experience, I think we just proved the point.

What started as "let’s add GitHub as another provider" also became a really useful opportunity to improve the product around it: better setup flows, cleaner connection management, smoother provider switching, and fewer little moments where users have to stop and think.

A lot of that comes from having had the privilege to work with some brilliant product and UX minds over the years. Those lessons keep showing up in the way Ibis Flow evolves.

For GitHub teams who have not bumped into Ibis Flow yet:
You can now bring your GitHub work into Ibis Flow and use it to collaborate, craft, deepen, estimate, and prioritise ideas before the work starts.

And for AI-native teams, this opens up a nice workflow:
With your domain experts, shape the work properly in Ibis Flow, then label the ticket in GitHub to trigger your AI engineering workflows with better context.

14-day free trial is live. Message me if you need longer.

Love what you do, do what you love 👍

16/05/2026

Software architecture is as important as ever today if you want to scale your business and not miss opportunities.

Ibis Flow started with supporting only Jira; which was simply opportunistic because I was working with a client at the time and speed was more important to get the products first capabilities out the door.

Obviously things didn't stop there, but Jira as a first class citizen in Ibis Flow had not only outlived it's usefulness, it had also made itself very much at home.

It was in our UI, in our application domain, in rules and logic. Everywhere..

Bringing in a new provider (Azure DevOps for a pilot customer) meant tidying all this up.

Finding all of the if/else statements, all the logic branching in our CQRS or UI, and pushing all of these providers leaks back into the provider domain and out of the application domain.

We have such an elegant and tidy system now, we work with keyed services with dependency injection, we receive an ITicketProvider[X]Service and can move on with the application logic. My personal favourite is the ITicketProviderCapabilitiesService which lets every implementation describe itself.

Our abstractions have helped us to introduce the 3rd provider, our own, within the space of a couple of weeks. Now it doesn't matter if you are on GitHub, GitLab, Jira AzureDevOps, or want to use Ibis Flow as your provider.

Businesses start quickly with monoliths and quick/working solutions, but they scale with stable, reliable abstractions that allow their staff to focus on fixing problems, creating new capabilities, and thus servicing their market.

I am very happy with what we can achieve now, no barriers to entry for new customers, and the ability to handle "the next ticket system".

Drop me a line, and let me know what ticket system you're using and would like to try out Ibis Flow with.

14/05/2026

𝗕𝗶𝗴 𝗜𝗯𝗶𝘀 𝗙𝗹𝗼𝘄 U𝗽𝗱𝗮𝘁𝗲 🚀

You can now use 𝗮𝗹𝗹 𝗜𝗯𝗶𝘀 𝗙𝗹𝗼𝘄 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀 without connecting Jira or Azure DevOps first.

That sounds simple, it was not 😅

Until now, many teams signed up, got curious, and then hit the same wall: “Connect your ticket system.”

And in a real company, that is not just a button.

It can mean DPO checks, CISO questions, ISMS requirements, ISO policies, internal approval, procurement, and someone asking why a planning tool needs access to Jira before they have even seen the value.

So we removed that wall, you can now start directly in Ibis Flow.
✅ Create tickets
✅ Shape ideas
✅ Collaborate with the team
✅ Estimate
✅ Prioritise
✅ Plan

No Jira required.
No Azure DevOps required.
No integration required just to understand what the product can do.

For teams already using Jira or Azure DevOps, those integrations are still there, but they are now exactly what they should be: 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻𝘀, not the starting point.

This is a big step for Ibis Flow, because it means teams can explore the value first and connect their systems later.

And for teams that do not need a full ticket system, Ibis Flow can now stand on its own as a lightweight way to turn ideas into better planned work.

Try Ibis Flow without connecting anything:
https://ibisflow.com

11/03/2026

11/03/2026

🚀 New in Ibis Flow: Prioritisation

When we started building Ibis Flow, we focused on estimation.

But after speaking with dozens of product teams, something became clear:

👉 Estimation is rarely the real problem.

You can estimate perfectly, plan carefully, and still deliver the wrong thing if the priorities are wrong.

Most teams don't struggle with ideas.

They struggle with deciding what matters most.

So we built a new capability in Ibis Flow to help teams prioritise work with context, not guesswork.

With the new prioritisation features you can:

• collect input from stakeholders asynchronously
• compare options using structured decision techniques
• capture the reasoning behind decisions
• avoid the “loudest voice wins” problem

Better conversations.
Better decisions.
Better products.

If you're a Product Owner, PM, or team lead trying to cut through the noise of feature requests and competing ideas, this is for you.

👇 See how it works
https://ibisflow.com/features/prioritisation/

10/03/2026

New in Ibis Flow: The AI-powered PO Assistant

Let’s face it, writing detailed tickets can sometimes feel like a chore. But ambiguous tickets lead to endless refinement sessions and misaligned expectations.

We want to fix that.

Imagine selecting a ticket and instantly seeing:
✔ An evaluation of its readiness for refinement
✔ What context or acceptance criteria might be missing
✔ An interactive Q&A tailored to your existing description (or just the title)
✔ A stronger, rich-text story specification generated in minutes

Once your ticket is sharpened, you can share the recommended questions, complexity signals, and risks directly with your team via Slack or MS Teams before the session even starts.

It effectively gamifies the ticket crafting experience, making it genuinely fun to create better specifications.

Because simply put: better tickets avoid guesswork and drastically increase your team's chances of delivering exactly what you intended.

We've packed a lot of new value into Ibis Flow recently, and this is a feature I'm really excited to share.

You can check out how it works and give it a try here: https://ibisflow.com/features/po-assistant

09/03/2026

Are we accidentally building the new COBOL era of software engineering? 🤔

Right now, AI is accelerating output for senior developers, but it’s masking a massive problem: the hollowing out of junior roles and the loss of institutional knowledge.

When the legacy systems break, who is going to know how to fix them?

Our founder, Aaron Gregg, just published a deep-dive into the "Innovation Paradox"—why true scaling requires "boring" stability, and how teams can bridge the gap between isolated AI tricks and resilient, systematic workflows.

If you care about the future of your engineering team, this is a must-read.

Read the full article here: https://www.linkedin.com/pulse/why-ai-acceleration-requires-boring-stability-next-generation-gregg-qfoff
(Or check the comments below!)

The software engineering industry is currently experiencing a profound identity crisis. On one hand, AI development tools have unlocked unprecedented levels of individual productivity.