Build for the operator
The person using the system all day is who we design for.


Our partners carry years of delivery behind them in health risk administration, enterprise integration and multi site infrastructure, on systems that had to work on Monday morning. That depth is why we commit to an outcome rather than a rate card.
We own our code, our two product lines and our client relationships. The partners who win the work are the partners who do it, and the people who scope your engagement are the people who deliver it.




No handover to a junior bench after signature
To be the partner organisations turn to when the system they need does not exist yet.
To design, secure and deploy custom systems that give our clients a real advantage in their market, and to make advanced technology feel simple to the people who use it every day.
The person using the system all day is who we design for.
Security is part of the architecture, not a layer added at the end.
Measured on whether it works in production, not on whether it shipped.
Clear code, documented decisions, no single point of knowledge.
Four ways to work with us on services, and a licence model for each product. We will recommend the one that fits the problem, not the one that bills best.
A defined outcome, a fixed price and a fixed date. Best where the problem is well understood.
A standing team billed monthly, working to your roadmap. Best for continuous product work.
Named engineers embedded in your team, under your delivery lead.
Monitoring, maintenance and support against a defined response window.
Per member per month, tiered by volume, with implementation and integration scoped after discovery.
Per farm or per hectare subscription, with setup and sensor integration scoped after the farm survey.


Regulated buyers cannot take a supplier on trust. These are the controls we build into every system, and the standards we work to in each product domain.
Data classification, retention, consent, subject access and a defined breach process
Threat modelling, penetration testing, code review and a rehearsed incident response process
The maker of a transaction cannot be its checker or its payer. Enforced in the platform, not stated in a policy
Every decision and payment traceable to a user, a rule and a timestamp
Backup strategy, disaster recovery design and recovery testing, evidenced not assumed
Source code, data model and documentation transferred in full at the end of every engagement
| Health, MedicalBytes | Council for Medical Schemes context, prescribed minimum benefits, scheme rules and provider contracting, ICD10 diagnosis and CPT procedure coding, tariff sets maintained as authoritative reference data. |
|---|---|
| Agriculture, CultiBytes | GlobalG.A.P. and LocalG.A.P., HACCP hazard points and controls, SIZA social and environmental audit evidence, buyer and export traceability requirements. |