Software delivery consulting
Ship fast. Don't break things. Make it count.
If your team is shipping slowly or breaking things, I can help. We'll measure where you are with DORA metrics, the research-backed standard for software delivery, find what's holding you back, fix it together, then measure again to make sure it's working and moving your business forward.
I'm Tristan Barrow. I've devoted the last 5 years of my life to solving one problem. I help dev teams ship fast without breaking things and ensure what's built actually counts toward the company's bottom line. Book a call to see if I'm a good fit for you.

How it works
We start with the gold standard for determining development team productivity. How fast is my team going? How much time does my software spend out of order? Is the work my dev team is doing moving the business forward?
- 01Measure
- Four DORA metrics cover speed and stability, and product owner task cycle time shows whether the work moves the business. Measuring and regularly tracking these five will help us determine success.
- 02Diagnose
- Now that we can see our problem in the numbers, it's time to find the bottleneck keeping us there.
- 03Fix
- Next, we'll work together to implement the solution.
- 04Repeat
- Problem solving is a process of iteration. We'll remeasure to see how well our solution worked and course-correct if we need to.
On the name
Robur Ignis, the strength to withstand the fire.
In Latin, robur means oak, the hard timber, and also strength. It's where the English word robust comes from. Ignis is fire.
AI is making things feel unstable right now, and the name has two meanings for me. It's the strength to withstand the fire, and also the strength of the fire. Together they stand for a balanced approach, one part realism and one part optimism.
From people I’ve worked with
About me
I'm Tristan Barrow. I've been building software for over a decade and I've been coaching and consulting for half of that. I still write code every day, so my advice comes from hands-on work, not theory.
I've intentionally tried to dabble in everything related to computers so I can have a high-level understanding of the stack from bottom to top. I've built processors from transistors. I've built assembly languages to run on those processors. I've written compilers to compile high-level languages down to assembly, and much more.
I've spent thousands of hours in the last 5 years trying to answer a single question. How do I make dev teams go fast without breaking things? It's a complicated enough question that there isn't a single, simple and satisfying answer, but I understand the problem and how to iterate a company towards its own solution.
Book a free 60-minute consultation
Tell me how your team ships today and where it slows down. Or email tristan@roburignis.com.