ABOUT

I build AI systems that ship, scale, and stay reliable in the real world.

I help teams turn messy AI ideas into operational systems: clear inputs, safe fallbacks, measurable outcomes, and workflows people actually use.

Based inSydney
FocusAI systems, automation
StylePractical, calm, rigorous

Timeline

The chapters that shaped how I build systems.

2010 to 2014

Education

Learning the fundamentals before real systems
Context
  • Completed a Bachelor’s degree in Information Technology
  • Built core programming and systems fundamentals
  • Learned the language that later made product and systems work possible
Learnt
I learned that fundamentals compound. The ability to reason clearly about systems becomes more valuable as complexity increases.
EducationLearning
2014 to 2017

Foundations

Learning how to make (and break) real systems
Context
  • Built and shipped full-stack features in production environments
  • Debugged real failures, edge cases, and performance issues
  • Worked close to code, infrastructure, and system boundaries
Learnt
I learned that systems rarely fail because of missing features. They fail because of unclear assumptions, weak boundaries, and poor handling of edge cases.
Software DevelopmentCoding
2017 to 2019

Product

Deciding what actually matters
Context
  • Moved closer to product and stakeholder decisions
  • Translated ambiguous requirements into buildable scopes
  • Managed trade-offs between speed, quality, and impact
Learnt
I learned that the hardest part of building products is not execution. It is deciding what problem you are truly solving.
ProductTrade-offs
2019 to 2023

Outcomes

Shipping is only the beginning
Context
  • Owned systems with real users, volume, and consequences
  • Handled operational issues after launch
  • Worked across product, operations, and delivery
Learnt
I learned that shipping is the start of the problem, not the end. Systems must be designed for monitoring, recovery, and human workflows.
OperationsDeliveryLeadership
2023 to now

Business Owner

Building systems where decisions have real cost
Context
  • Owned a solo business across sales, delivery, and execution
  • Designed AI assisted workflows used in live operations
  • Built automation across data pipelines, tools, and human handoffs
  • Made daily trade-offs across speed, cost, reliability, and risk
  • Delivered continuously without buffers, teams, or safety nets
Learnt
I learned that AI is not the product. The system around it is. Guardrails, feedback loops, cost control, and human override define whether AI creates leverage or debt.
BusinessOwnershipAISystems

What that journey gave me

Capabilities that show up consistently across my work.

AI product strategy
Turn messy goals into clear user jobs, constraints, and measurable outcomes.
Automation systems
Design end to end workflows across tools, data sources, and handoffs.
AI experience design
Shape interactions that feel predictable, useful, and low friction.
Delivery and governance
Ship with guardrails, observability, and practical QA for real operations.
System design thinking
Map flows, edges, and trade-offs like a platform, not a single feature.
Execution under constraints
Move fast without breaking trust, by cutting scope intelligently.

What I am focused on now

The direction I am leaning into as AI systems become more operational.

Cost-aware AI product decisions
Human-in-the-loop workflows that scale
Failure-safe automation patterns
AI systems that feel calm and predictable

If this resonates

If you are building AI systems and want them to feel calm, reliable, and measurable, we will probably work well together.