Skip to content
Clix CRM

Roadmap

Tenancy contracts prepared in the CRM and registered without rekeying them.

Leasing work ends in a registered tenancy contract. Preparing it in one system and registering it in another is where the errors come from.

Planned

Tenancy contract preparation and Ejari registration support is planned for Clix. It is specified to cover tenancy contract generation from the listing, tenant and landlord records, the data Ejari registration requires, registration status tracking against the tenancy, and renewal reminders. Clix today generates documents from versioned templates and issues signature requests, which is the layer this builds on.

Available in Clix today

  • Document templates with versions
  • Documents generated with record data filled in
  • Signature requests through DocuSign or a manual path
  • Owner records against a listing
  • Agreements and Documents screen

Specified and in progress

  • Tenancy contract generation from the listing and tenant records
  • Landlord and tenant party records on the tenancy
  • The field set Ejari registration requires
  • Registration status tracked against the tenancy
  • Renewal reminders before expiry
  • Clear separation of what Clix prepares from what the authority issues

Why it is sequenced this way

Sequenced with property management, because a tenancy contract without a tenancy record to attach it to is a document rather than a workflow. The same rule as the compliance workspace applies: Clix will never present a document it generated as though an authority had issued it.

Roadmap items are not included in the current price and have no committed delivery date.

Roadmap

Need one of these now?

Tell us which module matters most to your business before you start a trial, and we will tell you honestly where it stands.

1 month free · No credit card required · $10/user/month