Current project

Sojago

Software that helps rental agencies keep track of rent, unpaid balances, receipts, expenses, and the money owed to property owners.

Role · Founder and product engineer

Visit project
  1. Rent expected
  2. Payment
  3. Allocation
  4. Receipt
  5. Owner report
Sojago operating flow

Sojago started with a familiar problem: an agency may have all the information it needs, but that information is scattered across notebooks, spreadsheets, messages, and people’s memories.

Answering a simple question about rent can mean piecing the whole story together again.

What the product needs to do

Sojago connects properties, tenants, leases, rent, payments, expenses, commissions, and owner accounts.

The important part is not putting those records on one screen. It is keeping them consistent enough that an agency can explain every number. A payment should update the right balance. A correction should not erase the past. The receipt, tenant account, and owner statement should agree.

The agency should always be able to answer three questions: what was due, what was paid, and what happens next?

The decisions I care about

Money makes small product decisions important.

A partial payment needs a clear destination. An advance should not look like ordinary rent. If somebody fixes an error, the original entry should remain visible. On mobile, the action and its result should never be ambiguous.

I also want the language to match the way agency teams already talk about their work. A technically correct label is not useful if it makes a familiar task feel foreign.

The first month matters

Agency records are rarely ready for import. Someone has to clean them, check opening balances, explain the new workflow, and stay close during the first monthly cycle.

I am treating that work as part of the product, not as a temporary inconvenience. It affects the interface, the import tools, the support process, and the price an agency can reasonably pay.

Where it stands

The current work covers rent and arrears, payment allocation, receipts, owner reporting, and a simpler onboarding flow for nontechnical teams.

What remains unproven is just as important. I still need to see agencies use the workflow every month, trust it enough to leave their parallel records behind, and pay enough to support the help they need.

That is the next stage of Sojago: less work in isolation, more real agency data, completed month-ends, and direct evidence that the product earns its place.