Custom software, AI agents and automation, engineered around how your operation actually runs.
Three live systems: one built for a client, two we run ourselves.
status as of Oct 2026A parcel and errand delivery platform connecting customers with a managed courier fleet through delivery requests, automated dispatch, live tracking and delivery operations.
Including dispatch, live tracking, multi-stop delivery and a driver wallet.
A multi-vendor food-delivery platform connecting customers, restaurants, drivers and operations teams through ordering, dispatch, delivery tracking and restaurant operations.
Including dispatch, live tracking and a restaurant POS.
A student-services platform supporting the process of studying in Rwanda through university services, document equivalence, housing, currency exchange and integrated support.
Including chat, document equivalence and a news and social feed.
Four more on the work page: an ERP and accounting system, two websites and a productivity app.
See all workSoftware that runs the operation, AI that understands and decides, automation that connects and acts, and the cloud and testing that keep it standing.
The system itself: sales, stock, accounts, apps and the business logic your operation runs on.
handoff / your software's data feeds the agent
The layer that reads your data, reasons over it and takes part in the work.
handoff / the agent's decision triggers the workflow
The layer that acts: moving work between people, systems and the tools you already use.
handoff / everything above runs on tested, hosted infrastructure
The ground it stands on: tested before launch, hosted on the cloud, and connected.
Not sure which layer you need? Start with the problem; we’ll work out the system with you.
Start a projectWhere we test intelligent systems, automation and decision tools before we treat them as products.
status as of Sep 2026SudaFood's backend already flags orders a restaurant leaves pending too long, and an operator then had to contact the restaurant by hand. This prototype tests automating that follow-up without giving a model unrestricted control. It acts on the backend's pending_late signal; it does not detect delays itself.
After a manual start it finds eligible orders, checks them, decides whether to send a reminder, sends it on WhatsApp and logs the send. It cannot change orders, dispatch drivers, contact customers or run continuously on its own.
How can we evaluate a startup opportunity without mistaking desk research for market validation?
Idea Scout turns an idea into hypotheses and research questions, researches the most critical one on the live web, classifies the evidence and returns decision support with a next experiment. It cannot approve an MVP, contact customers or run field validation.
BUILD_CANDIDATE means ready for founder review and field validation. It is not an approval to build.
The Lab page lists each experiment's evidence and where it stands.
Explore the LabAn African technology company that runs live products of its own, so every client system is built by a team that knows what it takes to operate one.
how we work / build · launch · scale
Engineer the whole system, not only the screens.
Put it into real use and learn from how it operates.
Improve, automate and extend what proves valuable.
A core team owns every project end to end. Specialists join around the technical needs each project actually has.
We started MOTNIX because we wanted to build, operate and learn from real systems — not just deliver screens.
No inflated case studies: every project here is labelled for exactly what it is — client work, our own venture, a prototype or a simulation.
A clear process, a written agreement, and one team accountable from the first conversation to after launch.
process / from first call to support
We start with how your operation runs, not with a feature list: a call or a short brief, then the questions that shape the system.
A written scope, timeline and estimate for your project, so you know what you are getting and what it costs before work starts.
Short cycles with working builds you can see and test, and one point of contact from start to finish.
We launch with you, then a review period for your feedback and revisions.
Maintenance, improvements and new features, agreed with you per project.
It depends on the scope: the roles, integrations and platforms the system needs. After discovery we send a written estimate for your project, so you know the cost before any work starts.
It varies from project to project. The proposal sets out a timeline with clear milestones, and you see working progress throughout.
Payment terms differ from one project to another, so we do not publish a fixed schedule. Get in touch and we will agree one with you, then set it out in the proposal and the contract.
Ownership, licensing and handover are agreed with you and set out in the contract before work starts.
Yes. We are glad to sign an NDA, and several of the systems we have built are under confidentiality agreements.
Every project includes a review and revision period after delivery. Ongoing support, maintenance and further development are agreed per project.
Of course. For serious projects we arrange a discovery call: message us on WhatsApp or by email, or send a short brief, and we will set a time that suits you.
Our office is at Norrsken House Kigali, Rwanda. We work with clients in Rwanda, Sudan and beyond, in person and remotely.
Whichever your users speak. We build in Arabic, French, Swahili and Kinyarwanda, among others, and treat right-to-left interfaces as a first-class direction, not an afterthought.