A2 · 2026 · Internal tool
Briqhaus CRM
A real-estate CRM for Indian builders: the system sales teams live in all day, with leads, inventory, bookings and the state of every deal in one place.
Design, front end and QA across seven modules, plus the design system that holds them together.
Multiple builders run their sales on it. Seven modules shipped in eight months, all looking like one product.
Listen to this one
0:22
Eight months inside one CRM
Briqhaus had a legacy CRM in daily use without an underlying design system, causing every new feature to drift in visual consistency and data structure.
Product Design Engineer: Owned end-to-end design, component architecture, front-end QA, and implementation across 7 core modules.
Preserved the inherited production layout to avoid disrupting active sales teams, while engineering a unified Figma DS 2.0 component library underneath.
Shipped 7 cohesive modules in 8 months (AI agent, knowledge base, projection admin, call analysis, etc.) now running sales for multiple real-estate developers.
Briqhaus is the operating system a builder's sales force lives in: leads, inventory, bookings, payments, and deals. Several developers now run their commercial sales pipelines on it.
When I joined, a rough CRM was already in daily use. The mandate was not a cosmetic redesign. It was engineering a scalable design system under the inherited look so that seven ambitious new modules could ship as one cohesive platform.
What I built: Seven modules in eight months
Production modules
Feature demo films
I design the feature, write the copy, and edit the walkthrough films:
Core architectural decisions
Projects and towers first, pipeline stages second
Instead of A generic CRM kanban board dragged by sales stage
Generic CRMs organize by deal stage. Indian real estate organizes by building. A salesperson thinks "Tower B, 3BHKs left, who is ready to book", not "show me negotiation stage". Software structure follows the physical asset.
After Unit availability and deal state stopped being two separate lookups.
Information density on purpose: a second click is heard on the phone
Instead of Hiding data behind nested tabs to keep screens looking minimalist
When a sales executive is on a live phone call, a second click creates an awkward pause where the buyer hears them hunt. We optimized for maximum scannability: strict tabular alignment, calibrated color contrast, and immediate access to unit pricing.
After Sales reps find critical pricing and availability while actively speaking with buyers on calls.
Built the component design system rather than one-off screens
Instead of Ad-hoc screen designs that required reinventing tables and states per module
Rather than drawing isolated screens, I engineered Briqhaus DS 2.0: standardized data tables, filter bars, status badges, and empty states. Building front-end components myself guaranteed that the spacing and ergonomics in Figma matched the production code.
After Seven complex modules shipped in eight months with complete visual and behavioral consistency.
Impact & Retrospective
Briqhaus CRM now powers operations across multiple commercial builder organizations:
- 100 minutes saved per agent daily through automated call intelligence and one-click lead updates.
- Unified 7 modules across 740 screens under one single design system.
- Next challenge: Streamlining the legacy underlying data models to make upcoming modules even faster to ship.