Skip to content

Selected work

Production software, integrations and modernisation across CRM, messaging, data platforms, ecommerce, operations and fintech — including Pacifica products and principal-led work.

Four different problems. One pattern: software has to work inside a real operation.
  • Messaging
  • Data
  • Commerce
  • Modernisation

Selected work

Principal-led experience · Commerce & operations

Relevant work led by Pacifica's principal.

Connecting online ordering to the operation behind it

A customer-facing ecommerce platform connected to inventory, supplier purchasing, finance, fulfilment, delivery scheduling, CRM and marketing automation.

  • 30k+ MAU
See the operating system behind the store
  1. Order
  2. Payment
  3. Stock
  4. Supplier purchasing
  5. Delivery planning
  6. Customer

Pacifica product · CRM & messaging automation

Built and run by Pacifica.

Calendar-driven follow-up across real communication channels

A workflow-driven CRM that connects calendar events, contact resolution, templates, asynchronous delivery and user-owned WhatsApp and email identities.

  • Rails
  • PostgreSQL
  • WhatsApp
  • Go
Explore the messaging architecture
  1. Calendar event
  2. Contact resolved
  3. Template & rules
  4. Queued delivery
  5. WhatsApp / Gmail / SMS

Principal-led experience · Application modernisation

Relevant work led by Pacifica's principal.

Rails 2 / Merb to Rails 7.1 — without a full rewrite

A staged modernisation across framework, Ruby runtime, data layer and infrastructure — without discarding the business logic that still mattered.

  • Rails 7.1
  • Ruby 3.3
  • ActiveRecord
  • Ubuntu 22.04
See the staged modernisation path
  • FrameworkRails 2 / MerbRails 7.1
  • RuntimeRuby 1.9Ruby 3.3
  • Data layerDataMapperActiveRecord
  • Operating systemUbuntu 10Ubuntu 22.04

Principal-led experience · High-throughput data platform

Relevant work led by Pacifica's principal.

Keeping a high-volume data pipeline flowing

Resilient ingestion across multiple sports with asynchronous processing, flexible storage and downstream reporting.

  • Rails
  • PostgreSQL
  • Sidekiq
  • JSONB
See the ingestion pipeline
5 sportscollected continuously; a failing source never stalls the others
  • schedule
  • collect
  • parse
  • persist
  • report

Start from the problem

Each link lands on the section of the service page that answers that problem. Confidential client information is omitted where required.

Recognise the problem in one of these?

Describe the system as it is today. A finished specification is not required.

Discuss a project