LeasePro turns the leasing lifecycle — property, listing, application, lease, signature, rent, renewal — into one workflow, on a multi-tenant Postgres schema with row-level isolation and separate landlord, tenant and owner surfaces. This page states plainly what is built, what needs configuration, and what is not built.
Every figure below was measured directly from the repository. None is an estimate.
lp_ schema, across 30 migrations
application, billing, signing, screening, messaging
plus 30 client components
LeasePro-specific TypeScript/TSX
landlord, tenant, owner, admin
across residential, commercial and specialty
A buyer’s first job is separating shipped software from a roadmap. We have done that separation here rather than leaving it for diligence to uncover.
Working in the live application today.
Properties, units and leases
Portfolio structure with per-unit rent, occupancy and lease records; renewals and lease-end tracking.
Applications pipeline
Applicant intake from a public listing link, a review board with approve/decline, and lease creation on approval.
Lease drafting and e-signature
Document generation with an interview flow, then in-product signing that records signer name, timestamp, IP address and user agent.
Rent and expense tracking
Payment records against leases, outstanding balances, IRS Schedule E expense categories, and CSV exports for the rent roll and operating statement.
Maintenance and inspections
Tenant-submitted requests with photo upload to object storage, priority and status workflow, and move-in/move-out inspections.
Tenant and owner portals
Separate authenticated surfaces for renters and for property owners, alongside the landlord console and an admin view.
Multi-tenant data isolation
Row-level security policies scope every record to its account; team members carry roles with capability limits and owner-only deletes.
Jurisdiction-aware drafting
18 curated jurisdiction rule sets (deposit caps, notice periods, rent control, required disclosures) injected into lease generation.
Code exists; a key or partner turns it on.
Rent collection and subscriptions (Stripe)
Stripe Connect with direct charges is implemented — the landlord is the merchant of record and rent settles to their own bank, with no platform fee on rent. Subscription checkout, billing portal and webhooks are written. Activates when Stripe keys are set.
Tenant screening
A provider-agnostic bureau integration (order, webhook, adverse-action support) written against a generic REST contract. No consumer-reporting agency is currently connected; until credentials are set the product records the request and never fabricates a score.
AI assistance
Lease drafting, listing copy and applicant summarisation are implemented against a shared provider abstraction. In production today no model key is set, so these endpoints return deterministic fallback text and report provider: "demo". Adding a key switches them to live generation.
Mobile subscriptions (StoreKit)
RevenueCat/StoreKit purchase, restore and entitlement webhook are implemented for the iOS app, priced from StoreKit rather than hardcoded values.
Stated up front so it can be priced.
Automated test suite
The repository contains a single test file. There is no meaningful automated coverage — this is the most significant engineering gap and should be priced in.
Android application
No Android project exists. The web app is installable as a PWA; a Play build would need to be created.
iOS App Store release
An iOS shell (Capacitor, bundle net.leasepro.app) is built and submitted, but the app is not released — it is working through App Review. It is server-driven, so the shipped UI follows the web app.
Formal compliance certification
No SOC 2, FCRA or fair-housing certification has been obtained. Screening is regulated activity and would require a compliant bureau relationship before launch.
Public API and white-label
No external API surface or tenant-branded deployment exists today. Both are plausible extensions of the current architecture, not shipped features.
Commercial metrics — revenue to date, active subscriptions, and units under management — are provided directly in diligence rather than advertised here. LeasePro makes no claim of scale, customer count or transaction volume on this page.
Each stage below exists in the product. Payment collection is written but requires Stripe credentials.
Property & units
Portfolio structure with rent and occupancy.
Listing & applications
Public apply link; applicants land in a review board.
Screening
Request recorded; bureau connection required to pull a report.
Lease & e-signature
Draft, send, and sign with a recorded audit trail.
Tenant onboarding
Renter portal for lease, documents and requests.
Rent tracking
Payments against leases, balances and receipts.
Maintenance
Photo-backed requests through to completion.
Renewal & reporting
Lease-end tracking, rent roll and operating statement exports.
Client
Landlord console, tenant portal, owner portal, admin — plus an iOS shell that loads the same application.
Application layer
Next.js App Router with server components; host-based routing serves LeasePro from a shared codebase.
Domain services
Lease drafting and jurisdiction rules, signing, screening contract, reminders, reporting and exports.
Data
Postgres on Supabase — 16 tables, row-level security scoping every record to its account.
Integrations
Stripe Connect and subscriptions, StoreKit via RevenueCat, object storage for documents and photos, a provider-agnostic screening contract, and a pluggable model provider.
Properties, units, leases, applications, payments, expenses, maintenance, inspections and their items, documents, messages, unit photos, lease templates, team members, billing and push tokens.
Row-level security policies scope records to the owning account, with team roles limiting write access and deletes reserved to the account owner. No penetration test has been performed.
A server-driven iOS shell means product changes ship to the app without an App Store release. The app itself is not yet released; there is no Android build.
The leasing lifecycle — property through application, lease, signature, payment and renewal — is already modelled in a working schema and UI.
Authentication, multi-tenant isolation, role-based team access, document generation, signing, storage and exports exist rather than needing specification and build.
Subscription tiers, entitlement enforcement, billing portal and mobile purchase flow are written; activation is configuration, not development.
Next.js App Router, TypeScript and Postgres on Supabase — a stack most product teams can take ownership of without retraining.
No development-cost estimate is offered here; a buyer’s own engineering team is better placed to price the equivalent build.
Categories where LeasePro would plug into an existing portfolio or customer base. No conversation with any named company is implied.
Own the leasing stack instead of licensing it per door, and deploy it across an existing portfolio.
Add leasing workflow and e-signature to an adjacent product without building the lifecycle from scratch.
Offer leasing infrastructure to agents handling rentals alongside sales.
Digitise internal leasing operations on software you control.
Run rental operations across a portfolio on a single system.
Acquire a built vertical product and apply an existing distribution motion to it.
Scope is subject to a definitive agreement and diligence. Third-party accounts transfer only where the provider permits it.
Shared with qualified parties under NDA. Credentials, keys and any customer data are never included in pre-agreement materials.
Tell us who you are and what you would do with it. We will follow up to arrange a walkthrough.
Looking for the product instead? See what LeasePro does.