BuiltDesigned

Vaasova

Rental property management software for Indian landlords with 5 to 50 units, replacing chat groups, agents and spreadsheets.

Smart Rentals. Real Trust.

Launch site built and live. Full product plan designed. Product apps in development.

27
part product and technical specification: 64
features with user stories, across MVP and two later phases: 6
apps and 5 shared packages in one repository: 4
personas: owner, tenant, service partner, admin: 1
launch site, live at vaasova.com

How it fits together

Owner, tenant and partner apps
Three web apps, three mobile apps
One typed API
Shared by every app
Postgres with row-level security
Second security layer on every table
Payments, eSign and identity checks
Regulated providers, confirmed server-side

The problem

Landlords, especially those living abroad, manage rent, agreements and repairs through messages and phone calls. They often do not know who has paid until they chase.

The goal

A landlord wakes up on the 2nd of the month and already knows who paid, who did not, and what was done about it, without making a call.

Who it serves

Owners, tenants, service partners and an admin team, each with their own app. Tenants are mobile only by design.

What I did as founder

Business: Business clarity, pricing model, growth strategy, and a written critique of my own plan.
Product: Requirement documents, scope by phase, personas, journey maps, 64 features with user stories and acceptance criteria.
Design: Brand name, tagline, logo, launch site, screen designs in Figma.
Architecture: System architecture, database design with row-level security, API design, security architecture.
Compliance: Indian data protection law, data kept in India, identity numbers masked, no customer funds held.
Delivery: Test cases, code review standards, deployment plan, delivery tracked in Linear.

Decisions that shape the product

A flat fee per unit: Never a commission on rent.
Verify before you sign: Identity checks must pass before a rental agreement can be generated.
Payment is confirmed by the server: Only a verified server-side notification marks rent as paid. A redirect in the browser is never trusted.
Data stays in India: The database is hosted in an Indian region, with no exceptions.
Identity numbers are masked: Only the last four digits are stored, whatever the verification provider returns.
No customer funds held: Money moves through a regulated payment provider, never through Vaasova's own accounts.

Architecture highlights

Six apps and five shared packages in one repository: three web apps and three mobile apps.
One typed API layer shared by every app, so web and mobile cannot drift apart.
Security in two layers: API middleware and database row-level security on every table.
Payment and payout handlers are idempotent, because notifications can arrive more than once.
Accessibility target of WCAG 2.1 AA across web and mobile.

How the plan was built

Vaasova was planned in 27 steps before any product code was written. The same method produced Karya.

Steps 1 to 8: Business clarity, requirement documents, scope, personas, journeys, feature breakdown and user stories.
Steps 9 to 12: Technology stack, system architecture, database design and API design.
Steps 13 to 17: Brand assets, design scaffolding and a component library in Figma.
Steps 18 to 21: Code review standards, security architecture, legal and compliance, DevOps and deployment.
Steps 22 to 27: AI integration plan, pricing, growth strategy, a critique of the plan, an operating routine for a solo founder, and the AI tool stack.

Technology

Built with

Next.js 15
TypeScript
Tailwind CSS
Turborepo
pnpm
Vercel

Designed for the product apps

Chosen and designed for. The product apps are scaffolds today.

Expo (React Native)
Supabase
Postgres with row-level security
tRPC
Cloudflare R2
Sentry

Planned integrations

Selected in the architecture. Not yet integrated.

Razorpay
RazorpayX
SignDesk eSign
IDfy identity checks
MSG91
Expo Push

Planning and delivery

Notion
Linear
Figma
Miro
Claude Cowork
Claude Code