GrihoDeal.

About the client

Gopal Barui↗ (opens in a new tab) is the client identified for this delivery. The GrihoDeal site's dedicated links-page implementation presents him as Founder & CEO. The project itself is branded GrihoDeal / গৃহ ডিল, with a Kolkata contact address and messaging focused on buyers, sellers, renters, and local real-estate discovery across West Bengal.

The client's detailed professional history, company registration status, and operational team structure were not confirmed and are not represented here.

Business context

Real-estate discovery involves varied search intents: a buyer may know their desired city, a renter may be comparing prices or housing types, and a property owner or broker may need a structured way to present inventory. GrihoDeal addresses these activities through a single branded application instead of a disconnected collection of property posts and contact links.

The live homepage explicitly targets West Bengal and gives quick access to Kolkata, Howrah, Siliguri, and Durgapur. The About-page implementation positions the brand around trust, community, service, and Bengali cultural identity.

Why this project mattered

The observable product opportunity was to create a regional real-estate presence that could support both property discovery and listing operations. This is a description of the delivered solution's function, not a quotation from an undocumented client brief or a claim about the client's original purchasing trigger.

Product problem addressed

The completed product is structured around three practical needs:

• Discovery: Give prospective buyers and renters a searchable place to explore properties by location and type.
• Property presentation: Standardize listing information such as price, location, floor area, property category, images, amenities, and contact options.
• Inventory operations: Provide authenticated users with an interface for creating, updating, organizing, and removing property listings.

These are needs inferred from the implemented workflows and screen structure. No baseline website, previous system, stakeholder interview, or documented before-state was supplied, so no redesign or migration claim is made.

Regional and product considerations visible in the delivery

• An English/Bengali language choice supports the brand's regional positioning.
• West Bengal city shortcuts reduce the effort needed to begin location-based browsing.
• Property categories include apartment, house, villa, plot, and commercial.
• Listings support sale, rent, and sale-or-rent classifications.
• The homepage includes a defined empty state rather than invented featured inventory when no featured properties are available.

Primary objective

Deliver a public-facing, regionally recognizable property platform that supports finding, presenting, and managing real-estate listings in West Bengal.

Supporting objectives

• Establish GrihoDeal's visual and verbal brand identity.
• Make property browsing accessible through homepage search and city shortcuts.
• Provide property-type filtering and structured detail pages.
• Support English and Bengali interface text.
• Give authenticated users tools to maintain their property records and profiles.
• Provide clear routes for general enquiries and property-specific contact.
• Include company, legal, and social/contact information pages.

Observable success criteria

These criteria describe delivered interfaces and code paths, not contract acceptance results or successful end-to-end transaction tests.

Intended audiences

• Property buyers: Search by location and explore prices, specifications, and available property details.
• Renters: Browse listings classified for rent and contact the associated property representative.
• Sellers, brokers, and listing managers: Use authenticated workflows to add and maintain property records.
• Local prospects: Learn about GrihoDeal, locate the company's contact channels, and start an enquiry.

User journeys supported by the application

1. Search by location: A visitor enters a search term or chooses Kolkata, Howrah, Siliguri, or Durgapur and proceeds to the properties route.
2. Refine property discovery: A visitor uses text search and one or more property-type filters to narrow results.
3. Evaluate a listing: A visitor opens a listing to see price, address, area, rooms, descriptive content, amenities, images where available, and representative contact details.
4. Contact a representative: A visitor can open a property-specific enquiry form; the application contains validation and a Supabase submission path.
5. Manage inventory: An authenticated user can access their dashboard, create property entries, edit existing entries, and remove listings through the implemented interface.

Product decisions visible in the implementation

Public-facing product areas

• Home: GrihoDeal identity, regional hero imagery, search, city shortcuts, featured-property area, and value propositions.
• Property catalogue: Searchable property grid with city-based query routing and category filters.
• Property details: Structured listing view with optional image gallery, description, amenities, price, location, key specifications, and broker/owner contact actions.
• About: Brand story, mission, and values including trust, community, service, and cultural pride.
• Contact: General enquiry form, Kolkata location text, telephone, email, and WhatsApp link.
• Links: Brand/founder introduction and a directory of social and contact destinations.
• Legal information: Privacy Policy and Terms of Service pages.

Application-management features documented in source

• Sign-in and account-creation interfaces, including an administrative access workflow.
• User profile management with name, phone, bio, and profile-image handling.
• Property creation and editing forms with listing type, property type, price, location, size, room counts, amenities, status, and featured designation.
• Image selection, preview, and upload for new property listings.
• Authenticated dashboard separating active/under-construction properties from other statuses.
• Listing edit and delete controls.
• Property-specific enquiry recording and general contact-form submission logic.

Property types and listing statuses

Final deliverable

Delivery represented by this case study

This case study documents GrihoDeal as a client deliverable supplied by the project's developer. The associated source code is accessible in the developer's project repository, and the public deployment is available under the supplied Netlify URL. Together they substantiate the existence of the delivered website and its implemented application capabilities.

The source and deployment do not establish an exact breakdown of individual contributions across possible collaborators, so this document does not claim sole design authorship, a specific team size, exclusive backend ownership, or a measured development schedule.

Engineering and product work evidenced by the delivery

Solution overview

