Illustrative run. No real orders, customers or teams.
Build · Launch · Scale
02 / selected work
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.
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.
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.
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.
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
01signalpending_late received
02orderstate: pending
03restaurantstate: open
04historyprevious reminder: none
05decisionsend reminder
06whatsapp apisuccess
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.
02 / 02PROTOTYPE
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.