Work

Built and run in production. Then handed over.

Two kinds of work sit here. Five product systems we build and operate — each on its own subdomain. And the client engagements delivered around the same discipline: a named client beats any percentage.

Delivered engagements

Real, named, already delivered
Field Operations · AI

Swire Renewable — VBSM

Real-time van booking system with an AI agent and copilot.

A real-time booking and dispatch system for a renewables field-service operation, with an AI agent handling scheduling and a copilot assisting the coordinators.

It ran in production with the client. On completion the source code was transferred to them. Chris Illum was the live user at Swire during the engagement and is a standing reference.

Ran live with the client. Source code handed over on completion.

Field Operations

Swire App

Field and operations app built for the same client, ahead of VBSM.

The operations app that preceded VBSM for the same client — the groundwork that VBSM built on.

Delivered and run in production.

Field Operations

AA App

Operations application delivery.

Scope to be confirmed — one line.

Delivered engagement.

B2B Retail · Commerce

b2b.maplesage.com

Headless BigCommerce storefront with HubSpot CRM integration.

A headless BigCommerce storefront wired to HubSpot CRM — the same integration pattern MapleSage runs for branded apparel and wholesale.

Built and live.

B2B Retail · Commerce

store.maplesage.com

Shopify build with the same integration pattern.

A Shopify build carrying the same storefront-to-CRM integration as b2b.maplesage.com.

Built and live.

Swire needs no clearance — Chris Illum was the live user at Swire during the engagement, now works at a comparable company, and is a standing reference. Name the client, describe what was delivered, verify by a phone call.

See one running

The product clusters come up on request. Ask for a walkthrough.

Request a live walkthrough