Systems architectSystems Architect & Technical Partner · Belfast
Operations platforms for care, training, recruitment and clinical businesses, with access rules and an audit trail enforced in the code.Operations platforms for care, training, recruitment and clinical businesses: the ones holding safeguarding records, learner data and clinical notes. Access rules, encryption and an audit trail are enforced in the code, so they hold whether or not anyone remembers the policy.
Who we build for
Care providers, training and apprenticeship providers, recruiters and clinics. We design, write and run the software that holds those records, then hand it over intact.
Spreadsheets, inboxes and three systems that disagree with each other. We replace them with one platform your team logs into: staff, learners, clients, placements and money in the same place.
Knowledge living in one person's head is a risk. We turn how you actually operate into software, with permissions, approvals and a record of who did what, so the process holds without supervision.
Safeguarding, clinical and learner records carry a legal duty. Access control, encryption and an append-only audit trail go in with the first database table, so the evidence exists before anyone asks for it.
The system your team logs into every day, with the right access for each role and a record of every change.
Protections enforced by the software for records about clients, patients, learners and staff.
Fast public sites wired to your systems, built to be found in search and to route each lead to the right person.
Online, subscription and in-person payments, with the amount checked on the server before anything is charged.
Repeat work, such as documents and course material, turned into a pipeline people review instead of produce.
What we build
The work
Every system is labelled live, pre-release or offline, and every figure names the record it came from. All 6 systems
The public site and admin console for an 18-branch recruitment, training and care group, with its own mail infrastructure and SEO stack.
5.4×more enquiries and applications a month through the site in four months, May to August 2026
A private wellness operating system: public brand site, member hub, live subscription memberships and a clinical practitioner workspace.
How it is built
The same controls go into every system we build, whether it holds learner records, clinical notes or card payments. Each one below points at the system it is built into.
Permissions are not a screen-level convenience. Every table has row-level security, roles live in their own table, and automated checks stop shortcuts before they ship.
Roles are held apart from user profiles and checked on the server, and the database itself limits which roles one person can hold.
Personal information is tiered, masked by default and encrypted where it matters. Revealing a masked value writes an audit record.
The most sensitive fields are encrypted at rest, so a record can be destroyed irrecoverably when its retention period ends.
Critical actions go to an append-only audit trail that is checked on a schedule. If the trail stops adding up, the system raises it rather than carrying on quietly.
Clinical actions are stamped with the member of staff who took them, and flagged cases can be held for nurse review.
Code, database and hosting sit in your accounts with standard tools and written runbooks. After the first 12 months you can run it yourselves or hand it to another developer.
The group holds the code, the data and its own email sending domain.
Mapped to
The standards our systems' own policies and evidence packs are written against. Mapped, not certified: NEXUZ holds no certification of its own.
Hosting runs on Lovable, whose platform holds ISO 27001 certification and a SOC 2 Type II report. Those credentials cover the hosting platform, not NEXUZ or any client system. Verify at Lovable Trust Centre
How we work
The exact time depends on size: a public site with its admin tools is at the short end, a full operations platform at the long end. You see working software throughout, so there is no reveal at the finish.
A working session on the process itself: who touches it, where it breaks and what it costs today. You get a written problem statement we both agree on.
Data model, access rules, integrations and money paths, including what is left out on purpose. Costed, with running costs stated up front. Approve it, change it, or walk away with it.
Working software in front of you throughout, in short cycles. Roughly an hour a week of your time to review and steer.
Live with your team, with backups and monitoring in place and the runbooks written down.
Repositories, infrastructure, data and documentation are already in your accounts. After 12 months you can run it yourselves.
Ways to work together
Where most clients start
Embedded partner
A long-term technical seat inside one business
Any business with real operational complexity and no technical lead of its own, that wants someone permanently on the hook rather than a project team that leaves.
Continuity
The system does not depend on one person's memory. Code, database and hosting sit in your accounts from day one, and our platforms ship with written runbooks and a handover pack covering how they are built, backed up and restored.
Bringing in another developer is a documented step, not a favour. After the first 12 months you can move operations in-house or elsewhere whenever you choose.
Next step
No pitch deck and no discovery fee. If something off the shelf would serve you better, we will say so before either of us spends money.
Or email zbarnett@nexuz.uk
