06 · Integrations & tourism
Commerce, travel, tourism
Citizen Duka · ViuTravel · The Governors Camp · VFAW
Products feel finished when the edges connect — payments clear, messages land, APIs behave, and tourism operators can run without guessing what the systems will do next.
- Patterns
- Payments · SMS · USSD · APIs · notifications
- Domains
- Enterprise commerce · travel · tourism systems
- Also
- Async remote with EU stakeholders
Three fronts, one skill
Integrations look different in every industry and feel the same underneath: third parties on their own calendars, failure modes nobody demoed in the sales call, and business teams who need a rollout story that isn’t written in JSON.
Citizen Duka / Royal Media
Program delivery for Citizen Duka enterprise commerce and media — CMS work with payments, SMS, and USSD in the path, plus change management so adoption didn’t die after go-live.
ViuTravel
Platform and systems delivery for travel aggregation: payments, notifications, external APIs, cloud migration, async processing, and monitoring. The kind of stack where one flaky partner can make the whole product feel broken.
The Governors Camp (tourism)
Short consultancy with a tourism operator: internal systems support for the IT team — clarifying how operational assets and related records stay visible, owned, and usable day to day. High-level by design; no guest-facing product claims and no internals published.
VFAW — Voices for Animal Welfare
Remote systems support for a Paris-based international NGO bridging Europe and Africa — async collaboration, documentation, and operational continuity from Nairobi. Full story →
Partner takeaway
If your roadmap is blocked on channels, vendors, or tourism/hospitality systems that somehow never finish, I treat those as programs with owners, interfaces, and escalation paths — not as tickets hoping for luck.