AxisIQ for real estate developers and brokerages

AxisIQ runs a developer's sales and collections: RERA projects, unit inventory, leads, site visits, bookings, payment plans, demands, registration and handover.

AxisIQ is the sales, collections and possession system for Indian real estate developers and large brokerages: one live workspace where every RERA project, tower and unit sits beside the leads enquiring about it, the site visits they make, the booking that blocks the unit, the construction-linked payment plan behind it, each demand letter and receipt, the buyer's home loan, the registration at the sub-registrar and the final handover with its snag list. The Real Estate template sets this up at signup — apps, record types, roles, five automation flows and a home dashboard — and Ask Axis, the built-in assistant, then reshapes it around how your company sells and builds.

The work this replaces

A mid-size developer runs on systems that never meet. Inventory is an Excel sheet the sales head colour-codes by hand, and two executives occasionally promise the same 2 BHK on the same weekend. Portal leads land in another sheet or a salesperson's phone, and partners send buyers over WhatsApp — who brought whom is argued when commission is due.

After booking, the CRM team works out instalments in a spreadsheet, types demand letters in Word when a slab is cast and chases payments by phone. Accounts books receipts in Tally and separately tracks 26QB. Loans, stamp duty, registration and the snag list each live with a different person. "How much is overdue on Tower B" takes an afternoon of VLOOKUPs.

What the Real Estate template sets up

Six apps, sixteen record types, plus two extra fields on the built-in invoices and one on payments:

Demand letters are the built-in invoices, each carrying a Booking and a Milestone reference; receipts are the built-in payments, carrying a Booking reference. So a buyer's account is every invoice and payment on their booking, and a tower's overdue amount is one query.

The template also publishes two forms — Property enquiry and Book a site visit, each creating a lead — ships two PDF layouts, a Demand letter on invoices and an Allotment letter on bookings, and numbers new records itself: leads ENQ-, site visits VIS-, bookings BKG-, demands DMD-.

How a week runs in it

Leads come in. Enquiries become numbered Lead records — typed in from a portal's lead email or call, imported from a portal CSV, or created by the Property enquiry and Book a site visit forms on your website once the owner opens them to the public. Each lead names its source and, if a broker brought it, the Channel partner. The salesperson sets a next follow-up date, and the dashboard lists the ones that slipped.

Weekend site visits. A Site visit records the lead, project, date, pickup, who attended and the outcome. The lead moves on to negotiation.

A booking. The executive creates a Booking for a specific Unit, with the buyer, booking amount and payment plan, and generates the Allotment letter from it. The moment it saves, a flow marks the unit booked, so the inventory chart and the next executive both see it. The booking's Payment milestones lay out the plan — on booking, on agreement, plinth, slabs, top slab, finishing, possession — each with its percentage, amount, GST and due date. KYC documents are logged as they arrive.

A slab is cast. The site engineer marks the tower's Construction stage completed and architect certified. The CRM team raises the matching demand for each booking in that tower — an invoice linked to booking and milestone — generates the Demand letter PDF from it in Documents, and can add a payment link through Payments. When the demand is marked paid, a flow closes the instalment. The receipt is a payment record; the buyer's TDS (26QB) row tracks the acknowledgement and the Form 16B. Where a bank is funding, the Home loan record shows what has been sanctioned and disbursed against the demands.

Agreement and registration. A Registration row holds the sub-registrar office, stamp duty, registration fee and date. Signing the agreement marks the unit sold; registering it marks the unit registered.

Possession. A Handover records the offer and inspection; each defect the buyer finds is a Snag line, assigned to the site team until fixed and verified.

Automations included

Five flows ship switched on:

• Booking blocks the unit — a new booking marks its unit booked so nobody else sells it.
• Agreement marks the unit sold — when the agreement for sale is signed, the unit moves to sold.
• Registration marks the unit registered — when the agreement is registered, the unit moves to registered.
• Cancellation releases the unit — a cancelled booking puts its unit back in available inventory.
• Paid demand closes the instalment — when a demand letter is marked paid, its payment-plan instalment is marked paid.

Each is an ordinary flow you can edit or switch off in Automation.

Roles

