What we build, and why it works.
Seven ways we help businesses run and grow. Each starts with the problem you have today, not the technology.
01 / 07
Custom software and SaaS
Web platforms built for how your business actually runs, multi-tenant when needed.
- The problem
- Off-the-shelf software makes you work its way. Spreadsheets and WhatsApp groups stop scaling once you have more than one branch.
- What we build
- Web platforms shaped around your real workflow
- Multi-tenant SaaS, with each customer's data kept separate in the database
- Dashboards and reports for owners and managers
- Typical stack
- Python (FastAPI, Django)
- Next.js
- PostgreSQL
- Redis
- Example
- Kwanix
A multi-tenant SaaS for inter-city bus companies, with data isolation enforced in PostgreSQL.
02 / 07
Web and mobile apps
Next.js web apps, React Native and PWA mobile apps, offline-first where the network is unreliable.
- The problem
- Your staff and customers are on phones, often on patchy mobile data. Apps that freeze without a connection lose sales and records.
- What we build
- Fast Next.js and React web apps
- React Native and installable PWA mobile apps
- Offline-first apps that sync when the connection returns
- Typical stack
- Next.js
- React
- React Native
- PWA
- TypeScript
- Example
- Nkabom
An offline-first PWA for daycares that works on unreliable connections and needs no app store.
03 / 07
ERP and Odoo
Implementation, custom modules and integration with the systems you already use.
- The problem
- Stock, payroll and approvals live in different places, so nobody trusts the numbers and audits take weeks.
- What we build
- Odoo implementation and configuration
- Custom modules: inventory, payroll, audit trails, org charts
- Integration with your existing systems
- Typical stack
- Odoo
- Python
- PostgreSQL
- Example
- GMAK Properties
A real-estate site with an Odoo backend for leads, contracts and properties (founder's project).
04 / 07
Payments, SMS and integrations
Mobile Money and card payments, SMS, WhatsApp notifications and store-to-ERP sync.
- The problem
- Customers want to pay with Mobile Money and hear back by SMS. Online orders that don't reach your ERP mean overselling and manual re-entry.
- What we build
- Mobile Money and card payments with Paystack
- SMS with Arkesel, and WhatsApp notifications
- Shopify or WooCommerce to ERP sync
- Typical stack
- Paystack
- Arkesel
- Shopify
- WooCommerce
- Celery and Redis
- Example
- MCEES Engine
Async middleware that syncs Shopify and WooCommerce into Odoo, with Redis locks to prevent overselling (founder's project).
05 / 07
AI for business
Question-answering over your documents, data extraction and automation. On-premise when data must stay in-house.
- The problem
- Your team spends hours searching documents and copying data between systems. Sensitive records can't be sent to just any cloud service.
- What we build
- Document question-answering (RAG) over your own files
- Data extraction and workflow automation
- On-premise models so sensitive data stays in-house
- Typical stack
- Python
- LangChain
- OpenAI API
- On-premise LLMs
- Example
- AI CV optimiser
Upload a CV and a job description; AI returns specific improvements (founder's project).
06 / 07
Cloud, DevOps and modernisation
Monoliths to microservices, CI/CD, Docker and Kubernetes, AWS and uptime monitoring.
- The problem
- Releases are risky, the old system is slow to change, and you find out about downtime from your customers.
- What we build
- Moving monoliths to microservices
- CI/CD pipelines for safe, repeatable releases
- Docker and Kubernetes on AWS, with uptime monitoring
- Typical stack
- Docker
- Kubernetes
- AWS
- CI/CD
- Monitoring
- Example
- WASSCE Analytics
A parsing service with Celery workers, Redis and S3-compatible storage, with each school isolated in its own schema.
07 / 07
Product and UI/UX design
Brand identity, design systems and mobile app UI kits.
- The problem
- A product that is hard to use doesn't get used, especially by first-time smartphone users.
- What we build
- Brand identity
- Design systems
- Mobile app UI kits
- Typical stack
- Brand identity
- Design systems
- UI kits
- Example
- FlexiFund
Brand identity and a mobile app UI kit for underbanked savers: onboarding, savings goals and loan applications.
Let's build something that lasts.
Tell us what slows your business down, and we'll suggest the simplest system that fixes it.