Skip to main content

Key Concepts

Vruksha models a real-estate business as a set of connected building blocks. Once you understand these eight core objects and how they relate, the rest of the application makes sense. This page introduces each one in plain language.

The core objects​

Organization​

The Organization is the top of the tree — your company's isolated workspace. Everything else (partners, projects, sales, documents) belongs to exactly one organization. When you sign up, you create an organization, and you become its first administrator. Other tenants can never see your organization's data.

Partner​

A Partner is a person or company that holds ownership in your business. Partners come in two flavours:

  • Individual — a single person.
  • Company — an organization partner, which can have its own stakeholders (individual partners with their own holding percentages).

Partners are the people whose money is at stake, and whose share of profit Vruksha keeps exact.

Partnership​

A Partnership is a business entity formed by partners — for example, a joint venture set up to develop a piece of land. Each partnership has a holdings table listing its partners and their percentages.

The holdings rule: Holdings must sum to exactly 100%, and at least one managing partner is required.

A partnership moves through statuses: Draft → Active → Suspended → Closed.

Stock​

Stock is your land and building inventory — the raw real estate you acquire before it becomes a sellable product. A stock parcel records its area, seller details, payments, and a status that tracks it from interest to ownership and beyond (Wishlist → In Negotiation → Under PO → Advanced → Registered, and onward through allocation and sale). Stock can be allocated to projects, fully or partially. See the full lifecycle in the Status Lifecycles reference.

Project​

A Project is a top-level development container, mapped to a partnership or joint venture and tied to a location. It groups the subprojects, units, and stock allocations that make up a single development effort. Projects have their own status flow: Draft → Planning → Active → On Hold → Completed / Cancelled.

Subproject​

A Subproject is a buildable component of a project — a specific layout, apartment tower, or set of villas. Subprojects carry a type (which determines their custom fields and the kinds of units they contain), a location, and SVG layouts that visually map out the units and amenities. Subprojects are also the boundary for subproject roles (see the Roles Overview).

Unit​

A Unit is an individual sellable item within a subproject — a plot, flat, villa, shop, or parking space. Units are what your customers actually buy. Each unit tracks its area, cost, shareholders (whose holdings also sum to exactly 100%), boundaries, and a status that runs from Draft → Available → Blocked → Booked → Advanced → Registered (or Cancelled / Frozen). See the full unit lifecycle in the Status Lifecycles reference.

Party​

A Party is any external person or organization you transact with, captured in one unified master. A party can be one or more of: Buyer, Seller, or Vendor. Buyers appear on sales orders, sellers appear on stock purchases, and vendors supply goods and services. Keeping them in a single master means one record, no duplicates.

How they fit together​

Here is the relationship map. Read it top to bottom: ownership flows down from partners and partnerships, while inventory flows from stock through projects and subprojects into the units that parties buy.

Reading the diagram​

  • Partners hold percentages in Partnerships. Those holdings must sum to exactly 100%, and one managing partner is required.
  • Partnerships own and fund Projects. A project is mapped to the partnership (or JV) that finances it.
  • Stock is allocated to Projects. Land inventory becomes the basis for a development.
  • Projects contain Subprojects, which contain Units. This is the path from a broad development down to an individual sellable item.
  • Parties interact at the edges. Buyers purchase units (through quotations and sales orders); sellers provide the stock you acquire.
  • Ownership appears again at the unit level. Individual units also have shareholders whose holdings sum to exactly 100%.

A worked example​

Imagine "Sunrise Developers" (an Organization). Two Partners, Asha and Bharath, form a Partnership holding 60% / 40%. The partnership acquires a Stock parcel of farmland from a seller Party. That parcel is allocated to a Project, "Sunrise Gardens", which is divided into a Subproject layout called "Sunrise Layout". The layout is carved into 120 Units (plots). A buyer Party, Mr. Kumar, books Unit P-045 — which flows through the Sales module as a quotation, then a sales order.

That single thread touches every core concept. Everything else in Vruksha is detail layered on top of these building blocks.

What's next​

Now that you know the vocabulary, learn how to get access in Signing Up, or jump to Navigating the App to see where these objects live in the interface.