Designing Viewing-to-Offer Pipelines in a Custom Real Estate CRM

👉 Book a free 30-minute Bitrix24 demo

A buyer asks for a viewing. Someone drops the time into a WhatsApp group. The offer lands in an email thread. The manager asks “where is this deal?” and three people paste different screenshots. That is not a sales problem. It is a pipeline design problem.

This walkthrough shows how to design viewing-to-offer pipelines in a custom real estate CRM — stages your agents will actually use, fields that matter in the UAE, and hand-offs that do not depend on memory. No invented agencies, no fake conversion rates. Just a practical blueprint Closerholic uses when we tailor Bitrix24 or a custom CRM for brokerages.

Why viewing and offer need their own stages

Many brokerages collapse everything after “Qualified” into a vague “In progress.” That hides the moments where deals stall: confirmation of the viewing, no-shows, post-viewing feedback, offer drafting, and negotiation. If those moments are not stages (or clear sub-statuses), managers cannot coach and automation cannot help.

A custom CRM for real estate should make the sales motion visible. Bitrix24 supports separate deal pipelines with their own kanban stages. A tailored setup can go further with property-linked processes and fields your team already uses on the ground. For context on when a tailored approach pays off, see our earlier post on custom CRM for real estate.

A clean viewing-to-offer pipeline (secondary sales example)

Use this as a starting point, then rename stages to match how your desk talks:

1. Viewing requested — buyer or tenant asked for a slot; unit and preferred windows captured
2. Viewing booked — time confirmed with client and listing side; location and access notes ready
3. Viewing done — feedback logged the same day
4. Offer drafting — commercial terms being prepared
5. Offer sent — document or written offer with the client
6. Under negotiation — counter-offers and conditions
7. Accepted / EOI — next legal or booking steps begin

Leasing and off-plan deserve their own pipelines. Application packs and developer reservation steps are not the same as secondary sales offers. Separate pipelines keep reports honest.

Fields that belong on viewing stages

• Preferred date/time windows and language
• Community and unit reference (link to the property record if you use one)
• Who holds keys / access instructions
• Accompanying parties (buyer alone, with spouse, with POA)
• No-show reason if the viewing fails

Fields that belong on offer stages

• Offer amount and currency
• Payment structure notes (without stuffing legal advice into CRM fields)
• Validity date of the offer
• Conditions (furniture, handover date, snagging)
• Decision-maker vs influencer on the client side

Resist inventing twenty “nice to have” fields on day one. Start with what managers ask for in standup. You can expand after people use the board for two weeks. That lesson also appears in our myth-buster on custom real estate CRM myths.

Stage exit criteria (so kanban does not become theatre)

Every stage needs a simple “done when” rule. Examples:

Without exit criteria, agents park deals where they look busy. With them, stuck cards become coaching opportunities.

Want a viewing-to-offer board designed around your desks? Book a free 30-minute Bitrix24 demo and we will map stages with your sales manager — no generic template dump.

Tasks and reminders at the dangerous moments

Pipelines alone do not chase people. Pair stages with tasks: confirm the viewing the day before, collect feedback within a few hours of the visit, and chase an unanswered offer before it goes stale. In Bitrix24, tasks can be created from the CRM item form and linked to the deal so the history stays on the record. Automation rules can create those tasks when a deal enters a stage — covered in our guide to Bitrix24 automation rules for real estate follow-up.

If chat is still the only “system of record,” fix channel capture first. Open Channels and WhatsApp connectivity matter before fancy stages; see WhatsApp and Open Channels in Bitrix24.

Property context without cluttering the deal

Agents need the unit in front of them while they move a deal. A custom CRM often uses a property process (for example Bitrix24 Smart Process Automation for a property database) linked to deals. Keep listing facts on the property; keep buyer behaviour on the deal. That split stops every deal card from becoming a messy copy of the brochure.

Reporting managers will actually open

Once stages are real, simple questions become answerable:

• How many viewings booked this week vs completed?
• How long do deals sit in “Offer sent”?
• Which communities convert viewings to offers more often?

You do not need vanity dashboards on week one. Start with stage counts and age-in-stage. Add lead scoring later if assignment volume justifies it — see lead scoring and assignment in a custom real estate CRM.

Rollout sequence that respects busy agents

1. Agree stage names with sales leads in one workshop
2. Migrate one pipeline (usually secondary sales) before leasing and off-plan
3. Train with live deals, not screenshots only
4. Turn on task creation for viewing booked and offer sent
5. Review age-in-stage with managers after two weeks and prune unused fields

Closerholic builds custom real estate CRM setups and Bitrix24 implementations around UAE brokerage workflows — portals, WhatsApp, viewings and offers — so the board matches the street, not a generic SaaS demo.

Common mistakes to avoid

• Copying a software vendor’s sample stages without renaming them to local language
• One mega-pipeline for sales, leasing and off-plan
• No feedback field after viewings
• Offers tracked only in email with CRM stages left behind
• Changing stage names every week so historical reports become useless

Design the viewing-to-offer path once, protect the names, and improve fields slowly. That is how a custom CRM becomes daily habit instead of another abandoned login.

👉 Book a free 30-minute Bitrix24 demo