How to make an app for a builder

A builder's sales office follows hundreds of enquiries, books site visits, keeps track of which flat in which tower is sold, and then collects payments from each buyer as construction reaches each stage. An app for your sales and accounts team keeps all of that in one place, by project.

Updated 2026-11-09

Who uses the app

The sales team, the site office and accounts, often on different phones. Since they must all see the same unit list and buyers, connect your own Supabase database with sign-in for each person. A small builder with one sales person can start with data on one phone.

The screens a builder app needs

• Enquiries: Each lead with name, phone, flat type wanted, budget, source and the next follow-up date
• Site visits: Visits by date with who came, which flats they saw and the sales person's notes
• Units: Every flat by tower and floor with type, carpet area, price and status: available, on hold, booked or sold
• Bookings: Buyer details, flat booked, agreed price, booking amount received and the payment plan
• Payment stages: Each buyer's instalments linked to construction stages, such as plinth or each slab, with what is paid and due
• Projects: Each project with towers, construction stage and dated site photos

Features worth asking for

• A unit list that changes a flat to booked once a booking is saved, so two sales people can't sell it twice
• A demand letter PDF for a construction stage with the buyer's name, flat and amount due
• A WhatsApp button that sends a site visit time and the Google Maps link to the site office
• A follow-up list of enquiries due today
• A cost sheet PDF for a chosen flat with base price and the charges you list
• A dues list of buyers who haven't paid the current stage
• Construction progress photos attached to each project by month

Where the data lives

A shared unit list needs your own Supabase database, connected from the chat, so sales and accounts see the same flats and buyers. Booking amounts can be paid online through your own Razorpay account; large instalments usually come by bank transfer, which you record in the app.

How to make it with AppCub, step by step

1. Decide what the app does. List the screens you need, for example: Enquiries, Site visits, Units, Bookings, Payment stages.
2. Describe it to AppCub. Paste the request below, changed to your own business and details.
3. Check the plan. AppCub shows the screens and features it will build. Change them in the chat until they are right; seeing the plan is free.
4. Try it on your phone. The app runs live next to the chat. Scan the QR code to install it, and ask for changes.
5. Share it. Share it as a web link, an APK file, or publish it on Google Play from your own developer account.

Copy this request, change the details to match your builder, and paste it into AppCub:

Tips for a builder app

• Start with enquiries, site visits and the unit list. Add payment stages and demand letters after the first month.
• Load the unit list once from your sales chart, tower by tower, and check it with the sales head before going live.
• Write down your payment plan and stage percentages exactly as in your agreement, and give AppCub the same.
• Give each person only the screens they need, such as sales without the accounts screens, and keep sign-in on.
• Have your accountant check the cost sheet and demand letter formats before they go to buyers.

What it costs

• Describing your app and seeing AppCub’s plan for it is free.
• A new app usually takes 60 to 110 credits. Start with the 2-day trial for ₹99 (150 credits, enough for one app and a few changes) or the one-time App Pack for ₹499. Starter is ₹1,599 a month for 700 credits.
• Google Play needs a paid plan (it includes the Play Store bundle and your app’s signing key) and your own Google Play developer account, a one-time US$25 fee to Google.
• Work that fails or is rolled back costs no credits.

See all plans

Good to know

• AppCub doesn't connect to your accounting software, bank statements or property portals, and sends nothing automatically. Demand letters and reminders go out when your team shares the PDF or taps the WhatsApp button.
• AppCub builds Android apps. You can also share the app as a web link that opens on any phone; for the iPhone App Store, AppCub’s team can do it for you.

Questions

Can the app stop the same flat being sold twice?

Yes, when it uses your own Supabase database. Once a flat is marked on hold or booked, every sales phone shows it as taken.

Can the app make demand letters for each construction stage?

Yes. Mark the stage reached for a tower, and the app makes a demand letter PDF for each buyer in it with the amount due, to share or print.

Can I track which sales person brought each booking?

Yes. Ask for a sales person on every enquiry and booking, and a report of site visits and bookings for each person by month.

Can buyers check their payment status in an app?

It can be built with sign-in, so each buyer sees only their own flat, payments and construction photos. It needs your Supabase database.

Can buyers pay the booking amount in the app?

Yes, with a payment button on your own Razorpay account, after you connect Razorpay and Supabase in the chat. The money goes to you, not AppCub.

Can enquiries from property portals come into the app?

Not by themselves. AppCub doesn't connect to property portals; your team adds those leads with the source noted, so you can see which source brings visits.

Read next

• How to make a website for a builder
• App for a coworking space
• App for a guest house
• App for a homestay
• App for a hostel
• App for a hotel
• App for a housing society
• All guides: property and stay
• All app guides by business