I build and lead technology that holds up in the real world.

For more than 25 years, I have worked where product, technology, and operating decisions meet: from one of Australia’s first online bookmakers to regulated platforms, AI-enabled operations, and independent products.

InfoAddict is the public record of that work. It brings together the systems I have helped build, the experiments I can show, and the questions I keep testing.

Researching the work with an AI agent? The public evidence brief is complete on the page, with optional plain-text, JSON, and read-only MCP formats.

Portrait of Dan Crane
Technology, product, and AI leadership grounded in practical delivery.

A career built around consequential systems.

I started in 1996 helping stand up one of the world’s first online bookmakers. At Tatts Group, I identified the need for a centralised digital function, built the case for it with the board, then led the team from three people to more than 80. That work helped deliver tatts.com as Australia’s first combined wagering and lotteries platform, reaching A$1bn annual turnover.

At Horizon State, I helped build an enterprise decision-making platform and later returned as COO to operationalise the business and own the product roadmap. At AnRKey X, I led digital product and technology operations for a gaming platform. At Presper Labs, I led technology strategy, product delivery, AI deployment, and IT operations across five concurrent brands.

The thread is consistent: understand the operating reality, make the technical choice explicit, and carry the work through to something people can use.

High-availability delivery
Regulated, customer-facing systems where reliability, speed, and operational clarity matter together.
Product to operating model
Work that links strategy, governance, delivery, commercial decisions, and the team that has to sustain it.
Applied AI
Model, workflow, and automation choices tested against an actual job, risk boundary, and measure of usefulness.

How I work

Start with the operating reality. Make the technical choices explicit. Build something people can use and sustain. These are the principles I return to across teams, products, and experiments.

Systems under pressure

Start with the constraint, not the next vendor, roadmap, or process. Delivery rhythm, decision rights, architecture, and hand-offs all shape whether a system can recover.

  • Technology and delivery risk
  • Team operating rhythm
  • Architecture and vendor decisions
See the Tatts Group work

AI as operating change

Useful AI work joins a real problem to the right model, workflow, governance, and measure of value. A model demonstration is not a strategy on its own.

  • Problem and workflow selection
  • Model and tool fit
  • Governance, evaluation, and adoption
See Upgrade the System

Durable digital systems

Runtime boundaries, content, data, performance, cost, and observability belong in the same decision. The aim is a product that stays understandable as it changes.

  • Cloudflare-native application architecture
  • Performance and resilience
  • Operational clarity and cost awareness
See Aunty Archibald

Explore the evidence.

Explore the projects and career history, or take a closer look at the tools and prototypes I am testing.