Skip to content

Experience · Systems · Architecture · Data · AI

Systems I've Worked On

I've spent much of my career working on systems where data, technology, business rules, and external services have to come together.

From fintech and credit decisioning to data migrations, APIs, integrations, white-label platforms, automation, and AI, much of my work has involved understanding complicated systems and figuring out how the pieces should fit together.

  1. Business Problem
  2. Data
  3. Systems
  4. Integrations
  5. Decisions

FINTECH · CREDIT · DATA

Credit Decisioning & Scorecard Optimisation

Worked on credit decisioning systems where multiple sources of financial and customer data had to be brought together to support lending decisions.

  • Credit decisioning
  • Scorecard optimisation
  • Data ingestion
  • Data modelling
  • Decision rules
  • External APIs
  • Financial data
  • Automation

Building the scoring model itself was the easy part. The harder problem was figuring out which data actually mattered, then pulling it in from sources that each had their own format and their own way of being unreliable at exactly the wrong moment. And the rules kept changing - what counted as relevant one quarter didn't always hold the next, so the integrations had to be built to bend without breaking.

  • KYC Provider
  • Open Banking
  • Credit Reference Agency
  • Accounting Platform
Credit Decisioning
Credit Result

DATA · ARCHITECTURE · MIGRATION

From Third-Party Platform to an Internally Owned System

Worked on the migration of data and business processes from a third-party platform into an internally owned system, including a complete rebuild of the underlying database.

  • Data migration
  • Database architecture
  • Data modelling
  • Schema design
  • Legacy/third-party systems
  • Data transformation
  • System redesign
  • Internal platform architecture

Copying the records across was never the hard part. The real work was untangling a data model that had been shaped by someone else's constraints, then deciding what the business actually needed instead of just rebuilding the old limitations in a new database.

  1. Third-Party System
  2. Migration & Transformation
  3. Internal System
  4. New Database

Moving away from a third-party system creates an opportunity to rethink the underlying model, rather than simply reproduce the limitations of the old one.

INTEGRATIONS · API · ARCHITECTURE

Connecting Systems Through APIs

Designed and worked with APIs that connected internal systems with external providers, partners, and clients - including KYC, open banking, accounting platforms, e-signature, and credit reference agencies.

  • KYC
  • Open banking
  • Accounting platforms
  • E-signature
  • Credit reference agencies

Getting two systems to talk to each other is the easy question. The harder one is how they should talk - and the same handful of concerns tend to come up regardless of which provider is on the other end.

Data contracts

What information enters and leaves each system?

Reliability

What happens when an external service is unavailable?

Authentication

How should external clients and providers securely connect?

Data boundaries

What information should each system be allowed to access?

Change

What happens when an external API changes?

Observability

How do you know when an integration fails?

PLATFORMS · API · B2B

White-Label Systems & External Client Platforms

Worked on white-label systems designed to allow external clients to provide services through their own branded experience while connecting to shared internal infrastructure.

  • White-label architecture
  • Multi-client considerations
  • External APIs
  • Internal services
  • Data isolation
  • Authentication
  • Client-specific configuration
  • Reusable platform capabilities

No single client integration is the hard part of a white-label platform. The hard part is the shared layer underneath - APIs and internal services that stay reusable across clients, keep each one's data properly separated, and still leave room for per-client configuration without turning into a pile of bespoke systems.

Internal System
  • Client A · White-Label
  • Client B · White-Label
  • Client C · White-Label

AI · AUTOMATION · SYSTEMS

AI Agents, Automation & Intelligent Workflows

More recently, I've been exploring and working with AI agents and automation, particularly where they can improve workflows, reduce manual processing, or help systems work with information that previously required human intervention.

  • AI agents
  • Workflow automation
  • LLM-powered processes
  • Human-in-the-loop systems
  • Context and reliability
  • AI vs deterministic automation
  • Information processing
  • Decision support

AI for its own sake is not the point. The more useful question is where it actually earns its place inside a system, versus where plain deterministic automation is simpler, cheaper, and more likely to just work.

Not every automation problem needs AI. Not every AI problem should be automated.

Cross-cutting

The common thread

The projects have varied, but the underlying challenge has often been similar: there are multiple systems, multiple sources of information, competing requirements, and uncertainty about the best way forward.

That's where I tend to do my best work - understanding the moving parts, making the problem visible, exploring the options, and designing a system that is practical to build and operate.

  1. Problem
  2. Requirements
  3. Data
  4. Systems
  5. Integrations
  6. Architecture
  7. Decision

Principles

Things I've learned from working on complex systems

Start with the problem

The technology is rarely the first question that needs answering.

Data changes architecture

Where data comes from, who owns it, how reliable it is, and how it changes often determines how the system should work.

Integrations are part of the architecture

An external API isn't simply a connection. It introduces dependencies, failure modes, contracts, and change.

Simple beats sophisticated

Complexity should solve a real problem, not create one.

Constraints matter

The technically elegant solution isn't always the right one once cost, time, people, regulation, and existing systems are considered.

AI changes the design space

AI makes some previously expensive workflows possible, but reliability, context, and boundaries still matter.

Path

How this took shape

  1. Software Engineering
  2. Fintech
  3. Technical Leadership
  4. Architecture, Data & Integrations
  5. AI & Automation
  6. Agaya Cloud

Areas I've worked across

  • Cloud
  • APIs
  • Databases
  • Data
  • Integrations
  • Automation
  • AI
  • Distributed Systems
  • Fintech

Now

What I'm working on now

Today, I'm the founder of Agaya Cloud, where I'm building TrueSignal around post-purchase intelligence - helping companies understand what happens after a transaction and turn those signals into useful product and customer insights.

Have a complicated system to figure out?

If you're dealing with a messy architecture, a difficult integration, unclear requirements, or a technical decision you're not sure about, I'd be happy to compare notes.