Offline-first
Works without a connection and syncs when one appears — so a dropped signal doesn't stop the work.
Field · 06
Technology that holds up where it's hard.
AI and the tools around it have to run where power, signal, devices and languages all vary. We design and deploy for those conditions from the start — because that's where most technology quietly falls over. Eight years of doing this across six African countries goes into every deployment.
Who it's for
When the deployment site is the hard part.
The tech may work fine in the office. This is for getting it to work where your programme actually runs.
- 01
Sites with unreliable power, patchy signal, or no internet for stretches of the day.
- 02
A mix of old and new devices, shared between many people.
- 03
Several languages, and users with a wide range of digital confidence.
- 04
A tool that works in a pilot but keeps breaking once it's out in the real programme.
What we handle
The things that decide whether it survives the field.
Alternative power
Set up to run on whatever power a site actually has — solar or a generator — rather than assuming reliable mains electricity.
Real devices
Tested on the phones and machines your people actually use, old ones included.
Languages
Built to work across the languages your programme runs in, not just English.
Simple to use
Designed for a wide range of digital confidence, so training stays short and adoption sticks.
Keeps running
Set up so your team can keep it going, fix small things, and know when to call us.
Investment
Scoped to your sites and how many of them.
A single site is very different from a national roll-out. We scope to your programme and agree the price before we start.
PriceEngagement-basedSet by the number and difficulty of your sites; agreed up front.
ShapeOften alongside a buildUsually paired with an AI Pilot Build or a Sovereign Deployment.
Good to knowField roll-out costs sit naturally in a programme or grant budget.
Included
- Design for offline, low-power, multi-device use
- Testing on your real devices and conditions
- Roll-out across your sites
- Short, practical training for local staff
- A plan for keeping it running
Not included
- The core tool itself, if it doesn't exist yet (that's the AI Pilot Build)
- Hardware costs, which we'll name up front
- Long-term on-site staffing
Questions
What people ask.
Is this a separate thing from the build?
They fit together. If we build the tool, we design it for field conditions from the start. Field Deployment is for taking a tool — ours or an existing one — and making it survive across real sites.
Do you go on-site?
Where it's needed and makes sense, yes — and we lean on local partners and staff, who often know the ground better than anyone flown in.
What about no internet at all?
That's our home ground. Content and many tools run fully offline on a Hyracbox Edge Server; running the AI itself offline is a Sovereign AI Deployment.
Related
Often alongside.
Works in the office, breaks in the field? That's the part we're good at.
Tell us about your sites and we'll map what it takes to make it hold up.