About Project Catalysts

Technology delivery is often harder than it needs to be. Handoffs multiply, specs drift, and people are left reconciling versions instead of solving the problem. Project Catalysts exists to remove that friction — so teams can focus on outcomes that matter.

What we solve

Typical challenges we take on

How we work

We favour small, senior teams, tight feedback loops, and artefacts you can run — not slideware. You'll see the shape of the solution early, and we'll prove it with executable specs and measurable checks.

Engagement steps

  1. Model first — agree the data shapes, rules, and success criteria. Artefacts: schemas, dependency maps, acceptance checks.
  2. Executable spec — encode rules and tests beside the transforms. Artefacts: test suites, fixtures, validation harness.
  3. Iterate & deliver — short cycles with visible increments. Artefacts: working builds, performance budgets, release notes.
  4. Handover & harden — runbooks, monitoring, and a clear path to maintain or extend. Artefacts: ops docs, SLOs, ownership map.

What you can expect

Tools we bring

We use pragmatic tools that keep structure, rules, and documentation in lockstep. MIXT — authored and tested by Rik — is our catalyst for delivery: a schema-first language for deterministic data and document transformation that publishes to web, PDF, and DOCX from one source.

We've applied these patterns across payments and financial systems — from New Zealand's ISO 20022 migration to RTGS modernisation and global mobile banking delivery. The common thread is the same: clarity, executable specs, and outcomes you can measure.

See Delivered Outcomes Meet Our People Learn about MIXT

Engagement options

Contact

If you have a concrete outcome in mind, or a problem that needs solving, we're keen to help. Share a few bullets on goals, constraints, and timelines, and we'll bring the catalysts to turn your goals into delivered outcomes.

Email us