Eastwind Systems

How we work

Fast at the start, slow and careful where it counts, and in the client's name from the first day.

An engagement

Week one
The call and the proposal

One conversation with the people who will use the thing, not only with the people who sign for it. Then a written proposal: what we will build, what it costs, what date it is usable, and what we need from you. If we are the wrong firm for it, the proposal says so.

Weeks two to six
A working system, not a prototype

The first version runs on real infrastructure with real accounts and a real rule set, used by a small group at one site. It is small on purpose. Everything after that is widening, not rebuilding.

The months after
Hardening and widening

Scope rules, audit, exports, offline behaviour, the second language, the hundredth site. This is the slow part and it is where a system either becomes national or quietly dies as a pilot.

For as long as it runs
Operation

We watch it, we are reachable when it breaks, we change it when the situation changes, and the client gets a monthly report of what happened. A system nobody operates is a system nobody trusts.

What we commit to

The institution owns everythingCode, data and accounts are in the client's name from the first day. We work under a service agreement and can be replaced without loss. There is no lock in to take away.
Somali and English, side by sideEvery screen, every message, every report, in both. Arabic where the public needs it. The words are the ministry’s, not a translation we chose for them.
Built for the fieldLow bandwidth first. A system that only works in an office with fibre is not a national system. We test on the connection the district actually has.
Tested before deployedEvery permission, every scope rule, every state change has a test, and nothing ships unless the tests pass. We learned this the expensive way and it is now a gate, not a habit.
Operated, not handed over and forgottenMonitoring, on call, changes as the situation changes, a monthly report to the client.
No invented numbersA score, a category, a threshold, a risk level: all of them come from a rule the client approved and can read. We never quietly make one up to fill a dashboard.

What we need from you

Most systems that fail in this region fail for one of these four reasons, not for a technical one.

Money

Build, then operateA fixed price for the build, with the dates in the proposal. Then a monthly retainer to run it, which is a fraction of the build and can be stopped.
Small first contractThe first engagement is deliberately small, so you can judge us on something delivered rather than on a brochure.
No per seat pricingA national system should not cost more because a ministry added a district. You pay for the system, not per person using it.

Start with the call

A paragraph about the problem is enough to begin. The proposal follows within a week.

Talk to us