Team Building

You have built the team, delivered for customers, and the fires are starting to overwhelm you. I give small teams the mechanisms to minimise surprises and grow without growing pains.

My Approach to Team Building

It is not enough to hire the best people and give them a roadmap. Small engineering teams typically lack the technical foundations (testing, operations, alarms, metrics), the process foundations (project management, ticketing, reporting) and the human foundations (1:1s, growth direction, leadership support). It is never easy to know which to prioritise first, or for how long. You need to deliver. You can't spend all your time sharpening your axe.

The biggest risk isn't a missing process. It's not knowing it's missing until you lose an engineer over it. I help you see what's missing, prioritise what bites first, and build the systems (and the reasons behind them) your team will keep using.

I have been on both sides of this. At Plentify, I was the first engineer and helped take HotBot from an idea into thousands of homes. I saw firsthand what is missed when you are focused on building. As a manager at AWS, I built those processes for an 8-person Security team, while mitigating 50+ embargoed security events with zero breaches. I know what is needed first and what can wait.

Team Building Outcomes

• Faster delivery: when teams are aligned and their needs are met, they can focus on delivery.
• Higher quality: improved team cohesion and ownership produces high-quality deliverables.
• Predictable timelines: standardised mechanisms and processes allow for repeatability and predictable delivery.

How It Works

• Diagnose: a free 60-minute call to identify the gaps.
• Prioritise: we agree which gap bites first and scope the engagement.
• Build: I embed with your team for 3 to 6 months, in person or remote.

Currently working with one startup. Onboarding another in June.

The diagnosis is free. Scope and price depend on what we find together.