Tyme is a multi-country digital banking group focused on serving consumers and SMEs across South Africa, the Philippines, and Indonesia, Hong Kong. Trusted by over 17 million customers and 150,000 SMEs, Tyme has reached unicorn status in late 2024 following a US$250 million Series D capital raise and made it onto TIME’s 2025 list of the 100 Most Influential Companies in the World.

We design, build, and enable our digital banks, by leveraging technology innovatively, through a high tech-high touch approach, to meet the needs of customers. From building the bank to running the platform, Tyme puts in place an expert team of engineers, designers and problem solvers to grow and scale with the bank. A tech business strategy is only as good as the people behind it.

Many platform teams build tools, but forget their real goal: helping developers work faster, safer to provide better banking experiences for our end customer. In this session, I’ll share how our team changed from building services (Platform-as-a-Service) to building real products for developers (Platform-as-a-Product). We learned to treat our internal users like real customers. We listened to their needs, improved usability, and focused on adoption—not just delivery. I’ll show the steps we took, what worked, and what mistakes we made. If your platform team is stuck doing support tickets or struggling with adoption, this talk will give you a clear way forward.

Key result:

Understand the difference between platform as a service vs. platform as a product.

Learn how to group and understand your internal developer users.

See how feedback, demos, and small launches help improve adoption.

Use easy tools like office hours and release notes to connect with your users.

Avoid common mistakes like overbuilding and poor migration plans.