Une plateforme de sécurité ne peut pas se permettre la latence — mais une équipe de 9 personnes ne peut pas couvrir chaque canal non plus.
MyHives est une application de sécurité personnelle pour les personnes qui ont besoin de voir le risque avant qu'il ne s'intensifie — navigation par itinéraires plus sûrs, un Journal de Sécurité pour les moments inquiétants, vérifications de confiance, escalade rapide en deçà du 112. En parallèle de l'application grand public, MyHives vend aux Organisations — écoles, employeurs, municipalités, autorités de transport — qui le déploient pour les personnes qu'elles servent.
Two product lines, one small team, and a category where response time is the product. A consumer user asking "how does the Safety Diary work?" at 11pm on a Saturday needs the same urgency as a school's Head of Safeguarding deciding whether to roll MyHives out to 4,000 students.
Before Joble, those two messages landed in different inboxes, handled by different people, with no shared memory between them. The team was rebuilding context, every conversation, from scratch.
Worse: the consumer support inbox, the Organisations sales pipeline, the partner onboarding tracker for businesses listed as Safety Signals, and the incident-escalation pager all lived in different tools. One person needed five tabs open to answer one question.
Hiring out of the problem was off the table. A mission-driven product on a careful budget can't scale the way a venture-funded SaaS does — every new hire is a real trade-off against feature work.