Systems that work where the internet does not.

The week you already know.

A field officer leaves at seven in the morning with a bag of paper forms. She sees eight families. She writes carefully, in the rain if it is raining. She gets back after five and starts typing it all in again, or she puts it in a shared sheet that only updates when she reaches the office wifi.

Nobody chose this. It grew, one spreadsheet at a time, because the work had to get done.

So the numbers you see are always a few weeks behind the truth. Reporting season arrives and someone good loses two weeks to copying, matching, and chasing. A funder asks a fair question, and the answer sits somewhere in twelve files with names like final_v3_updated. And when a coordinator who knew how all of it fitted together moves on, a lot of that knowledge goes with her.

That last part is the one people assume they have to live with. They do not. When the system is written down and installed, the knowledge stays in the system, and the next person starts on solid ground.

What an offline-first field system actually is.

Offline-first means the app works with no internet at all, and catches up later. Not a lighter version. The same app, doing the same job, with zero bars of signal.

It works with no signal.

The app lives on the phone or tablet your team already carries. Your officer opens it standing in a field an hour from the nearest tower, and it behaves exactly as it does in the office. She fills the form, saves it, moves on.

It syncs when it finds a signal.

When the device reaches wifi or a mobile signal, it sends what it collected and pulls down whatever changed. Nobody has to remember to press anything. If the connection drops halfway, it picks up where it stopped.

It is encrypted on the device.

The app is locked behind a PIN, and the information stored on the device is encrypted, which means scrambled so it cannot be read without the key. If a phone is lost on a road somewhere, the data on it is not readable.

One record per person, not fifty spreadsheets.

A person has one file. Every visit, every form, every note attaches to that one file. You stop reconciling versions, because there is only one version.

Good systems do not ask the field to change. They meet it where it already stands.

What it changes for the three people who care.

The field officer.

Her visit is recorded while she is still in the room, in a form that looks like the paper one she knows. She stops carrying a bag of documents she is afraid to lose. She stops typing the same thing twice. She goes home at the normal time.

The program manager.

You see this week's work this week. Who was visited, what came up, what is overdue, which sites have gone quiet. Not a picture of last month assembled next month. When something is going wrong in one district, you find out while you can still do something about it.

The person who writes the funder report.

The report becomes a filter on data that is already sitting there, correct and current. What used to take two weeks of copying takes an afternoon of checking. And when the funder asks the follow-up question, you can answer it in the meeting instead of promising to come back.

Where this runs today.

If you are the person recommending this, a good idea is not enough. You want to know someone has already built it, in a place as hard as yours, and that it held. So here is what we can actually show you, not what we promise.

We built and run field systems, under contract, for an international NGO with programs in four countries: Cambodia, Liberia, Sierra Leone, and the Philippines. The organization owns the systems and the data; Prodigi holds no beneficiary records.

The programs running on these systems reach more than 4,000 children. That is reach, the number of children the programs serve. It is not a database we hold.

This exact thing has been built before, in places with no connectivity, and the organization owns it.

The data scope, stated once and written into the agreement. The organization owns and controls the data. We build the system and we run it. We never hold information about the people a program serves, and we never publish anything about them.

How it gets built, and how it gets handed over.

Four stages. The same four every time, so you always know where you are.

Safeguarding, as a principle.

When a system holds information about children and families, the rules are not a feature list. They are the reason the system is allowed to exist. So we state ours plainly.

The data is yours.

It belongs to your organization, in the agreement, in writing, from day one. If you ever end the engagement, you leave with your system, your data, and your documentation. We hold nothing back to keep you as a client.

People see only what their job needs.

A field officer sees the families she works with. A manager sees her district. Access follows the role, and it is reviewed when people join, move, or leave.

We do not hold beneficiary information.

We build the system and we keep it running. The records stay with the organization that is accountable for them. That is the correct place for them to sit.

What it costs.

Field and monitoring systems start at $15,000. Fixed fee. We put the number in writing before any work starts, so nothing moves after you sign. What sits above the floor depends on how many forms, how many sites, and what has to connect to what, and we tell you that at the end of Diagnose, not at the end of the project.

If you want us to stay on afterwards, membership is a monthly fee tied to a stated scope. You always know what you are buying.