THE PROBLEM
Neebu is a travel app: plan a trip day by day with friends, keep it in one journal, then share it on a feed.
By late 2025 it had taken far longer than planned to reach the stores, and it still hadn’t settled. Each fix seemed to surface a new problem elsewhere. Neebu needed one team for the whole product.
WHAT WE BUILT
We took charge first, then steadied it.
Fix causes, not symptoms. We traced each item on the client’s list to where it broke, in the app or on the server, and fixed it there. So the same bug stopped coming back elsewhere.
Update the foundations first. We brought the app’s building blocks up to date, so later releases wouldn’t bring surprises.
Ship on a rhythm. Small, regular releases to both stores, with the client’s list as release notes.
THE RESULT
Neebu now releases on a schedule, and its open issues get fewer instead of moving around. One team runs the app, the server and the store listings.
The takeover became a standing retainer.
Search one city or several, starting from popular picks.
Schedule, travel companions and place to stay, in one trip.
No idea where to go? Get a ready-made plan.
Posts and tapes from other travellers. Follow the ones you like.
Save places by country; draft or archive your posts.
Every trip kept as a journal to look back on.
In the product.
Everything that shipped.
Need something like this?
Tell us what's broken or what you want to build. We'll reply with what we'd make and what it would take.
