Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Use case · Real estate · India

Taking a real estate developer's sales, collections and customer portal mobile

A Flutter app on top of a real estate ERP that covers pre-sales, site visits, bookings, collections follow-up, channel partners, documents and a customer portal.

Client details are kept confidential. This use case describes the problem and what we built.

The brief

A software vendor that provides ERP systems to real estate developers wanted to take its sales and customer modules mobile. Developers’ sales, collections and channel-partner teams spend most of their day away from a desk, and buyers expect to check their bookings and payments from a phone.

We designed and built the Flutter app on top of the vendor’s existing ERP APIs. It covers the full journey from first call to post-sales collections, with portals for channel partners and buyers.

The challenge

What needed solving

Sales teams work in the field

Tele-callers, site-visit executives and sales managers were tied to desktop ERP screens, while most of their work happened on the phone or at the project site.

A long, multi-stage sales cycle

A flat moves from enquiry to site visit, quotation, token, booking, approvals, agreement and then months of payment demands and collections follow-up.

Partners and buyers need access too

Channel partners needed to register leads and download project documents. Buyers wanted to see their bookings, demands, receipts and agreements without calling the office.

The solution

What we built

  1. Pre-sales and tele-calling

    Tele-calling lists, calendar, customer search, follow-ups and re-open or discard flows, with call history and planned site visits.

  2. Sales to booking

    Enquiries and follow-ups, site-visit entry, visitor booking, unit quotation, token, unit booking, an approval process and a booked-unit list, all from the phone.

  3. Post-sales collections

    A recovery calendar with follow-ups and full follow-up history helps the collections team chase payment demands.

  4. Channel partner and customer portals

    Partners create executives, register leads and track booked leads. Buyers see booking, agreement, demand and receipt details, mapped documents, complaints and referrals.

  5. Documents and dynamic forms

    A document management module with folders and a file explorer, plus server-driven dynamic forms, let the ERP add fields without a new app release.

  6. Configurable, connected Flutter app

    Built in Flutter with the Stacked architecture and Dio, the app points at a configurable ERP server, uses Firebase for sign-in, push notifications, Crashlytics, Remote Config and analytics, and supports multiple languages and WhatsApp sharing.

The outcome

What changed

The ERP in every salesperson's pocket

Field teams update leads, visits and bookings as they happen instead of re-entering them at a desk.

Fewer calls to the office

Buyers and channel partners get self-service access to the information they ask for most.

One app, many deployments

Configurable server addresses and dynamic forms let the same app serve different ERP installations.

Technology used

  • Flutter
  • Dart
  • Stacked
  • Dio
  • Firebase Authentication
  • Firebase Cloud Messaging
  • Firebase Crashlytics
  • Firebase Remote Config
  • Firebase Analytics
  • Google Sign-In
  • Syncfusion Calendar
  • fl_chart
  • Geolocator

Have a similar problem to solve?

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk