I'm Timothy Mwangi, based in Nairobi, Kenya. My career started at ALX, first in software engineering and then the virtual assistant programme. I volunteered in the community and supported more than 2,000 learners across my roles. For VA cohort 14, I ran weekly sessions and gave one-to-one support, routing issues to the right people. I walked 160+ learners from week one to graduation at the ALX hub, Nation Centre, Nairobi.
I was the main contact for 70+ founders in Startup Garage Academy cohort 1 from May to September 2025, following up with every founder through to graduation. Today I coordinate Hackhouse Wazee, a group of entrepreneurs who meet every Wednesday at Hackhouse Africa. I make sure each meetup happens and the work gets done. I also run Hackhouse's social media, help with the Residency and look after alumni relations at AfricaHackon.
I build and run the Latitude59 Partner Hub, the partner CRM behind Estonia's flagship tech conference. At AfriESG Metrics, I do product work and built the public website and CMS. Since June 2026, I have shipped eight production systems. The latest is Canvathon Kenya's event platform, built in one day. I also helped plan the student design hackathon and run it on 3 October 2026.
How I work.
What you can expect when we work together.
01
Follow up before someone disappears.
A missed session is a reason to check in. I make room for one-to-one support and get problems to the person who can resolve them.
02
Put a name and a date next to it.
A task sitting between two people is easy to lose. I make sure someone owns the next step and knows when it is due.
03
Write the process before automating it.
I run through the steps with the team first. Then I automate the repeat work, so a confused process does not become a faster confused process.
04
You should not have to chase an update.
I write down what is done and what is stuck. If I need a decision from you, I say which one and when.
05
Start with the work that hurts most.
I would rather fix the report that takes your Friday than build a dashboard nobody opens. We agree on the problem before choosing the tool.
06
Watch someone use it.
Feedback from the people doing the work belongs in the next release. I check the flow with them and change what gets in their way.
07
Stay after launch.
A live system needs an owner. I agree on the ongoing support and keep the runbook current so the team knows what to do when something stops working.
08
Hand over the keys.
Your team should be able to change a page or run a report without waiting for me. I hand over access and walk you through the system.