Business applications
We build internal-facing software for organisations whose case management, workflow or compliance can't be solved with off-the-shelf SaaS. Intranets, eForms, CRMs, ordering systems, records-transfer pipelines, secure portals for cleared partners. Often connected into systems you already run.
What we build, in practice
- Case management and workflow systems for regulators, ombudsmen, and inquiry bodies.
- eForm and intake systems with backend workflow, approval chains and audit trail. UK DWP and several state agencies use these in production.
- CRMs and internal portals for membership organisations, publishers, and distributed teams.
- Records integration — FHIR for healthcare, custom protocols for everything else.
- Intranets that consolidate documents, news, events, and discussion into one place rather than five.
- Ordering and procurement systems for sectors that don't fit a generic shopping cart.
Secure portals
Give people outside the organisation controlled access to what is inside it — accounts provisioned from the systems of record, access granted per document or per area and withdrawable, and a guarded route through to internal systems that were never built to face outwards.
Secure file exchange
One kind of integration comes up often enough to name. Sharing tender material, regulatory evidence, investigation files or care records with people outside the organisation usually means email attachments or a consumer file-sharing account, neither of which anyone is comfortable defending afterwards.
So we build the exchange into the workflow instead: recipients authenticate, access is granted per document and can be withdrawn, and every transfer is logged for the audit that follows. Where the files live is a decision you make, not one the vendor makes for you.
We run this as Vaultmatix for the organisations we have built it for — government departments sharing sensitive material with external parties, regulators handling complainant evidence, and health and welfare bodies sharing records with practitioners. It is a capability we build into your workflow rather than a product to subscribe to.
Why us, not a SaaS off the shelf
For workflows where the off-the-shelf product doesn't fit, the choice is usually "customise the SaaS until it does" or "build to fit". The SaaS-customisation route looks cheaper at year one and ends up the most expensive thing in your stack by year five. We build to fit — but on a battle-tested platform (Plone, Postgres, Python) so the codebase has a future, and on patterns we've shipped before so the timeline is predictable.
How engagements run
Most projects start with a 2–4 week discovery covering current state, user research, requirements, integrations, and a realistic project plan with milestones. Build phases are typically 8–16 weeks for an initial release, with managed hosting and ongoing partnership after.