A real estate operating system built around the property

Start with the work you do

These public guides introduce each audience. A guide is a starting point for evaluation; account access and a discussion of your requirements establish which workflows fit your situation.

Walk through a real handoff before deciding

Use one property and one task to evaluate ARX. Ask for a demonstration that starts with the information a participant supplies and ends with the next person knowing what to do.

1. Establish the starting point. Identify the property, the record source and the people responsible.
2. Review the information. Confirm what each role can see or change, and which facts still require verification.
3. Handle a missing document. Ask how the gap is recorded, who requests the document and what must wait. Include manual follow-up.
4. Confirm the next step. Show the receiving role's view and distinguish an update in ARX from an action completed by an outside professional.

This is an evaluation sequence. It does not establish that every stage is automated or available for every account.

Connect the conversation around a property

The property-centered model starts with the property, then asks which people, records and decisions belong in the workflow. A record's source and a participant's permissions matter as much as the record itself.

Property

Which property is being discussed, and which source establishes each fact?

People and access

Who is involved, and what information is appropriate for each role?

Records and decisions

What has been supplied, what needs review, and who is responsible for the next action?

Connecting a record to a workflow does not make ARX the authority for its legal status, ownership, valuation or financing. Verify those facts with the appropriate source or professional.

Evaluate what you can actually see

You can read the public role guides and workflow overview without creating an account. For a product decision, request a demonstration of the specific workflow and ask to see the relevant roles, permissions and exception steps.

A category explanation describes the approach. A demonstration establishes what is supported in a particular release and account; neither by itself proves a customer outcome.

Check capability and availability for your use case

Use these questions alongside the public guides. Confirm availability, coverage and account conditions with Stone ARX before relying on a workflow. These entries are evaluation topics, rather than a promise that every capability is included.

Keep integrations and professional authority explicit

For each connection you need, ask whether it is a native integration, a file transfer, or a task someone performs outside ARX. Confirm supported formats, permission requirements and any limits before planning around it.

Legal advice, title conclusions, lending decisions and licensed brokerage responsibilities remain with the appropriate professionals. Do not assume access to an MLS, government record system or another vendor solely because a property or document appears in a workflow.

Discuss setup, support and cost with your requirements in view

Bring your current process, the roles involved and an example of the information you need to move. Ask which setup steps are supported, who performs them, what can be imported or exported, and which support and commercial terms apply.

Use the contact page for a product or workflow inquiry. Existing users can use the support center for help with an account.

Match the workflow to the problem

Explore the approach and the people behind it

Read why Stone ARX takes this approach, meet the company on the about page, or return to the role guides with your workflow questions. Keep the category model, demonstrated product behavior and measured results separate when comparing options.