BeMyNanny — Case Study

The first mobile application for finding a babysitter in Armenia. Verified nannies, structured selection, in-app booking and payment. Live at bemynanny.am; iOS app published on the App Store.

Summary

BeMyNanny is a two-sided marketplace where parents in Armenia find a vetted babysitter by need — when the service is required, where it'll happen, what type of nanny — and book and pay through the app. The platform is the first of its kind in Armenia and has been operating since 2023. topsweteam built it end-to-end with a small two-person engagement: one fullstack engineer plus one product manager. React Native on mobile, Django on the backend. The iOS app is live in the App Store.

• Client: BeMyNanny (bemynanny.am)
• Industry: Family services / Two-sided marketplace
• Region: Armenia
• Engagement: Full build — 1 fullstack engineer + 1 PM
• Timeline: Build started 2026
• Team: 1 fullstack engineer, 1 PM
• Status: Implemented; iOS app live in the App Store

Challenge

Childcare is a category where trust does the heavy lifting. The product can't simply be a search-and-book interface — it has to support a structured selection process behind the scenes (multi-stage screening, training and qualification standards, safety and ethical compliance) and surface the resulting trust signals cleanly in the app. On top of that, this is a regional marketplace in a small country: it has the same product surface as a marketplace in a large one, but has to ship at a fraction of the cost or it never breaks even. Doing both at once meant every architectural choice had to favor leverage.

Approach

The shape of the engagement was deliberate. One fullstack engineer plus a PM is enough to build a regional consumer marketplace if the tooling is right — and is much harder to manage if it isn't. Django gave us the operational surface for free (its built-in admin replaced an entire workstream of bespoke moderation tooling), and React Native let the same engineer ship the mobile app without learning two native platforms.

• Django for the backend. Auth, admin, ORM, forms, migrations all out of the box. The Django admin handles the operations side of the business — managing the nanny roster, screening status, and content — without a custom back-office.
• React Native for mobile. One codebase across iOS and Android; iOS is the published platform.
• PM embedded in the engagement. With a one-engineer build, the PM's role is to keep scope honest. Cutting features early is more valuable than building them well late.

Solution

The product covers the full marketplace flow on top of a structured nanny pipeline that runs operationally. The user journey is six steps: log in to the app → set needs (when, where, what type of nanny) → choose a nanny from the matched list → wait for the nanny to confirm the request → pay through the app → service begins. Backend is a Django monolith; mobile is React Native; operations is handled through the Django admin, which is also where the multi-stage screening status of every nanny is managed.

Key features shipped

• Sign-in and parent onboarding — the entry point to the app
• Need-based search and filters — when the service is needed, where it will take place, what type of nanny is required
• Nanny profiles — clear, comparable, with the verification status that backs the trust narrative
• Booking flow — request → nanny confirmation → service start
• In-app secure payment — the parent pays after the nanny has confirmed; the booking activates on payment
• Operations / nanny pipeline in the Django admin — managing the multi-stage screening, training, and compliance state of the nanny roster

Outcome

The app is published on the App Store and operating in market in Armenia. The two-person engagement model held up — the product shipped without needing to scale the team mid-build. BeMyNanny markets itself as the first mobile app for finding a babysitter in Armenia and has been running since 2023.

• iOS app live on the App Store
• bemynanny.am operating in market
• First-of-its-kind in Armenia
• Two-person engagement (1 engineer + 1 PM) shipped a full marketplace end to end

Tech stack

Backend: Python, Django Mobile: React Native Region: Armenia (Armenian-language web; iOS app live in the regional App Store)

What we learned

• One engineer plus one PM is the right shape for a regional consumer marketplace — provided the engineer is fullstack and the PM owns scope discipline. Adding a third person at this size adds coordination cost without proportional throughput.
• Django's built-in admin is the leverage point. A custom back-office for a marketplace this size is throwaway work; using the admin frees an entire workstream and is the right surface for the multi-stage screening pipeline.
• Trust-heavy categories live or die on the operational pipeline behind the app. The visible product is a marketplace; the underlying business is a structured screening process. The case study has to honor both.