Lost & Found Listing Platform · Urban mobility · Public transport · Civic services

One map for everything a city loses

Supremacy designed and built Loztapp — a lost-and-found listing platform for a whole city. A mobile app for the public, a map-first search layer over stations, bus routes and public areas, and an operator dashboard for the counters that actually hold the items.

Start a project See the outcome

6 months — listing core and mobile app (3 months), maps, matching and chat (2 months), operator dashboard and city launch (1 month)

The Lozt operator overview on a MacBook Pro beside the app’s route search on an iPhone in a stand, on a desk at the edge of a railway platform: 1,482 active listings, 320 claims pending, ₹24,36,800 held in escrow and 812 items returned on the laptop, and 11 items found along the Route 14 bus from Mill Road to Riverside Central on the phone

48,000+

Items listed in year one

Across 9 railway stations, 340 bus routes and public areas

61%

Reunited with their owner

Of listings closed as returned within 30 days

36 hrs

Median time to first match

From a found item being posted to the owner being notified

Losing something in a city meant starting a search with no map. Every railway station kept its own paper register, every bus depot its own cupboard of unclaimed bags, and everything else — parks, markets, cabs, cinemas — had nowhere to report to at all. People filed the same description four times over WhatsApp, station counters, and social media posts that went nowhere, while the item itself often sat two kilometres away in a lost-property drawer nobody could search. Roughly nine in ten found items were never matched to an owner, not because they were gone, but because the person looking and the person holding had no shared place to look.

01Console
The operator console
Station staff and moderators work the same records the public app writes to. The overview opens on the four numbers that decide the day — active listings, claims pending, value held in escrow, items returned — beside a recoveries-this-week chart, the top categories a city actually loses, and a live activity feed. Users carries the trust model: found-and-returned counts, ratings, verification level and a flag state. Reports is the moderation queue, severity-ranked, with resolved reports auto-archiving after thirty days. Settings is where the economics live — service fee per recovery, escrow hold period, minimum reward, the category tree, and the verified Safe Meet points across the city.
- Operator & moderation dashboard
02Listings
Every item in the city, on one board
The listings console holds all 128 live items in a single filterable table — item, category, location, who posted it, the reward offered and where it sits in the lifecycle. Filter to Active, Claimed or Returned, search across items, claims and users from one bar, and post a found item straight from the counter on a resident's behalf.
- Category taxonomy & filters
03Claims
Claims reviewed on evidence, not instinct
Each claim arrives as a card with the owner's verification answers set against the finder's private notes, and the system says outright whether they match, partially match, or have a follow-up question outstanding. Approve or reject in one action; claims left waiting past the SLA are flagged Overdue so nothing sits unanswered.
- Match, claim & handover engine
04Payments
Rewards held in escrow until the handover is real
Payments and escrow in one ledger: what is held, what was released this month, and the service fee earned on each recovery. Every transaction shows the item, both parties, the method — UPI, card or net banking — and its state, from In escrow to Released to Refunded when a handover never happens.
05Trust
Trust, built in
A lost-and-found platform lives or dies on whether a handover is safe. Claim verification can be made mandatory, reported listings auto-hide after three independent reports, ID documents in photos are detected and blurred, and every reward sits in escrow on a seven-day hold that auto-refunds if the handover is never confirmed. None of it was bolted on after launch — it is the settings page the product shipped with.
06Listing app
List
A one-minute posting flow with photos and a deep category tree, map-first browse and search, saved searches, bookmarks, and public listing pages that are shareable and indexable.
- iOS & Android listing app
07Maps
Locate
Clustered map pins, Places autocomplete, street-level geocoding, radius and route-corridor search, transit-hub geofences and directions to the handover point.
- Map & geo-search layer
08Matching
Reunite
Automatic lost-to-found matching on category, place and time window, push notifications to both sides, in-app chat, ownership verification and a logged handover.
09One record
One record, from report to reunion
A lost report, a found item, the match, the chat, the claim and the handover are stages of the same record — so nothing has to be reconciled by hand between a station counter, a moderator and the person on the app.

Delivery

Built module by module

Seven surfaces in the operator console, each delivered production-grade and rolled out in stages — first a single railway line, then the bus network, then open public areas — so coverage grew without a risky city-wide cutover.

The Lozt operator overview on a MacBook Pro, the app’s “Lost something?” home screen on an iPhone beside it, on a desk on a metro platform: 1,482 active listings, 320 claims pending, ₹24,36,800 held in escrow and 812 items returned in the last 30 days, over a recoveries-per-day chart, a map of the last 24 hours’ activity across Rivermere, the categories the city loses most — phones, wallets, bags, keys — and a latest-activity feed

