Hire us
The most useful first message is not a feature list. It is a description of what currently goes wrong, how often, and what it costs when it does. We will tell you honestly whether we are the right people for it.
Email is best — it gives us something to think about before replying. You will get a reply from the person who would do the work, usually within two business days.
360 DEVZ LTD
Imena, Kiyovu, Nyarugenge
Kigali, Rwanda
None of this has to be precise. Rough numbers and an honest description of the mess beat a polished specification.
Schools
If you run a school, the same address reaches us — but read how EduCloud works first, so the conversation starts from whether it fits your term rather than from what it is.
Questions
Moses Sebagabo, the founder, does the engineering. Supervised interns take on scoped work as the company grows, and every change they make is reviewed before it ships. You will be talking to the person building your system, not an account manager.
Yes, for development and assessment work. Hosting is a different question — where your data is allowed to live may be set by your regulator, not by us, so we agree the region before anything is deployed.
You do, for work commissioned and paid for as custom development. We keep ownership of our own general-purpose libraries and tooling, and we name those in the contract rather than leaving it vague. We do not reuse one client's business logic for another.
No. We build systems that record payment status, reconcile payments and report on arrears. Money settles through a licensed payment service provider — our partnership is with Centrika, and funds move on its licensed rail. We never take custody of funds.
Agreed with you before deployment, and written into the contract. Access is least-privilege: we hold only what is needed to run and support the system, access to production is logged, and we do not copy production data onto laptops or into third-party tools without your written approval.
On Essential, next-business-day email support — appropriate for a site that is not business-critical, and we say so rather than implying more. On Managed and Assured you get a named contact and a response time written into the contract. We commit to what we can meet: a promise of 24/7 cover that nobody actually answers is worth less than a stated window that always holds.
You are not locked in, by design. The code lives in a repository you own, or is handed to you on request. Every system ships with a written deployment runbook — how it is built, where it runs, what the environment variables are, how backups are taken and restored. Standard tools and no proprietary framework, so another engineer can pick it up. We would rather you never need any of that, but you should not have to trust us on it.
Tell us the numbers and we will answer honestly. The systems we build are multi-tenant and designed for thousands of records and concurrent users — that is an architecture question, not a headcount question. Where a project needs more hands than we have, we will say so before the contract rather than after, and we will not take it on the assumption that it works out.
Development is scoped and quoted per project, with a deposit at the start and the balance against agreed milestones. Assessments are fixed scope and fixed price. Hosting is a monthly retainer. We do not do unpaid customisation, and we would rather re-quote a changed scope than absorb it silently.
Often, yes. It starts with a paid review of what exists — the code, the server, the backups and whatever documentation there is — so we can tell you honestly whether it should be maintained, refactored or replaced. Nobody benefits from us guessing at that for free.
Before you write
We only take work we can stand behind for the life of the system. If we are not the right people for what you need, you will hear it in the first reply rather than in month three — and where we can, we will point you at someone who is.
