About Orber & Co
Hi, I'm Orber. I'll be the one running your audit.
I've spent 12 years inside engineering teams, and the last 9 of them leading people. I started out writing the code, then grew into leading the teams who write it, through delivery, technical management and engineering management. Most recently I ran engineering for a B2B software companies, reporting to their CEOs.
Over and over, I've seen founders describe the same problem: engineering feels slow and expensive, and nobody can say exactly why. It's rarely the engineers. It's the system around them: how work is chosen, how it flows, what it costs to run, and who owns what.
Orber & Co exists to find those problems quickly, put numbers on them, and hand you a plan your team can actually run.
In tech
12+ yrs
Leading teams
9+ yrs
Track record
- 21 → 3 days
- Delivery cycle time
- £432k → £240k
- Annual AWS spend
- ~90%
- Fewer serious production incidents
- ~100
- Engineers hired
- Six-monthly → daily
- Release cadence
- 2×
- Team velocity within six months
- ~60%
- Better estimation accuracy
- £2M+
- Contract renewal after a turnaround
Career
From writing the code to running the team.
Developer, tech lead, engineering manager. Those three lenses are what the audit uses. Employers and clients stay anonymous: you'll get the same discretion.
Senior Engineering Manager
B2B SaaS · reporting to the CEO
Full ownership of engineering delivery and operations. Cut serious production incidents by ~90% and moved from six-monthly releases to daily deploys.
Engineering Manager
Digital product studio · hospitality and energy brands
Led multiple squads across client-facing platforms and internal products, and delivered AI-driven features that grew client accounts.
Senior Technical Manager
Fintech · post-acquisition
Led ~20 engineers across 3–4 teams and merged two engineering organisations into a single operating model.
Engineering Tech Lead
Automotive e-commerce · 15 engineers across time zones
Turned around a failing engagement and secured a £2M+ contract renewal.
Developer → Tech Lead
Enterprise SaaS and regulated environments
Where it started: hands-on engineering, from IC to leading teams.
BSc Software Engineering, Lancaster University
How I work
Data before opinions
Findings come from your repos, tickets and bills. If I can't show the evidence, it doesn't go in the report.
Fix the system, not the people
Slow teams are almost always slowed by process, structure or tooling, not effort.
A plan you can run without me
Every recommendation has an owner and a success measure. You're never dependent on Orber to act on it.
Honest, even when it's awkward
You're paying for an outside view. Sometimes that means saying the thing nobody inside can.
I still write code. I design, build and run two live consumer apps of my own, so recommendations about tooling and delivery come from someone who ships, not just someone who manages.
Next step
Let's look at your engineering.
Start with the free 3-minute scorecard, or book a 30-minute call. No pitch deck, just your questions.