Case studies

Casestudies:architecture,delivery,andoutcomes.

The narratives below are structured like real client programmes. Names and line-of-business detail are illustrative where confidentiality applies; technical approaches and trade-offs reflect how we work.

01Fintech, core banking

Atlas:amulti-currencyledgerforacross-borderfintech

A double-entry ledger engine handling millions of daily transactions across 14 currencies, replacing a legacy mainframe module that had become impossible to change safely.

Timeline14 months, 9-person team
ShippedSeptember 1, 2024
StackGo, PostgreSQL, Kafka, Kubernetes, Terraform, Datadog, gRPC
Challenge

Our client's existing ledger ran on a 20-year-old mainframe system. Every change required multi-week regression cycles, and new product launches were blocked behind a three-month release queue. Compliance needed sub-second audit queries the legacy system could not deliver.

Solution

We designed a new ledger service in Go, backed by Postgres with an append-only event store, exposing a strict idempotent API. We ran it in shadow mode for six months against the legacy system, reconciling down to the last yen, before cutting over region by region.

Architecture

Event-sourced ledger with a hot OLTP path and a stream-projected OLAP path. Transactions land as immutable events, projections rebuild balances and journal views. All writes are idempotent with deterministic IDs; reconciliation is a pure function of the event log.

Impact
  • 01Reduced monthly release lead time from 90 days to 6 days
  • 02Cut infrastructure spend by 38% versus the legacy mainframe
  • 03Audit queries now return in under 400 ms (previously 45 s)
  • 04Zero discrepancies across 6-month shadow-run reconciliation
02Analytics, logistics

Orbit:areal-timeanalyticsplatformforlogistics

A unified analytics surface for a national logistics operator, collapsing four legacy BI tools into a single real-time platform used by 2,000+ staff daily.

Timeline11 months, 7-person team
ShippedFebruary 1, 2024
StackClickHouse, dbt, Kafka Connect, Next.js, TypeScript, Airflow, Grafana
Challenge

Operations, finance, and field teams were each using different analytics tools with incompatible metric definitions. A single question often had three different answers. Ingestion lagged up to 24 hours behind operational reality.

Solution

We shipped a semantic layer in dbt as the single source of truth, built a ClickHouse-based real-time warehouse, and delivered a custom React analytics app with role-based dashboards. Ingestion runs through a CDC pipeline that keeps data under 30 seconds behind production.

Architecture

CDC from operational Postgres via Debezium into Kafka, materialised into ClickHouse through streaming ETL. dbt models define all business metrics. The frontend consumes a thin typed query API; no one writes raw SQL against production data.

Impact
  • 01Replaced four BI tools with one, saving ¥87M/year in licensing
  • 02Reduced time-to-answer for new metrics from 3 weeks to 2 days
  • 03Sub-30-second data freshness for every dashboard
  • 04Drove a 12% reduction in same-day delivery misroutes through better ops visibility
03AI, automation

Relay:anAIautomationsuiteforcustomeroperations

An LLM-powered automation platform that resolves 62% of inbound support tickets without human escalation, routed through Chatwoot and WhatsApp.

Timeline6 months, 5-person team
ShippedMay 1, 2025
StackOpenRouter, Claude, pgvector, n8n, Chatwoot, WhatsApp Cloud API, Supabase
Challenge

Our client's support volume had grown 4× in 18 months. Average handling time was climbing, hiring couldn't keep pace, and customers were dropping off before first human response. Any automation had to respect the company's strict tone guidelines and handle Japanese, English, and Portuguese.

Solution

We built a multi-agent system on OpenRouter, fronted by Chatwoot for unified channel handling. A tuned retrieval layer surfaces approved knowledge-base passages; guardrails enforce tone and policy. Every interaction is evaluated nightly against a growing test harness.

Architecture

A router agent classifies intent and selects specialist agents (refunds, account, how-to). Retrieval hits a pgvector index over the approved KB. Outputs pass through a guardrail chain for tone, compliance, and PII redaction before going to the customer via Chatwoot. Human escalation is one click.

Impact
  • 01Auto-resolved 62% of tickets within 24 hours
  • 02Reduced average first-response time from 4 h to 11 s
  • 03Support headcount productivity up 3.1× on complex tickets
  • 04Compliance approval on 100% of deployed tone guardrails
04Integration, enterprise

Lattice:anintegrationplatformforamanufacturinggroup

An integration platform connecting 18 production plants, 6 ERPs, and 24 SaaS tools into a unified event stream, powering a realtime executive view across the group.

Timeline18 months, 11-person team
ShippedJanuary 1, 2025
StackKafka, NATS JetStream, Apache Camel, PostgreSQL, Node.js, TypeScript, Kubernetes
Challenge

A manufacturing group's digital transformation stalled because no two systems spoke the same language. Reporting took 2 weeks of manual reconciliation. Supply chain disruptions took days to surface across regions.

Solution

We built a canonical domain model and an event bus that every system publishes to and subscribes from. Connectors for each ERP translate vendor shapes into the canonical form. The same events feed the exec dashboard, the ML forecasting stack, and the audit store.

Architecture

Canonical event contracts published through Kafka. Plant-level edge services batch and forward; ERP connectors run bidirectional sync with replay tooling. An audit store holds every event with tamper-evident hashing.

Impact
  • 01Executive dashboard latency from 2 weeks to under 60 seconds
  • 02Cut integration development time for new tools by 70%
  • 0318 plants unified under a single operational model
  • 04Full audit trail reducing annual compliance cost by ¥52M