Founder
Mwesigwa Trevor Joseph
Software engineer and technology entrepreneur, working from Kampala, Uganda. He founded Trevor Digital Solutions to take on client software the way he thought it should be done — understand the business first, scope honestly, build properly, and stay responsible for the result.
Mwesigwa Trevor Joseph
Founder & CEO
Kampala, Uganda
Professional introduction
Trevor works across the whole software lifecycle rather than one layer of it — the conversation that establishes what a business needs, the data model underneath, the interface on top, and the infrastructure it runs on.
That range came from the kind of work available in Kampala, where a client rarely wants a specialist for one slice of a system. They want the system: the stock control and the reporting and the phone app the branch staff use, delivered by someone who will still be there when it needs changing.
Alongside business software he specialises in trading technology, building expert advisors and indicators for MetaTrader 4 and 5. The discipline there is unforgiving — an ambiguous rule becomes a losing trade rather than a support ticket — and it shaped how he writes requirements everywhere else.
As a technology consultant he also advises organisations on architecture, cloud migration and where automation or AI genuinely earns its cost, including when the honest answer is that a project should not be built at all.
Working with him directly
Discovery conversations, architecture reviews and project scoping happen with Trevor himself rather than a sales team. For most clients that means the person estimating the work is the person who will do it.
What he focuses on
Five areas of hands-on work.
Not a list of everything touched once. These are the areas he builds in regularly, with the tools used day to day.
- 01
Software engineering
Full-stack delivery across the whole lifecycle rather than one layer of it: the conversation that establishes what a business needs, the data model underneath, the interface on top and the infrastructure it runs on.
Architecture decisions get made by the person who will also maintain the result, which tends to produce more conservative and more durable choices.
Works with
- TypeScript
- React
- Next.js
- Node.js
- Python
- PostgreSQL
- 02
Business systems
SACCO and financial platforms, inventory and stock control, CRM and sector-specific management systems — including the process mapping and data migration that decide whether a system is adopted or quietly abandoned.
The hard part is rarely the code. It is documenting how the work is actually done, workarounds included, before any of it is automated.
Works with
- PostgreSQL
- Supabase
- Node.js
- Redis
- Docker
- 03
Web and mobile development
Company websites and web applications built to be fast on mobile data and legible to search engines, plus Android and iOS applications from a single Flutter codebase.
Built for the networks users actually have: offline-tolerant where staff work in the field, and light enough to load on a low-end phone.
Works with
- Next.js
- React
- Flutter
- Dart
- Tailwind CSS
- Vercel
- 04
AI and automation
Narrow, measurable automation of repetitive work: document and invoice processing, support assistants, classification and routing, and workflows that move data between systems without anyone re-typing it.
Scoped to the tasks that genuinely consume staff time, and evaluated against a measured accuracy figure rather than an impression.
Works with
- Python
- FastAPI
- Claude API
- OpenAI API
- PostgreSQL
- 05
Trading technology and Expert Advisor development
Automated trading systems for MetaTrader 4 and MetaTrader 5: expert advisors coded to a documented strategy, custom indicators, backtesting and optimisation, risk management modules and multi-account dashboards.
An unforgiving discipline — an ambiguous rule becomes a losing trade rather than a support ticket — and it shaped how requirements get specified everywhere else.
Works with
- MQL4
- MQL5
- MetaTrader 4
- MetaTrader 5
- Python
- C++
Approach
Software rarely fails for purely technical reasons. It usually fails because the wrong thing was agreed to build.
That is why discovery is treated as engineering work here rather than a sales formality, why scope is written down before development starts, and why a client occasionally gets told their project is not worth building. It is a slower way to win work and a considerably cheaper way to deliver it.
How TDS worksWork directly with the founder.
Early-stage conversations, architecture reviews and project scoping happen with Trevor himself, not a sales team.