Contracts Hub – Standardizing Rental Agreements
Contracts are a core part of any rental process—but in Kuwait, landlords and property managers lacked a consistent, digital way to manage them. We built the Contracts Hub in Ajar to give users a unified, customizable, and reusable way to create and store bilingual rental agreements—all within the platform.
The Problem
We were hearing two types of complaints from our users:
New landlords didn’t know how to write a proper contract.
Kuwait doesn’t have a standard government-issued rental agreement. Landlords just starting out were unsure of what terms to include or how to structure the agreement.Experienced property managers were wasting time with manual contracts.
Most had their own Word templates saved somewhere. Every time a new tenant signed, they had to:Find the template
Manually edit tenant details
Save or print it separately
This process was inefficient, error-prone, and disconnected from the rest of the platform.
Language expectations were not being met.
Since rental agreements in Kuwait are often reviewed by Arabic-speaking landlords and English-speaking tenants (or vice versa), having contracts in only one language created unnecessary back-and-forth.
My Role
As Product Manager and Design Lead, I worked on:
Understanding the workflow of both new and experienced landlords
Collaborating with legal experts to define a default rental contract template
Designing a flexible feature that supports both standard and custom contracts
Introducing side-by-side Arabic/English support to reflect local expectations
Coordinating with engineering to build a scalable contract engine within Ajar
Research & Insights
We gathered feedback from support tickets, client interviews, and sales calls. What we found:
New users wanted a ready-to-go contract they could trust
Property management companies had internal templates they reused but needed help digitizing
Everyone wanted to store, access, and re-use contracts from within Ajar—without external tools
Contracts needed to be generated in both Arabic and English side-by-side to ensure clarity and legal protection for both parties
Takeaway: We weren’t just building a document tool. We were solving for trust, efficiency, clarity, and multilingual access in a very sensitive part of the rental process.
User Flow
The feature evolved in phases, starting with the most common needs:
Unified Contract Template:
Users choose to generate a “Standard Rental Contract”
Auto-filled with common clauses vetted by lawyers
Output: Bilingual PDF (Arabic and English shown side-by-side)
Custom Template Upload:
Clients send their own Word template to our team
We build it into their Ajar account as a reusable form
Supports bilingual layout formatting per client preference
Build-Your-Own Contract (Advanced):
A WYSIWYG editor for advanced users
Build and save templates from scratch
Drag and drop fields like unit, tenant name, rent amount
Option to add side-by-side translations as you go
Storage & Reuse:
All contracts saved in the system under each unit
Easy to view, print, or resend at any time
Users can always download a bilingual contract version
Core Features
Prebuilt Kuwaiti Rental Contract: Aligned with legal norms for new landlords
Reusable Templates: Store and reuse company-specific contracts inside Ajar
Auto-Filled Fields: Save time by inserting tenant and unit data dynamically
WYSIWYG Editor: Build templates from scratch without needing Word or PDFs
Bilingual Contract Support: Arabic/English contracts generated side-by-side in a legally clear, professional format
Centralized Access: All contracts linked to tenant and unit profiles in the system
What I Learned
Legal content needs clear ownership. Working with lawyers early helped us build trust with users and avoid back-and-forth.
Start small, then scale. Launching with just the standard contract validated the need before we built out complex templates.
Language matters. The bilingual support became one of the most appreciated aspects of the feature—helping bridge gaps between landlords, tenants, and legal authorities.
Users want flexibility, not complexity. Giving both plug-and-play and power-user tools made the feature usable across experience levels.
Outcome
The Contracts Hub became one of our most adopted features, especially among new users
It reduced time spent on contract creation for property managers significantly
Clients could finally centralize their contract process inside Ajar—no more Word docs floating around
Bilingual contracts increased clarity and trust between landlords and tenants, especially in a multilingual market like Kuwait
It positioned Ajar not just as a payment tool, but as a more complete, legally-aligned property management solution