The found-items board on a MacBook Pro, the app’s route search on an iPhone beside it, on a desk on a station platform: 1,482 active items tabbed beside 320 claimed and 812 returned, every row carrying the item, its Lozt reference, category, location, who posted it, the reward and the date found, with a black backpack found at Riverside Central, platform 3, open in the detail panel

01Overview
Overview
The day in four numbers — active listings, claims pending, value held in escrow and items returned — with a recoveries-this-week chart, the categories the city loses most, and a live activity feed running from claims submitted to escrow released to listings reported.
02Listings
Listings
All live items in one filterable table: item, category, location, who posted it, reward and lifecycle state. Filter by Active, Claimed or Returned, search items, claims and users from a single bar, and post a found item on a resident's behalf from the counter.
03Claims
Claims
Claims arrive as review cards pairing the owner's verification answers with the finder's private notes, marked as matching, partially matching, or awaiting a follow-up. Approve or reject in one action; anything past the SLA is flagged Overdue.
04Payments
Payments
One escrow ledger — held, released this month, service fees earned — and a transaction list carrying the item, both parties, the method (UPI, card or net banking) and its state from In escrow to Released to Refunded.
05Users
Users
The trust model, made legible: when someone joined, how many items they have found versus returned, their rating, their verification level, and whether they are active or flagged — so a badge on a public listing means something specific.
06Reports
Reports
The moderation queue, severity-ranked across spam, duplicates, wrong category and personal information visible in a photo — with who reported it, how long it has been open, and Review or Dismiss on every row. Resolved reports auto-archive after thirty days.

The operator overview: 1,482 active listings, 320 claims pending, ₹24,36,800 in escrow and 812 items returned, over recoveries per day, a map of the last 24 hours across Rivermere, the top categories and a latest-activity feed — on a MacBook Pro beside the app’s home screen on an iPhone

The found-items board: 1,482 active items in one filterable table — item, reference number, category, location, who posted it, reward and date found — with a black backpack opened in the detail panel beside it — on a MacBook Pro beside the app’s route search on an iPhone

The claims queue: twelve pending claims down the left, and a claim setting the owner’s answers against the finder’s private notes row by row — each marked match, partial match or follow-up needed — over reject and approve, with the evidence photos and the handover point alongside — on a MacBook Pro beside the claim flow on an iPhone

The payments console: ₹24,36,800 held in escrow, ₹18,52,400 released this month, ₹1,24,600 refunded and ₹92,340 in service fees earned, above a ledger carrying the item, the finder, the owner, the payment method — UPI, credit card or net banking — and whether it sits in escrow, released or refunded — on a MacBook Pro beside the reward payment on an iPhone

The reports and moderation queue: reported listings tabbed by spam, duplicates, wrong category and personal info, each row carrying the reason, who reported it, how long it has been open, its severity and Review or Dismiss, beside the moderation policies and the Safe Meet points — on a MacBook Pro beside the Report Listing screen on an iPhone

The settings console: a ₹49 service fee per recovery, a 7-day escrow hold, a ₹100 minimum and ₹5,000 maximum reward, moderation switches for auto-hiding after 3 reports, claim verification, blurring ID documents and guest claims, nine categories with their live listings and the claim questions for bags, and four Safe Meet points across Rivermere on a map — on a MacBook Pro beside the claim confirmation on an iPhone

The app’s home screen asking “Lost something?” over a search of 1,482 found items, with transport, stations, public areas and civic services shortcuts and a recently-added rail of white earbuds and a black backpack — on an iPhone

Search along a route: the Route 14 bus from Mill Road to Riverside Central, 11 items clustered along the corridor on the map, and white earbuds found on the bus docked at the bottom with a ₹300 reward — on an iPhone

The reward payment for a black backpack: a ₹500 reward and a ₹49 service fee, ₹549 in all, by UPI, card or net banking, held in escrow from payment made through item handed over to finder paid, with an auto-refund after 7 days — on an iPhone

Mobile app — report a listing — on an iPhone

“Your claim is confirmed” for a black backpack: handover code L-4821, the platform 3 counter at Riverside Central as the Safe Meet point, tomorrow at 5:30 pm, and ₹549 held in escrow until the handover, over Open chat with the finder and Get directions — on an iPhone

0107Overview

Approach

Making people describe a loss by journey, not by address

Verifying a claim without putting anyone in a risky handover

