We engineer
the systems
businesses
run on.

Software, AI agents and automation — built for real operations, not for demos.

DEMO · SIMULATED DATAScenario: a flagged order
  1. t+0.00signal.receiveddemo-order-01done
  2. t+0.10order.checkstate: pendingdone
  3. t+0.20restaurant.checkstate: opendone
  4. t+0.30decisionsend reminderdone
  5. t+0.40whatsapp.sendrestaurantrunning
  6. t+—log.recordedagent_logsqueued
Illustrative run. No real orders, customers or teams.
Build · Launch · Scale

Selected work

Three systems from our work: one for a client, two of our own. Each is labelled for exactly what it is.

status as of Sep 2026
01 / 03CLIENT PROJECT
status: advanced development, pre-production

Zajil

A parcel and errand delivery platform connecting customers with a managed courier fleet through delivery requests, automated dispatch, live tracking and delivery operations.

scope / what we built
Customer app
Driver workflow
Admin operations
Manager dashboard

Including dispatch, live tracking, multi-stop delivery and a driver wallet.

live customer tracking
multi-stop order summary
manager dashboard or driver active delivery
fig. 01 / zajil, product screensstack: flutter, firebase, typescript cloud functions, google maps / routesCase study in preparation
02 / 03MOTNIX VENTURE
status: soft launch / live pilot — Kigali

SudaFood

A multi-vendor food-delivery platform connecting customers, restaurants, drivers and operations teams through ordering, dispatch, delivery tracking and restaurant operations.

scope / what we built
Customer app
Restaurant operations
Driver workflow
Admin operations

Including dispatch, live tracking and a restaurant POS.

customer / restaurant discovery
meal search / discovery
restaurant operations / point of sale
fig. 02 / sudafood, product screensstack: flutter, firebase, node.js cloud functions, google maps / routesCase study in preparation
03 / 03MOTNIX VENTURE
status: active development

The Vision

A student-services platform supporting the process of studying in Rwanda through university services, document equivalence, housing, currency exchange and integrated support.

scope / what we built
Student app
Admin operations
Housing and broker workflow
Currency-exchange workflow

Including chat, document equivalence and a news and social feed.

student home
housing marketplace
admin dashboard
fig. 03 / the vision, product screensstack: flutter, firebase, node.js cloud functionsCase study in preparation

The full work page adds our other products, labelled the same way.

See all work

What we build

Software that runs the operation, AI that understands and decides, and automation that connects and acts.

01 / 03

Software engineering

The system itself: the apps, backends and business logic your operation runs on.

Full-stack applications
Mobile applications
Web applications
Business systems
Internal tools
APIs and backend systems
MVP development
Rescue and modernization of existing projects
frontend and mobile: flutter, react, javascript, bootstrapbackend: node.js, .net, laravel, djangodata: firebase, mongodb

handoff / your software's data feeds the agent

02 / 03

AI systems

The layer that reads your data, reasons over it and takes part in the work.

AI agents
AI-powered applications
AI integrations
Intelligent operational workflows
See our agent experiments in the Lab

handoff / the agent's decision triggers the workflow

03 / 03

Automation & integrations

The layer that acts: moving work between people, systems and the tools you already use.

Workflow automation
Business-process automation
API integrations
WhatsApp and messaging automation
Internal operations automation
AI connected to existing systems

Not sure which layer you need? Start with the problem, and we will work out the system with you.

Start a project

Lab

Where we test intelligent systems, automation and decision tools before we treat them as products. Each entry is labelled for exactly where it stands.

status as of Sep 2026

SudaFood Operations Agent Restaurant delay resolution

python · gemini api · cloud firestore · whatsapp cloud api
problem explored

SudaFood'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.

autonomy

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.

manual start
firestore signalpending_late
agentgemini tool loop
guardrails
decisionsend or skip
whatsapp apimeta cloud api
agent_logs
operational summary
fig. 04 / from backend signal to logged reminder
ANONYMISED RECORDED RUNOne order, one reminder
  1. 01signalpending_late received
  2. 02orderstate: pending
  3. 03restaurantstate: open
  4. 04historyprevious reminder: none
  5. 05decisionsend reminder
  6. 06whatsapp apisuccess
  7. 07agent_logsrecorded
Recorded from a real prototype run. Restaurant names, phone numbers, order and database IDs removed.step wording pending verification against the recorded trace.
fig. 05 / anonymised recorded run
Guardrail checks, then
  • Open, pending, not yet contactedsend
  • Restaurant closedskip
  • Already contactedskip
  • Order no longer pendingskip
fig. 06 / send or skip
received WhatsApp reminder, redactedredacted screenshot pending
fig. 07 / real proof, redacted
implemented
  • Real WhatsApp Cloud API sending
  • Live Firestore connection
  • Order state re-checked before acting
  • Duplicate-reminder suppression
  • Closed-restaurant suppression
not yetcontinuous deployment · reply handling · broader operations automation
known limitationSome policy rules are still enforced through model instructions, not an independent deterministic layer.

MOTNIX Idea Scout Startup-opportunity research

python · gemini api · structured schemas · live web research
problem explored

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.

idea
hypotheses
researchlive web
evidenceclassified
unknowns
decision
next experiment
fig. 08 / from idea to next experiment
Evidence cardREAL CARD PENDING
type
confidence
source
linked question
Values from the anonymised recorded run.
fig. 09 / evidence card, real card pending
Research state
knownestablished by evidence
believedsignals and assumptions
unknownopen questions
riskywhere it could fail
fig. 10 / how evidence is separated
Decision states
KILLHOLDFIELD_VALIDATEBUILD_CANDIDATE

BUILD_CANDIDATE means ready for founder review and field validation. It is not an approval to build.

fig. 11 / decision support, not decisions
implemented
  • Live web research
  • Structured evidence extraction
  • Fact / signal / assumption / unknown classification
  • Risk and uncertainty tracking
  • Validation-experiment generation
not yetpersistent memory · field validation · production decision calibration
known limitationSome partially answered research questions can be closed too early. Decision-sufficiency logic is still being refined.

Full recorded traces, implementation checklists, architecture and limitations live on the Lab page.

Explore the Lab

We build for clients the way we build for ourselves.

An African technology company building software, AI and automation, for clients and for the products we run ourselves.

how we work / build · launch · scale

Build

Engineer the whole system, not only the screens.

ZajilCLIENT PROJECT
Client system: four roles, one application.
Launch

Put it into real use and learn from how it operates.

SudaFoodMOTNIX VENTURE
Soft launch / live pilot — Kigali.
Scale

Improve, automate and extend what proves valuable.

SudaFood Operations AgentPROTOTYPE
Exploring how a running operational system can be extended with intelligent automation.

One core team. The specialists each project needs.

A core team owns every project end to end. Specialists join around the technical needs each project actually has.

ventures to client work / what we learn running our own products comes back into client work

MobileFrontendBackendAIAutomationDesignCore team
fig. 12 / capabilities assembled around the core team, per project
a note from the founders

We started MOTNIX because we wanted to build, operate and learn from real systems — not just deliver screens.

The same discipline we apply to our own ventures shapes how we build for clients.

Abdelmoamen Mohammed AbdallaCo-Founder
Motman KabashiCo-Founder

Every project on this site is labelled for exactly what it is: client work, venture, prototype or simulation.

Let's build the system your business runs on.

Prefer to talk first?WhatsAppEmail