Eigna is a property management platform for small landlords managing roughly one to ten units. It brings properties, tenants, leases, inspections, deposits, rent, maintenance, expenses and tax into one connected product. Designed for India and the US, it adapts to local currencies, terminology, payment methods and compliance requirements without asking landlords to manage each responsibility through a separate tool.
03 / THE PROBLEM
A small portfolio can still create a lot of work.
A landlord with three properties may track rent in one place, store leases somewhere else, handle maintenance through messages and keep inspection photos on their phone. At tax time, they have to reconstruct the financial story. These are ordinary tasks, but each affects the next while the information needed to connect them lives in different places.
04 / Defining the product
Design around the landlord lifecycle.
I started with the relationships between responsibilities. A move out inspection can lead to a deposit deduction. A maintenance request becomes an expense. Lease information affects compliance, while rent and expenses feed reporting and tax. Following those connections made the property record the natural foundation for the product.
01One property record
A property keeps its tenancy, documents, condition and financial history together. Information collected in one workflow should remain useful in the next.
02Local rules, shared product
Location changes payment methods, lease terminology, deposit rules, tax documents, electronic signatures and address formats. Geography belongs in the configuration of a shared product.
03Show what matters now
A landlord managing two or three properties needs current state, upcoming obligations and actions requiring attention. Detailed records can wait until there is a reason to open them.
05 / Designing the system
The property became the connecting layer.
Portfolio, tenancy, inspections, deposits, maintenance, financials and tax share the same property context. The map groups related responsibilities so their connections stay readable: inspections support deposit decisions, while rent and maintenance expenses feed the financial record. India and US requirements adapt the details of this common structure.
PropertyCONNECTED PRODUCT
Portfolio
Tenants + leases
Inspections + deposits
Maintenance
Rent + financials
Tax
Connected landlord lifecycle / India + US
06 / Key product challenges
The decisions that shaped the product.
Breadth without a crowded starting point.
01The thinking
Showing every operational area at the same level would make a small portfolio feel like enterprise software. Hiding them in separate tools would lose the connections the product was built around.
02The decision
Use the portfolio for current state and upcoming work, then open the property record for tenancy, condition and financial detail. Market specific requirements belong within the relevant workflow.
03The result
The information hierarchy separates everyday attention from detailed record keeping, while both views refer to the same property.
07 / The solution
The whole property, at the right level of detail.
JOURNEY 01
From today’s obligation to the right record.
The everyday journey starts with work requiring attention, then moves into the relevant property or tenancy. Current state and upcoming actions belong at portfolio level; lease detail, condition records and financial history belong in the context of the property. Completing one task should leave its information useful for the next.
01Find pending work
02Open property context
03Complete the task
04Return to the portfolio
Daily work / current state and contextual detail
JOURNEY 02
From property condition to a financial decision.
An inspection does not end with a set of photos. Its findings can inform a repair, an expense or a deposit decision. The workflow keeps the condition record, tenancy and financial consequence together, while leaving the landlord responsible for the decision.
01Record the condition
02Review the findings
03Decide the deduction
04Update the deposit
Inspection to deposit journey
01Keep the evidence attached
Condition information and supporting documents remain part of the property history, so a financial decision can be understood in its tenancy context.
02Separate a finding from a charge
Recording damage and deciding how to account for it are different tasks. The connection supports judgement without treating every inspection finding as a deduction.
JOURNEY 03
Ask the portfolio.
The assistant uses the context already connected throughout Eigna. A landlord can ask when a lease expires, how much was spent on repairs, which payments were late or which property needed the most maintenance. The question starts with an everyday concern, rather than a search across several unrelated records.
01Dates and obligations
Lease dates and upcoming tenancy events help the landlord identify what needs attention next.
02Spending and payment history
Repair expenses and rent records answer financial questions in the context of the relevant property, rather than as isolated totals.
08 / Outcome & impact
A property record that carries the work forward.
My design contribution was the product architecture connecting the landlord lifecycle: a shared property record, a hierarchy for everyday work and deeper detail, and a common structure for India and US workflows. The inspection to deposit journey shows why those connections matter. Information captured for one task stays useful when the landlord makes the next decision.
01One product, different rules
Market configuration handles local differences without separating the portfolio, tenancy and financial experience into different products.
02What I learned
Designing the connections between workflows can matter more than designing each workflow individually. A clearer inspection screen only solves part of the problem if its findings still have to be copied into a deposit decision or reconstructed as an expense later.
09 / Success criteria
Success criteria: measure the work across the lifecycle.
Evaluate whether connected property records make daily obligations easier to complete and reduce repeated work between operations.
Task completion
≥95%
Portfolio, tenancy and property tasks completed successfully, including the inspection to deposit journey.
Repeated entry
≤1
Entry of each property detail across connected workflows. Shared records should remove repeated input.
Missed obligations
0
Overdue rent, lease or maintenance actions that go unnoticed in the portfolio view.