We rode the routes. Two weeks were spent at station lost-property counters, in bus depots, and with commuters who had recently lost something, and the pattern was consistent: people describe a loss by journey, not by address. Nobody says '18.9° north' — they say 'the 7:40 fast local, somewhere between Dadar and Andheri.' So the map had to speak in stations, routes, and landmarks before it spoke in coordinates. The second finding shaped the claim flow: counter staff were not short of items, they were short of proof, and had no safe way to hand something over to a stranger who sounded convincing. That is why verification questions, chat history, and a designated handover point are part of the listing rather than bolted on after a match.

Built for the public, not just the counter

The app has to work one-handed on a platform with a train pulling in. Posting is three steps, search opens on a map, and nothing needs an account until a claim starts.

Location as a first-class field

Stations, routes and landmarks are modelled properly at the data layer — not free text — so a report can be searched by radius, by route corridor or by geofence.

Safe by default

Ownership proof, moderated images, verified handover points and a logged exchange on every claim, so a match never turns into an unsafe meeting.

React Native (iOS + Android)Mobile app
Node.jsBackend
PostgreSQL + PostGISDatabase
Google Maps Platform (Maps SDK, Places, Geocoding)Maps
ElasticsearchSearch
Next.js (operator dashboard)Framework
AWS S3 + image moderationCloud
DockerContainers

Category: Lost & Found Listing Platform
Industry: Urban mobility · Public transport · Civic services
Scope: 6 months — listing core and mobile app (3 months), maps, matching and chat (2 months), operator dashboard and city launch (1 month)

Delivered5

01
iOS & Android listing app
02
Map & geo-search layer
03
Category taxonomy & filters
04
Match, claim & handover engine
05
Operator & moderation dashboard

In the first year the platform carried more than 48,000 listings across nine railway stations, 340 bus routes, and open public areas — and closed 61% of them as returned to their owner, against a baseline where fewer than one in ten found items ever found a claimant. Median time from a found item being posted to the right person being notified settled at 36 hours, most of it waiting for the owner to open the app rather than for the system to find the match. Station counters saw walk-in enquiries drop by 38% as people checked the map first, and the operator dashboard turned what had been shelves of anonymous property into a searchable, auditable inventory.

Production, not prototypes
Moderation queues, audit trails, abuse reporting and claim SLAs were built in from the first release — a public platform can't add them later.
Depth where it counts
Route-corridor and geofence search over live map data is hard to get right. We modelled it properly on PostGIS rather than approximating with a bounding box.
Built for a public marketplace
Image moderation, duplicate and fraud flags, reporting on every listing and a severity-ranked review queue — the things a platform open to a whole city cannot add later.

“We were never short of lost property — we were short of a way for the right person to find it. Now the shelf is a searchable list, and most of it walks back out with its owner.”

— Head of Passenger Services, City Rail

Next projects

01UNO MindaProduction Management & QC System
02NeuroSynk ResearchERP · LMS · Aviation
03WindzardEnterprise HR, Finance, Work & Events Platform

Your project

Let's build yours.

One conversation to scope it. One team from first screen to launch.

Start a project See all work

Loading…

FAQs

Frequently Asked Questions

SaaS and platform products, custom software built for one company, and the management systems a business runs on — ERP, CRM, HRMS and payroll, invoicing and finance, inventory and warehouse management. Around those: web applications, native mobile apps for iOS and Android, marketplace and e-commerce platforms, and AI integration built into the systems rather than bolted beside them.

A focused first release typically ships in 8–12 weeks. Multi-module enterprise platforms run 4–9 months, delivered module by module so you are using working software long before the final release rather than waiting on a single big-bang launch.

Both. A well-defined scope gets a fixed price against a signed specification. Longer or evolving builds run as a dedicated team on a monthly retainer. Either way you get a written estimate with every assumption listed before a contract exists, so you can see exactly what moves the number.

Discovery and scoping, then UI/UX design, then two-week build sprints that each end in a working demo. You get a staging environment from the first week, and QA, security review and deployment run inside the sprint instead of being bolted on at the end.

You do, in full, on final payment. Source code, design files, infrastructure and documentation are handed over in your own repositories and cloud accounts. We keep no licence over your product and there is no lock-in to our hosting.

Yes. We connect to the ERP, CRM, HR and accounting platforms you already run, payment gateways, WhatsApp Business, warehouse and production systems, and legacy in-house databases. Where no API exists we build a sync layer and migrate historical records with reconciliation reports your finance team can check line by line.

Every project closes with a handover: documentation, team training, and a warranty period covering defects at no cost. After that you can run support in-house or keep us on a monthly plan covering monitoring, security patches, and an agreed block of enhancement hours.

We sign your NDA before the first technical conversation. Builds ship with role-based access, encryption in transit and at rest, and audit logging as standard. Production data stays inside your infrastructure and access is limited to the engineers assigned to your project.

Start a project