
Software6 min
Software has to survive the person who built it
A tool that only the builder understands is a temporary fix. The operation has to be able to keep it.

About
A product is not finished at launch. Usage changes. Integrations pile up. The organisation moves, and the app has to move with it or people stop opening it.
We build mobile apps for the people who buy, for partners, and for teams. Then we stay with them, or we hand them over so someone else can keep them.

25%
global median still using the app on day 1
6%
still using it on day 30
9%
day 30 median for fintech and lifestyle
2%
day 30 median for hyper casual
Figures from Adjust, mobile app retention benchmarks. Adjust reports 2022 global median retention of 25% on day 1, 9% on day 14, and 6% on day 30. Fintech and lifestyle led day 30 at 9%. Hyper casual sat at 2% on day 30.
Offerings
A polished first version is easy. A mobile app someone else can run next week is the actual job.
01
Screens, navigation and performance for a hand, not a desktop layout squeezed down.
02
Screens that match how people actually move through the work on a phone, including the cases that look ugly in a deck.
03
Integrations after the core works. Connecting everything first is how a launch slips.
04
We stay as usage changes, or we hand over access, logging and an owner so it does not sit in a folder.
Insights

Software6 min
A tool that only the builder understands is a temporary fix. The operation has to be able to keep it.

Approach5 min
If nobody else can run it next week, it is not live. Handover is part of the product.

Design4 min
A polished demo is easy. A screen people will use on a Tuesday is the actual job.