Question 1

Who is REX-OPS for?

Accepted Answer

REX-OPS is a property-sales platform for developers and real estate agencies. It connects units, buyers, partner sales and enquiry handling, with the setup shaped around each team’s operation.

Question 2

How is it different from a standalone CRM?

Accepted Answer

The main workflow connects property availability, buyers, partner information, presentations and sales follow-up. Configured automations and connected channels support that process; CRM is one of its working capabilities.

Question 3

Do we have to start with every module?

Accepted Answer

Start with the complete property-sales process your team needs. Deeper transaction, rental, campaign and knowledge capabilities can extend it. Required automation and connections are considered with the main workflow; the actual setup is agreed together.

Question 4

What does the published +250% result measure?

Accepted Answer

The number of properties sold grew by 250% over one year in the developer business where REX-OPS was created. It is not a revenue figure. The case describes that company’s use of REX-OPS together with configured automations, integrations and process changes.

Question 5

Is the developer case a promise for every customer?

Accepted Answer

The results describe one real operating business. Your process, stock, team, channels and configuration determine how REX-OPS is used. The demonstration helps you understand the relevant workflows and setup.

Question 6

Which languages does REX-OPS support?

Accepted Answer

REX-OPS works with any modern language across the system interface, property presentations and AI assistant. This includes languages written from right to left (RTL). Teams can work, prepare client materials and communicate with the assistant in the languages they need.

Question 7

Can existing data be brought across?

Accepted Answer

Migration planning begins with a sample of your projects, units, contacts and active deals. Source formats, cleanup work and the required history determine the approach.

Question 8

How long does implementation take?

Accepted Answer

Timing depends on the scope, information quality, integrations and team availability. Agree the milestones after those requirements have been reviewed.

Question 9

What should we prepare for a demo?

Accepted Answer

A description of your current process, the teams involved and the handovers you want to improve is enough to start. Do not send customer data or confidential documents through the initial enquiry form.

Question 10

How do we plan training and support?

Accepted Answer

Include the people who will use and own the configured workflow, and agree team guidance, ongoing responsibilities and support arrangements as part of the rollout.

Question 11

Where is platform data processed?

Accepted Answer

The technical evaluation should confirm the hosting setup, providers, data locations and processing arrangements relevant to your proposed scope.

Question 12

Can we connect our property portals and website?

Accepted Answer

Bring the actual channels and required data exchanges. Connector support, access and update behavior need to be confirmed for each system.

Question 13

Can we export our information?

Accepted Answer

Define the records, documents and formats you need during evaluation. Supported export workflows and transition arrangements should be confirmed in the agreed scope.

Question 14

Where can our team learn about the workflows?

Accepted Answer

The public documentation covers platform concepts, core workflows and implementation preparation. Use it alongside a review of your configured workspace.

Understand the product and the setup.

Product & fit

Implementation

Data & connected systems

Have a question about your sales process?