teko mobile

TEKO Platform – What was rebuilt and why

sales analysis and management dashboard

business platform built for desktop added a mobile, pocket-ready product people actually use for real-world moments

Quick summary

TEKO is the one-stop business platform for SMBs handling everything from CRM and inventory to bookings, payments, and a built-in website builder. A growing share of new users (about 14%) were in beauty and HoReCa, and they overwhelmingly used phones, not desktops. The platform wasn’t designed for that. I led the initiative to rethink TEKO around how people actually work – on smartphones, in noisy shops, between customers and make the essential tools accessible in one thumb.

Problem

TEKO offered many interconnected tools: CRM, POS, builder, analytics – but each was optimized for desktop. On mobile, features were hard to find, slow to load, and overwhelming.
Beauty and HoReCa businesses relied on their phones, not laptops, yet our flows ignored that context. Common tasks like updating availability or syncing listings felt clunky.
Our analytics showed a mobile bounce rate that undermined engagement across products.

Process

Segment audit

I mapped TEKO’s toolset and looked at usage by segment — beauty/HoReCa comprised 14% of users but had high mobile activity

1
Mobile-accessible roadmap

Facilitated workshops to figure out what tasks users really need fast: update items, check bookings, manage payments, update site – all on the go

2
Component overhaul:

Built responsive versions for every key element — collapsible lists, one-tap actions, lightweight navigation suited to low-power devices

3
Shared design tokens

We created mobile-first component guidelines that cascaded across modules – easier for engineering and visual consistency.

4
Testing on-site

I ran quick live sessions in cafés and salons to validate and iterate — in real noise, real light, real busy people – not labs

5

Hero decisions

Good Defaults

prioritize timely tasks like updating availability over buried menus
Thumb Zones

tap sizes, bottom nav, quick actions — designed for one-handed, hurried use
detailed onboarding

gently guided with all the information needed

Outcome

engagement

Platform engagement on mobile rose fast – people used TEKO during business hours much more often
simplicity

Support calls broke less – making changes felt possible, not intimidating
sustainability

Teams released new features faster, reusing mobile patterns across modules
growth

The shift set a new roadmap tone: future features must work on mobile as well as desktop, always