GrihoDeal is a real-estate web application, not simply a marketing landing page. Its publicly visible homepage introduces the regional brand and routes visitors toward property discovery. The application code supports the next stages of the journey: searching listings, viewing property information, and sending enquiries. For the supply side, authenticated interfaces support maintaining property data and images.

Main user experience

Discover: The homepage opens with Bengal-themed imagery, a clear property-finding message, a text search, and direct city choices. The featured-properties block handles empty inventory visibly instead of displaying fabricated listings.

Compare: The catalogue is designed to show property cards with image, price, property type, city, size, and optional bedroom/bathroom information. Search supports title, city, and address matching, with property-type filters.

Evaluate and enquire: Individual property pages can display an image carousel, description, specifications, amenities, and contact information. The enquiry form collects visitor details and a message associated with the selected property.

Maintain: Authenticated users can work from a property dashboard, create and edit listings, update statuses, manage their profiles, and remove listings.

What makes the solution appropriate

The design joins two sides of the property experience—visitor discovery and inventory maintenance—within a consistent branded product. The localized English/Bengali presentation and culturally specific visual direction make the interface recognizable for a West Bengal-oriented audience. Using a hosted application backend also provides a structured foundation for storing listings and enquiries without placing all content directly into static pages.

Honest before-and-after framing

This is a requirements-to-delivery comparison, not proof that an earlier manual process or previous system was replaced.

Architecture overview

GrihoDeal uses a client-rendered React/TypeScript single-page application built with Vite. React Router coordinates the main website and application routes. The application uses Supabase for database-backed property information, authentication, file storage, and enquiry persistence. The public frontend is deployed on Netlify, with a rewrite rule that routes client-side paths through the SPA entry point.

Property data is modeled separately from property images and amenities. The public catalogue queries the property records and associated images. Property detail pages load additional context, while authenticated forms submit updates to application tables and upload images to Supabase Storage.

Confirmed technology stack

Important implementation details

• Catalogue queries: The listings page requests active and under-construction properties, supports URL-based city selection, and searches title, city, and address fields.
• Structured inventory: Property records can represent sale/rental intent, category, location, price, size, bedroom and bathroom counts, construction-related details, status, and featured designation.
• Related media: Listing images are stored separately and loaded with the corresponding property; gallery views are conditional on available images.
• Enquiries: The source includes separate submission paths for general contact messages and property-specific enquiries, with Zod checks on the entered fields.
• Account workflows: Profile editing, sign-in, authenticated dashboard access, and listing management are implemented. Administrative sign-in includes a role lookup in the client code.
• SPA hosting: Netlify configuration provides route fallback for browser refreshes on client-side paths, alongside basic response-header settings.

Security, privacy, and operational limits

The repository contains authentication handling, client-side input validation, and role-aware UI logic. These are implemented controls, not evidence of completed penetration testing, audited authorization policies, or verified secure transactions. Database row-level permissions, production access restrictions, backup practice, monitoring, and real-world availability were not independently audited for this case study.

The source also contains a site-visit scheduling interface, but its production booking handoff was not independently verified. For that reason, the case study does not count completed bookings or a proven scheduling integration among the outcomes.

Observable outcome

One public regional property-platform deployment, accompanied by an implemented multi-page application covering discovery, property presentation, listing operations, localization, and contact.

Business value enabled

The delivered application gives the GrihoDeal brand a single destination that can be shared with property seekers and used to publish and maintain listings. Its information architecture supports browsing and enquiries, while the internal management functions provide a basis for maintaining inventory as the business operates.

These are capabilities enabled by the product. They are not proof that inventory was uploaded, customers converted, properties were sold or rented, or operational costs declined.

What was not measured

No reliable baseline or post-launch data was supplied for visitor traffic, live-property count, enquiry submissions, conversion rate, site visits, verified listings, deals closed, revenue, search visibility, support time, or operational efficiency. No performance benchmark, accessibility audit, or uptime analysis was completed for this curation.

As of the homepage review on 9 November 2026, the featured-property area showed no available featured properties. This does not independently establish whether other listing categories contain inventory.

The private project codebase was used only to verify product architecture and implemented behavior. It is not presented as a public source repository or evidence that every feature was tested against production services.

Product and engineering principles demonstrated

• Local relevance belongs in the primary navigation path. City shortcuts and bilingual presentation make the product's intended market clear immediately.
• Property listings need a reusable structure. Standard fields make discovery and comparison more consistent than one-off advertisements.
• A marketplace requires both sides of the workflow. Browsing is only one part; listing creation, updates, media handling, and enquiry capture matter operationally.
• Empty states are part of the experience. The homepage reports when featured inventory is unavailable instead of inventing a populated marketplace.
• Technical capability and adoption are different milestones. Implementing search, dashboards, and enquiries is demonstrable; acquiring listing supply and proving conversion requires independent measurement.

What this project demonstrates

The delivery demonstrates the construction of a branded, data-backed web application that spans customer-facing discovery, multi-language UX, CRUD-style inventory workflows, media storage, authentication, and enquiry interfaces. It does not establish a verified security posture, a volume of marketplace activity, or measured business growth.

Potential next steps — recommendations, not delivered results

For future iterations, the highest-value checks would be to validate a complete property listing and enquiry journey in production; confirm that intended owner/admin permissions are enforced server-side; verify the site-visit booking destination; audit mobile accessibility and page performance; and add consent-aware conversion measurements. Operationally, populating trustworthy, complete listings is the main prerequisite for testing real customer demand.