• Sales head — the funnel, inventory pricing, partners and bookings; runs campaigns and enquiry forms.
• Sales executive — calls leads, schedules and runs site visits, books units.
• CRM & collections — everything after booking: KYC, demand letters, receipts, loans, registration and handover.
• Site engineer — updates construction progress and fixes snags before possession.
• Accounts — books receipts, reconciles the escrow account, TDS and channel-partner commissions.

Each role is editable app by app.

Your home dashboard

Sales & collections opens with four numbers — Collections, Bookings, Overdue demands, Overdue follow-ups — then Collections by day, Unit inventory by status, Leads by stage and Leads by source over 90 days, and three working tables: Site visits this week, Follow-ups to chase and Demands past due. Every widget is SQL over your own records, so you can edit one or add another in Analytics.

Platform apps that come switched on

• Calendar — site visits and inspections on a shared calendar, plus booking pages.
• Forms — the Property enquiry and Book a site visit forms, plus any you add.
• Messaging — email, SMS and WhatsApp through your own provider account; WhatsApp to buyers uses Meta-approved templates.
• Web Campaigns — Meta and Google Ads spend beside the leads it produced; creating ads stays in the ad platforms.
• Content Studio — project pages, amenities and FAQs for your website, published from the same workspace.
• Invoices & Payments — payment links through your own Razorpay account for booking amounts and demands.
• Accounting ledger, Sheets, PDF templates (the Demand letter and Allotment letter layouts) and Knowledge Base (brochures and price sheets your team can search).

Switched off: In-Store Checkout, Marketplaces, Work Queues and Functions — a developer has no retail counter, online store or barcode floor. Turn any of them on in Settings → Apps.

Make it yours

After signup Ask Axis asks what is different about your company, and you answer in plain words:

• "When a construction stage is completed, notify the CRM & collections team."
• "When a booking has a channel partner, create an accrued commission for it."
• "Add a dashboard widget for collections due in the next 30 days by tower."

Ask Axis changes the live workspace under your permissions and asks before anything destructive. See Ask Axis. The example data — three projects, 41 units, 36 leads, 16 bookings and the rest — never sets off the automations, and Settings → Industry template → Clear example data removes it, and only it, in one click. Started blank? The template can still be applied to an empty workspace from Settings.

What AxisIQ doesn't do

• No automatic property-portal lead sync. Leads from 99acres, MagicBricks and Housing.com are entered, imported by CSV or captured through your own forms.
• No RERA filing. The RERA number, phase, escrow account and possession dates are recorded; quarterly updates to the authority are filed by you.
• No home-loan bank integration. Sanction and disbursement are recorded by your team, not fetched from the lender.
• No e-stamping or registration filing. Stamp duty, fees and dates are records; the sub-registrar process happens outside.
• No GST return filing, e-invoicing or TDS filing. GST is on each instalment and the ledger balances; your CA files from there. No Tally sync or export, no payroll, no offline mode.

Sub-verticals

• Real estate developers — RERA projects, tower and unit inventory, construction-linked plans, demand letters, registration and possession.
• Brokers & channel partners — portal leads, site visits, follow-ups and commissions.

More industries at /industries.

FAQ

Is AxisIQ a real estate CRM? Yes, and more than the lead funnel: leads and site visits sit in the same workspace as unit inventory, bookings, payment plans, collections, registration and handover, so sales and CRM teams work from one record of each buyer.

Can AxisIQ manage construction-linked payment plans? Each booking carries its payment milestones with percentage, amount, GST and due date. Demands are invoices linked to booking and milestone, printed with the template's Demand letter layout, and a flow closes the instalment when one is paid.

How does AxisIQ stop double-selling a unit? A flow marks the unit booked the moment a booking is saved, and a cancelled booking returns it to available, so inventory status always follows the bookings.

Does AxisIQ pull leads from 99acres or MagicBricks automatically? No. Portal leads are imported by CSV or entered; website enquiries arrive through the Property enquiry and Book a site visit forms. Every lead keeps its source.

Can I track TDS under section 194-IA? Yes, as records: each TDS (26QB) row links the booking and receipt with the acknowledgement number, amount and whether Form 16B has been received. AxisIQ does not file it.

Start with the Real Estate template — or see AxisIQ in action.