01
Lead Pipeline
Capture, routing, stages, follow-up and escalation.
01Real Estate
Leads do not
go cold. They go missing.
DevelopersBrokeragesChannel PartnersMulti-Project
Software for developers, brokerages and channel partners across India. Lead capture and routing, site visit tracking, unit inventory, bookings and broker payouts on one system — so an enquiry from a portal is still traceable six weeks later.
What we build
What the system handles, before any custom work.
- Routing
- Instant
- Portal lead to agent in seconds
- Visits
- Geo-logged
- Captured at the site, offline-safe
- Inventory
- Live
- One truth per unit, per project
- Payouts
- Tracked
- Broker commission to settlement
02The Gap
The enquiry you paid for, unanswered.
Portal leads are the most expensive thing a property business buys and the most casually handled. The loss is invisible because nobody counts the ones that were never called.
01
What it costs you
Portal leads sitting unread in a shared inbox
Instant capture and routing to a named agent
Enquiries from portals, ads and your own site land in one pipeline and route by project, location or round-robin within seconds — with escalation when nobody responds.
02
What it costs you
Site visits remembered, not recorded
Visits logged at the site, with location
Agents capture the visit on their phone with notes, interest level and next action, geo-tagged and offline-tolerant, so the record exists whether or not the site has signal.
03
What it costs you
Two agents selling the same unit
One live inventory across every project
Unit status — available, held, booked, registered — updates once and is visible to everyone, so a hold placed in the morning is not sold again in the afternoon.
04
What it costs you
Broker commissions argued over in spreadsheets
Payouts computed from the booking record
Slab and milestone-based commission calculated from the actual booking and collection, with a statement each channel partner can see rather than dispute.
05
What it costs you
No idea which campaign produced a sale
Source attribution through to booking
Every lead carries its source and campaign to the point of booking, so spend is judged on registrations rather than on enquiry volume.
03Modules
Start with what leaks. Add the rest later.
You are not obliged to take all eight. Most firms begin with the pipeline and site visits, then add inventory and payouts once the funnel can be trusted.
02
Site Visits
Scheduling, geo-tagged capture and outcome logging.
03
Inventory
Unit status, holds, pricing and availability per project.
04
Bookings
Applications, agreements, milestones and collections.
05
Channel Partners
Broker onboarding, attribution and commission slabs.
06
Payouts
Commission computation, approval and settlement tracking.
07
Documents
KYC, agreements and approvals held against the deal.
08
Reports
Funnel, source attribution, inventory ageing and collections.
Most firms start with the lead pipeline and site visits, because that is where enquiries are lost. Inventory and payouts follow once the funnel is trustworthy.
04Where To Start
Configure, build, or build plus app.
A small brokerage rarely needs a custom system, and we will tell you that. The calculation changes the moment inventory and channel partners enter the picture.
01Off the shelf
Configure a CRM
Choose when volume is modest
For a small brokerage running one or two projects, configuring an existing CRM is usually the honest answer, and we will set it up rather than sell you a build.
- Live in
- Two to three weeks
- Cost
- Lowest
- Best for
- Small teams, few projects
02Your process
Custom build
Choose when inventory and payouts matter
Once unit inventory, channel partners and commission structures are involved, generic CRMs stop fitting. A build to your process pays back through what it stops leaking.
- Live in
- About thirteen weeks
- Cost
- Scoped, owned outright
- Best for
- Developers, multi-project firms
03Extended
Custom plus field app
Choose when the team lives on site
The same system with a dedicated mobile app for agents at site — offline visit capture, unit availability in hand, and documents collected on the spot.
- Live in
- Thirteen weeks, then the app
- Cost
- Build plus app scope
- Best for
- Large site teams
05How We Work
Fifteen things that are true every time.
Whichever route you take, these hold. They are the terms of working with us rather than features of a package.
01
How We Scope
- We map your current process before proposing anything
- A written specification before a number is given
- Fixed price against that scope, not hourly drift
- Modules sequenced by what costs you most today
- Told plainly when a product you can buy beats a build
02
What Gets Built
- Role-based access enforced server-side
- An audit trail on every record change
- Mobile-ready screens for staff away from a desk
- Offline-tolerant capture where coverage is unreliable
- Reports generated from live data, not exports
03
What You Keep
- Source code and documentation in your name
- Infrastructure and accounts you control
- Full data export, in standard formats, any time
- No per-seat fee that grows as you hire
- A handover walkthrough so another team could continue
06Process
Five stages, process first.
We map how your sales floor actually operates before designing anything, and migrate records only once they reconcile against your own totals.
- 01Weeks 1-2
Process Mapping
We sit with the people doing the work and map what actually happens, not what the manual says. This is where most projects in this sector quietly fail, so it happens first and in person where possible.
Deliverables
- Current-state process map
- Data quality audit
- Scope and priority
- 02Weeks 3-4
Design & Data Model
The shared record behind every screen is agreed before build, and interfaces are designed for people entering fifty records a day rather than for a demo.
Deliverables
- Entity and role model
- Screen designs
- Approval workflows
- 03Weeks 5-10
Build & Integration
Work ships in two-week sprints against the agreed model, with the integrations you depend on wired in as each module lands and a staging environment your team can test throughout.
Deliverables
- Production modules
- Integrations
- Staging for user testing
- 04Weeks 11-12
Migration & Training
Existing records are cleaned, imported and reconciled against your own totals. Staff train on their real data, and the old process runs in parallel until both sides agree.
Deliverables
- Reconciled migration
- Role-specific training
- Parallel-run comparison
- 05Week 13 onward
Go-Live & Iterate
Cutover happens with support through the first full cycle, then settles into scheduled reviews driven by what the data shows rather than by a fixed roadmap.
Deliverables
- Production cutover
- First-cycle support
- Review cadence
07Questions
Answered properly.
What developers and brokerages ask before changing the system their revenue runs on.
It depends on whether you need a configured off-the-shelf CRM or a build covering inventory, channel partners and payouts. For a small brokerage the honest answer is often the former, and we will say so. A custom build is quoted against a written specification after process mapping, at a fixed price rather than per user per month.
Yes, where the portal exposes a lead feed or API, and by email parsing where it does not. Leads from portals, paid campaigns and your own website land in the same pipeline with their source attached, so attribution survives all the way to booking.
That is the main design constraint. Visit capture is mobile-first and offline-tolerant, queuing notes, interest level and next action until signal returns. Agents can check live unit availability from their phone rather than calling the office to ask.
Commission structures — flat, slab-based or milestone-linked — are configured per partner, and payouts compute from the actual booking and collection record rather than from a separate spreadsheet. Each partner gets a statement showing how the figure was reached, which removes most disputes before they start.
Yes. Inventory is structured by project, tower, floor and unit, with pricing, holds and status per unit. Teams can be scoped to the projects they sell, and reporting rolls up across the portfolio or drills into one tower.
Yes, where an API or a scheduled exchange exists. Bookings, collections and payouts are the usual integration points, and we confirm what is possible with your specific system during scoping rather than promising blind.
About thirteen weeks for a custom system: two weeks of process mapping, two of design and data modelling, six of build, two of migration and training, then go-live with support through the first full sales cycle. A configured CRM is live in two to three weeks.
You do. Source code, database and infrastructure accounts are in your name from the start, and you can export every lead, booking and document at any time in standard formats. There is no per-seat fee that grows as you add agents.
08Adjacent Work
The CRM is one part of the funnel.
What generates the enquiry and what the agent carries to site, either side of it.
09Next Step
Tell us where leads are going missing.
Describe how an enquiry travels through your team today and where it stalls. You will get a read on what is causing it and a scoped plan — before any commitment.
- hello@asematic.com
- Phone
- +91 82600 61212
- Studio
- Bhubaneswar, Odisha, India.
- Response time
- Within one business day