Rent collection and repair requests, built by Claude Code on Elements
Tenants pay rent by card or autopay and report repairs with photos. The landlord sees a live rent roll and a repair queue.
How it's built
Leaseleaf needed a live rent roll, rent by card and autopay, a maintenance queue with photos and comments, tenant invites, and scheduled reminder emails. Each of those is a part of Elements, so the agent spent its 27 minutes on the property app itself.
- Live rent and maintenance. Rent charges, maintenance requests and their comments are LiveTables, so a payment shows as paid on the landlord's rent roll the moment it lands, and a tenant sees a request move to scheduled or done as the landlord changes it.
- Rent by card and autopay. A tenant pays a month's rent through Stripe or saves a card for autopay, each with one
@rpccall. Payments are recorded once whether the return page or Stripe's webhook arrives first. Until a Stripe key is set, the pay button opens a test checkout inside the app that records rent the same way, and in production the app registers its own webhook the first time a tenant pays. - One daily job. A one-line cron schedule runs the rent cycle every morning at 9: it creates the month's charges, charges autopay cards on the due date, and emails a reminder three days before and a late notice the day after, each once.
- Maintenance updates by email. Only the landlord changes a request's status, and each change emails the tenant. Tenants attach photos when they file a request.
- Invites and sessions. The landlord invites a tenant by email, and accepting the invite sets a password, starts the lease and creates the first charge in one step. Landlord and tenant pages each check the signed-in role.
- Data from SQL files. Migrations define the app and seed a landlord, two buildings with eight units, seven tenants, three months of rent with two tenants behind, and a maintenance queue with photos.
Why Elements
Elements is an integrated full-stack app framework and a project server. The project server checks the agent's work as it builds: it type-checks the server and browser code, analyzes the program, applies migrations and runs the tests, then reports the results to the agent. A security mistake, such as calling a server-only function from the browser, is a compile error. The agent reads the report and fixes its own mistakes before it tells you a feature is done. The same checks run on every feature you ask for next.
Run it yourself
- 1 Sign up
Already have an account? Sign in
- 2 Install and run the demo One prompt to paste into your agent.
The prompt
What Claude was given to build this app.
Build a property management app named leaseleaf for a landlord with a few small buildings. Accounts: landlord and tenant. The landlord invites tenants by email. TENANT - See their lease: unit, monthly rent, due day. - Pay rent by card, or set up autopay. - Submit a maintenance request with a description, urgency and photos, and follow its status and comments. LANDLORD - Buildings and units, and who lives where. - Rent roll for the month: paid, due, late. - Maintenance queue: new, scheduled, done, with comments to the tenant. - A reminder email goes to tenants three days before rent is due, and a late notice the day after. Payments by Stripe. Seed the landlord, two buildings with eight units, seven tenants, three months of rent payments, and maintenance requests with photos. Show the seeded logins on the sign-in page. Payments and maintenance status update in real time.