All projects

Walkthrough

Walk through LeaseLoop

Real screens from LeaseLoop's demo build, with Lyra and the accounting feature switched on. Pick a role or step through it.

ManagerLyraOwnerProvider

LeaseLoop

1. 01One list of what needs a personToday pulls maintenance, rent and leases into a single queue. Lyra adds a short note to each row, like how many quotes are in or that a report mentions gas.
2. 02Quotes compared on what's verifiedFor a leaking toilet, two plumbers quoted $380 and $560. Lyra lays out the budget, availability and which licences and insurance were actually checked, and flags the one over budget.
3. 03Possible emergencies go to a personLeaseLoop doesn't decide whether a gas smell is an emergency. Lyra marks it urgent and says plainly that a person should review it now.
4. 04Evidence, recommendation, decisionEvery suggestion shows what it read, what it recommends and the choices left to you. Decisions are logged with a name and a time.
5. 05Lyra's queue, and an off switchEverything Lyra prepared, grouped by urgency, with an activity log of what it actually did and a Pause button.
6. 06Applications against the unit's criteriaApplicants are compared only with the criteria set for the unit. A low income is flagged for review, not treated as a rejection, and LeaseLoop never approves or declines anyone.
7. 07A bill arrives as a draftA provider's $189 invoice lands as a draft. LeaseLoop asks who paid and points out the field it read with low confidence before anything touches the books.
8. 08Posted entries split between ownersPosting records who paid and each owner's share in one step. Entries are never edited; mistakes are corrected or reversed in full.
9. 09Who owes whomSettlements net out what each owner paid against their agreed share, here $168 from one co-owner to the other.
10. 10The provider's sideThe plumber sees quote requests, visits agreed with renters and jobs in progress. A quote isn't a booking; the job still has to be accepted.

Previous1 of 10Next

Every person, property and company here is fictional demo data. Lyra ran on its deterministic rules for these screens, with no AI calls.

1. 01 Problem

   Renting out a property runs on scattered texts, spreadsheets and email threads. Owners can't see what's happening, renters can't tell whether a repair is moving, and nobody has a reliable record of who agreed to what.

2. 02 Approach

   Put properties, leases, rent records, maintenance, documents and messages in one place, and let each person see only what their relationship to the property allows. Pair it with an operations agent that handles the follow-up work but leaves every decision to a person.

3. 03 Implementation

   Node.js and Express 5 on PostgreSQL, with Better Auth sessions and strict zod validation on every input. Authorization is relationship-based and enforced on the server for every request: managers are assigned per property, renters reach only their active lease, and providers reach only the work assigned to them. Every change is written to an append-only audit log in the same transaction. The agent runs on deterministic rules, with a language model optional. Integration tests run against an embedded Postgres, with Playwright for the browser.

4. 04 Outcome

   The public site is live at leaseloop.ca, and the product is being hardened for a wider beta.