My services
I work with founders and tech leaders whose teams are capable but stuck. How I help depends on what you need. A sounding board when you're making decisions alone. A delivery risk scan when you need a clear picture of what's going wrong. Or someone embedded in the team until it runs without you.
Sparring
You're the person making the product calls. What to build, what to cut, what to promise the client. And you're doing it alone.
You don't need a coach. You don't need a framework. You need one hour with someone who's been in the seat and will tell you what they actually think.
People bring all kinds of things to these sessions. A roadmap that feels wrong but they can't explain why. A stakeholder conflict they need to think through. A backlog with 200 items and no idea which 5 matter. A hire they're not sure about.
60 minutes. Video or in person. You get follow-up notes with anything we discussed.
Book when you need one. No subscription, no commitment.
I've spent nearly 10 years in product and delivery across SaaS and marketplaces. I'm not going to give you a framework. I'm going to tell you what I'd actually do.
Delivery risk scan
You know something is off. Projects that were 'almost done' three weeks ago are still 'almost done.' Deadlines move but nobody flags it until it's too late. Your planning meetings are based on gut feel and best guesses, and the quarterly review is where you find out how wrong those guesses were.
The worst part: you don't have a way to see it coming. You find out when it's already too late to do anything meaningful about it.
This scan changes that.
How it works
We start with a conversation. I need to understand your teams, your initiatives, and what you've promised to whom. Then I talk to the people closest to the work, usually someone in product and someone in engineering. Data tells you what is happening. People tell you why.
I connect to your issue tracker and analyse your team's actual delivery data. I map how work flows through your teams, identify where it gets stuck, and use your historical completion patterns to calculate the real likelihood of hitting each deadline. Not a best guess. Not an average. A forecast based on how your teams actually work.
The whole process takes one to two weeks.
What you get
A report you can take into your next leadership meeting and make decisions with. Per initiative: whether it's on track, the probability of hitting the deadline, where work is getting stuck, and what's causing it. Plus a prioritised list of what to change first and why.
This is not a dashboard you need to interpret. It's a clear answer to 'are we going to make it, and if not, what do we do.'
What I need from you
Access to your issue tracker, Jira or Azure DevOps. I only need workflow states and transition dates. No ticket descriptions, no comments, no sensitive content unless you choose to share it. You control exactly what gets exported.
What's not in the report
Implementation. The scan tells you what's at risk and what to change. It doesn't fix it. That's deliberate. Some teams take the report and act on it themselves. Some bring me in to help. Either way, you're making decisions based on your team's real data instead of opinions and estimates.
Some teams use this once to get clarity. Others come back quarterly to track whether things are improving.