Jarvis Office Hub
A browser-based operating environment for the work that keeps multi-company offices moving.
View project
Founder · Operator · Botswana
I turn real operational problems into useful software, applying AI and entrepreneurship to the everyday work of learning, mobility, tourism and running businesses.
01 / The work
Six public products across office operations, learning, mobility, identity and tourism. Each starts with a workflow that needs to become clearer, safer or easier to access.
A browser-based operating environment for the work that keeps multi-company offices moving.
View project
A study workflow that turns source documents into useful active-recall practice.
View projectBotswana Class B/EB road-theory preparation built around practice, explanation and access.
View project
A Botswana-focused verification network for safer, more accountable car-rental records.
View project
A reusable authentication, profile and role-routing foundation for reliable access.
View project
A discovery and planning platform for finding Botswana’s places, experiences and local operators.
View project
02 / Shared foundations
Different sectors repeat the same underlying needs. Building those foundations well makes every product more dependable.
03 / Operations before software
Contracts, cars, compliance, finance, tenders, records, project delivery and everyday office operations shape what gets built. They reveal where information goes missing, where decisions slow down and where accountability needs a stronger trail.
Software follows that reality. The goal is to preserve the controls that matter, remove avoidable friction and leave the people doing the work with a system they can trust.
04 / Building in Botswana
Botswana already has valuable services, knowledge and operators. The opportunity is often to improve discovery, connect fragmented workflows and make that value easier to access digitally.
That means respecting familiar channels, practical constraints and the way trust is established locally. Technology is strongest when it fits the setting instead of asking the setting to fit the technology.
05 / What I’m learning
Choosing the smallest useful improvement before adding another surface.
Making decisions and processes legible beyond the person who created them.
Keeping enough history to understand what happened and why.
Seeing identity, records, permissions and outcomes as one connected flow.
Learning across accounting, compliance, software and operations.
Sharing useful thinking without overstating unfinished work.
06 / Now
The work remains connected by a practical question: what system would make this operation more reliable?
07 / Notes
Short observations about product work, operational reality and the infrastructure people rarely see.
The best starting point is often not a feature list, but a real sequence of work that already has consequences.
Read noteAutomation becomes dependable when the information underneath it has ownership, context and a traceable history.
Read noteWhat feels simple to a user is often supported by careful decisions about identity, permissions, failure and recovery.
Read note