Appopoleis
Ops systems for field teams that cannot afford messy follow-up.
Appopoleis turns the messages, calls, and voice notes your teams already send into logged work, routed tasks, and clear owner updates. Built in Mumbai, live on vessels, rentals, shops, and field teams internationally.
Live proof: 6 vessels · 30 crew · 1,000+ voice notes a week.
Mumbai-built ops systems
Built in Mumbai. Live on vessels, rentals, shops, and field teams in India, the UK, the US, and other international markets.
Flagship proof
Marine proves the ops system under real pressure.
We started with vessels because the operating pressure is unforgiving. Work comes in through messages, calls, and voice notes. Crews move fast. Owners need clear updates without chasing the bridge, the office, or old chat threads.
Live across 6 vessels · 30 crew · 1,000+ voice notes a week
See the marine system runningAlready live beyond marine
The same ops model runs across rentals, property, and shops.
SafarSetu uses the model for fleet rentals. LalaRente uses it for property follow-up. Khaki Post uses it for local marketing and shop operations. Different industries, same pattern: field messages become logged work, routed tasks, and owner-ready updates.
Marine / Riya
Bridge messages become logged work, routed tasks, and owner summaries — without chasing chat threads.
6 vessels · live
SafarSetu
Fleet rental ops: enquiry through booking and CRM until the vehicle is locked and the owner is clear.
safarseturentals.com
Khaki Post
Local shop ops: missed and completed calls route into one thread so replies and follow-up stay logged.
khakipost.com
LalaRente
Property follow-up ops: owner, tenant, vendor, and staff each see the jobs, money, and documents they need.
Multi-role property apps
Full portfolio with screenshots: appopoleis.com/pitch-deck
How we work
Four steps. You always know what is live.
Proof first. Then a quote. If we cannot show a live system that looks like your problem, we should not sell you one.
- 01
Name the constraint
What breaks today: missed calls, logsheets, arrears, bookings. Who has to use it. Which field channels already carry the work.
- 02
Thin slice, written
Scope, price, and a go-live date for one production path. Not a six-month transformation plan.
- 03
Ship and demo weekly
You see the real system, not a Figma. Crew or staff try it on their phones.
- 04
Run it
Deploy, hand over, and keep the same team on the ops box when something fails.
Questions
Straight answers
Describe the operating problem.
Who uses WhatsApp or the current app. What fails today. What has to be true in production. We reply from [email protected].