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
- Standards & interoperability: ISO 20022 changes, coexistence, and clean translations without breaking downstream systems.
- Mission-critical payments: RTGS replacements, settlement choreography, and operational readiness without service interruption.
- Deterministic pipelines: schema-first transformations with strict validation, audit-friendly logs, and repeatable builds.
- Documentation that stays true: web/PDF/DOCX generated from the same source as code and rules, so guidance never lags reality.
- Rescue & re-alignment: projects that have stalled, where clarity, scope alignment, and crisp delivery are urgently needed.
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
- Model first — agree the data shapes, rules, and success criteria. Artefacts: schemas, dependency maps, acceptance checks.
- Executable spec — encode rules and tests beside the transforms. Artefacts: test suites, fixtures, validation harness.
- Iterate & deliver — short cycles with visible increments. Artefacts: working builds, performance budgets, release notes.
- Handover & harden — runbooks, monitoring, and a clear path to maintain or extend. Artefacts: ops docs, SLOs, ownership map.
What you can expect
- Clarity up-front: we make unknowns explicit and de-risk early decisions.
- Measurable progress: every iteration lands something you can run, test, or show.
- Determinism: same inputs → same outputs across environments — by design.
- Straight talk: we challenge assumptions and explain trade-offs in plain language.
- Care for operations: runbooks, error wording, and on-call empathy are part of the delivery, not an afterthought.
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.
- MIXT for schema-first transforms, executable specs, and multi-output publishing.
- Go for reliable services with clear interfaces and low-latency paths.
- Validation harnesses that explain failures with precise context.
- Builds that are reproducible and audit-friendly.
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
- Industry delivery leadership: align stakeholders, shape scope, and land the programme.
- Solution design & build: schema-first pipelines, validations, and services that are easy to run.
- Project rescue: re-scope, re-plan, and ship a credible path to production.
- Capability build: patterns, templates, and coaching so your team can own it.
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.