Work
Described by the problem, not the logo.
We do not publish client names. What follows is the sector, what was wrong, what we built and what it runs on, which is the part that tells you whether we can help.
A multi-tenant communications and giving platform
Member organisations were running contact lists in spreadsheets, campaigns through three unconnected tools, and donations through a payment link with no reconciliation back to the person who gave.
What we built
- Multi-tenant architecture with per-tenant isolation, custom subdomains and Entra ID single sign-on
- Campaign delivery across email, SMS and WhatsApp from one composer, with segmentation over the contact graph
- Giving, Gift Aid declarations and event management reconciled back to member records
- A member-facing portal and an admin console over the same tenant model
- Next.js
- Node
- PostgreSQL
- Azure Container Apps
- Front Door
- Entra ID
Replacing four business systems with one
Quoting, point of sale, product specification and accounting each lived in a different product. Nothing reconciled, every order was re-keyed at least twice, and no one could answer what a job had actually cost.
What we built
- Odoo 19 implementation mapped to the real procurement process rather than the textbook one
- Migration off the incumbent POS, quoting and specification tools, with data reconciliation at each step
- Cutover planning and phased go-live so the business keeps trading through the switch
- Odoo 19
- Python
- PostgreSQL
- ETL
Two school sites rebuilt on a fixed fee
A specialist education group ran two sites on ageing builds that were hard to update, slow on mobile and failing basic accessibility for an audience that needed it most.
What we built
- Two full site rebuilds sharing one component system and content model
- Accessibility treated as a build requirement rather than an audit at the end
- Editor tooling so staff can publish without coming back to us
- Next.js
- TypeScript
- Tailwind
- Azure Static Web Apps
Document automation inside Word
Caseworkers were assembling long, heavily-structured documents by hand from templates, with formatting and compliance errors caught late or not at all.
What we built
- A Word add-in on Office.js that assembles documents from a governed template library
- Structured content stored and versioned in SharePoint rather than on shared drives
- Release and versioning process for shipping updates into a managed desktop estate
- Office.js
- Microsoft Graph
- SharePoint
- TypeScript
Natural-language campaign building
Building a segmented multi-channel campaign meant understanding the data model well enough to write the segmentation yourself. Most users never got past the default list.
What we built
- A LangGraph service turning a plain description of an audience into a validated segment and draft campaign
- Human review before anything sends, with the generated segmentation shown as editable rules rather than a black box
- Per-tenant spend caps and provider fallback so cost and availability are both bounded
- FastAPI
- LangGraph
- OpenRouter
- PostgreSQL
A generation platform with a budget it cannot exceed
Image and video generation across several products meant several accounts, no shared asset library, and no way to see what any of it was costing until the invoice arrived.
What we built
- Model routing across providers with per-model cost accounting on every request
- Hard budget ceilings enforced before the call is made, not reported afterwards
- A shared asset gallery so generated work is reused rather than regenerated
- Next.js
- fal.ai
- Zustand
- Azure Blob Storage
Get in touch
Recognise your situation in any of these?
A conversation with the people who would actually do the work, and an honest answer about whether we are the right fit for it.