I work with software teams and their leaders — and with construction, property and industrial firms who are building software in-house for the first time.
Book a free discovery callYou've probably seen one of these.
Everyone reports. No one talks. It's a calendar item, not a team.
One brilliant engineer holding the whole thing up. That's a risk, not a strength.
Ten productive people, pulling ten directions at once.
Most engagements begin with the review.
Two to three weeks with your team — survey, interviews, watching how you actually work. You get a written report and a prioritised roadmap worth acting on, debriefed with leadership.
Twelve weeks embedded with your team — fortnightly sessions, ceremony observation, leadership syncs. This is where change holds.
For firms without software DNA: hiring plan, team structure, tooling, vendor guidance, and a 90-day operating plan — so your first team isn't your most expensive mistake.
Everything I offer, from assessment to leadership development, is on the services page.
My career in five lines: games, payments, media, then ten years leading construction SaaS teams — software people phoned about within 30 seconds of downtime. Now I coach.
Games, then payments, then media, then a decade running engineering for construction SaaS — software used to estimate most of the buildings in Australia, where customers phone within 30 seconds of downtime.
I kept a team whole through two changes of ownership, formed an ML team, and spent a year retraining existing engineers for AI. Now I coach teams full time.
PSM · PSPO · Certified Agile Leadership · Heart of Agile
Free, 30 minutes. You describe the team; I tell you what I'd look at.
2–3 weeks. A written report and a prioritised roadmap.
Coaching, guardrails, or building your first team — from the report.
A free guide to running a small software team in the AI era. By email.