Features late, wrong or broken — even with AI?
The right features, predictably delivered — release after release.
In a client's words
Tom helped our team shift its focus from searching for solutions to consistently delivering results.
His systematic and gradual approach first established the fundamentals, making our output stable and predictable, before helping us steadily increase both performance and maturity.”
Cargobase is a logistics tech scale-up with Singapore headquarters and engineering in Kuala Lumpur: 10 people across 2 product and engineering teams. I have coached them since September 2025.
When I started, delivery was unpredictable, with frequent quality problems.
What changed
- A structured way to plan, build and test.
- Coaching for the leads.
- AI-assisted coding with stronger checks.
Not the right features.
Work gets built, but it doesn't move the numbers that matter.
Quality keeps biting back.
Releases bring bugs, rework and firefighting.
Delivery is unpredictable.
What was planned isn't what arrives, and nobody can say when it will.
AI can make you faster. It can't make you right.
It amplifies the system you have. What's usually missing isn't a person: it's structure — a regular way to plan and ship work, a shared standard for quality, and checks at every step from idea to release.
Product Engine Diagnostic
Find out what's really holding your team back — in one half-day.
One half-day with your team, followed by a written diagnosis within 2 working days.
On the day
On the day, nobody spends more than an hour with me. I talk to your founder or CEO, head of product or engineering, and 2–4 colleagues. No access to your code is needed.
I look at where leaders and team disagree, how ideas become features, and how AI-assisted code is checked.
What you receive
- Written diagnosis within 2 working days: top 3 root causes, whether to hire or fix structure first, first 90-day steps.
- One-hour walk-through with you and your leads.
What happens next
You can act on the written diagnosis yourself. If you want me alongside your team, coaching runs for a minimum of 3 months, typically 4–8 hours a week, at a fixed monthly fee agreed in writing first. Before it starts, I agree 3 success measures with you.
Prefer to read it first? Ask for the two-page overviewPrice and terms
- Credited in full against coaching if you start within 30 days of the walk-through.
- Payment within 15 days of the walk-through.
- Confidential: I sign a non-disclosure agreement first.
How I'd work with you
- Diagnose: one half-day.
- Agree 3 success measures up front.
- Coaching alongside your team: minimum 3 months, typically 4–8 hours a week, fixed monthly fee agreed in writing first.
I don't replace anyone: I coach your people to solve their own problems, then step out.
I ask the hard questions that are difficult to ask from inside a team, and I keep it respectful. That is often what gets a stuck problem moving.
“Tom asks the tough questions and creates an environment of respectful accountability that drives teams to deliver.”
Thomas Lozza (Tom)
Independent product transformation coach, Kuala Lumpur.
Hi, I'm Tom. I help product teams ship the right features, predictably.
21 years building software, from engineer to Chief Product Officer at Accendo Technologies, where I saw planned work delivered rise from 30% to above 80%, and clients lost each year fall from over 20% to under 10%.
I work alongside product and engineering teams at product companies in Kuala Lumpur.
Master of Science, ETH Zurich, Switzerland.
I have also trained 150+ founders in Malaysian accelerator programmes.
Common questions
Do you need access to the code?
No. No access to your code is needed. I look at how work moves from idea to release: how it is planned, built, tested and shipped, using what your team already has, such as the backlog, the release history and the bug reports.
Should I hire a head of product first?
The written diagnosis tells you whether to hire or fix structure first.
Is it confidential?
Yes. I sign a non-disclosure agreement first.
Where does it take place?
I'm based in Kuala Lumpur and happy to come to you. Coaching is mostly on site with your team, with remote follow-up in between.
Who is it for?
Best for companies with a live product and an in-house team. Not a fit before launch.
Who is it not for?
- Teams that have not launched a product yet.
- Companies whose software is built entirely by an outside agency.
- Anyone looking for someone to run the team. I coach your people; I don't replace them.
Not sure whether this fits? Let's talk for 30 minutes.
I'll tell you honestly whether I can help — and if I can't, who might.
I reply within one working day.
Prefer to write first?
Tell me what's going on.